5 Replies Latest reply on Feb 13, 2004 7:03 AM by pants

Thread leak

sstephens Jun 1, 2003 4:46 PM

I upgraded to JBoss 3.2.1 from 3.0.6. I have found that the number of threads keeps growing at arate of about 40 to 50 per day and I believe its related to JMS.

I have a client sending messages to a JMS queue with an OIL2 ConnectionFactory. I have also experienced the same thing with both UILConnectionFactory and UIL2ConnectionFactory. I have a MDB reading this queue. Does anyone have any ideas on this? Below is my thread trace. You can see the threads that are leaking in Thread-49 through Thread-444. I have turned on debug and these threads print nothing to the debug log. Is there any way I can get more information as to what is spawning these threads? I eventually have to restart my server to clean them up.

Thanks,
Shawn

Total Threads: 184Total Thread Groups: 7Thread Group: system : max priority:10, demon:falseThread: Reference Handler : priority:10, demon:trueThread: Finalizer : priority:8, demon:trueThread: Signal Dispatcher : priority:10, demon:trueThread: AdapterThread : priority:10, demon:trueThread: CompileThread0 : priority:10, demon:trueThread: RMI TCP Accept-0 : priority:5, demon:trueThread: RMI Reaper : priority:5, demon:falseThread: GC Daemon : priority:2, demon:trueThread: RMI TCP Accept-0 : priority:5, demon:trueThread: RMI LeaseChecker : priority:5, demon:trueThread Group: main : max priority:10, demon:falseThread: DestroyJavaVM : priority:5, demon:falseThread Group: jboss : max priority:10, demon:falseThread: Thread-1 : priority:5, demon:trueThread: ScannerThread : priority:5, demon:trueThread: Thread-2 : priority:5, demon:trueThread: Thread-3 : priority:5, demon:trueThread: Thread-4 : priority:5, demon:trueThread: SessionScavenger : priority:5, demon:trueThread: Rollover : priority:5, demon:trueThread: Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080] : priority:5, demon:falseThread: PoolThread-0 : priority:5, demon:falseThread: PoolThread-1 : priority:5, demon:falseThread: PoolThread-2 : priority:5, demon:falseThread: PoolThread-3 : priority:5, demon:falseThread: PoolThread-4 : priority:5, demon:falseThread: PoolThread-5 : priority:5, demon:falseThread: PoolThread-6 : priority:5, demon:falseThread: PoolThread-7 : priority:5, demon:falseThread: PoolThread-8 : priority:5, demon:falseThread: PoolThread-9 : priority:5, demon:falseThread: Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8009] : priority:5, demon:falseThread: PoolThread-0 : priority:5, demon:falseThread: PoolThread-1 : priority:5, demon:falseThread: PoolThread-2 : priority:5, demon:falseThread: PoolThread-3 : priority:5, demon:falseThread: PoolThread-4 : priority:5, demon:falseThread: SessionScavenger : priority:5, demon:trueThread: hypersonic-default : priority:5, demon:falseThread: Thread-23 : priority:5, demon:falseThread: JBossMQ Cache Reference Softner : priority:5, demon:trueThread: Thread-24 : priority:5, demon:falseThread: Thread-25 : priority:5, demon:trueThread: Thread-26 : priority:5, demon:falseThread: Thread-27 : priority:5, demon:falseThread: Thread-28 : priority:5, demon:falseThread: SessionScavenger : priority:5, demon:trueThread: SessionScavenger : priority:5, demon:trueThread: Thread-33 : priority:5, demon:trueThread: Connection Consumer for dest QUEUE.cometPersistenceQueue : priority:5, demon:falseThread: Connection Consumer for dest QUEUE.cometScheduleResponseQueue : priority:5, demon:falseThread: SessionScavenger : priority:5, demon:trueThread: Thread-34 : priority:5, demon:falseThread: JNP Server : priority:5, demon:falseThread: PoolThread-10 : priority:5, demon:falseThread: PoolThread-11 : priority:5, demon:falseThread: Thread-49 : priority:5, demon:falseThread: Thread-53 : priority:5, demon:falseThread: Thread-57 : priority:5, demon:falseThread: Thread-60 : priority:5, demon:falseThread: Thread-61 : priority:5, demon:falseThread: Thread-64 : priority:5, demon:falseThread: Thread-68 : priority:5, demon:falseThread: Thread-72 : priority:5, demon:falseThread: Thread-76 : priority:5, demon:falseThread: Thread-80 : priority:5, demon:falseThread: Thread-84 : priority:5, demon:falseThread: Thread-88 : priority:5, demon:falseThread: Thread-92 : priority:5, demon:falseThread: Thread-96 : priority:5, demon:falseThread: Thread-104 : priority:5, demon:falseThread: Thread-108 : priority:5, demon:falseThread: Thread-112 : priority:5, demon:falseThread: Thread-116 : priority:5, demon:falseThread: Thread-120 : priority:5, demon:falseThread: Thread-124 : priority:5, demon:falseThread: Thread-128 : priority:5, demon:falseThread: Thread-132 : priority:5, demon:falseThread: Thread-136 : priority:5, demon:falseThread: Thread-140 : priority:5, demon:falseThread: Thread-144 : priority:5, demon:falseThread: Thread-148 : priority:5, demon:falseThread: Thread-152 : priority:5, demon:falseThread: Thread-156 : priority:5, demon:falseThread: Thread-160 : priority:5, demon:falseThread: Thread-164 : priority:5, demon:falseThread: Thread-168 : priority:5, demon:falseThread: Thread-172 : priority:5, demon:falseThread: Thread-176 : priority:5, demon:falseThread: Thread-180 : priority:5, demon:falseThread: Thread-184 : priority:5, demon:falseThread: Thread-188 : priority:5, demon:falseThread: Thread-192 : priority:5, demon:falseThread: Thread-196 : priority:5, demon:falseThread: Thread-200 : priority:5, demon:falseThread: Thread-204 : priority:5, demon:falseThread: Thread-208 : priority:5, demon:falseThread: Thread-212 : priority:5, demon:falseThread: Thread-216 : priority:5, demon:falseThread: Thread-220 : priority:5, demon:falseThread: Thread-224 : priority:5, demon:falseThread: Thread-228 : priority:5, demon:falseThread: Thread-232 : priority:5, demon:falseThread: Thread-236 : priority:5, demon:falseThread: Thread-240 : priority:5, demon:falseThread: Thread-244 : priority:5, demon:falseThread: Thread-248 : priority:5, demon:falseThread: Thread-252 : priority:5, demon:falseThread: Thread-256 : priority:5, demon:falseThread: Thread-260 : priority:5, demon:falseThread: Thread-264 : priority:5, demon:falseThread: Thread-268 : priority:5, demon:falseThread: Thread-272 : priority:5, demon:falseThread: Thread-276 : priority:5, demon:falseThread: Thread-280 : priority:5, demon:falseThread: Thread-284 : priority:5, demon:falseThread: Thread-288 : priority:5, demon:falseThread: Thread-292 : priority:5, demon:falseThread: Thread-296 : priority:5, demon:falseThread: Thread-300 : priority:5, demon:falseThread: Thread-304 : priority:5, demon:falseThread: Thread-308 : priority:5, demon:falseThread: Thread-312 : priority:5, demon:falseThread: Thread-316 : priority:5, demon:falseThread: Thread-320 : priority:5, demon:falseThread: Thread-324 : priority:5, demon:falseThread: Thread-328 : priority:5, demon:falseThread: Thread-332 : priority:5, demon:falseThread: Thread-336 : priority:5, demon:falseThread: Thread-340 : priority:5, demon:falseThread: Thread-344 : priority:5, demon:falseThread: Thread-348 : priority:5, demon:falseThread: Thread-352 : priority:5, demon:falseThread: Thread-356 : priority:5, demon:falseThread: Thread-360 : priority:5, demon:falseThread: Thread-364 : priority:5, demon:falseThread: Thread-368 : priority:5, demon:falseThread: Thread-372 : priority:5, demon:falseThread: Thread-376 : priority:5, demon:falseThread: Thread-380 : priority:5, demon:falseThread: Thread-384 : priority:5, demon:falseThread: Thread-388 : priority:5, demon:falseThread: Thread-392 : priority:5, demon:falseThread: Thread-396 : priority:5, demon:falseThread: Thread-400 : priority:5, demon:falseThread: Thread-404 : priority:5, demon:falseThread: Thread-408 : priority:5, demon:falseThread: Thread-412 : priority:5, demon:falseThread: Thread-416 : priority:5, demon:falseThread: Thread-420 : priority:5, demon:falseThread: Thread-424 : priority:5, demon:falseThread: Thread-428 : priority:5, demon:falseThread: Thread-432 : priority:5, demon:falseThread: Thread-436 : priority:5, demon:falseThread: Thread-440 : priority:5, demon:falseThread: Thread-441 : priority:5, demon:falseThread: Thread-442 : priority:5, demon:falseThread: Thread-443 : priority:5, demon:falseThread: Thread-444 : priority:5, demon:falseThread Group: JBossMQ Server Threads : max priority:10, demon:falseThread: OIL Worker Server : priority:5, demon:falseThread: UIL Worker : priority:5, demon:falseThread: OIL2 Worker Server : priority:5, demon:falseThread: UILServerILService Accept Thread : priority:5, demon:falseThread: OIL2 Worker-0 : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2 Worker-1 : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2 Worker-2 : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2 Worker-3 : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2 Worker-4 : priority:5, demon:trueThread: Message Pushers-1 : priority:5, demon:trueThread: OIL Worker-0 : priority:5, demon:falseThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL2SocketHandler Thread : priority:5, demon:trueThread: OIL Worker-1 : priority:5, demon:falseThread: OIL2SocketHandler Thread : priority:5, demon:trueThread Group: JBossMQ Client Threads : max priority:10, demon:falseThread: OILClientILService-0 : priority:5, demon:trueThread: Connection Monitor Thread : priority:5, demon:trueThread: OILClientILService-1 : priority:5, demon:trueThread Group: ASF Session Pool Threads : max priority:10, demon:falseThread Group: RMI Runtime : max priority:10, demon:false

