RE: Tomcat 4.1 Runaway Java Procs on Debian LINUX
Howdy, It's also been explained numerous times on this list, which is likely where JGuru copied the answer ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Lukas Bradley [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2003 12:22 AM To: [EMAIL PROTECTED] Subject: Re: Tomcat 4.1 Runaway Java Procs on Debian LINUX First, this was my main contention point. It was answered on JGuru. [N.B.: Under Linux, each Java Thread appears in the process list (ps) as a separate process. This is because native Linux threads are implemented as lightweight processes. However, there is still only one Java process space -- the memory/CPU reported by each thread is actually shared among all threads. -A] Lukas Bradley [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] What determines the number of Java procs running catalina upon startup? The OS is Debian Linux, and it's Tomcat 4.1. If you look closely below, between ids 268 and 317 was full of java instances. That's 49 java instances running the bootstrap. What would make this happen? Is this normal? Is this what happens when a server gets throttled? I tried shutting them down, but was unable. The catalina.out log was filled with this: StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer. doWr i te(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityO utpu t Filter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuf fer. j ava:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java :384 ) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411 ) then this: CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .jav a :164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext. invo k eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:5 94) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Conn e ction(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 65) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:619) at java.lang.Thread.run(Thread.java:536) If the server were rebooted, why would 25 or so processes start? Any ideas? Any consultants in Atlanta want to make some money tomorrow? Thanks for any and all help. nat447:# ps auxww|grep java root 268 2.7 9.5 253720 49036 pts/0 S 17:55 0:05 /usr/local/java/bin/java - Djava.endorsed.dirs=/usr/local/tomcat/common/endor sed -classpath /usr/local/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat - Djava .i o.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start -snip- root 317 0.0 9.5 253720 49036 pts/0 S 17:56 0:00 /usr/local/java/b in/java -Djava.endorsed.dirs=/usr/local/tomcat/common/endorsed -classpath /usr/l ocal/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr /local/tomcat -Dcatalina.home=/usr/local/tomcat - Djava.io.tmpdir=/usr/local/ tomc at/temp org.apache.catalina.startup.Bootstrap start - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e
Tomcat 4.1 Runaway Java Procs on Debian LINUX
What determines the number of Java procs running catalina upon startup? The OS is Debian Linux, and it's Tomcat 4.1. If you look closely below, between ids 268 and 317 was full of java instances. That's 49 java instances running the bootstrap. What would make this happen? Is this normal? Is this what happens when a server gets throttled? I tried shutting them down, but was unable. The catalina.out log was filled with this: StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri te(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutput Filter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j ava:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) then this: CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) If the server were rebooted, why would 25 or so processes start? Any ideas? Any consultants in Atlanta want to make some money tomorrow? Thanks for any and all help. nat447:# ps auxww|grep java root 268 2.7 9.5 253720 49036 pts/0 S 17:55 0:05 /usr/local/java/bin/java -Djava.endorsed.dirs=/usr/local/tomcat/common/endor sed -classpath /usr/local/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.i o.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start -snip- root 317 0.0 9.5 253720 49036 pts/0 S 17:56 0:00 /usr/local/java/b in/java -Djava.endorsed.dirs=/usr/local/tomcat/common/endorsed -classpath /usr/l ocal/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr /local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/ tomc at/temp org.apache.catalina.startup.Bootstrap start - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1 Runaway Java Procs on Debian LINUX
First, this was my main contention point. It was answered on JGuru. [N.B.: Under Linux, each Java Thread appears in the process list (ps) as a separate process. This is because native Linux threads are implemented as lightweight processes. However, there is still only one Java process space -- the memory/CPU reported by each thread is actually shared among all threads. -A] Lukas Bradley [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] What determines the number of Java procs running catalina upon startup? The OS is Debian Linux, and it's Tomcat 4.1. If you look closely below, between ids 268 and 317 was full of java instances. That's 49 java instances running the bootstrap. What would make this happen? Is this normal? Is this what happens when a server gets throttled? I tried shutting them down, but was unable. The catalina.out log was filled with this: StandardWrapperValve[default]: Servlet.service() for servlet default threw exception java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri te(InternalOutputBuffer.java:668) at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutput Filter.java:160) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j ava:523) at org.apache.coyote.Response.doWrite(Response.java:524) at org.apache.coyote.tomcat4.OutputBuffer.realWriteBytes(OutputBuffer.java:384) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:439) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:359) at org.apache.coyote.tomcat4.OutputBuffer.writeBytes(OutputBuffer.java:411) then this: CoyoteAdapter An exception or error occurred in the container during the request processing java.lang.NullPointerException at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :164) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) If the server were rebooted, why would 25 or so processes start? Any ideas? Any consultants in Atlanta want to make some money tomorrow? Thanks for any and all help. nat447:# ps auxww|grep java root 268 2.7 9.5 253720 49036 pts/0 S 17:55 0:05 /usr/local/java/bin/java -Djava.endorsed.dirs=/usr/local/tomcat/common/endor sed -classpath /usr/local/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava .i o.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start -snip- root 317 0.0 9.5 253720 49036 pts/0 S 17:56 0:00 /usr/local/java/b in/java -Djava.endorsed.dirs=/usr/local/tomcat/common/endorsed -classpath /usr/l ocal/java/lib/tools.jar:/usr/local/tomcat/bin/bootstrap.jar -Dcatalina.base=/usr /local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/ tomc at/temp org.apache.catalina.startup.Bootstrap start - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
