ur web requests are
> > served by a servlet, you have to add the try/catch
> > block to the servlet
> > class, too.
> >
> > Robert
> >
> > > -Original Message-
> > > From: Dola Woolfe [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, O
class, too.
>
> Robert
>
> > -----Original Message-----
> > From: Dola Woolfe [mailto:[EMAIL PROTECTED]
> > Sent: Friday, October 14, 2005 8:43 AM
> > To: Tomcat Users List
> > Subject: RE: Suppress "Connection reset by peer:
> socket write er
vlet
class, too.
Robert
> -Original Message-
> From: Dola Woolfe [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 14, 2005 8:43 AM
> To: Tomcat Users List
> Subject: RE: Suppress "Connection reset by peer: socket write error".
>
>
> Hi Robert,
>
>
ace analysis
> above is
> perfect. The other down side of this approach is
> that future
> versions of Java and/or Tomcat may change the
> exception message
> texts and/or the structure of the stack trace. But
> currently
> (JDK 1.5 / Tomcat 5.5) this approach does what was
> i
nd/or Tomcat may change the exception message
texts and/or the structure of the stack trace. But currently
(JDK 1.5 / Tomcat 5.5) this approach does what was intended.
Robert
> -Original Message-
> From: Dola Woolfe [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 14, 2005 3:17
Hi Bill,
Thanks for your answer and sorry for the delay in my
reply!
I'm using standalong Tomcat 5.5 listening on port 80.
I'm using jdk 1.5 on WinXP. I'm not using any special
logging. I'm running Tomcat in a console, simply by
typing "startup" in tomcat/bin.
What I don't want happening is for
