Created
October 5, 2012 13:53
-
-
Save jpoetker/3839907 to your computer and use it in GitHub Desktop.
StackTrace from ServiceMix + MQ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Exception in thread "JMSCCThreadPoolMaster" java.lang.IllegalThreadStateException | |
| at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:859) | |
| at java.lang.Thread.init(Thread.java:365) | |
| at java.lang.Thread.<init>(Thread.java:493) | |
| at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.<init>(WorkQueueManagerImplementation.java:950) | |
| at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation.createNewThread(WorkQueueManagerImplementation.java:496) | |
| at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation.getWorkerThread(WorkQueueManagerImplementation.java:433) | |
| at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation.access$100(WorkQueueManagerImplementation.java:46) | |
| at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$WorkQueueManagerThread.run(WorkQueueManagerImplementation.java:848) |
After posting my last comment, I found out the issue. My application, had a cleanup module that was "destroying" ThreadGroups that had zero active Threads. It was inadvertently destroying the JMSCCThreadPool ThreadGroup. It looks like IBM corrected an issue with leftover Threads in version 7, which resulted in the ThreadGroup being left with zero active Threads.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Did you ever get to the bottom of this issue?