CachedConnectionManager Configuration

The CachedConnectionManager is responsible for two things (both related)

• Keeping track of which applications have which connections open

• Late enlistment of connections in UserTransactions

It is configured in deploy/jbossjca-service.xml (JBoss4) or deploy/transaction-service.xml (JBoss-3.2.x)

Default Configuration

  <!-- 
     | The CachedConnectionManager is used partly to relay started UserTransactions to 
     | open connections so they may be enrolled in the new tx.
   -->
  <mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager" 
         name="jboss.jca:service=CachedConnectionManager">
    <depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>

    <!--SpecCompliant false means JBoss will close connections left open when you 
        return from a method call and generate a loud warning.  SpecCompliant true
        means JBoss will disconnect connection handles left open on return from a
        method call and reconnect them with an appropriate (security, tx) 
        connection on the next call to the same object.-->
    <attribute name="SpecCompliant">false</attribute>

    <!-- Enable connection close debug monitoring -->
    <attribute name="Debug">true</attribute>

  </mbean>

Configurable Attributes

• SpecCompliant - set this to true if you want to use <resource-ref>s marked as Unshareable that hold connections open across transactions and method invocations

• Debug - whether JBoss should keep track of unclosed connections and close them with a warning if the application fails to do it itself

• TransactionManagerService - the object name of the TransactionManager

Informational

• Instance - the CachedConnectionManager instance

• InUseCount - the total number of unclosed connections

Operations

• listInUseConnections - list of stacktraces showing the point of allocation for unclosed connections