Hi,
I found out why I was so consistently able to reproduce the NIO busy
wait bug: I was closing the http socket on the client side with a
SO_LINGER value of 0, causing a RST packet to be received by Tomcat
while the SelectionKey was still registered with interestOps of 0.
Commenting out the
Filip Hanik - Dev Lists wrote:
Jeanfrancois Arcand wrote:
Hi,
Sebastiaan van Erk wrote:
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug r
Filip Hanik - Dev Lists wrote:
Sebastiaan van Erk wrote:
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug report + workaround confirming this
Jeanfrancois Arcand wrote:
Hi,
Sebastiaan van Erk wrote:
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug report + workaround confirming this
Hi,
Sebastiaan van Erk wrote:
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug report + workaround confirming this issue as a
Linux JDK bug.
Sebastiaan van Erk wrote:
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug report + workaround confirming this issue as
a Linux JDK bug.
The w
Hi,
Filip Hanik - Dev Lists wrote:
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
I just found the Sun bug report + workaround confirming this issue as a
Linux JDK bug.
http://bugs.sun.com/bugdatabas
Hi,
I'm running an embedded tomcat, so I don't have the server.xml file.
When I place a breakpoint in the selector loop though I find that the
value of selectorTimeout is 1000.
Regards,
Sebastiaan
Martin Gainty wrote:
curious what the value tcpSelectorTimeout is defines in
%TOMCAT_HOME%/con
curious what the value tcpSelectorTimeout is defines in
%TOMCAT_HOME%/conf/server.xml
Bedankt/
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email
Hi,
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
Well Ubuntu is pretty big, so I'd expect other people to have seen this
as well.
I have been able to reproduce a select busy loop in the JDK myself,
it will return 0 after the timeout has expired if there was no events.
most likely its not a bug in the JDK but in your linux kernel/distro
so far I haven't seen the behavior you've explained.
Filip
Sebastiaan van Erk wrote:
Hi,
I have a problem that sometimes the NIO selector goes into a bus
11 matches
Mail list logo
