Re: COMObjReleaser

> I noticed COMObjReleaser uses the name of the current executing thread to
> keep track of RawCOMRefs but it doesn't "expire" any objects that haven't
> been used by an idle thread.

I does it implicitly if you create a new COM object.

And you may explicitly call COMObjReleaser().closeDeadObjects(), but only
from the thread that created the COM object.

Claude Eisenhut

----- Original Message -----
From: "George Talusan" <[email protected]>
To: <[email protected]>
Sent: Wednesday, August 09, 2006 4:05 PM
Subject: [JAWIN] COMObjReleaser


> Hello,
>
> I've been using JAWIN in an application server environment with a huge
> (500+) thread pool.  Threads never go dead, and could potentially go
unused
> for a long period of time.
>
> I noticed COMObjReleaser uses the name of the current executing thread to
> keep track of RawCOMRefs but it doesn't "expire" any objects that haven't
> been used by an idle thread.
>
> Is there a way to remedy this as it appears our app server is leaking
memory
> when threads go idle.