Problem | The methods that are called are removed. |
User response | Use the new connection pooling API. |
Problem | One of the DataSource properties is in an unexpected format. |
User response | Verify that all of the properties for the DataSource are correct. |
Problem | A required property is missing. |
User response | Verify that all of the required properties are configured on the DataSource. |
Problem | An exception occurred during the decryption of a password. Either the encrypted password data is corrupt or is encoded in an unsupported encryption. |
User response | Replace the encrypted password with uncorrupt data or make sure that it is encoded with a supported encryption algorithm. |
Problem | An exception occurred during the encryption of a password. The password data is corrupt. |
User response | Replace the corrupted password with an uncorrupt password. |
Problem | The DataSource password is supplied, but the user ID is not; the password is ignored. |
User response | Supply the user ID that corresponds to the password or remove the password. |
Problem | The DataSource user ID is supplied, but the password is not; the user ID is ignored. |
User response | Supply the password that corresponds to the user ID or remove the user ID. |
Problem | The DataSource class name that is supplied cannot be found. |
User response | Verify that the Java archive (JAR) file with the specified class name is installed. If the DataSource is accessed by a direct Java Naming and Directory Interface (JNDI) lookup, rather than through a resource reference or a Container-Managed Persistent (CMP) enterprise bean, add the JAR file to the ws.ext.dirs Java virtual machine (JVM) system property on the Application Server. |
Problem | The system cannot map this driver to a portability layer, including the generic portability layer. |
User response | Verify that the cm.jar file is in the class path and is accessible. |
Problem | The system is trying to call 'prepare' on a one-phase resource. |
User response | No user action is required. |
Problem | A connection cannot be created. |
User response | Verify that the database can create as many connections as the connection pool. |
Problem | The system is unable to get an XA resource while destroying a connection. Calling destroy means to close the connection and remove it from the free pool. |
User response | No user action is required. |
Problem | A password is supplied, but no user ID is supplied. |
User response | Supply a valid user ID and password, or remove the password. |
Problem | The default password is missing. |
User response | Supply a valid password for the default user. |
Problem | This message is expected during the shut down of an Application Server. |
User response | No user action is required. |
Problem | All connections in the pool are in use for the duration of the connectionTimeout period. |
User response | 1) Increase the connectionTimeout Value. 2) Increase the maximum number of connections and verify that the database can handle the increased connection load. |
Problem | The database is unable to service a request for a new connection. |
User response | Examine the SQL state code from the database to determine the exact cause of the problem. |
Problem | The system has issued a StaleConnectionException error. |
User response | Examine the SQL state code from the database to determine the exact cause of the problem. |
Problem | This exception is unexpected. The cause is not immediately known. |
User response | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The database is unable to service the request. |
User response | Examine the SQL state code from the database to determine the exact cause of the problem. |
Problem | The connection has work that is either uncommitted or not rolled back. |
User response | Commit or roll back the work on the connection prior to using the connection in a global transaction. |
Problem | This informational message indicates that one type of exception is received and another type is issued. |
User response | No user action is required. |
Problem | A required class is not found. The Java virtual machine (JVM) or the class loader cannot find the |
User response | Verify that the class exists in the classpath and is accessible by the user. |
Problem | The call to enlist with the transaction returned false or issued an exception. |
User response | Examine the WebSphere Application Server logs and the database logs for messages that might indicate why the resource is unable to enlist. |
Problem | This connection cannot be enlisted in a transaction if it is already associated with a different transaction. |
User response | Avoid caching a connection for use by more than one thread in multiple concurrent transactions. |
Problem | unilateralCommit was called on a JTAEnabled connection in a global transaction. |
User response | Do not use unilateralCommit on a JTAEnabled connection in application code. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | An SQLException was received while validating the connection. The connection pool is purged and a new connection from the pool is returned. |
User response | No user action is required. |
Problem | A connection that was in use by an application is held without being used or closed past the duration of the orphanTimeout value. |
User response | Verify that all of the connections in the application are closed after each use. |
Problem | A custom property was set when creating the JDBC provider on an Oracle system. The property requires Oracle patch 2511780. |
User response | If the patch is installed, no user action is required. Otherwise, contact Oracle support to obtain the patch. |
Problem | This warning message indicates that a non-SQL exception occurred while creating a connection. |
User response | No user action is required. |
Problem | This informational message indicates which connection manager diagnostic options are currently set. |
User response | No user action is required. |
Problem | This warning message shows all the active connection tracers when a connection timeout occurs. |
User response | No user action is required. |
Problem | This warning message describes how to turn on diagnostic information to detect orphaned connection code paths. |
User response | Set the diagnostic options to the value that is mentioned in the message. |
Problem | The database product ID or the driver class name is not found in the list of known databases. |
User response | Verify that the spelling is correct and that the database is supported. |
Problem | An error occurred during introspection of the DataSource class. |
User response | Examine the underlying exception for more details. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The property to set does not exist on the class. |
User response | Verify that the specified property name is correct. |
Problem | A method to write the property to does not exist on the class. |
User response | The property that is specified exists, but a write method does not; verify that the specified property can be written to the DataSource. |
Problem | An exception occurred setting the specified property to the DataSource. |
User response | Examine the underlying exception for more details |
Problem | The DataSource class that is provided must implement the javax.sql.ConnectionPoolDataSource or the javax.sql.XADataSource interface. |
User response | Consult your database documentation and provide a class name that implements one of these interfaces. |
Problem | An exception occurred instantiating the specified DataSource. |
User response | Examine the underlying exception for more details. |
Problem | A mapping between the exceptions is occurring. |
User response | No user action is required. |
Problem | A transaction is storing an update to a CMP entity bean. If another concurrently running transaction is storing the same container-managed persistence (CMP) entity bean, the updates of one transaction might overlay the updates of the other transaction. |
User response | Verify if the application can ensure that concurrent transactions never update the same container-managed persistence (CMP) entity bean. If this action cannot be done, then the CMP entity bean must be redeployed using either the Java Database Connectivity (JDBC) repeatable read or serializable isolation level. Remember to redeploy all the other beans that are accessed by the transaction to use the same isolation level. |
Problem | A transaction is storing an update to a container-managed persistence (CMP) entity bean and the bean is deployed using read only access intent. If another transaction is storing the same CMP entity bean, the updates of one transaction can overlay the updates of the other transaction. |
User response | The application must ensure that concurrent transactions never update the same CMP entity bean. If this action cannot be done, then the CMP entity bean must be redeployed using an update access intent rather than a read-only access intent, to maintain data consistency. |
Problem | A transaction is storing an update to a CMP entity bean. The bean is deployed using read-only access intent and either a Java Database Connectivity (JDBC) repeatable read or a JDBC serializable isolation level. If another transaction is storing the same CMP entity bean, a database deadlock can occur as a result of promotion of a read and share lock to a write exclusive lock. |
User response | The application must ensure that concurrent transactions never update the same CMP entity bean. If this action cannot be done, then the CMP entity bean must be redeployed using an update access intent rather than a read-only access intent. |
Problem | The code needs to load the class for the JDBC DataSource, but the JAR or ZIP file for the DataSource class is not found on the provider library path for the DataSource. |
User response | Either correct the installation of WebSphere Application Server so that the DataSource class can be found on the provider library path or add the DataSource class JAR or ZIP file to the class path. |
Problem | The code needs to load the class for the Java Database Connectivity (JDBC) DataSource, but the JAR or the ZIP file for the DataSource class is not found on the provider library path for the DataSource or in the class path. |
User response | Either correct the installation of WebSphere Application Server so that the DataSource class can be found on the provider library path or add the DataSource class JAR or ZIP file to the class path. |
Problem | Either the user ID or password, but not both are set on a test connection request. |
User response | Specify both the user ID and password, or specify neither. |
Problem | A test connection was attempted from the administrative console. This operation failed with the listed exception. |
User response | Examine the exception for an explanation of the failed connection. |
Problem | The was.install.library property is required and needs to be set. |
User response | Set the was.install.library property. |
Problem | Delist is a Java Database Connectivity (JDBC) specified operation. |
User response | No user action is required. |
Problem | The exception that is listed was received while delisting from the local transaction. |
User response | Examine the exception to find the root cause of the problem. If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | Only enterprise beans in V1.1 modules can be used with a V4.0 DataSource. |
User response | Either reconfigure the enterprise bean in a 1.1 module, or configure your enterprise bean to use a V5.0 DataSource. |
Problem | Only servlets with versions earlier than 2.3 can be used with a V4.0 DataSource. |
User response | Either reconfigure to use an earlier servlet version, or configure your servlet to use a V5.0 DataSource. |
Problem | The runtime is unable to determine if the DB2Connect backend is a DB2/390 database. |
User response | If the problem persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/. |
Problem | The method that is invoked is a JDBC V3.0 compliant method, and is not supported on this JDBC 2.0 compliant connection manager. |
User response | Do not invoke this method, or use a JDBC 3.0 compliant connection pooling mechanism. |