Alan Williamson wrote:
> but under Linux, isn't the "too many files" handles apply to sockets as
> well as files? i am sure i read that on the t'internet!
Yes. Can you do a netstat -an | grep <<port>> when that happens? Which
JDK are you using? Those issues are sometimes created by the JDK...
A+
-- Jeanfrancois
>
> Jeanfrancois Arcand wrote:
>> 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 :-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>