Cached connection manager use in a production JBoss environment

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 7
  • 6
• use-ccm attribute 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

• Should the cached connection manager (ccm) be used (use-ccm="true") in production environments?

Resolution

• As defined in the jboss-as-dataources_*.xsd, use-ccm is set to true by default (e.g. if not explicitly overridden).
• The cached connection manager should remain enabled in most production environments.
• There is no specific advantage/value in disabling the cached connection manager.

As explained in the JCA Subsystem documentation¹, the cached connection manager is used to support lazy enlistment of a connection in a transaction.

The cached connection manager also supports debugging connection usage (tracking whether a connection is used and released properly by an application) when debug is enabled. Note that enabling the cached connection manager does not enable debug but enabling the cached connection manager is a prerequisite for enabling the debug facility. When turning off debug (i.e. setting debug="false"), it is not necessary (nor recommended) to set use-ccm="false".

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.