Explanation | A database error occurred for which the SQL state and the Error code are listed. |
Action | Use the information associated with the error code to fix the problem in the database. |
Explanation | A stack is provided. This stack is related to the problem reported above. |
Action | Use the information associated with the stack to fix the problem. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A valid, non-null DataSource implementation class name is required when creating a JDBC provider. |
Action | Enter a valid DataSource implementation class name and retry. |
Explanation | Unable to locate the DataSource implementation class specified. |
Action | Verify the DataSource class name you provided is correct and is in your classpath. |
Explanation | An error occurred instantiating the DataSource. |
Action | Verify the DataSource class has a public constructor taking no parameters. |
Explanation | Object cannot be cast to the specified interface because it does not implement it. |
Action | Verify that the correct implementation class is provided. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred in the WebSphere code. |
Action | Please collect all trace and system logs, along with a description of what you were attempting to do. Then contact WebSphere support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Attempted to perform an operation on an object which is closed. |
Action | Retrieve a new instance of the object and retry the operation. |
Explanation | The database back end generated an exception which was caught by the Data Store Adapter and reported to you. |
Action | Try to fix the primary problem reported by the database software. |
Explanation | possible reasons: 1)database returned null, 2) WebSphere internal error. |
Action | for reason 1 batch update should not be used, or switch to a database that supports batch update, and/or contact your database support. for reason 2, contact support with the following trace (RRA=all=enabled and PMGR=all=enabled) and the FFDC files. |
Explanation | one of the batched updates failed which caused the database to return -3 in the batch update count. -3 is returned if the database continues to execute the batched updates after one fails |
Action | examine your database logs |
Explanation | The operation was successful, however, the number of rows updated is not known. The database returned -2 in the batch update count. This exception is thrown to avoid any possible data integrity issues |
Action | repeat operation |
Explanation | some or all of the rows were not updated because of a collision usually caused by the use of the optimistic-concurrency-control AccessIntent. |
Action | repeat operation or change AccessIntent if error persists. |
Explanation | the operation indicated resulted an exception indicated. |
Action | examine the operation, exception and database logs, the exception is ignored in this case. |
Explanation | Batch operation specified above had a problem, see reason above. |
Action | examine your database logs and contact WebSphere support if no obvious reason was found. |
Explanation | An internal error has occurred. |
Action | Contact support |
Explanation | WebSphere has detected that the database started a transaction and will attempt to resolve the transaction as configured in the DataSource's custom properties. |
Action | None. |
Explanation | WebSphere has detected that the database started a transaction and will attempt to resolve the transaction as configured in the DataSource's custom properties. An error occured preventing the transaction from being resolved |
Action | Gather FFDC and any server logs. If the error is not related to a database outage or otherwise expected contact support. |
Explanation | The database has started a transaction on the connection, WebSphere will rollback the transaction before returning the connection to the pool. |
Action | Evaluate the application code to determine what may be causing the implicit transaction. The application code may be able to prevent further implicit transactions explicity, or an explicit action to take may be configured for the DataSource. |
Explanation | Usually this indicates a typo when configuring the DataSource custom property. |
Action | Ensure that one of the expected values is specified for the custom property. If there is a typo correct it and save the changes to the configuration. |
Explanation | Usually this indicates a typo when configuring the DataSource custom properties. |
Action | Update the new connection validation properties with the desired values then remove the deprecated properties. |
Explanation | Usually this indicates a typo when configuring the DataSource custom properties, but it can be a remnant of an older configuration file, or from an older wsadmin script. The new properties will take precedence over the deprecated names, however the old properties may be used at this time. |
Action | Update the new connection validation properties with the desired values then remove the deprecated properties. |
Explanation | An illegal attempt was made to load a non-WebSphere class. Only known WebSphere classes are allowed to be loaded by internal WebSphere utilities. |
Action | Do not attempt to use internal WebSphere utilities to load non-WebSphere classes. Contact IBM WebSphere support if no such attempt was made. |
Explanation | GenericDataStoreHelper has been initialized |
Action | None if this was the intention |
Explanation | An exception was detected while cleaning up the ManagedConnection for destroy. |
Action | Try to fix the primary problem reported by the database software. |
Explanation | The operation requested is not allowed during a transaction. |
Action | Perform the operation before beginning or after completing the transaction. |
Explanation | A request was initiated by the user to purge the pool, which invalidates existing connections in the pool. |
Action | Exit transaction and or method boundary and retry logic with a new connection. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A two phase operation on the database resulted in an exception. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A two phase operation on the database resulted in an exception, more details of the exception are displayed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Attempted to perform an XAResource operation with an Xid other than the Xid used for XAResource.start. |
Action | Obtain a new connection and retry the transaction. |
Explanation | The ResourceAdapter.endpointActivation method should not be used on the WebSphere Relational Resource Adapter because it does not support message inflow. |
Action | Do not use the ResourceAdapter.endpointActivation method on the WebSphere Relational Resource Adapter. |
Explanation | The default connection manager received an error while resetting a ManagedConnection to its default state. |
Action | Take action to return the database to a useable state, if necessary. |
Explanation | The default connection manager received an error while destroying a ManagedConnection. |
Action | Take action to return the database to a useable state, if necessary. |
Explanation | The default connection manager received an error when requesting validation of pooled ManagedConnections. |
Action | Take action to return the database to a useable state, if necessary. |
Explanation | The connection pool has reached its maximum limit for open connections. Further connections cannot be established until some of the open connections are closed. |
Action | Adjust the application to require fewer connections open at the same time. |
Explanation | The connection will not be reset for connection pooling because the application failed to explicitly close all handles. |
Action | Modify the application to always close all connection handles. |
Explanation | The connection cannot be reset for connection pooling because a fatal connection error occurred while it was active. |
Action | Take action to return the database to a usable state, if necessary. |
Explanation | The 'next' operation was invoked on an iterator that does not contain any more elements. |
Action | Invoke 'hasNext' on the iteration before invoking 'next' to determine whether the iteration contains additional elements. |
Explanation | The 'remove' operation was invoked with the iterator not positioned on any element. |
Action | Position the iterator to a valid element before invoking the 'remove' operation. |
Explanation | The JNDI name of the delegate datasource cannot be null or an empty string |
Action | Set the JNDI name of the delegate datasource on the map for that specific Base Proxy DataSource |
Explanation | The delegate datasource JNDI names are configured in the custom property jndiNames using semicolor-delimited syntax. The JNDI name is not in the jndiNames custom property. |
Action | Check whether the custom property jndiNames is set to a right value or not. If so, set the JNDI name of the delegate datasource to a valid value. |
Explanation | The datasource lookup failed. The DataSource is probably not created or created in a wrong scope. |
Action | Make sure the datasource is created correctly. |
Explanation | The command was not executed because it failed validation. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | The command failed while being executed. |
Action | Evaluate the reason specified in the message to determine the problem. |
Explanation | The command was not executed because an invalid parameter value was specified. |
Action | Specify a valid value for the specified parameter and retry the command. |
Explanation | The command was not executed because an invalid provider name was specified. |
Action | Specify a valid value for the provider name parameter and retry the operation. |
Explanation | The command was not executed because an invalid JDBC provider was specified. |
Action | Specify a valid value for the JDBC provider parameter and retry the operation. |
Explanation | The command step failed during execution. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | The command was unable to update the specified resource property with the specified value. |
Action | Specify a valid value for the resource property and retry the operation. |
Explanation | The command step was not executed because a value was not specified for a required resource property. |
Action | This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | The command step was not executed because an invalid parameter value was specified for a required resource property. |
Action | This problem usually occurs when the parameter value does not conform to the parameter type. Correct the problem, and retry the operation. |
Explanation | Could not map the exception, see the exception that occurred during the mapping. |
Action | Verify exception mapping in the DataStoreHelper error map table and the exception constructor. |
Explanation | MSSQLhelper methods can only be called from DataDirect helpers. |
Action | Use DataDirectDataStoreHelper.class in your setup. |
Explanation | Part or all of the necessary connection information is missing. |
Action | See the Java documentation for the DataStoreHelper.showLockInfo() method for a description of the connection information which is required. |
Explanation | The showLockInfo method does not support the specified Operating System |
Action | Use the correct Operating System |
Explanation | An exception occurred when an operation was attempted on the database to collect lock information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | DB2 wrote lock information into the filename listed. |
Action | Open the file listed. It contains information on locks in your database. This information may be helpful in resolving deadlocks in the application. |
Explanation | Oracle does not support Serializable isolation level when using XA protocol. |
Action | Do not use PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE since it cause a Serializable isolation level to be used. |
Explanation | DB2 requires the use of DB2 Universal driver |
Action | use the above DB2 driver |
Explanation | the trace file you specified on the datasource doesn't exist |
Action | make sure to use an existing file |
Explanation | user set an a custom property when creating the oracle JDBC provider, the property requires Oracle patch 2511780 |
Action | if patch is installed, no action is required, otherwise, user must contact oracle support to obtain patch. |
Explanation | The user sets the driverType datasource custom property to 2 which is not supported on Cloudscape. WebSphere will change the value to 4 at runtime. |
Action | To avoid future warnings, the user must change the driverType value to 4 in the admin console and/or the jacl scripts or omit setting it completely in which WAS will make it default to 4. |
Explanation | The user sets the driverType datasource custom property which is not supported by the JDBC driver. |
Action | Remove the driverType from the datasource custom property. |
Explanation | The DB2 Universal JDBC driver has been switched to run in a RRS environment on DB2 for zOS. |
Action | This is the information for the JDBC driver running environment. |
Explanation | The user sets the driverType datasource custom property to 2 on the DB2XADataSource. This configuration is not supported by DB2 for z/OS |
Action | either use DB2ConnectionPoolDataSource or switch to DB2 Universal JDBC driver type 4 if available. |
Explanation | The JDBC driver version used does not support the getPooledConnection(GSSCredential) method. |
Action | Use a JDBC driver that supports the getPooledConnection(GSSCredential) method. |
Explanation | An IOException occurred when trying to open the specified trace file. |
Action | Examine the exception, fix the IO problem, and start the WebSphere Application Server again. |
Explanation | An Exception occurred when trying to get/access the database metadata object. |
Action | verify that metadata is enabled on your backend database. |
Explanation | WebSphere DataSource is configured with the wrong DataStoreHelper. |
Action | Configure WebSphere DataSources with Oracle10gDataStoreHelper when running using Oracle10g jdbc driver. |
Explanation | GenericDataStoreHelper does not know how to collect lock information. |
Action | Write or use your database specific DataStoreHelper. |
Explanation | The DB2 Universal XA datasource custom property, retrieveMessagesFromServerOnGetMessage, was configured with a value of true. WebSphere has changed the value to false at runtime to avoid problems during exception processing. |
Action | To avoid this message, user must change the retrieveMessagesFromServerOnGetMessage value to false in the admin console and/or the configuration scripts or remove the property completely. This only applies to DB2 Universal XA datasources. |
Explanation | Deprecated API is being used. |
Action | Use non deprecated version of the API, see java docs and/or contact IBM technical support. |
Explanation | The reauthentication datasource custom property cannot be enabled when propagateClientIdentityUsingTrustedContext datasource custom property is enabled. |
Action | Disable propagateClientIdentityUsingTrustedContext or reauthentication datasource custom property. |
Explanation | The ThreadIdentity cannot be enabled when propagateClientIdentityUsingTrustedContext datasource custom property is enabled. |
Action | Disable propagateClientIdentityUsingTrustedContext datasource custom property or ThreadIdentity. |
Explanation | Reauthentication is enabled without providing the connection reauthentication implementation code in the DataStoreHelper class. |
Action | ovewrite the doConnectionSetupPerTransaction DataStoreHelper method and provide connection reauthentication implementation code or disable connection reauthentication can be done by one of the following: 1)uncheck WebSphere Application Server data source properties "enable database reauthentication" checkbox. 2) set reauthentication DataSource custom property to false. |
Explanation | This is the lock information reported by the Cloudscape database for your application. |
Action | This is information on locks in your database. You might want to use the information to resolve deadlocks in your application. |
Explanation | The datasource custom property cannot be enabled in the current environment. |
Action | Disable datasource custom property. |
Explanation | The datasource property is invalid in this context. |
Action | No action is needed as the WebSphere runtime will ignore the property. |
Explanation | Migration of Cloudscape instance failed, see the exception and the <dbinstance>_migration.log located in WASHOME/profiles/<profileName>/logs file for details. |
Action | fix migration problem as described by exception and migration log, delete the newly created database if it exists, and rerun the database migration tool (WASHOME/derby/bin/embedded/db2jMigrate.bat/sh) manually. |
Explanation | Migration of Cloudscape instance was partially completed, see missing steps for more details on what needs to be redone manually |
Action | fix migration problem as described by migration log, create the missing parts. Note that there is no need to rerun the migration tool as the missing parts can be recreated manually. |
Explanation | An attempt is made to delete the newly created Derby database. |
Action | No action is required, this is just an information message. |
Explanation | The attempt to delete the newly created Derby database has failed. |
Action | Delete the newly created Derby database manually |
Explanation | The Attempt to delete the newly created Derby database was successful. |
Action | no action is required, this is just an information message. |
Explanation | The providerType was not found |
Action | Please contact WebSphere support with the following data: {0} |
Explanation | Unable to locate any jar or zip files in the JDBC provider library path specified. |
Action | Verify that the path specified is correct and the necessary jars and zips are there. |
Explanation | MalformedURLException occurred attempting to read a JDBC provider jar or zip file. |
Action | Verify that the path specified is correct and the necessary jars and zips are valid. |
Explanation | An IntrospectionException occurred attempting to retrieve setter methods from the DataSource. |
Action | DataSource properties will not show up in the GUI. You will need to enter them manually. |
Explanation | Could not find a setter on the DataSource to set the requested property. |
Action | Verify the property name specified is correct. |
Explanation | Unable to locate the specified DataSource property. Possible reasons: 1) The DataSource property is spelled or capitalized incorrectly. 2) The specified property does not apply to the DataSource being configured. 3) WebSphere contains the default configuration for a different version of the specified JDBC driver, causing a mismatch of DataSource properties. |
Action | Verify that the property specified is correct for the DataSource. Fix any misspellings or capitalization errors. Delete the property if it does not apply (or no longer applies) to the JDBC driver used. |
Explanation | An exception occurred setting the specified property on the DataSource. |
Action | Verify that the value specified for the property is valid. |
Explanation | Test of DataSource connection was successful. |
Action | The DataSource can now be used by applications. |
Explanation | Test of DataSource connection was successful, but warnings were issued. |
Action | Review the DataSource configuration to fix the errors indicated by the warnings. |
Explanation | Test of DataSource connection failed. |
Action | Review the DataSource configuration to fix the error that is occurring. |
Explanation | Test of DataSource connection failed. |
Action | Review the DataSource configuration to fix the error that is occurring. |
Explanation | Possible causes are the following: 1) The wrong DataStoreHelper class was specified. 2) The DataStoreHelper class name or package name was specified incorrectly. 3) The DataStoreHelper class is not included in the classpath. 4) The JDBC Provider used may not be supported in the WebSphere release being used. |
Action | Based on the corresponding cause, perform one of the following actions: 1) Switch to the appropriate DataStoreHelper class. 2) Correct the DataStoreHelper class or package name. 3) Correct the classpath. 4) Use a different JDBC Provider or different level of WebSphere. |
Explanation | DataStoreHelper implementation class cannot be an interface or abstract class. |
Action | Provide a class which fully implements the DataStoreHelper interface. |
Explanation | DataStoreHelper class cannot be instantiated because it does not have a public constructor taking a Properties object as the parameter. |
Action | Create a public constructor for your DataStoreHelper taking a Properties object as its parameter. |
Explanation | WebSphere cannot access your DataStoreHelper constructor because it is not public. |
Action | Make your DataStoreHelper constructor a public method. |
Explanation | The DataStoreHelper constructor issued an exception. |
Action | Verify that the Properties passed to the constructor are correct, and that the DataStoreHelper constructor is implemented correctly. |
Explanation | Custom DataStoreHelper class does not implement DataStoreHelper. |
Action | Update the custom DataStoreHelper class to implement the DataStoreHelper interface. |
Explanation | Unable to execute the specified DataStoreHelper method. |
Action | If using a custom DataStoreHelper, ensure that the code in the specified DataStoreHelper method is correct. Otherwise, check your DataSource configuration properties. |
Explanation | See the linkedException for more information. |
Action | See the linkedException for more information. |
Explanation | The 'enable2Phase' property may only be set to false if the DataSource class implements ConnectionPoolDataSource. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | The 'enable2Phase' property may only be set to true if the DataSource class implements XADataSource. |
Action | Set 'enable2Phase' to true for XADataSource or false for ConnectionPoolDataSource. |
Explanation | This is a warning message that is displayed during DataSource configuration. |
Action | Read the warning message and take appropriate action to fix the problem, if necessary. |
Explanation | This is a warning message that is displayed during DataSource configuration. |
Action | Read the warning message and take appropriate action to fix the problem, if necessary. |
Explanation | Database product name |
Action | The named Database product is now used by applications. |
Explanation | Database product version |
Action | The Database product version is now used by applications. |
Explanation | The JDBC driver name. |
Action | The JDBC driver name is now used by applications. |
Explanation | The JDBC driver version. |
Action | The JDBC driver version is now used by applications. |
Explanation | Oracle does not honor the setReadOnly method. A method setReadOnly(true) will not make the connection as readonly connection. In addition, setReadOnly(false) is ignored by Oracle and a transaction is implicitly started by Oracle. Therefore, WebSphere will not invoke the setReadOnly(false) method on Oracle in order to prevent unnecessary transaction to be started. |
Action | Inspect your application to make sure that your application does not depend on a transaction after the setReadOnly(false) method is called. |
Explanation | The JDBC driver type. |
Action | The JDBC driver type is now used by applications. |
Explanation | The specified JDBC driver might not be officially certified in future releases of WebSphere Application Server. |
Action | Continue using the JDBC driver or switch to the recommended JDBC driver. |
Explanation | The database which is represented by the backend ID may not exactly match the data source connected to. |
Action | Inspect the database version between deployment and runtime datasource. If they are not the same, use a backend ID which matches the datasource to deploy the EJB, or change the datasource to match the backend ID. |
Explanation | Backend id checking is disabled so no validation of backend id will be done. |
Action | Set disableBackendIdChecking DataSource custom property to false or remove property to enable backend id checking. |
Explanation | The DataStoreHelper name. |
Action | none, this is an information message. |
Explanation | Application is using a JDBC provider that is no longer supported by WebSphere Application Server. |
Action | Use a different JDBC provider as stated in the message. |
Explanation | An error occurred while closing the specified JDBC object. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while closing the specified child object. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while closing the Statement. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Application attempted to access Connection or its corresponding Statements, ResultSets, or MetaData from a different thread. |
Action | If multithreaded access was intended, configure the WebSphere DataSource property 'enableMultithreadedAccessDetection' to false. Otherwise, adjust the application to avoid multithreaded access. |
Explanation | The method being invoked is part of the JDBC 3.0 specification, and does not exist on the provider. |
Action | Ensure that your JDBC Provider supports the JDBC 3.0 specification, or do not use this method. |
Explanation | DataStoreAdapterException was created to map a SQLException. |
Action | None. |
Explanation | The specified method is not supported by the WebSphere implementation. |
Action | Do not use the method. |
Explanation | This method is provided only for internal use by WebSphere. |
Action | Do not call this method. |
Explanation | Attempted to perform an operation on an object which is closed. |
Action | Retrieve a new instance of the object to perform the operation on. |
Explanation | Attempted to perform an operation on an inactive Connection handle. |
Action | Enable the InactiveConnectionSupport property for the Resource Adapter. |
Explanation | Attempted to invoke either a JDBC method or a disallowed proprietary method with the 'jdbcCall' method. |
Action | Call the method on the JDBC object directly. |
Explanation | Using the WebSphere 'jdbcCall' method on non-JDBC objects is not allowed. |
Action | Use the WebSphere 'jdbcCall' method only with JDBC objects. |
Explanation | The wrapper specified does not contain the wrapped object type specified. |
Action | Verify the wrapper and wrapped object parameters are specified correctly. |
Explanation | WebSphere does not permit the specified method to be invoked via jdbcPass. |
Action | If the method does not alter the state of its native JDBC object parameters in any way, the customer may contact WebSphere support to request the method be added to the list of permitted methods for jdbcPass. |
Explanation | The user is not allowed to call setTypeMap, setReadOnly or setCatalog on Shareable Connections while a global transaction is active. |
Action | Do not call setTypeMap, setReadOnly or setCatalog on Shareable Connections in a global transaction, or switch to Unshareable Connections. |
Explanation | The user is not allowed to call commit, rollback, setSavepoint or releaseSavepoint on the Connection while a global transaction is active. |
Action | Do not call commit, rollback, setSavepoint or releaseSavepoint on the Connection while in a global transaction. |
Explanation | Performing operations while in the current transaction state is not allowed. |
Action | Get a new Connection for performing the operation. |
Explanation | The current Connection handle could not be reassociated. |
Action | Try getting a new Connection. |
Explanation | Connection handles may only be reassociated from the INACTIVE state. |
Action | Close your current Connection handle and obtain a new one. |
Explanation | Connection handles may only be reassociated if all child objects are closed. |
Action | Close your current Connection handle and obtain a new one. |
Explanation | An operation is currently being performed on the Connection handle; it cannot be dissociated during the operation. |
Action | Wait until all operations on the handle have finished, then dissociate the handle. |
Explanation | The fetch size may only be set to a non-negative value. |
Action | Choose a non-negative value for the fetch size. |
Explanation | The custom property preTestSQLString may not be empty if the pre-test connection option is selected. If users choose to leave the preTestSQLString property unspecified, the performance will be worse. |
Action | Provide a valid SQL statement for preTestSQLString. |
Explanation | The passed-in Statement object cannot be set to null. Set the Statement object to a non-null object. |
Action | Set the Statement object to a non-null object. |
Explanation | The object cannot be cloned. |
Action | Do not call the clone() method. |
Explanation | Invalid passkey was passed on the getConnection method. |
Action | Please contact WebSphere support. |
Explanation | The getConnection method on this datasource can only be issued by JMS and CMP Applications. |
Action | Define another datasource for JDBC applications or set jmsOnePhaseOptimization property to false. |
Explanation | The jmsOnePhaseOptimization datasource checkbox can only be checked on non XA-capable datasources. |
Action | Use a non XA-capable datasource or uncheck the jmsOnePhaseOptimization datasource checkbox. |
Explanation | JMS is attempting to get an optimized connection. This action requires the jmsOnePhaseOptimization datasource checkbox to be checked. |
Action | Check the jmsOnePhaseOptimization checkbox on the datasource, or contact IBM technical support |
Explanation | The DataStoreHelper method specified in the exception is not called. |
Action | Examine the reason and possible cause. Call WebSphere support for help if issue is not resolved after examining the reason and cause. |
Explanation | The Connection cannot be null. Users have to pass a valid connection object. |
Action | Pass a valid connection object. |