Jaimes,
I am also getting these exceptions. They seem to occur when a webbrowser (or
any
other user agent) starts requesting something from Tomcat and then closes
the
connection (i.e. the socket) abruptly before the conversation is complete.
I can reproduce that behavior by requesting something
Are you using the servlet to connect to another socket?
If so, you should try synchronizing access to the socket and not closing the
connection prematurely.
Or use a single-threaded model for your servlet so only 1 request at a time
will be served and avoid socket connection being reset.
I believ
