tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ferran Arís <>
Subject Broken Pipe
Date Thu, 27 Dec 2001 10:36:50 GMT

I'm using Tomcat 4.01 Standalone
Debian 2.2r4 Kernel 2.2.19
JDK 1.3.1 BlackDown

I have the following problem.

Tomcat works fast, good for a time. You can do a "ps x -C java" on the machine and you see
the processes correctly working. Most of them are i S state (sleeping) some running in R state
logically they R when some connections are handled. Until now every thing ok, it works for
a long time. Two days later you look at the same ps and you can see one of the java processes
that it is in R state for about 21 hours and is consumming 74 of CPU. No clients are attached,
requesting (i know this for sure, nobody at the firm except me). This child process is still
running but i don't know what is doing. I try to look at the logs and try to find what was
happening 21 hours ago and the only thing i found a "Servlet.service() exception Broken Pipe"
round this time. When i try to shutdown tomcat the nice way ( stop) nothing happens,
ps x -C java show that java is still running, no way to get out the only solution is to "kill"
the parent java process.

Is it a way to know what happend?, to debug this and know why? because if you run Tomcat for
longer time without stopping Tomcat stops responding.

I need help on that please because i must restart tomcat everyday.

Thanks everybody in advance.

Ferran Arís.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message