James
QProcessor::Run method calls this.destroy in the exception handler code
where it handles InterruptedException .
Thanks
Sunil
James Taylor
<james To: Turbine JCS Users List
<[EMAIL PROTECTED]>
@jamestaylor. cc:
org> Subject: Re: Is this defect ???
12/05/2002
01:54 PM
Please
respond to
"Turbine JCS
Users List"
On Thu, 2002-12-05 at 14:43, Sunil Pandit wrote:
> Hello JCS Users
>
> I came across an interesting defect in JCS .
> During an Initialization of JCS instance when it creates a CompositeCache
> instance, It creates an instance of ElementEventQueue. ElementEventQueue
> further creates a thread in form of an instance of QProcessor.
> This thread is never destroyed. If we test our application under heavy
> load we found that several of these threads remain active. This thread is
> created per instance of CompositeCache and therefore should be destroyed
> when the composite cache is disposed.
Yes, ElementEventQueue.Destroy should definitely be called in
CompositeCache.Dispose
> Also there is one more defect in JCS in same context. To correct the
above
> defect I thought I can use ElementEventQueue::Destroy method which calls
> interrupt on QProcessor. The run method for this thread calls
> Thread::Destroy method which is unimplemented in JDK 1.4 . So we just
> modified the run method to set the destroy flag to true on Interrupt
event
> so that the thread can gracefully exit.
That sounds reasonable also, where exactly is Thread.destory called?
Just want to be sure I am following you.
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