1. Re: Thread leak

adrian.brock Jun 2, 2003 5:04 AM (in response to sstephens)

You are not closing connections.

Regards,
Adrian
Actions
2. Re: Thread leak

sstephens Jun 2, 2003 11:38 AM (in response to sstephens)

Thanks for the response. I have a JMSClient that is used by 24 modem controller objects to send messages to a queue. Are you saying that I need create and close a QueueConnection with each message sent? Or can I just reuse one connection and create and close individual queueSessions. The overhead of creating individual queueConnections per message is too great. It really slows performance?
When I have the thread leak I am using the same queueSession and the same queueConnection and just creating and closing and new QueueSender with each message. Can you point me to the proper way to send many messages across a long session without having to create and close a connection with each message?

Thanks,
Shawn
Actions
3. Re: Thread leak - Solved

sstephens Jun 2, 2003 12:41 PM (in response to sstephens)

solved, Refer to this thread http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= have a connection per modem and I create new QueueSession objects per message.
Actions
4. Re: Thread leak

sstephens Jun 3, 2003 10:21 AM (in response to sstephens)

This did not fix my problem. I later discovered my thread leak is still leaking. It is related to the hsql database. Please see the thread here.

http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=
Actions
5. Re: Thread leak

pants Feb 13, 2004 7:03 AM (in response to sstephens)

What is the issue with the HSQL db? I'm getting thread leaks as well. Is there a fix?
Actions

Go to original post