Hi Tigran,
I'd probably need more details on that.
Do you know what was the reason of OOM?
ConcurrentModificationException exception occurred after you got OOM
during server stopping?
Thanks.
WBR,
Alexey.
On Jan 15, 2010, at 9:17 , Tigran Mkrtchyan wrote:
>
> Hi,
>
>
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> at java.util.HashMap$KeyIterator.next(HashMap.java:828)
> at
> com
> .sun
> .grizzly
> .SelectorHandlerRunner.handleSelectedKeys(SelectorHandlerRunner.java:
> 255)
> at
> com
> .sun
> .grizzly
> .SelectorHandlerRunner.continueSelect(SelectorHandlerRunner.java:154)
> at
> com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:
> 114)
> at com.sun.grizzly.util.FixedThreadPool
> $BasicWorker.dowork(FixedThreadPool.java:379)
> at com.sun.grizzly.util.FixedThreadPool
> $BasicWorker.run(FixedThreadPool.java:360)
> at java.lang.Thread.run(Thread.java:619)
>
>
> This is grizzly 1.9.19-SNAPSHOT. The exception popup after we got
> out of memory exception.
>
> Regards,
> Tigran.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>