On 04/12/2011 03:38 PM, wild wrote:
> I've just made an heap dump and the problem is not the same as the previous
> one.
>
> In my actuel heap dump, there is a huge amount of DefaultProcessorTask in a
> list named processorTaks in SelectorThread.
>
> It is weird because the SelectorThread of the Administration Console is
> holding all the DefaultProcessorTask.
>
> Are they share between all the SelectorThread even if they are not listening
> on the same port ?
No.
> If I use comet, did the task will return to the pool after calling
> addCometHandler ?
Yes, it should, but to the appropriate listener's pool, not to admin
console's one.
Can you pls. create a simple testcase for it? I'll check locally.
Thanks.
WBR,
Alexey.
> Regards,
>
> William.
>
> --
> View this message in context: http://grizzly.1045725.n5.nabble.com/Grizzly-slowly-leaking-with-comet-support-on-version-1-0-39-tp4295847p4298204.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.