Salut,
I've looked at the code and found one step that was missing
(unregistering the RequestInfo). Just for my understanding, are you
explkicitely calling:
SelectorThread.unregisterComponents()?
When calling that method, all JMX bean should go away.
Thanks
-- Jeanfrancois
Jeanfrancois Arcand wrote:
> Salut,
>
> Mark Hig wrote:
>> Also we have noticed a Management Bean in JConsole called
>> RequestProcessor.
>> This bean seems to be added by Grizzly and retains details of every
>> request
>> and are never cleared away. This is leading to massive memory
>> retention and
>> an eventual out of memory exception.
>>
>> Is this normal behaviour?
>
> No it must be destroyed.
>
> Could this be related to our previous post above?
>
> Probably. Digging...Can you file an issue here if you have a chance:
>
> https://grizzly.dev.java.net/issues/
>
> A+
>
> -- Jeanfrancois
>
>>
>> Thanks,
>>
>> Mark.
>>
>> http://www.nabble.com/file/p19374200/jconsole.jpg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
