Salut,
Oleksiy Stashok wrote:
> Hi Alan,
>
>
>> Alexey, i *think* the issue maybe related to "too many files" open.
>>
>> I am running some tests at the moment that will confirm this one way
>> or another. But its always the way, as soon as you get a new
>> spanking JAR file, nothing crashes!!!
>>
>> I will update this bug thread as soon as i know more concrete
>> information.
> This is very possible!!! Because recently I ran some tests on my local
> machine on "maximum allowed client connections" and ran in to the same
> issue :) So, looks like it is really the cause.
but I don't think this message is the same. The "maximum allowed client
connections" message is from the pipeline queue. A file descriptor leak
is different IMO :-)
A+
-- Jeanfrancois
>
> Thanks.
>
> WBR,
> Alexey.
>
>>
>>
>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>
>> thanks again for all your efforts.
>>
>> Oleksiy Stashok wrote:
>>> Alan, if one day you'll find out what caused such a problem with
>>> logging - please let us know :))
>>> Thank you.
>>> WBR,
>>> Alexey.
>>> On Jun 19, 2008, at 17:58 , Jeanfrancois Arcand wrote:
>>>>
>>>>
>>>> Alan Williamson wrote:
>>>>> fantastic ... thank you.
>>>>> it is now running, and i will let you know the results.
>>>>
>>>> You are welcome. I've filled:
>>>>
>>>> https://grizzly.dev.java.net/issues/show_bug.cgi?id=164
>>>>
>>
>> ---------------------------------------------------------------------
>> 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
>