Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SOAP over JMS running out of JMS connections



JMS connection pools full when running Rule-Connect-SOAP through JMS binding.

Error Messages

Thread dump would show something like this:

3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at java/lang/Object.wait(Native Method)
4XESTACKTRACE                at java/lang/Object.wait( Code))
4XESTACKTRACE                at com/ibm/ejs/j2c/FreePool.queueRequest(
4XESTACKTRACE                at com/ibm/ejs/j2c/FreePool.createOrWaitForConnection( Code))
5XESTACKTRACE                   (entered lock: java/lang/[email protected], entry count: 1)
4XESTACKTRACE                at com/ibm/ejs/j2c/PoolManager.reserve( Code))
4XESTACKTRACE                at com/ibm/ejs/j2c/PoolManager.reserve( Code))
4XESTACKTRACE                at com/ibm/ejs/j2c/ConnectionManager.allocateMCWrapper( Code))
4XESTACKTRACE                at com/ibm/ejs/j2c/ConnectionManager.allocateConnection( Code))
4XESTACKTRACE                at com/ibm/ejs/jms/JMSConnectionFactoryHandle.createConnection( Code))
4XESTACKTRACE                at com/pega/apache/axis2/transport/jms/SOJSpecOutTransportInfo.createJMSSender(Bytecode PC:219(Compiled Code))
4XESTACKTRACE                at com/pega/apache/axis2/transport/jms/SOJSpecSender.sendMessage(Bytecode PC:71(Compiled Code))
4XESTACKTRACE                at com/pega/apache/axis2/transport/base/AbstractTransportSender.invoke(Bytecode PC:63(Compiled Code))
4XESTACKTRACE                at com/pega/apache/axis2/engine/AxisEngine.send( Code))
4XESTACKTRACE                at com/pega/apache/axis2/description/OutInAxisOperationClient.send( Code))

Steps to Reproduce

Load test with many concurrent SOAP calls.

Root Cause

A defect or configuration issue in the operating environment:

The system behaves as expected.  The JMS connection pool size needs to be adjusted to accommodate the load.


Make the following change to the operating environment: 

Adjust the JMS connection pool size to accommodate the load. 


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us