0 Replies Latest reply on Dec 31, 2003 10:13 AM by F Zemen

    Tomcat 4.1.24 threads "stuck" on apache (JBoss 3.2.1)

    F Zemen Newbie

      We have a cluster of JBoss servers receiving web requests. Our Tomcat max processors is set at 150. After awhile of high load, we notice an increasing amount of threads in the following state. In fact, eventually the application stops responding and all threads are in this state; it appears we have thread starvation. The JBoss version is 3.2.1 and Tomcat version is 4.1.24. Apache thorugh mod_jk is what invokes the requests.


      "Thread-439" daemon prio=5 tid=0x181bca8 nid=0xfd6 runnable [99781000..99781994]
      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 <d69bfef0> (a java.io.BufferedInputStream)
      at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:498)
      at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:436)
      at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:551)
      at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679)
      at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
      at java.lang.Thread.run(Thread.java:536)