Randy--
Will "System.exit(0)" inside the servlet crash the JVM?
----- Original Message -----
From: "Randy Layman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 4:42 PM
Subject: RE: Tomcat as Service Crashing.
>
> I don't think that this is the problem that is typically found in
> the archives. This stack trace indicates that Tomcat was trying to read
> from the socket, not write to it. IE won't close the socket before it
sends
> the request.
>
> However, I would say that I doubt that this is causing your Tomcat
> to crash - each thread handles a request and Tomcat takes precautions so
> that crashes in one thread doesn't crash others.
>
> Look at your system - there are only three ways to crash (kill) a
> Java process:
> 1. Kill it yourself. Probably not your problem unless you are
> running JDK 1.3 as a service (if so, read the NT-Service HOWTO again for
> information on why this combination is bad)
> 2. JVM crashes. Sun is usually pretty good about printing out
> messages when this type of crash occurs, check the jvm.stderr and
jvm.stdout
> for messages.
> 3. Other native code crashes it - Sun can't protect against this
> killing the JVM and sometimes can't trap it to display a message. This is
> usually accompanied by a Dr. Watson dialog, but I believe that its
possible
> to disable this popup. Check any native code that you might be using. If
> you are using the JDBC-ODBC bridge, then you can stop looking, this is
your
> problem - its not thread safe, considered experimental by Sun, and its use
> is not advised for production systems by Sun (see Sun's Bug Parade for
more
> information).
>
> Randy
>
> > -----Original Message-----
> > From: Christian Rauh [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, June 13, 2001 4:45 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Tomcat as Service Crashing.
> >
> >
> > Robert Slifka wrote:
> > >
> > > Oh man we really need a FAQ or something, or this might be
> > in the one that
> > > exists =)
> >
> > Probably.
> >
> > > I think someone answered this yesterday... Internet
> > Explorer is closing the
> > > connection, something like that, I think you can ignore it.
> > Search the
> > > archives for the last couple of days!
> >
> > I cheked out the archives and found exactly what you said.
> > The problem is
> > that, if this isn't the problem that is crashing my tomcat,
> > then what is?
> >
> > How may I find out if there is nothing else abnormal on the logs?
> >
> > I know there is an issue with the service stopping when the
> > user logs off.
> > But when I log off it continues working, it crashes after a
> > day or two.
> >
> > Ideas?
> >
> > Christian Rauh
> >
> > >
> > > > -----Original Message-----
> > > > From: Christian Rauh [mailto:[EMAIL PROTECTED]]
> > > > Sent: June 13, 2001 2:45 PM
> > > > To: Tomcat User Discussion List
> > > > Subject: Tomcat as Service Crashing.
> > > >
> > > >
> > > > Dear People,
> > > >
> > > > I have set up Tomcat to work as a service in Win2000.
> > > > Everything works fine
> > > > but it crashes after some time up. What I am getting on the
> > > > stderr is the
> > > > following:
> > > >
> > > > ContextManager: SocketException reading request, ignored -
> > > > java.net.SocketException: Connection reset by peer:
> > JVM_recv in socket
> > > > input stream read
> > > > at java.net.SocketInputStream.socketRead(Native Method)
> > > > at
> > java.net.SocketInputStream.read(SocketInputStream.java:86)
> > > > at
> > > > java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
> > > > at
> > > > java.io.BufferedInputStream.read(BufferedInputStream.java:204)
> > > > at
> > > > org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpR
> > > > equestAdapter.java:115)
> > > > at
> > > > org.apache.tomcat.core.BufferedServletInputStream.doRead(Buffe
> > > redServletInputStream.java:106)
> > > > at
> > > > org.apache.tomcat.core.BufferedServletInputStream.read(Buffere
> > > > dServletInputStream.java:128)
> > > > at
> > > >
> > javax.servlet.ServletInputStream.readLine(ServletInputStream.java:138)
> > > > at
> > > > org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequ
> > > > est(HttpRequestAdapter.java:129)
> > > > at
> > > > org.apache.tomcat.service.http.HttpConnectionHandler.processCo
> > > > nnection(HttpConnectionHandler.java:195)
> > > > at
> > > > org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoin
> > > > t.java:416)
> > > > at
> > > > org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPo
> > > > ol.java:498)
> > > > at java.lang.Thread.run(Thread.java:484)
> > > >
> > > >
> > > > Any ideas on what is causing this?
> > > >
> > > > Yours,
> > > >
> > > > Christian Rauh
> > > >
> >
