tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53074] [websocket] java.net.SocketTimeoutException: Read timed caused by server.xml' connectTimeout
Date Tue, 15 May 2012 08:18:59 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53074

--- Comment #3 from Mark Thomas <markt@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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message