[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #9 from rstoyanc...@yahoo.com --- Okay thanks Mark. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-un

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #8 from Mark Thomas --- If you have an issue sending more than 8k then that is a separate question for the users mailing list. Tomcat imposes no such limitation as it has no need to buffer then entire message. -- You are recei

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #7 from rstoyanc...@yahoo.com --- I guess that makes the combination of WebSocket and BIO pretty unusable. Good to know in any case. I have to double check the behavior with Servlet 3 async in the same scenario with NIO. BTW wh

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #5 from rstoyanc...@yahoo.com --- Thanks, when you say it's expected to work this way, does it also mean the send timeout cannot be enforced with the BIO connector? Can anything meaningful be done if an application can detect a

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #4 from Mark Thomas --- Add info from the users list that the timeout does occur after approx 15 minutes. This is - believe it or not - working as designed! See this thread from SO (it is off topic for SO but spot on for this p

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-24 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #3 from Mark Thomas --- For the record, I can reproduce this with 8.0.x using: - Unbuntu 12.04.04 LTS VM as the server (fully patched) - Latest 8.0.x code - Oracle 1.7.0_45 64-bit JVM - Snake WebSocket example - Firefox on OSX (

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #2 from rstoyanc...@yahoo.com --- The reference to Windows is for the server. I am using default server configuration on both Tomcat 7 and 8 so I guess that probably accounts for the different behavior. I can try Tomcat 7 with N

[Bug 56304] WebSocket send locks and timeout does not occur after 20 seconds

2014-03-23 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 --- Comment #1 from Mark Thomas --- Are you sure you used the same connector on Tomcat 7 and Tomcat 8? The default connector on Tomcat 7 is BIO whereas it is NIO on Tomcat 8. When you refer to Windows or Linux is that client side, server s