Salut,
David M. Lloyd wrote:
> It sounds a lot like
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6403933 to me...?
Or that one:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6693490
The patch will show the real exception, if exception happens. If not,
then I do agree it will be the same as 6403933...which I filled but
can't apply the same workaround (patch 1 failed).
A+
-- jeanfrancois
>
> - DML
>
> On 12/18/2008 09:16 AM, Jeanfrancois Arcand wrote:
>> Salut,
>>
>> second try. I've added some logging when the issue arise, and when I
>> try to recover from the failure.
>>
>> Thanks!
>>
>> -- Jeanfrancois
>>
>> Jussi Kuosa wrote:
>>>
>>>> Let me know if that fix the issue.
>>>
>>> Hi Jean-Francois,
>>> and thank you for your incredibly fast response!
>>>
>>> I put your fix to test this morning and it ran almost 4 hours before
>>> going
>>> into 100% for one core. The symptoms are the same: selector thread
>>> for port
>>> 8282 is hot sitting in epollWait. As always, eden space mem graph
>>> looks like
>>> a heart-attack after the thrashing due to the amount of temporary
>>> objects
>>> that are created just to notice that there's nothing to do...
>>>
>>>>> One workaround for you is to set the
>>>>> CometContext.setExpirationDelay(-1). This will not enabled that
>>>>> extra Selector.
>>>
>>> I was supposed to do this in the morning, but I'll put that to test now.
>>> I'll let you know ASAP.
>>>
>>> -Jussi
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>