Hello Apache / Cortexity:
I am a software engineer that works as an Enterprise Support Specialist at MapInfo Corporation, which is located in the United States of America. One of our main products (MapInfo's "MapXtremeJava4.0") ships with TOMCAT3.2.2, and as of recent, we have been getting *customer complaints* that this version of Tomcat (i.e. version 3.2.2) is throwing the following exception for no apparent reason: 2001-10-31 04:42:40 - ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.socketAvailable(Compiled Code) at java.net.PlainSocketImpl.available(Compiled Code) at java.net.SocketInputStream.available(Compiled Code) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(Compiled Code) at org.apache.tomcat.service.TcpWorkerThread.runIt(Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(Compiled Code) at java.lang.Thread.run(Compiled Code) (NOTE: we at MapInfo are able to consistently reproduce this error ourselves, in our testing lab.) After researching this exception on the internet, I came across the following site that appears to be a "bug report" list hosted by "BugRat," which claims this exception is a bug in the TOMCAT3.2.1 release. Here's a link to the site that says this: http://w6.metronet.com/~wjm/tomcat/2001/Jan/msg00721.html I am writing you both (i.e. both apache & cortexity) in order to confirm that this is indeed a bug. Specifically, here are my questions: [1] Is this a bug in TOMCAT3.2.1??? [2] Is this a bug in TOMCAT3.2.2??? [3] If it is a bug, can we safely IGNORE it? (Or is TOMCAT broken?) [4] Lastly, if it is a bug, will there be a PATCH issued? (Or some type of fix?) Thank you in advance for any information you can give regarding this matter. Sincerely, John Dove ------------------------------ John Dove MapInfo Corporation -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>