How to monitor the JMS connectionPool usage in SOA-P 5

Solution Verified - Updated -

Issue

In our SOA environment, the esb services are heavily using jms. Therefore, we have increased the org.jboss.soa.esb.jms.connectionPool and org.jboss.soa.esb.namingcontext.poolsize parameter values. We are now interested in monitoring the actual pool usage, in order to verify if the newly defined sizes are appropriate. This should help to avoid potentially waiting threads on resources.

Environment

  • Red Hat JBoss SOA Platform (SOA-P)
    • 5.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