ok, if you are using the HTTP protocol, you must know that the server has no
responsibility in keeping the connection alive.
Tomcat (Coyote) keeps the connection alive if the Keep-Alive is set, but you can't
send raw data up and down the HTTP connection and expect it to work. The data has to
This is an interesting proposition! I read both of your posts.
Personally, if I were you, I would create a custom server. David Flanagan's
Generic Multithreaded Server (as given in O'Reilly's Java Examples in a
Nutshell) would be a good starting point (if you're using it commercially,
there's a
There's nothing in the logfiles (we are only using catalina.out) that would suggest
that Tomcat even knows about a connection problem. The server just goes on as if
nothing happened, but the messages it sends to the 'dead client' are never delivered.
This might indeed be a load/config issue,
