uCosminexus Application Server, Common Container Functionality Guide
This subsection describes the functionality available for the database connections.
The following table provides a database-wise description of the J2EE components and functionality available for the database connections.
Table 3-21 Available J2EE components and functionality
| Items | HiRDB | Oracle11g | SQL Server | XDM/RD E2 | |
|---|---|---|---|---|---|
| J2EE components | Servlet/JSP | Y | Y | Y | Y |
| Stateless Session Bean | Y | Y | Y | Y | |
| Stateful Session Bean | Y | Y | Y | Y | |
| Singleton Session Bean | Y | Y | Y | Y | |
| Entity Bean (BMP) | Y | Y | Y | N | |
| Entity Bean (CMP 1.1) | Y | N | N | N | |
| Entity Bean (CMP 2.0) | Y#1 | N | N | N | |
| Message-driven Bean (database access from the onMessage method) | Y | Y | Y | Y | |
| Available functionality | Connection pooling | Y | Y | Y | Y |
| Connection pool warming up | Y | Y | Y | Y | |
| Connection sharing association | Y | Y | Y | Y | |
| Caching the DataSource object | Y | R#5 | Y | Y | |
| Optimizing the container-managed sign-on for DB Connector | Y | Y | Y | Y | |
| Connection count adjustment functionality | Y | Y | Y | Y | |
| Connection sweeper functionality | Y | Y | Y | Y | |
| Displaying the connection pool information (cjlistpool command) | Y | Y | Y | Y | |
| Clearing the connection pool (cjclearpool command) | Y | Y | Y | Y | |
| Connection test for resources | Y | Y | Y | Y | |
| Detecting the connection errors | Y | Y | Y | Y | |
| Timeout in detecting connection errors | Y | Y | Y | Y | |
| Waiting to obtain connections during connection depletion | Y | Y | Y | Y | |
| Retrying a connection | Y | Y | Y | Y | |
| Auto-closing a connection | Y | Y | Y | Y | |
| Suspending a connection pool | Y | R#6 | N | Y | |
| Restarting a connection pool | Y | R#6 | N | Y | |
| Statement pooling | Y#2 | Y | Y | Y#2 | |
| Statement cancellation | Y | Y#3 | Y | Y | |
| Statement setQueryTimeout method | Y | Y#3 | Y | N | |
| Optional name functionality for J2EE resources | Y | Y | Y | Y | |
| Functionality for reporting exceptions occurring in Client APIs | Y | Y | Y | Y | |
| PRF trace output of the connection ID | Y | Y | N | Y | |
| Output of the SQL statement for troubleshooting | Y | Y | Y | Y | |
| Connection pool clustering | N | Y#4 | N | N | |
#1: The CMR functionality, which is the CMP 2.0 functionality, is not available.
#2: The HiRDB auto-reconnect functionality and the statement pooling functionality cannot be used together.
#3 Precautions need to be taken when you connect to Oracle. For details, see 3.6.6 Preconditions and notes on connecting to Oracle.
#4: This functionality is available when the RAC functionality is used and when Oracle JDBC Thin Driver is used for connection.
#5: This functionality is not available when you use a member resource adapter to connect to Oracle11g.
#6: This functionality is available when you use a member resource adapter to connect to Oracle11g.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.