Hi, Original message from: Randy Layman > Broken Pipe and Connection Reset by Peer exceptions indicate that >the client web browser closed the connection before the server was ready for >it to happen. At least with Tomcat 3.2 and 3.3 these errors are not a >problem - they do not cause tomcat to crash, give errors or slow performance >(other than causing an extra page generation that wasn't used). These are a problem with Tomcat 4.0.1 at least, since it crashes out. Moreover we should be able to catch the resulting exception (SocketExcetpion), which is clearly *not* the case...
>[...] IE6 can produce this error, and Netscape as well. Simply push STOP or load another servlet before your first servlet has finished its work. > To the person getting error code 500, it sounds like either a >threading issue or a memory issue. I would suggest using an optimizing tool >like OptimizeIt! to find out what is going on. I've reduced the servlet to its simplest form, and service methods are synchronized. Tomcat still crashes. It has been reproduced with JDK1.3.1, 1.3.1_01, 1.4 B3 with corresponding JRE's. We tried with IBM's JRE 1.3.0 as well - same result. Can someone give any clue ? Regards, Guillaume Mathe Smartinnov -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
