Questions regarding datasource ManagedConnectionPool counts in EAP 5

Solution Verified - Updated -

Issue

  • We need a clarification about how the connection pool works on JBoss EAP 5.1. we are checking via JMX Console an MBean like this name=jdbc/test,service=ManagedConnectionPool with the scope to minimize the connection creation and connection established on a production environment.

  • What we've found on these values appeared to me a bit strange and we don't understand the real meaning.

  • The ConnectionCount (10) is lower than MaxConnectionsInUseCount (7). If the application never required more than 7 connection, why the pool is currently sized to 10?

  • The number of ConnectionDestroyedCount is very high for just a day of work if compared to the pool size. As far as I know if the StrictMin is set to FALSE, after the idle timeout only connections that exceed the min-pool-size can be destroyed. Is this correct?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.1.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.