Hi all, Ok the situation is..... I am currently building a web site using JSP and Javabeans with a Tomcat server. However, whenever, I try to log in to the system I get the following error: IOException in R(/myfolder+/jsp/login.jsp+null) Connection reset by peer: socket write error. Can anyone tell me what this means and how do I solve the problem? Any help at all will be very much appreicated. Many Thanks, Rita.
Ok, so I've done a bit of googling and it seems this is a well known, non-fatal 'error'.
What it means is that the client (your browser) has closed the tcp/ip connection between itself and Tomcat, before Tomcat thinks it is done sending data.
Since the images and pages seem to be 100% complete, one could wonder whether or not Tomcat is correct, but putting that aside... the problem is not Tomcat related, so much as it is connection related.
The 'solution' is to simply disable this message. In Tomcat 3.2.x, go to <TOMCAT_HOME>/conf/server.xml and modify the following: Change "INFORMATION" to "WARNING", and that particular message should no longer appear. You will still get all the error stack traces, but none of the 'information' messages.
I haven't found how to set this in Tomcat 4.x, however, I've developed on both Tomcat releases, and I have yet to see this class of message on my Tomcat 4.x output, so perhaps the real default in Tomcat 4.x is 'WARNING'.
I understand by change the INFORMATION TO WARNING you no longer see the verbose information, but what about the connection and the important thing i.e, when you select a button tomcat just waits for some user input on the console and then process the input. I am facing this situation in sporadic intervals and I am not sure why there is a pause from TOMCAT and what it is waiting for.... I am using JDK 1.3_05 version and Tomcat cat 3.2. Please let me know a solution to the above... Thanks, -Raj
In my application I also saw a lot of such "exceptions" and our solution was also not to show it on application console,but rather write it to the log file (it was for Tomcat3.X). But in our new version we are using Tomcat 4.0 integrated with JBoss (Tomcat is running as JBoss bean) and we once again started to see this exceptions in JBoss/Tomcat window but not with some frequency,now it happens ones in some days. I am searching for the same solution : or to turn such messages to some log file (just not to see it on the screen) or not to see it at all. I see this line in JBoss jcml file <Logger className="org.jboss.web.catalina.Log4jLogger" >verbosityLevel="trace"category="org.jboss.web.localhost.Engine"/> but I can't find what the another options for "verbosityLevel" attribute. Do you know what options it has or can other solution be found? And what does it mean "trace"?
Thank you for reply. I know about log4j and we are using it a lot. I think "trace" verbosity level it isn't one of standard log4j log level,but rather Catalina's custom level of "org.jboss.web.catalina.Log4jLogger" class. Amassing,but I can't find any reference for this level in their source.