I did the thread dump. Cool.

There are 25 threads that look like this:

"http-8100-Processor13" daemon prio=1 tid=0x083c6090 nid=0x99a in Object.wait() 
[bcdff000..bcdff8d0]
   at java.lang.Object.wait(Native Method)
   - waiting on <0x33feebc0> (a 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
   at java.lang.Object.wait(Object.java:429)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
   - locked <0x33feebc0> (a 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
   at java.lang.Thread.run(Thread.java:534)

There is 1 thread that look like this:

"http-8100-Processor25" daemon prio=1 tid=0x084badf8 nid=0x9a6 runnable 
[bb5ff000..bb5ff8d0]
   at java.net.PlainSocketImpl.socketAccept(Native Method)
   at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
   - locked <0x33ef71f0> (a java.net.PlainSocketImpl)
   at java.net.ServerSocket.implAccept(ServerSocket.java:448)
   at java.net.ServerSocket.accept(ServerSocket.java:419)
   at 
org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:60)
   at 
org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:368)
   at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:549)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:534)

There are 102 of these runnable processes and two waiting:

"TP-Processor39" daemon prio=1 tid=0x0809de40 nid=0x35d0 runnable 
[b53ff000..b53ff8d0]
   at java.net.SocketInputStream.socketRead0(Native Method)
   at java.net.SocketInputStream.read(SocketInputStream.java:129)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
   at java.io.BufferedInputStream.read1(BufferedInputStream.java:222)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
   - locked <0x3449e188> (a java.io.BufferedInputStream)
   at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:598)
   at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:535)
   at 
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:663)
   at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
   at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:534)

The total number of processes is now at 143 for this tomcat instance.
Yesterday evening it was at around 95. Most of the hits are the result of
our monitoring system.

I don't know how to make sense of the thread dumps. The application was
written by one of our developers. It performs a simple export compliance
task. The app simply grabs the user's name and checks to see if it is in
a database, if it isn't, the app displays an agreement, which the users
either accepts or rejects. If the user accepts the agreement, their name
is added to the database. After that, the user is redirected to either a
logout page if they don't accept the agreement, or they are redirected
to another server, if their name appears in the database.

Can you help with the tread dump?

--patty

On Thu, 14 Apr 2005, David Rees wrote:

> Date: Thu, 14 Apr 2005 04:56:17 -0700
> From: David Rees <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[email protected]>,
>      David Rees <[EMAIL PROTECTED]>
> To: Tomcat Users List <[email protected]>
> Subject: Re: ThreadPool logFull
>
> On 4/13/05, Patty O'Reilly <[EMAIL PROTECTED]> wrote:
> >
> > I'm running tomcat 5.0.30.
> >
> > After running for a week or so the server begins to slow down and
> > finally crashes because it is out of threads. I can see the java
> > processes accumulating day by day.
>
> Send the process a -QUIT signal if on Linux, do the equivalent on
> Windows and you can get stack traces showing where each thread is
> getting stuck instead of returning to the thread pool for new
> processing.
>
> > I'm pretty new to tomcat. Not sure if the error is in my apache
> > server's workers.properties, or the tomcat servers server.xml, or....
>
> It's probably not a Tomcat issue, but your something in your
> application which is getting hung up.
>
> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to