Hi, I was getting several requests lateley about strange log messages (Closed sockets: Current state = FLUSHED, new state = CODING) from tomcat (mine is 3.2.4) about which there is a post from me a couple of weeks back. Along with these messages went very bad server performance and finally a standstill of Tomcat.
I found out the following: When I had those errors I was using Sun SDK 1.4.0, this is reported to be buggy (see below: background). Switching back to IBM JDK 1.3 solved the problem reported but introduced some classpath difficulties, because Tomcat (3.2.4 s) jars (in particular XML parsers) appeared to be put into the application classpath before the application's own jars (WEB-INF/lib). Finally I copied my XML parsers to tomcats lib and renamed/deleted the existing ones. After that the problem was solved. Background: That FLUSHED and CODING stuff is reported to be due to pickyness/buggyness of SUN JDK 1.4 when it comes to writing to closed streams, which happens if requests to Tomcat (3.2.x) are interrupted and the browsers stop to read the response. (e.g. double click on links as some people do :-). The IBM JDK 1.3 handles this situation more gracefully. I never had (those) problems after the switch. Performance is very good with the IBM JDK 1.3 anyway. regards and good luck, Alexander Misha Birman wrote: > alexander, > i saw your posting while searching for solution to similar problem. did you > solve your problem? if yes please share your solution. > misha -- Mit freundlichen Gr��en Alexander Banthien _______________________________________ Questech GmbH Schwarzwaldstr. 19 79199 Kirchzarten Fon: +49 (0)7661 90 35-15 Fax: +49 (0)7661 90 35-20 www.questech.de _______________________________________
