activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject "AcitveMQ Connection Worker" threads
Date Sat, 29 Sep 2007 01:20:14 GMT

I'm having a serious problem with a recent AMQ nightly (apache- that is causing almost 1500  
threads to be created and sit in the background before the jvm runs  
out of memory (OutOfMemoryError: cannot create new native thread).

I have a simple case where I have a few webapps sending messages to  
an AMQ installation on another host on the local network.  After a  
few hours of operation, if I send a kill -SIGQUIT to the webapp jvm,  
I get a thread dump that shows almost 1500 threads shown as:

  "AcitveMQ Connection Worker: tcp://"  
daemon prio=1 tid=0x084d2c98 nid=0x53b waiting on condition  
         at sun.misc.Unsafe.park(Native Method)
         at java.util.concurrent.locks.LockSupport.park 
         at java.util.concurrent.locks.AbstractQueuedSynchronizer 
         at java.util.concurrent.LinkedBlockingQueue.take 
         at java.util.concurrent.ThreadPoolExecutor.getTask 
         at java.util.concurrent.ThreadPoolExecutor$ 

Since noticing this problem, I've tried turning on failover: to see  
if that made a difference as far as autoreconnect is concerned.  The  
main difference is that I start seeing hundreds of other threads  
piling up and the indication is that our webapp will crash in the  
very near future.  I'm not sure why this is the case, but it's almost  
certainly related to the AMQ problem.

This is straight-up java code going against the JMS api.

Any ideas for fixing this crippling problem?


PS Sidenote: "AcitveMQ" is misspelled in the source code.

                                    Philip Jacob

View raw message