Re: Excel processes lingering

Reuben Sivan <[email protected]>
Newsgroups gmane.comp.windows.devel.jawin
Message-ID <[email protected]>
Thanks Stefan.

I had indeed quite a few left-over COM references in my encapsulating classes.
After I released each of them the problem went away!

  Reuben


-----Original Message-----
From: Discussion of Java/Win32/COM integration with Jawin [mailto:[email protected]] On Behalf Of Stefan Zschocke
Sent: Thursday, October 14, 2004 9:07 AM
To: [email protected]
Subject: Re: [JAWIN] Excel processes lingering

Hi, Excel is very sensitive with respect to left-over COM references.
Even if you quit and release the application-instance, if you have
unreleased objects like Range or Workbook or Worksheet, Excel will stay
alive. You must pay particular attention to objects returned from method
calls like for example Workbooks.Add which returns a Workbook that needs
to be released by you.
Stefan
www.jacozoom.com


-----Ursprüngliche Nachricht-----
Von: Discussion of Java/Win32/COM integration with Jawin
[mailto:[email protected]] Im Auftrag von Reuben Sivan
Gesendet: Donnerstag, 14. Oktober 2004 13:50
An: [email protected]
Betreff: [JAWIN] Excel processes lingering


I have been succesfully using jawin for over a month, automating
PowerPoint, Word and Excel, happily reading and exporting content from
my java application. The one matter that puzzles me right now, is the
fact that, after using my application a number of times, I consistently
find Excel processes alive in the background. Those processes are not
visible in the task bar, by they do show under task manager/processes. I
do the same set of actions (or their equivalent) for all three
applications, but only Excel kind of stays alive, clogging my system
with unlimited instances of itself. I was wondering if anyone in this
list has experienced a similar behavior?

(I am running Office 2003 on Windows Server 2003.)

 Reuben
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.