More physical connections than expected created to database with use-strict-min=true

Environment

• Red Hat JBoss Enterprise Application Platform 6.3.2
• use-strict-min set to true as defined in:
  • jboss-as-datasources_1_0.xsd
  • jboss-as-datasources_1_1.xsd
  • jboss-as-datasources_1_2.xsd
  • jboss-as-resource-adapters_1_0.xsd
  • jboss-as-resource-adapters_1_1.xsd

Issue

• Application will use more connections to the database than the max-pool-size

Resolution

• Use the default value of false for use-strict-min. Note that the behavior of use-strict-min set to true is to prefill the pool and not check a number of connections (determined by min-pool-size) during the IdleRemover check. use-strict-min has been identified for deprecation.
• This issue is resolved in This content is not included.EAP 6.4.2 and later 6.4 releases

Root Cause

• This content is not included.BZ-1210570
• Content from issues.jboss.org is not included.JBJCA-1252

Diagnostic Steps

This issue cannot be detected by JBoss connection pool statistics. The leaked connections are not tracked by the pool - they are orphaned within the JBoss process. Pool statistics (as reported by JBoss), therefore, will not match connection counts reported by network monitors/the database server.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.