Express (Distributed operating systems), v8.0 > Reference > Messages
CONM
CONM0000E: The Connection Manager Application Programming Interfaces have been removed. Use the Connection Pooling Application Programming Interfaces.
Explanation The methods that are called are removed. Action Use the new connection pooling API.
CONM1000E: Value "{0}" is not valid for property ({1}) for DataSource ({2}).
Explanation One of the DataSource properties is in an unexpected format. Action Verify that all of the properties for the DataSource are correct.
CONM1001E: The required property ({0}) is missing for DataSource ({1}).
Explanation A required property is missing. Action Verify that all of the required properties are configured on the DataSource.
CONM1002E: An error occurred when decrypting default password: {0}
Explanation An exception occurred during the decryption of a password. Either the encrypted password data is corrupt or is encoded in an unsupported encryption. Action Replace the encrypted password with uncorrupt data or make sure that it is encoded with a supported encryption algorithm.
CONM1003E: An error occurred when encrypting default password: {0}
Explanation An exception occurred during the encryption of a password. The password data is corrupt. Action Replace the corrupted password with an uncorrupt password.
CONM1004W: The user ID for the supplied password is missing for DataSource ({0}).
Explanation The DataSource password is supplied, but the user ID is not; the password is ignored. Action Supply the user ID that corresponds to the password or remove the password.
CONM1005W: The password for the supplied user ID "{0}", is missing for DataSource ({1}).
Explanation The DataSource user ID is supplied, but the password is not; the user ID is ignored. Action Supply the password that corresponds to the user ID or remove the user ID.
CONM1006E: The DataSource class name "{0}" cannot be found for DataSource ({1}).
Explanation The DataSource class name that is supplied cannot be found. Action Verify that the JAR file with the specified class name is installed. If the DataSource is accessed by a direct 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 JVM (JVM) system property on the Application Server.
CONM2000E: The Connection Manager is unable to obtain a portability layer for DataSource ({0}).
Explanation The system cannot map this driver to a portability layer, including the generic portability layer. Action Verify that the cm.jar file is in the class path and is accessible.
CONM6000W: A resource cannot process the two-phase commit 'prepare' request because it supports the one-phase commit protocol only. The DataSource is: {0}
Explanation The system is trying to call 'prepare' on a one-phase resource. Action No user action is required.
CONM6001W: The system cannot expand the connection pool; waiting for a free connection instead.
Explanation A connection cannot be created. Action Verify that the database can create as many connections as the connection pool.
CONM6002W: The system cannot get an XA resource {0}
Explanation 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. Action No user action is required.
CONM6004E: The required default user ID for the supplied default password is missing for DataSource ({0}).
Explanation A password is supplied, but no user ID is supplied. Action Supply a valid user ID and password, or remove the password.
CONM6006E: The required default password for the supplied default user ID, "{0}", is missing for DataSource ({1}).
Explanation The default password is missing. Action Supply a valid password for the default user.
CONM6007I: The connection pool is destroyed for DataSource ({0}).
Explanation This message is expected during the shut down of an Application Server. Action No user action is required.
CONM6008W: The system timed out waiting for a connection from DataSsource ({2}). For information about the active connections, set the DataSource property "{0}" to {1} on DataSource "{2}".
Explanation All connections in the pool are in use for the duration of the connectionTimeout period. Action 1) Increase the connectionTimeout Value. 2) Increase the maximum number of connections and verify that the database can handle the increased connection load.
CONM6009E: The database is unable to get a connection to the database from DataSource ({0}).
Explanation The database is unable to service a request for a new connection. Action Examine the SQL state code from the database to determine the exact cause of the problem.
CONM6010W: A StaleConnectionException error occurred. Purging the entire connection pool for DataSource ({0}).
Explanation The system has issued a StaleConnectionException error. Action Examine the SQL state code from the database to determine the exact cause of the problem.
CONM6011E: A connection pooling internal error occurred. An illegal ConnectO state, "{0}", on DataSource ({1}) is detected.
Explanation This exception is unexpected. The cause is not immediately known. Action If the problem persists, see the problem determination on the WAS Support Web page on //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CONM6012E: A database error occurred when setting the AutoCommit value for DataSource ({0}).
Explanation The database is unable to service the request. Action Examine the SQL state code from the database to determine the exact cause of the problem.
CONM6013E: The connection has outstanding work and cannot join a global transaction for DataSource ({0}).
Explanation The connection has work that is either uncommitted or not rolled back. Action Commit or roll back the work on the connection prior to using the connection in a global transaction.
CONM6014I: The system received exception ({0}) in method ({1}) and is issuing a new exception ({2}). The original exception stack trace is: {3}
Explanation This informational message indicates that one type of exception is received and another type is issued. Action No user action is required.
CONM6015E: The system cannot load XAResourceFactory in method ({0}) because the class ({1}) is not found. Issuing new ({2}).
Explanation A required class is not found. The JVM (JVM) or the class loader cannot find the Action Verify that the class exists in the classpath and is accessible by the user.
CONM6016E: The system is unable to enlist with the transaction. Issuing new ({0}).
Explanation The call to enlist with the transaction returned false or issued an exception. Action Examine the WAS logs and the database logs for messages that might indicate why the resource is unable to enlist.
CONM6017E: In the enlist method, the connection is already associated with another transaction.
Explanation This connection cannot be enlisted in a transaction if it is already associated with a different transaction. Action Avoid caching a connection for use by more than one thread in multiple concurrent transactions.
CONM6018E: Calling unilateralCommit is not supported on a JTAEnabled connection in a global transaction.
Explanation unilateralCommit was called on a JTAEnabled connection in a global transaction. Action Do not use unilateralCommit on a JTAEnabled connection in application code. If the problem persists, see the problem determination on the WAS Support Web page on //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CONM6019W: A SQLException occurred while validating the connection for DataSource {0}. The exception is {1}.
Explanation An SQLException was received while validating the connection. The connection pool is purged and a new connection from the pool is returned. Action No user action is required.
CONM6020W: A connection is orphaned and returned to pool {0}.
{1}
Explanation A connection that was in use by an application is held without being used or closed past the duration of the orphanTimeout value. Action Verify that all of the connections in the application are closed after each use.
CONM6021W: A JDBC provider property (TransactionBranchesLooselyCoupled) is set in Oracle. Oracle patch 2511780 must be applied before setting this property.
Explanation A custom property was set when creating the JDBC provider on an Oracle system. The property requires Oracle patch 2511780. Action If the patch is installed, no user action is required. Otherwise, contact Oracle support to obtain the patch.
CONM6024W: An Exception, ({0}), was caught in createConnection method.
Explanation This warning message indicates that a non-SQL exception occurred while creating a connection. Action No user action is required.
CONM6025I: The following connection manager diagnostic options are activated on DataSource {0}: {1}
Explanation This informational message indicates which connection manager diagnostic options are currently set. Action No user action is required.
CONM6026W: Timed out waiting for a connection from DataSource {0}.
{1}
Explanation This warning message shows all the active connection tracers when a connection timeout occurs. Action No user action is required.
CONM6027W: A connection is orphaned and returned to pool {2}. For information about which code path is orphaning connections, set the DataSource property "{0}" to {1} on DataSource "{2}".
Explanation This warning message describes how to turn on diagnostic information to detect orphaned connection code paths. Action Set the diagnostic options to the value that is mentioned in the message.
CONM7000W: An unrecognized database or driver {0} is found; using generic settings
Explanation The database product ID or the driver class name is not found in the list of known databases. Action Verify that the spelling is correct and that the database is supported.
CONM7001E: The following exception occurred introspecting class {0}: {1}
Explanation An error occurred during introspection of the DataSource class. Action Examine the underlying exception for more details. If the problem persists, see the problem determination on the WAS Support Web page on //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CONM7002W: The system cannot find the property {0} on class {1}
Explanation The property to set does not exist on the class. Action Verify that the specified property name is correct.
CONM7003W: The system cannot find the method to write property {0} on class {1}
Explanation A method to write the property to does not exist on the class. Action The property specified exists, but a write method does not; verify that the specified property can be written to the DataSource.
CONM7004W: An exception occurred setting the property {0} on class {1}: {2}
Explanation An exception occurred setting the specified property to the DataSource. Action Examine the underlying exception for more details
CONM7005E: The class ({0}) does not implement the javax.sql.ConnectionPoolDataSource or the javax.sql.XADataSource interface.
Explanation The DataSource class provided must implement the javax.sql.ConnectionPoolDataSource or the javax.sql.XADataSource interface. Action Consult your database documentation and provide a class name that implements one of these interfaces.
CONM7006E: An exception occurred instantiating the class ({0}) for DataSource ({1}): {2}
Explanation An exception occurred instantiating the specified DataSource. Action Examine the underlying exception for more details.
CONM7007I: Mapping the following SQLException, with ErrorCode {0} and SQLState {1}, to a StaleConnectionException: {2}
Explanation A mapping between the exceptions is occurring. Action No user action is required.
CONM7008W: A repeatable read isolation level or stronger is needed to eliminate potential lost updates to bean {0} if updated concurrently by multiple transactions.
Explanation 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. Action 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 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.
CONM7009W: A read only intent is used to update bean {0}. An update intent is required to eliminate potential lost updates to bean {0} when used concurrently by multiple transactions.
Explanation 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. Action 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.
CONM7010W: A deadlock can occur while storing container-managed persistence (CMP) entity bean {0} during multiclient same-key access processing. A read-only method is followed by an update to the database. You might need to change a read-only method from an access intent of read to an access intent of update, to avoid potential deadlock problems.
Explanation A transaction is storing an update to a CMP entity bean. The bean is deployed using read-only access intent and either a 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. Action 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.
CONM7011W: The connection manager cannot find the JAR file or the ZIP file for the DataSource class {0} in the provider library path for the DataSource {1}. The code checks the class path for the JAR file.
Explanation 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. Action Either correct the installation of WAS 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.
CONM7012E: The connection manager cannot find the JAR or the ZIP file for the DataSource class {0} in the provider library path for the DataSource {1} or in the class path.
Explanation The code needs to load the class for the 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. Action Either correct the installation of WAS 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.
CONM7013W: Both the user ID and the password must be set for the test connection to work.
Explanation Either the user ID or password, but not both are set on a test connection request. Action Specify both the user ID and password, or specify neither.
CONM7014W: The test connection to the DataSource failed : {0}
Explanation A test connection was attempted from the administrative console. This operation failed with the listed exception. Action Examine the exception for an explanation of the failed connection.
CONM7015E: The was.install.library property is not set.
Explanation The was.install.library property is required and needs to be set. Action Set the was.install.library property.
CONM7016W: The ConnectO.destroy method failed during the delist process from the local transaction : {0}
Explanation Delist is a JDBC specified operation. Action No user action is required.
CONM7017E: An exception occurred on the delistResource for local transaction: {0}
Explanation The exception that is listed was received while delisting from the local transaction. Action Examine the exception to find the root cause of the problem. If the problem persists, see the problem determination on the WAS Support Web page on //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CONM7018E: The Connection Manager attempted to use a V4.0 DataSource with an enterprise bean that is not valid. The current EJB module is: {0}
Explanation Only enterprise beans in V1.1 modules can be used with a V4.0 DataSource. Action Either reconfigure the enterprise bean in a 1.1 module, or configure your enterprise bean to use a V5.0 DataSource.
CONM7019E: The Connection Manager attempted to use a V4.0 DataSource from a v2.3 or later servlet, which is not a valid configuration.
Explanation Only servlets with versions earlier than 2.3 can be used with a V4.0 DataSource. Action Either reconfigure to use an earlier servlet version, or configure your servlet to use a V5.0 DataSource.
CONM7020W: The connection manager is unable to determine the backend database type. DB2/390 semantics are not used.
Explanation The runtime is unable to determine if the DB2Connect backend is a DB2/390 database. Action If the problem persists, see the problem determination on the WAS Support Web page on //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
CONM8000E: Method {0} is not supported on a JDBC V2.0 compliant DataSource.
Explanation The method that is invoked is a JDBC V3.0 compliant method, and is not supported on this JDBC 2.0 compliant connection manager. Action Do not invoke this method, or use a JDBC 3.0 compliant connection pooling mechanism.
CONM8001E: Method {0} is not supported on a JDBC V2.0 compliant DataSource.
Explanation The method that is invoked is a JDBC V4.0 compliant method, and is not supported on this JDBC 2.0 compliant connection manager. Action Do not invoke this method, or use a JDBC 4.0 compliant connection pooling mechanism.
CONM8002E: The method that was invoked is not supported.
Explanation The method that was invoked is not supported on this JDBC 2.0 compliant connection manager. Action Do not invoke this method.