Explanation | The pool manager could not allocate a managed connection. This might be due to the properties associated with the pool manager (such as, maximum connections were exceeded). A NULL managed connection was returned by the pool manager. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This indicates that an attempt was made to use the connection within the context of an XA transaction along with other XA capable resources. This is not a valid operation for this resource adapter. |
Action | Modify the logic to separate the resource usage into separate transactions. |
Explanation | The pool manager created an exception when attempting to allocate a managed connection. The exception text might provide additional information for determining the problem. |
Action | If there are no user controlled indications, the message might be due to an internal error in the connection manager processing. Collect diagnostic data and visit the IBM support site for more information. |
Explanation | The resource adapter created an exception when attempting to call the getConnection() method. The exception text might provide additional information for determining the problem. |
Action | If there are no user controlled indications, the message might be due to an internal error in connection manager processing. Collect diagnostic data and visit the IBM support site for more information. |
Explanation | There was a problem attempting to clean records from a failed getConnection attempt. This message is informational and should be combined with other related messages for proper problem determination. |
Action | Examine the other related messages for explanations and user responses. |
Explanation | There was an attempt made to invoke an XA operation on a resource adapter that only supports local transactions. A local transaction resource adapter might have been included within the context of an XA transaction, along with other XA capable resources. |
Action | Modify the business logic to separate the resource usage into separate transactions. |
Explanation | There was a problem processing the given method. The interface defines specific exceptions that can be created, so the exception that was caught was mapped to the exception that was created. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the exception that was created and that it contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception. |
Explanation | There was a problem processing the given method. The interface defines specific exceptions that can be created, so the exception that was caught was mapped to the exception that was created. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the exception that was created and contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception. |
Explanation | There was a problem processing the given method. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the exception that was created and that it contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception |
Explanation | There was a problem processing the given method. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the exception that was created and that it contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception. |
Explanation | There was a problem processing the given method. The interface defines specific exceptions that can be created, so the exception that was caught was mapped to the exception that was created. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the exception that was created and that it contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception. |
Explanation | There was a problem attempting to delist resources from the transaction manager. This message is for informational purposes. |
Action | If this message occurs on a regular basis, collect diagnostic information and visit the IBM support site for more information. |
Explanation | This is most likely an error with the specific resource adapter. |
Action | Contact the resource adapter supplier. |
Explanation | There was an internal error in the connection manager processing. A valid transaction context is required for the given operation, but it was not found. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A connection wait timeout has occurred. A ConnectionWaitTimeoutException was created. |
Action | Reconfigure the connection pool. Increase the maximum number of connections or increase the connection wait time to avoid this error. |
Explanation | An error occurred during creation of a ManagedConnection. Usually this can be resolved by looking at the error messages from the resource adapter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Either an activity session, transaction, or local transaction work scope is ending and connection handles are not closed. Support for caching handles outside of the current unit of work scope is not supported for this configuration or release. |
Action | Inspect your application and ensure that the connection handles are closed before the associated unit of work ends. |
Explanation | The connection manager has been notified by the resource adapter that an error has occurred on the connection. This informational message is logged so that the user can see the exception that was returned. |
Action | The connection manager will remove the failing connection or all the connections from the pool, depending on the configuration. This is normal behavior. If this error appears unexpected, investigate the exception to determine the possible source of the problem. |
Explanation | This is a WebSphere internal error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This is most likely an application error. An example: A cached connection is enlisted in a transaction, then the connection is closed. Before the transaction completes another request it is sent to the same EJB that originally opened the connection. The cached handle is still associated with the original transaction and cannot be re-associated until that transaction commits. |
Action | Inspect the application and ensure that the transaction is committed as soon as possible after connections are closed. |
Explanation | This is a security runtime error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error occurred. Using the default value. |
Action | This is only a warning. If an error occurs later it may help in diagnosing the problem. Otherwise This can be ignored. |
Explanation | An internal error was received and the connection manager was not able to delist a connection from the transaction in which it was involved. The connection manager will attempt to destroy the connection. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An internal error was received and the connection manager was unable to enlist a connection with the current transaction. The connection manager will attempt to destroy the connection. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Normal connection management processing requires the presence of a transaction in order to run the current method. |
Action | Start any transactions that are required to successfully use the connection. |
Explanation | The connection manager was unable to obtain a LocalTransaction from the resource adapter. This indicates a problem with the resource adapter. |
Action | Look for error messages from the resource adapter to identify the problem. |
Explanation | The connection manager was unable to obtain a XAResource from the resource adapter. This indicates a problem with the resource adapter. |
Action | Look for error messages from the resource adapter to identify the problem. |
Explanation | The connection manager has detected an internal error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The connection manager has detected an internal error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The connection manager caught an exception while trying to perform an operation on a ManagedConnection. |
Action | Since the ManagedConnection is part of the resource adapter, look for messages from the resource adapter to further isolate the problem. |
Explanation | Multiple open connection handles can only share a single physical connection within the scope of a global transaction. When multiple connection handles are open within a local transaction containment boundary, each handle uses a different physical connection. Having multiple shareable connection handles open at the same time within a local transaction containment boundary can increase the requirement on the connection pool for maximum number of connections and can greatly increase the complexity of connection handle usage with respect to local transactions for applications that follow this pattern. |
Action | Ensure the connection pool is sized so that each thread can require multiple physical connections, and review the application code to verify that this usage pattern is desired and that the expected sharing scope is specified. |
Explanation | This message indicates a problem enlisting in a transaction. The resource might have already been enrolled in a transaction or the transaction might not have been in the correct state. |
Action | Check that the business logic of the application is properly catching the exception created and that it contains the necessary recovery logic. Check log files for previous errors (specifically transaction errors) that might have caused the exception. |
Explanation | An internal error has occurred. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An InterruptedException occurred on the thread for the garbage collector. J2C processing will continue, but unused and aged connections will not be collected. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The source of the event fired on the listener was not of type ManagedConnection |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An attempt was made to add a duplicate connector property. The property was not added. |
Action | A custom property of a connection factory or data source specified a user name or password, but a component-managed authentication alias was also specified. The alias takes precedence over the custom properties. This error might also be the result of a hand-modified resources.xml document. |
Explanation | A ConnectionWaitTimeout of 0 indicates an infinite wait time. This thread will sleep until a connection is freed. |
Action | There is no user action required. |
Explanation | A CONNECTION_CLOSED ConnectionEvent is required by the Java EE Connector Architecture to contain a valid connection handle associated with the ManagedConnection instance. |
Action | The resource adapter must use ConnectionEvent.setConnectionHandle() to supply the connection handle in the CONNECTION_CLOSED ConnectionEvent. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The connection manager was unable to make the requested change to the configuration variable at this time. |
Action | Attempt to change the configuration variable again. |
Explanation | A connection factory, activation spec or admin object has a resource property which is not valid. The value will remain unset. |
Action | Correct the resource property so the value is consistent with its data type. |
Explanation | The connection manager has been notified by the resource adapter that an unrecoverable error has occurred on the connection. No exception was received from the resource adapter. |
Action | The connection manager will remove the failing connection, or all the connections (depending on configuration) from the pool. This is normal behavior. If this causes adverse effects, it may be necessary to contact the resource adapter supplier. |
Explanation | The feature is not implemented by the application server. |
Action | No user action is required. |
Explanation | During de-serialization of an object, an expected field was not found. This is most likely due to an object that is being de-serialized by a version of the class that is different than the one that serialized the object. |
Action | This warning indicates a potential problem, but no user action is necessary unless further errors occur. |
Explanation | A call to the method getInvalidConnections() returned a resource exception. |
Action | Visit the support web site for the provider of the resource adapter. |
Explanation | An internal error occurred while processing the lazyEnlist() method. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This most likely indicates an error with the implementation of the resource adapter. The resource adapter called the lazyEnlist() method with a null value for the ManagedConnection. |
Action | Visit the support web site for the provider of the resource adapter. The resource adapter code has passed a null value to the lazyEnlist() method. See section 7.14.2 of the JCA 1.5 specification for more information on the Lazy Transaction Enlistment optimization. |
Explanation | This most likely indicates an error in the application. The application should not start local transactions when it is operating in a global transaction. |
Action | Examine the application code to determine where a local transaction is started inside a global transaction. Search the FFDC directory for this message to find a stack trace that may include the line numbers of the code in question - this can help to narrow the search. If the line numbers are not found, if the code has been JIT compiled or it is otherwise obfuscated for example, you might want to instrument the code with System.out.println() statements to help find the problem area. If the problem cannot be found visit the IBM support web site. |
Explanation | An attempt was made to add a duplicate connector property. The property was not added. |
Action | A custom property of a connection factory or data source was specified, but the property already existed. This could be a symptom of a hand-modified resources.xml document. |
Explanation | An internal error occurred during failover processing. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The attempt to reserve an MCWrapper failed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |