sounds like the sam problem I had when using mod_webapp I reconfigured it for good old jk_mod and all is well. B
-----Original Message----- From: Guillaume Mathe [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 2:32 AM To: [EMAIL PROTECTED] Subject: Help needed: SocketException killing Tomcat 4.0.1 !? Hi again, This post must have been lost in the flow... I really need help on that, because a self-destructing Tomcat will not help me deploy my commercial webapp... Here's the setup: - Tomcat 4.0.1, windows 98SE or 2000/Server - Direct servlet access from port 8080 - JDK/JRE 1.3.1 from Sun or JRE 1.3.0 from IBM, tested both - Also compiled with JDK1.4, just to make sure it's not my JDK - Crash test servlet: a image/jpeg content-type servlet, using Sun's JPEG codec. Using a BufferedOutputStream. The servlet works fine when called normally. (you can create a blank image, no need to draw anything - a wait loop would be useful though...) Crash test procedure: - Open a browser and call the servlet. (with a <img src="servlet" /> ) - BEFORE the servlet has finished encoding the JPEG, click on STOP, BACK, or a link going elsewhere. Result: - A SocketException: connection reset by peer shows up, as expected. - The exception is thrown by out.close() ('out' being the BufferedOutputStream given to the JpegEncoder) and is NOT catched by the servlet ! quite unexpected... - Catalina dies, now that is unexpected ! Logs generally do not reflect the fatal exception. - Under windows98SE it dies with a fatal error... My questions: - Is it a *known* bug of Catalina ? - If yes, has it been fixed in a recent build ? - How can i trap this exception ? I want to handle properly client disconnects by closing resources and stopping SQL queries etc... Currently even if i put a catch() at each level up to GenericServlet, it goes through. Regards, Guillaume Mathe Smartinnov -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
