Abstract
This troubleshooting guide helps you resolve common problems encountered in JMS integration scenarios with WSO2 ESB.
...
Too-Many-Threads and Out-of-Memory Issues
With some JMS brokers, WSO2 ESB tends to spawn new worker threads indefinitely until it runs out of memory and crashes. This problem is caused by a bug in the underlying Axis2 engine. A simple workaround to this problem is to engage the property mediator of the mediation sequence as follows:
...
This prevents the ESB from creating new worker threads indefinitely. You can use a jconsole like JMX client to monitor the active threads and memory consumption of the ESB.
...
JMSUtils cannot locate destination
If your topic or queue name has the characters ":" or "=", you must escape those characters with a backslash "\" in the jndi.properties file. Otherwise, JMSUtils will not be able to find the topic/queue and will give you the warning "JMSUtils cannot locate destination". For more information, see http://docs.oracle.com/javase/7/docs/api/java/util/Properties.html#load%28java.io.Reader%29.