[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-08-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #12 from fach hoch fachh...@gmail.com --- is this fix available in tomcat 7.0.50? I am getting this error in jdk1.7 64 bit tomcat 7.0.50 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-08-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #13 from Chuck Caldarale chuck.caldar...@unisys.com --- (In reply to fach hoch from comment #12) is this fix available in tomcat 7.0.50? No, it's in 7.0.55, as stated in comment #10. -- You are receiving this mail because:

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-29 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #10 from Mark Thomas ma...@apache.org --- The workaround and simple debug code was pretty simple so I have backported it to 7.0.x (it will be in 7.0.55 onwards) and proposed if for 6.0.x. -- You are receiving this mail

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #6 from Konstantin Kolinko knst.koli...@gmail.com --- Javadoc for ServerSocket.accept() says that SocketTimeoutException can be thrown by the method if a timeout was previously set with setSoTimeout. [1] [1]

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #7 from Mark Thomas ma...@apache.org --- (In reply to Konstantin Kolinko from comment #6) BTW, Javadoc for ServerSocket.setSoTimeout() says that to set an infinite timeout one uses the value of 0. Is somebody confusing '0'

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #9 from Mark Thomas ma...@apache.org --- Workaround added to 8.0.x for 8.0.10 onwards. If the timout occurs a warning is logged that reports how long accept was blocking for before the timeout. -- You are receiving this mail

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 Gustavo Lopes gust...@thehyve.nl changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #3 from Gustavo Lopes gust...@thehyve.nl --- The strace output may actually be a bug in strace because poll() takes a signed int as timeout; it would seem strace is interpreting the value as an unsigned int. Indeed: $ cat a.c

[Bug 56684] java7: java.net.SocketTimeoutException: Accept timed out

2014-07-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56684 --- Comment #4 from Gustavo Lopes gust...@thehyve.nl --- A quick observation: the poll syscall used to take a long, and now takes an int. Maybe strace hasn't been updated yet: http://lwn.net/Articles/483078/ -- You are receiving this