[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Mark Thomas ma...@apache.org --- Fixed in trunk and 7.0.x and will be included in 7.0.28 onwards. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #7 from Mark Thomas ma...@apache.org --- Fixed in trunk. Will be back-ported to 7.0.x once there has been a new release of the APR/native connector. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #8 from Jean-Francois Arcand jfarc...@apache.org --- Ok thanks! I will go ahead and test using trunk. Will report if I see any issues. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 mike_mac mike_mac...@yahoo.com changed: What|Removed |Added CC||mike_mac...@yahoo.com -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #6 from Mark Thomas ma...@apache.org --- Just a short progress update. I have committed a set of changes to the APR/native connector to permit per socket timeouts. It works with my simple tests but needs more testing and review by some proper C coders (which I am not). I also have a first draft of the changes to trunk to enable infinite timeouts for WebSocket connections. That also needs some testing. I should have something to commit in the next couple of days. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #5 from huck jdboudrea...@gmail.com --- Hi, +1 here for the option of configuring the timeout. My application requires an infinite connection which will be closed when required. I was negatively suprised to see tomcat has such a short timeout option. please add an option to configure this at the very least. meanwhile is there a workaround other than constant client reconnection? thanks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #3 from Mark Thomas ma...@apache.org --- I've been thinking about this and I think the following is the way to go. 1. Make the connection timeout infinite. 2. Add an idle timeout to the WebSocket implementation (defaults to infinite) that times out if there is no input or output after a predefined amount of time. This should be configurable per connection. 3. Add a ping every n milliseconds feature (disabled by default) to save applications re-inventing the wheel. Thoughts? As an aside, 1) will be tricky with the APR/native connector. That needs some separate work. I'll start a thread on that on the dev list. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #4 from Jean-Francois Arcand jfarc...@apache.org --- Hi Mark, +1 for making the connection timeout infinite. +1 also to add support for websocket timeout property/attribute (will be really useful). Not sure for the ping ... some applications don't need ping or that extra traffic on the wire. At least this should be configurable. Thanks for the work. -- Jeanfrancois -- You are receiving this mail because: You are the assignee for the bug.
DO NOT REPLY [Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #1 from Peter Rossbach p...@objektpark.de 2012-04-14 12:31:18 UTC --- Must we set the timeout to unlimited, or you thing it is better that client can overwrite it? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074 --- Comment #2 from Jean-Francois Arcand jfarc...@apache.org 2012-04-14 13:16:16 UTC --- Salut, I think it should be unlimited, but an idle timeout setting would be useful (I do support idle timeout with Atmosphere, but I think Tomcat could support the same as well). If you want to test using Atmosphere, download atmosphere-spring-websocket.war from search.maven.org (remove the -0.9 in the name) and deploy. After 20 seconds the app will stop working and Chrome will display a protocol exception. Ping me directly if that can help. Thanks! -- Jeanfrancois -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
