How to fix "Could not obtain a JMS connection from the pool after 30s" issue in JBoss ESB ?

Solution Unverified - Updated -

Issue

  • When sending 20000 odd messages from a JMS client to a server, the server stopped processing messages around 19800th message, while it resumed processing them the following exception occurred.
...
Caused by: org.jboss.internal.soa.esb.rosetta.pooling.ConnectionException: Could not obtain a JMS connection from the pool after 30s.
        at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.internalGetSession(JmsConnectionPool.java:299)
        at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:206)
        at org.jboss.internal.soa.esb.couriers.JmsCourier.getJmsSession(JmsCourier.java:160)
...

What is the root cause of this problem and how to solve it?

Environment

  • JBoss Enterprise SOA Platform (SOA-P)
    • 5.1.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content