Show Table of Contents
7.2.3. JBossManagedConnectionPool MBean
The
org.jboss.resource.connectionmanager.JBossManagedConnectionPool MBean is a connection pooling MBean. It is typically used as the embedded MBean value of the BaseConnectionManager2ManagedConnectionPool attribute. When you setup a connection manager MBean you typically embed the pool configuration in the connection manager descriptor. The configurable attributes of the JBossManagedConnectionPool are:
- ManagedConnectionFactoryName: This specifies the
ObjectNameof the MBean that createsjavax.resource.spi.ManagedConnectionFactoryinstances. Normally this is configured as an embedded MBean in a depends element rather than a separate MBean reference using theRARDeploymentMBean. The MBean must provide an appropriatestartManagedConnectionFactoryoperation. - MinSize: This attribute indicates the minimum number of connections this pool should hold. These are not created until a
Subjectis known from a request for a connection.MinSizeconnections will be created for each sub-pool. - MaxSize: This attribute indicates the maximum number of connections for a pool. No more than MaxSize connections will be created in each sub-pool.
- BlockingTimeoutMillis: This attribute indicates the maximum time to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for a permit for a connection, and will never throw an exception if creating a new connection takes an inordinately long time.
- IdleTimeoutMinutes: This attribute indicates the maximum time a connection may be idle before being closed. The actual maximum time depends also on the idle remover thread scan time, which is 1/2 the smallest idle timeout of any pool.
- NoTxSeparatePools: Setting this to true doubles the available pools. One pool is for connections used outside a transaction the other inside a transaction. The actual pools are lazily constructed on first use. This is only relevant when setting the pool parameters associated with the
LocalTxConnectionManagerandXATxConnectionManager. Its use case is for Oracle (and possibly other vendors) XA implementations that don't like using an XA connection with and without a JTA transaction. - Criteria: This attribute indicates if the JAAS
javax.security.auth.Subjectfrom security domain associated with the connection, or app supplied parameters (such as fromgetConnection(user, pw)) are used to distinguish connections in the pool. The allowed values are:- ByContainer: use
Subject - ByApplication: use application supplied parameters only
- ByContainerAndApplication: use both
- ByNothing: all connections are equivalent, usually if adapter supports reauthentication

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.