Thank you Chuck and Tim for the information. I did wonder if it was a
normal exception, now I know that it's at least nothing to worry about.
I have one more. This *IS* a real error, and is caused by something
breaking between MySQL and my servlets.
SQL Problem: Communication link failure:
From: Richard S. Huntrods [mailto:[EMAIL PROTECTED]
Subject: RE: Would like to know what might be causing this
exception in servlet
I have one more. This *IS* a real error, and is caused by something
breaking between MySQL and my servlets.
(Should probably start a new thread for this,
I think Chuck is right. One thing that most J2EE / web applications do not
do is to catch the IOError the container is supposed to throw when the
browser / client disconnects and closes the socket. That way the answering
thread can immediately stop its work, clean up, and go home.
Tim
I am getting this exception from time to time (maybe once in a day every
few days) with my application (Servlets). None of the code involved in
the stack trace is my code, so I'm wondering if anyone knows what is the
cause of this exception? Also, is there a workaround / fix?
Thanks very much in
From: Richard S. Huntrods [mailto:[EMAIL PROTECTED]
Subject: Would like to know what might be causing this
exception in servlet
Feb 1, 2006 9:09:33 PM org.apache.tomcat.util.net.PoolTcpEndpoint
processSocket
SEVERE: Socket error caused by remote host /204.244.137.23
