What are the differences between CachedConnectionManager and the default connection manager in JBoss?

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 6
  • Use of the use-ccm attribute as defined by the following schemas in <JBOSS HOME>/docs/schema:
    • jboss-as-datasources_1_0.xsd
    • jboss-as-datasources_1_1.xsd
    • jboss-as-resource-adapters_1_0.xsd
    • jboss-as-resource-adapters_1_1.xsd

Issue

  • What are the differences between CachedConnectionManager (CCM) and the default connection manager?
  • What does the CCM provide?

Resolution

The CCM is not an option to replace another type of configuration (there is not a no-cached connection manager). It is enabled by default (use-ccm=true)1.

Referring to the Cached connection manager section of the Administration and Configuration guide, the CachedConnectionManager is used for debugging connections and supporting lazy enlistment of a connection in a transaction, as well as tracking whether a connection is used and released properly by an application.

  1. See also CachedConnectionManager in a production JBoss environment ↩

Diagnostic Steps

  • Determine if references/explanation to Lazy Enlistment is needed

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.

Close

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