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
lephone or email and destroy the original
message without making a copy. Thank you.
- Original Message - From: "Sebastiaan van Erk"
<[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Thursday, May 03, 2007 1:07 PM
Subject: NIOSelector busy wait
Hi,
I h
y 03, 2007 1:07 PM
Subject: NIOSelector busy wait
Hi,
I have a problem that sometimes the NIO selector goes into a busy wait
loop.
In line 1430 the code of NIOEndpoint.java,
keyCount = selector.select(selectorTimeout);
select keeps returning 0 without waiting.
I
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
Hi,
I have a problem that sometimes the NIO selector goes into a busy wait loop.
In line 1430 the code of NIOEndpoint.java,
keyCount = selector.select(selectorTimeout);
select keeps returning 0 without waiting.
I'm running on the latest trunk version of tomcat 6, on
12 matches
Mail list logo
