We are seeing some strange behaviour with JBoss 3.2.3/Jetty 4.2.14 where under load the web server stops allocating new requests to idle threads in its thread pool.
Every new request results in a new thread being created and eventually the server stops responding with an OUT OF THREADS message. When a thread dump is taken you can see that there have been MaxThreads threads allocated but they are all idle. E.g.
"PoolThread-395" prio=1 tid=0xb44be308 nid=0x2fe4 in Object.wait() [bb682000..bb682cd8]
at java.lang.Object.wait(Native Method)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:482)
- locked <0x59fdd810> (a org.mortbay.util.ThreadPool$PoolThread)
Has anyone seen this behaviour before? Is it a bug that has been fixed in later versions of JBoss/Jetty?
