This does seem like a really severe bug.
I'll ask around internally about how we can get the JDK to look at it.
Jim
Jeanfrancois Arcand wrote:
>
>
> Ken Cavanaugh wrote:
>> On Thu, 2006-02-02 at 10:11, Jeanfrancois Arcand wrote:
>>
>>> Hi,
>>>
>>> GlassFish is currently suffering a file descriptor leak:
>>>
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6380347 [not yet
>>> available outside :-(]
>>>
>>> The problem is related to a VM bug:
>>>
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6215050
>>>
>>> fixed in Mustang, There is a workaround described here
>>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4726957
>>>
>>> WORKAROUND :
>>> -use Socket.shutdownOutput() and shutdownInput() instead of
>>> close(). The former results in a FIN segment.
>>> -use "new Socket(..)" instead of SocketChannel.open(..) if
>>> non-blocking IO is not needed
>>> -don't use setSoTimeout() if not needed
>>>
>>> This means that all modules that manipulate sockets needs to evaluate
>>> if the worksaround can be implemented. The components affected are:
>>>
>>
>>
>> Let me ask the obvious question: can we get this fixed in the
>> JDK, and then recommend the appropriate version of the JDK
>> for the various SJSAS releases?
>>
>> This seems to have been well understood since around 7/2002,
>> so I'm a bit surprised (only a little; I know how hard it is
>> to get to every bug that is worth fixing) that this has
>> lingered for so long.
>
> +1....but someone with power :-) will have to push the j2se team to
> backport the 6.0 fix to 5.0 ur?
>
> -- Jeanfrancois
>
>>
>> Ken.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>