Hello,
In servlets 3.0 specification regarding async sockets, setTimeout with 0 or
negative value should be used for infinite timeout (no timeout).
I am not sure if there is a bug or a particular design in Tomcat 7.0.14 (did
not tested with 7.0.16), but when I use setTimeout(0) or setTimeout(-1),
in Servlet 3.0 specification?
--- On Thu, 9/6/11, Paul Cazan wrote:
From: Paul Cazan
Subject: How to handle client disconnection in 'no timeout' async servlets?
To: users@tomcat.apache.org
Date: Thursday, 9 June, 2011, 3:22 PM
Hello,
I am using Tomcat 7.0.14. I used to have a
Hello,
I am using Tomcat 7.0.14. I used to have a servlet implementing CometProcessor
to process asynchronous streams, with timeout set very high
(Integer.MAX_VALUE), and all worked fine. When I close the browser, the servlet
is notified immediately about that (CometEvent.EventType.END) and I am
