1.2.2 Functionality for managing resource connections and transactions

The following table describes the functionality for managing resource connections and transactions. Select the functionality according to the purpose of the system. For details about the functionality, see the reference location.

Table 1-3 Correspondence between the functionality for managing the resource connections and transactions and the purpose of a system

Functionality namePurpose of the systemCompliance with Java EE standardsReference location
ReliabilityPerformanceOperation and maintenanceExpansionOthersStandardExpanded
Connection poolingNYNNNYY3.14.1
Functionality available with connection poolingNYNNNNY3.14.2
Connection sharing and associationNYNNNYN3.14.3
Statement poolingNYNNNNY3.14.4
Light transactionNYNNNNY3.14.5
In-process transaction serviceNYNNNYN3.14.6
DataSource object cachingNYNNNNY3.14.7
Optimizing container management sign-on in DB ConnectorNYNNNNY3.14.8
Detecting connection errorsYNNNNY#1Y#13.15.1
Waiting to acquire connections in the case of connection depletionYNNNNNY3.15.2
Retrying to acquire connectionsYNNNNNY3.15.3
Displaying the connection pool informationYNNNNNY3.15.4
Clearing the connection poolYNNNNNY3.15.5
Automatically closing a connectionYNNNNYN3.15.6
Connection sweeperYNNNNNY3.15.7
Transaction timeout and statement cancellationYNNNNYN3.15.8
Transaction recoveryYNNNNYN3.15.9
Issuing of SQL statements for troubleshootingNNYNNNY3.15.10
Automatic closing of objectsYNNNNYN3.15.11
Managing the resource adapter life cycle #2NNNNNYN3.16.1
Managing the resource adapter work #2NNNNNYN3.16.2
Message in-flow #2NNNNNYN3.16.3
Transaction in-flow #3NNNNNYN3.16.4
Looking up Administered objects #2NNNNNYN3.16.5
Specifying multiple connection definitions #2NNNNNYN3.16.6
Connection pool clustering functionality
(temporary stop, restart, and status display of the connection pool)
YNNNNNY3.17
Resource connection testNNYNNNY3.18
Functionality for operations in a firewall environmentNNYNNNY3.19
Legend:
Y: Supported
N: Not supported

Note: The functionality for which Y is specified in both Standard and Expanded columns of the Compliance with Java EE standards column indicates that the Application Server-specific functionality has been expanded to the Java EE standard functionality. The functionality for which Y is specified only in the Expanded column indicates the Application Server-specific functionality.

#1: In the case of Connector 1.0, Expanded. In the case of Connector 1.5, Java EE standards.

#2: This functionality can be used only when you use a resource adapter compliant with the Connector 1.5 specifications.

#3: This functionality can be used only when you use the TP1 inbound adapter from the resource adapters compliant with the Connector 1.5 specifications.