Explanation | This message indicates a problem with the Systems Management configuration of the Resource Adapter. A Deployment Descriptor does exist for this Resource Adapter, but it is not in the right format to read in and process. |
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 message indicates a problem with the Systems Management configuration for the Resource Adapter. A Deployment Descriptor does not exist for this Resource Adapter. |
Action | Check that resources.xml exists and contains a <resourceProviders xmi:type="resources.j2c:J2CResourceAdapter" . . .> element. If not, or if it looks incorrect, delete and re-create the resource adapter via the Admin Console. |
Explanation | This message indicates a problem with the Systems Management configuration of the Connection Factory. The Properties do exist for the Connection Factory, but they are not in the right format to read in and process. |
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 message indicates a problem with the Systems Management configuration of the Connection Factory. The Properties do not exist for this Connection Factory. |
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 message indicates a problem with the Systems Management configuration of the Connection Factory. The Connection Pooling Properties do exist for the Connection Factory, but they are not in the right format to read in and process. |
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 message indicates a problem with the Systems Management configuration of the Connection Factory. The Connection Pooling Properties do not exist for this Connection Factory. |
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 message indicates a problem with invoking a method on a deployed object. The names of these methods are determined by the name/value pairs contained in the JavaBean's Properties. These in turn are based on the contents of the Resource Adapter's ra.xml file. Processing will continue since the default values for this particular property may be sufficient to continue execution. Or, this particular property may not even be required by the specified deployed object. |
Action | This may indicate a mismatch between the Resource Adapter's XML definition and the actual Java class provided for the JavaBean's implementation. Examine the attributes supplied by the resource adapter. It may be necessary to provide this failure notification to the resource adapter provider. |
Explanation | This message indicates a missing method on a deployed object. The names of these methods are determined by the name/value pairs contained in the JavaBean's Properties. These in turn are based on the contents of the Resource Adapter's ra.xml file. Processing will continue since the default values for this particular property may be sufficient to continue execution. Or, this particular property may not even be required by the specified deployed object. |
Action | This may indicate a mismatch between the Resource Adapter's XML definition and the actual Java class provided for the JavaBean's implementation. Examine the attributes supplied by the resource adapter. It may be necessary to provide this failure notification to the resource adapter provider. |
Explanation | This message indicates a problem while attempting to create a ManagedConnectionFactory object. There are several possible reasons for this problem. The runtime (1) couldn't find the appropriate class for the ManagedConnectionFactory via the current class loader, (2) couldn''t create a TraceWriter object for the ManagedConnectionFactory, (3) or couldn''t create the ConnectionManager object for the ManagedConnectionFactory. Any of these could also be related to an invalid XML definition for the Resource Adapter. |
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 | The getObjectInstance method is invoked by the JNDI lookup processing of the Resource. The JNDI lookup implementation should be passing in a valid Reference object for the desired Resource. Either the Name Service is passing in a bad object or the "Reference" object was created incorrectly in the first place. |
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 message indicates a problem with the Reference object that was initially stored in the JNDI name space. |
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 message indicates a problem with the Reference object that was initially stored in the JNDI name space. |
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 indicates a problem with creating the ManagedConnectionFactory from the stored Reference in the JNDI name space. |
Action | This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses. |
Explanation | This exception indicates a problem with creating the Reference object to be stored in the JNDI name space for the named Resource. This problem will be detected and logged as an error later in the processing. |
Action | This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses. |
Explanation | The Pool Manager could not allocate a Managed Connection. This may be due to properties associated with the Pool Manager (ie. maximum connections exceeded). A NULL managed connection was returned by the Pool Manager. |
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 message 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 | This exception indicates a problem with creating the Serializable object to be stored in the JNDI name space for the named Resource. This problem will be detected and logged as an error later in the processing. |
Action | This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses. |
Explanation | This message indicates a problem with the Resource Adapter creating the desired Connection Factory. The exception text should provide additional details on the actual problem. |
Action | If the exception text does not indicate a situation that is user controlled, then contact support and collect diagnostic data for them. |
Explanation | This message indicates that due to other logged problems, the properties for the Managed Connection Factory could not be assembled. This may or may not cause runtime problems -- it will depend on the default values of the various properties as provided by the Resource Adapter. |
Action | Check for other related messages that will further explain the specific problems with the property data. If your connections seem to work okay, you could ignore this message. Otherwise, attempt to follow the User Response sections as documented by the other messages. |
Explanation | This message indicates that an exception was thrown by the Pool Manager when attempting to allocate a Managed Connection. The exception text should help with deciphering the problem encountered. |
Action | If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them. |
Explanation | This message indicates that an exception was thrown by the Resource Adapter when attempting to call getConnection. The exception text should help with deciphering the problem encountered. |
Action | If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them. |
Explanation | This message indicates that a problem was encountered while attempting to clean up after a failed getConnection. This message is informational and should be combined with other related messages for proper problem determination. |
Action | Examine other related messages for Explanation and User Responses. |
Explanation | This message indicates an attempt to invoke an XA operation on a resource adapter that only supports local transactions. This may indicate that a local transaction resource adapter was accidentally 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 | This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception. |
Explanation | This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception. |
Explanation | This message indicates a problem while 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 thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception. |
Explanation | This message indicates a problem while 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 thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception. |
Explanation | This may be a symptom of an incorrectly hand-modified resources.xml document. Alternatively if you are using an application with an embedded ResourceAdapter, this may be a symptom of an incorrectly hand-modified deployment.xml document. |
Action | If you have hand-modified either a resources.xml or a deployment.xml file, please correct any errors there. If you have not edited these files, this may be and internal application server error. |
Explanation | This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully. |
Action | Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception. |
Explanation | This message indicates a problem while attempting to delist resources from the transaction manager. This message is for informational purposes, unless it occurs on a regular basis. |
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 is most likely an error with the specific resource adapter. |
Action | Contact support for the resource adapter. |
Explanation | The set method does not exist for this class, the J2C runtime expected this method to exist. The resource adapter requires this set method to be executed to function properly, so the ManagedConnectionFactory is discarded. The class file for this ManagedConnectionFactory may be out of date, or there may be a miscommunication between WebSphere Systems Management and the J2C runtime. |
Action | Ensure that the class files for this resource adapter are up to date. |
Explanation | The set method could not be executed. The resource adapter requires this method in order to function correctly. The class files for this ManagedConnectionFactory may be out of date, or there may have been an error communicating between WebSphere systems management and the J2C Runtime. |
Action | Ensure that the class files for this resource adapter are up to date. |
Explanation | An internal error has occurred when reading properties from the namespace. |
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 internal error has occurred when reading properties from the namespace. |
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 | Internal error in the J2C runtime. A valid transaction context was required for the given operation but was not found. |
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 | Check the failing path string and verify that any non-expanded variables are valid (including their case). |
Action | Fix any invalid variables. |
Explanation | This indicates either that the path for the ResourceAdapter has been configured incorrectly or that the resources.xml file (or deployment.xml file if you are using an embedded RAR file) has been corrupted. |
Action | Correct the ResourceAdapter path configuration or corrupt xml configuration file. |
Explanation | An internal error occurred when getting a Subject. A container-managed authentication alias may not have been selected on the connection factory or datasource. |
Action | Check that a valid container-managed authentication alias is specified on the connection factory or datasource. |
Explanation | A connection wait timeout has occurred. A ConnectionWaitTimeoutException was thrown. |
Action | Reconfigure the connection pool. You may increase the maximum number of connections, or increase connection wait time to avoid this condition. |
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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | ResourceAdapter properties are only allowed to be of the following types: java.lang.Character, java.lang.String, java.lang.Boolean, java.lang.Byte, java.lang.Integer, java.lang.Long, java.lang.Float, java.lang.Double. |
Action | Fix the Resource Adapter code such that it is compliant. |
Explanation | The server was unable enable transaction recovery for this ResourceAdapter. Possible causes include: errors in the archive, class, or native paths; internal server errors. |
Action | Validate your archive, class, and native paths. |
Explanation | ResourceAdapters should be stopped only after all MessageEndpoints have been deactivated. MessageEndpoints get deactivated when the application which is supplying the MessageEndpoint is stopped. Currently, only MDB's can be a MessageEndpoint. |
Action | Make sure you stop your applications which contain endpoints which are associated with a particular ResourceAdapter before you stop that ResourceAdapter. |
Explanation | A connector property was not given a value, nor does it have a default. The set method is not called. This could be the root cause of a later error. |
Action | None. |
Explanation | An exception occurred while attempting to stop a ResourceAdapter. |
Action | Take appropriate action based on the exception text. |
Explanation | The JNDI lookup of the ActivationSpec failed. This could be caused by one of the following conditions: 1) the ActivationSpec referred to by the specified JNDI name has not been configured, 2) the JNDI Name is incorrect, or 3) some other problem exists as indicated by the exception. |
Action | Make sure the ActivationSpec had been configured for the ResourceAdapter you are using. Make sure that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter. |
Explanation | The resource adapter does not support a TransactionResourceRegistration setting of {1}. The J2C Runtime is using the default value of {0}. |
Action | None. |
Explanation | In order to activate a MessageEndpoint (MDB) a JNDI name to a configured ActivationSpec must be supplied during MDB deployment. |
Action | Make sure the ActivationSpec had been configured for the ResourceAdapter you are using. Make sure that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter. |
Explanation | Either a Activity Session, Transaction, or Local Transaction work scope is ending and connection handles have not been closed. Support for caching handles outside the current unit of work scope is not supported for this configuration or release. |
Action | Inspect your code and make sure you always close your connection handles before the unit of work the handle is involved in ends. |
Explanation | The Connection Manager has been notified by the Resource Adapter that a fatal error has occurred on the connection. This informational message is logged so that the user can see the exception returned. |
Action | The Connection Manager will remove the failing connection, or all the connections (depending on configuration) from the pool. This is normal behavior. If you look at the exception and determine that it is unexpected, then investigate the exception and correct the problem which is causing the exception to occur. |
Explanation | WebSphere internal error. |
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 | Usually this is due to an application error. An example : A cached connection is enlisted in a transaction, then the connection is closed. Before the transaction completes another request 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 | Check the application and make sure that the transaction is committed as soon as possible after connections are closed. |
Explanation | WebSphere internal error in the security runtime. |
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 recreating an XA Resource, the resource could not be recovered. |
Action | Check for other related messages that will further explain the specific problem. |
Explanation | The cleanup operation on a managed connection failed. The connection could not be cleaned up after recovery. |
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 | The destroy operation on a managed connection failed after recovery. |
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 | WebSphere internal error. |
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 | WebSphere internal error. |
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 | The resource adapter does not support the getter method as documented. |
Action | Contact the developer of the resource adapter. |
Explanation | An internal error occurred, using the default value. |
Action | This is a warning message, if an error occurs later it may help in diagnosing the problem. Otherwise this message can be ignored. |
Explanation | An internal error occurred. |
Action | This message is due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them. |
Explanation | An internal error occurred. |
Action | This message is due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them. |
Explanation | This message indicates number of connection(s) being held by a component. his message follows the resource unavailable exception when getConnection request failed in user code. |
Action | Check if one or more components are excessively holding connections. A user programming error may not be closing connection. If number of connections appear to be ok, try increasing "max pool size". |
Explanation | This may be a symptom of an incorrectly hand-modified resources.xml document. Alternatively, if you are using an application with an embedded ResourceAdapter, this may be a symptom of an incorrectly hand-modified deployment.xml document. |
Action | If you have hand-modified either a resources.xml or a deployment.xml file, please correct any errors there. If you have not edited these files, this may be and internal application server error. |
Explanation | Due to an internal error which was received, the Connection Manager was unable to delist a connection from the transaction it was involved in. As a result it will attempt to destroy the connection. |
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 | Due to an internal error which was received, the Connection Manager was unable to enlist a connection with the current transaction. As a result it will attempt to destroy the connection. |
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 | Normal connection management processing requires the presence of a transaction in order to execute the current method. |
Action | Start a transaction if your application requires a transaction to successfully use the connection. |
Explanation | Processing requires the presence of a transaction in order to execute the current method. The most common cause of a missing transaction context is that the transaction had timed out. |
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 | The Connection Manager was unable to obtain a LocalTransaction from the ResourceAdapter. This indicates some problem with the ResourceAdapter. |
Action | Look for error messages from the ResourceAdapter to identify the problem. |
Explanation | The Connection Manager was unable to obtain a XAResource from the ResourceAdapter. This indicates some problem with the ResourceAdapter. |
Action | Look for error messages from the ResourceAdapter to identify the problem. |
Explanation | The Connection Manager has detect an internal error. |
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 | The Connection Manager has detect an internal error. |
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 | The Connection Manager caught an exception while trying to perform an operation on a ManagedConnection. |
Action | Since the ManagedConnection is part of the ResourceAdapter, look for messages from the ResourceAdapter to further isolate the problem. |
Explanation | The resource adapter does not support an InactiveConnectionSupport setting of {1}. |
Action | Contact the developer of the resource adapter. |
Explanation | The ConnectionHandleManager caught an exception while trying to perform a handle re-association operation. This exception may or may not be a problem. This is expected behavior following a transaction time-out. In all other cases this should be considered a WebSphere internal error. |
Action | Look for messages indicating that a transaction has timed out. If time-outs are occurring you can ignore this message. If you don't see evidence of a transaction time-out, contact support. |
Explanation | Registration with the transaction service for recovery of transactions for inbound messages to this ResourceAdapter failed. Subsequent use inbound transactions may also fail. |
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 connector property was not given a value, nor does it have a default. The set method is not called. This could be the root cause of a later error. |
Action | None. |
Explanation | Shareable connections are not allowed within a local transaction containment boundary. |
Action | Connection was made non-shareable. This may have adverse effects. In the future, you will get an exception in this case. |
Explanation | This message indicates a problem enlisting in a transaction, the resource may have already been enrolled in a transaction or the transaction may not have been in the correct state. |
Action | Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors (specifically transaction errors) that may have caused the exception. |
Explanation | An internal error has occurred. |
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 | The ResourceAdapter threw an exception. This could indicate a problem with the ResourceAdapter. |
Action | Check the exception for more information. |
Explanation | Message was added after translation cutoff and so is not translated. |
Action | See message for details. |
Explanation | An unexpected InterruptedException occurred on the Garbage Collector thread. J2C processing will continue, however Unused and Aged connections will not be collected. |
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 | Message was added after translation cutoff and so is not translated. |
Action | See message for details. |
Explanation | Message was added after translation cutoff and so is not translated. |
Action | See message for details. |
Explanation | The transaction this operation was a part of has failed, possibly due to a transaction timeout. |
Action | See messages from the transaction service for more information on the failure. |
Explanation | MappingModule object could not be read. |
Action | See ffdc logs for more information on the failure. |
Explanation | The attempt to create a new MCWrapper failed, causing a NullPointerException on use. |
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 unexpected null value was returned from ContainerComponentMetaData.getLocalTran(). |
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 | The source of the event fired on the listener was not of type ManagedConnection |
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 attempt to run an EJB component incompatible with WebSphere Application Server was detected. |
Action | Evaluate the EJB version and CMP version supported by the EJB component, correct, and re-deploy. |
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 | RA miscellaneous configuration object could not be read. |
Action | See ffdc logs for more information on the failure. |
Explanation | An attempt to run an EJB component incompatible with WebSphere Application Server was detected. |
Action | Evaluate the EJB version supported by the EJB component, correct, and redeploy. |
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 datasource specified a UserName or Password while a component-managed authentication alias was also specified. The alias takes precedence over the Custom Properties. Alternatively, this could be a symptom of a hand-modified resources.xml document. |
Explanation | The authentication mechanism must be one of those specified in the resource adapter's ra.xml document element <authentication-mechanism-type>. |
Action | Use the Administrative Console to specify an authentication mechanism which is supported by the resource adapter. |
Explanation | This may be a symptom of a hand-modified resources.xml document. A Subject may contain null credentials. The resource adapter may or may not accept this Subject. |
Action | Use the Administrative Console to specify an authentication mechanism which is supported by the resource adapter. If the resource adapter does not support any authentication mechanism, choose none. |
Explanation | 5.0 DataSources are only supported for servlet level 2.3 WebModules. |
Action | Evaluate whether the servlet in question can be migrated to level 2.3, if so migrate the application and redeploy. If it cannot be migrated, the servlet must use a WAS 4.0 DataSource. |
Explanation | The component is accessing the connection factory or datasource with res-auth=Application, but no user/pw is available. This may result in an allocateConnection failure later on. |
Action | In some cases, this may be ignored. For example, if a valid user/pw in the ConnectionSpec is passed on the getConnection method, or if the back end resource does not require authentication. If you are experiencing problems logging in to the back end resource, use the Administrative Console to specify a component-managed authentication alias for {0}. |
Explanation | An internal error has occurred. The parent MBean should be created when the ConnectionFactory or DataSource is bound into the namespace. |
Action | Run collector.bat and provide the data to 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 | An internal error has occurred. The ObjectNames used on the lookup were not created. |
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 internal error occurred when trying to obtain a cached instance of J2CPerf. |
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 internal error has occurred. The MBeans should be created when binding the referenceable object into JNDI and during a JNDI lookup respectively. Both ObjectNames will be set to null, and the Pmi Data will be created, but will not link with the MBeans. |
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 internal error has occurred. The MBeans will not be linked correctly. This does not effect the use of the ConnectionFactory or DataSource, but may cause an error if you are using PMI. |
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 | The component did not specify a login configuration on the resource-reference to {0}. The deprecated container-managed authentication on the connection factory or datasource is used, but no container-managed authentication alias was specified. A Subject with empty user/pw is constructed. |
Action | In some cases, this may be ignored. If you are experiencing problems logging in to the back end resource, define a login configuration on the resource-reference using a deployment tool. If the deprecated mechanism for container-managed authentication is desired, use the Admin Console or scripting tools to create the connection factory or datasource with the proper container-managed authentication alias. Alternatively, if component-managed authentication is desired, change the resource-ref for the component to res-auth=application. |
Explanation | An internal error has occurred. |
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 properties file was not coded correctly. |
Action | Ensure that the root element of {0} is correct. |
Explanation | This is an informational message. |
Action | None. |
Explanation | The trace writer was not able to be set on the MCF. You will not see any Resource Adapter specific trace entries, WebSphere trace will work if it is enabled. |
Action | Check that there are no other exceptions in the FFDC logs - the other exceptions may indicate a problem with the ManagedConnectionFactory or in getting the correct PrintWriter. If there are no other exceptions, contact support for the resource adapter. |
Explanation | Usually this means an internal error has occurred. The DataSource MBean will not have all the information you may expect (some operations will return bad values). However the DataSource runtime object is still useable and this warning will not adversely effect any applications. |
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 internal error has occurred. However the error is non-terminal, the ConnectionFactory or DataSource will work correctly. An MBean might not be created for this object, and even if one is it may contain bad data. This can also effect PMI - it might not be able to link to the MBean. |
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 internal error has occurred and the J2C Runtime was unable to create an MBean. The ConnectionFactory or DataSource will still function, however statistics cannot be accessed through an MBean, this also effects the PMI link to the MBean. |
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 internal error may have occurred, but most likely a direct JNDI lookup was done on a ConnectionFactory or DataSource. Processing continues using the default resource-ref values. |
Action | None. |
Explanation | This is an informational message. |
Action | None. |
Explanation | This is an informational message. |
Action | None. |
Explanation | The XML document is not formed correctly. |
Action | See the XML document for possible errors. |
Explanation | The XML document is not formed correctly. |
Action | See the XML document for possible errors. |
Explanation | A ConnectionWaitTimeout of 0 indicates infinite wait time, this thread will sleep until a connection is freed. |
Action | None. |
Explanation | An Exception occurred while trying to start a ResourceAdapter. This has occurred either during the reading of the configuration properties or during the actual call to start the ResourceAdapter class for this Resource Adapter. Check the exception and other error messages for more details. |
Action | Take action based on the exception or the other errors in the log. |
Explanation | This message indicates a problem while attempting to create an ActivationSpec object. There are several possible reasons for this problem. The most common reason is that the runtime couldn't find the appropriate class for the ActivationSpec via the current class loader. This could also be related to an invalid XML definition for the Resource Adapter. |
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 J2C Authentication Data Entry corresponding to the Component-managed Authentication Alias was expected but not found. |
Action | Define a J2C Authentication Data Entry under Security > JAAS Configuration in the WebSphere Administrative console, and choose this for Component-managed authentication alias on the Connection Factory or Data Source configuration. |
Explanation | A set method does not exist for listed <activation-config-property> on the ActivationSpec class of the given resource adapter. This could be caused by: (1) the application's MDB was mapped to the wrong ActivationSpec class or MessageListenerType, (2) there is a case mismatch between the <activation-config-property> name and the actual method, or (3) the application assembler entered a non-existing property. |
Action | Redeploy the application and correct any mapping mistake, or reassemble the application with valid <activation-config-property>s. |
Explanation | The method caught an exception which is most likely due to a WebSphere internal error. |
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 | The ResourceAdapter marks certain ActivationSpec properties as required and the value has not been supplied. These properties can be set from two different spots. The first is when you create an ActivationSpec configuration object under the installed ResourceAdapter. The second comes from the application itself as an <activation-config-property> and may be modified using the application assembly tool. |
Action | Supply the required values on either the ActivationSpec which is configured on the installed ResourceAdapter, or in an <activation-config-property> within the application. |
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 | The BootstrapContext was unable to return a WorkManager to the ResourceAdapter due to a problem configuring the WorkManager. |
Action | See the exception and previous log entries for more details. |
Explanation | The BootstrapContext was unable to return an XATerminator to the ResourceAdapter due to an exception. |
Action | See the exception and previous log entries for more details. |
Explanation | The ResourceAdapter has rejected the ActivationSpec as it is currently configured. |
Action | See the exception from the ResourceAdapter for more details. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the exception and other log entries for more details. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the exception and other log entries for more details. |
Explanation | Message Endpoints that are stopped or deactivated cannot be paused. |
Action | Modify the application to verify the Message Endpoint is active before invoking the pause operation. |
Explanation | The transaction service was unable to de-register an ActivationSpec at this time. This may be due to outstanding transactional work involving this ActivationSpec and may be a transient error. |
Action | Restarting the server should clear up any outstanding transactions. If the error persists, contact customer service. |
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 | The component is using container-managed authentication, but no mappingConfigAlias was specified. DefaultPrincipalMapping will be used. |
Action | This is likely a scripting error with {0} or its corresponding CMPConnectorFactory. |
Explanation | The server was unable to start a ResourceAdapter. |
Action | See exception and previous log entries for more information. |
Explanation | The JNDI lookup of the Destination failed. This could be caused by one of the following conditions: 1) the Destination referred to by the specified JNDI name has not been configured, 2) the JNDI Name is incorrect, or 3) some other problem exists as indicated by the exception. |
Action | Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter. |
Explanation | The JNDI lookup of the Destination failed. This could be caused by one of the following conditions: 1) the Destination referred to by the specified JNDI name has not been configured, 2) the JNDI Name is incorrect, or 3) some other problem exists as indicated by the exception. |
Action | Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter. |
Explanation | A CONNECTION_CLOSED ConnectionEvent is required by the J2EE Connector Architecture to contain a valid ConnectionHandle associated with the ManagedConnection instance. |
Action | The ResourceAdapter must use ConnectionEvent.setConnectionHandle() to supply the ConnectionHandle in the CONNECTION_CLOSED ConnectionEvent. |
Explanation | UserName and/or Password assigned to the Authentication Alias being used by the MDB is not valid. |
Action | Make sure that authentication alias has been properly configured and assigned to either the ActivationSpec configuration, or as specified as part of the MDB deployment step. |
Explanation | The given ResourceAdapter could not be found to perform the operation. This may be due to the fact it has already been shut down. |
Action | Make sure the MBean you are using is still valid. |
Explanation | The given ResourceAdapter could not be found or was not in a started state so the message endpoint could not be activated. This may be due to the fact it has already been shut down. |
Action | Make sure the ResourceAdapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid ResourceAdapter. |
Explanation | The given ResourceAdapter could not be found or was not in a started state so the message endpoint could not be deactivated. |
Action | Make sure the ResourceAdapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid ResourceAdapter. Also, applications must be stopped before the Resource Adapter is stopped. |
Explanation | The requested ResourceAdapter was found but was not in a started state. A ResourceAdapter is not usable in a stopped state. This may be due to the fact it has stopped by an MBean request, the application server may be shutting down, or if the ResourceAdapter is embedded within an application, the application has been stopped. |
Action | Make sure the ResourceAdapter is started. |
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 | The JNDI lookup of the Authentication Alias assign to the ActivationSpec in use by the given MDB did not complete successfully. |
Action | Make sure that authentication alias has been properly configured and assigned to either the ActivationSpec configuration, or as specified as part of the MDB deployment step. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the exception and other log entries for more details. |
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 | 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 | The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored. |
Action | Take appropriate action based on the exception text. |
Explanation | The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored. |
Action | Take appropriate action based on the exception text. |
Explanation | You do not need to supply a destination JNDI name. |
Action | Do not supply a destination JNDI name. |
Explanation | The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored. |
Action | Supply a destination JNDI name which refers to an AdminObject which implements the javax.jms.Destination interface. |
Explanation | The JNDI lookup of the Destination failed. This could be caused by one of the following conditions: 1) the Destination referred to by the specified JNDI name has not been configured, 2) the JNDI Name is incorrect, or 3) some other problem exists as indicated by the exception. |
Action | Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter. |
Explanation | The internal data structures have not been initialized for this connection factory. Some MBean operations are not possible in this state. |
Action | Attempt the intended operation after the connection factory has been accessed. |
Explanation | It is against the programming model to use a connection handle in a component instance that is different from the component instance which first created the connection. Components consist of Servlets, JSP's, EJB's, MDB's, and ASYNC Beans. |
Action | Stop making the connection handle available to any component instance other than the one which did the first getConnection call. |
Explanation | It is against the programming model to concurrently access a connection handle from multiple threads. |
Action | Make sure your code does not share a connection handle by multiple threads. A common cause for this error is the storage of the connection in a Static variable. Additionally, since all servlet instance variable behave the same as static variables, another common cause is the storage of a connection in a servlet instance variable. |
Explanation | This message indicates a problem while attempting to create a ConnectionFactory object because it caught an Exception from the ManagedConnectionFactory. |
Action | Check the exception and contact support for the ResourceAdapter which is throwing the exception. |
Explanation | This indicates that the connection manager was unable to make the requested change to the configuration variable at this time. |
Action | Try again. |
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 | The J2C runtime was unable to find the given class. |
Action | Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shutdown. |
Explanation | This is an internal system error and is probably caused by an earlier failure. |
Action | Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM 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 | Some resource adapters can only tolerate one instance of their ResourceAdapter class to be instantiated within a JVM. If you have more than one such resource adapter instance configured to run on a given server, you will get this message. This can happen for any of the following reasons: 1) You configured the same resource adapter instance at more then one scope (i.e. cell, node, or server); 2) You deployed more than one Application which embeds the same resource adapter with a configuration such that the ResouceAdapter class says that the two instances are equal, or 3) you have one stand alone resource adapter deployed in a server and an application embeds the same resource adapter on the same server with a configuration such that the ResourceAdapter class indicates that both are equal. |
Action | Change you configuration such that the two resource adapters are not deployed to the same server. |
Explanation | An exception occurred while attempting to stop a ResourceAdapter. |
Action | Take appropriate action based on the exception text. |
Explanation | During de-serialization of an object, an expected field was not found. This is most likely due to the fact that the object is being de-serialized by a different version of the class than the one that serialized it. |
Action | This warning indicates a potential problem, but no user action is necessary unless further errors arise. |
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 | Configuration properties of a Resource Adapter or Activation Spec override their corresponding introspected properties, unless the type does not match. |
Action | Check the type of the config property. |
Explanation | User-defined properties of a Resource Adapter or Activation Spec override their corresponding introspected and config properties, unless the type does not match. |
Action | Check the type of the user-defined config property. |
Explanation | Required property {0} was missing from activation spec. |
Action | Supply a correct {0} property. |
Explanation | An application attempted to lookup a connection factory associated with another application's embedded resource adapter. |
Action | The application should use a connection factory associated with its own resource adapter or use a connection factory associated with a standalone resource adapter. |
Explanation | The property was not found via introspection on the underlying bean. |
Action | Compare this property in the ra.xml and the java bean. |
Explanation | A call to method getInvalidConnections returned a resource exception. |
Action | Contact the resource adapter provider. |
Explanation | This connections resource adapter does not support the pretest connection function. |
Action | Reconfigure pretest connection to false for this resource adapter. |
Explanation | This are either no or more than one ConnectionDefinitions defined. This implies an internal XML formatting error. |
Action | Make sure there is only a single ConnectionDefinition defined. |
Explanation | A pool properties value has been changed. |
Action | None. |
Explanation | The thread pool that was specified for the resource adapter must first be created or configured correctly using system administration before it can be used by a resource adapter. |
Action | Create the missing thread pool or fix the configuration for the thread pool. |
Explanation | The thread pool that was specified for the resource adapter has not been configured. |
Action | Configure the missing thread pool. |
Explanation | Application ear file has supplied an non-existed <activation-config-property>. |
Action | Fix the application descriptor. |
Explanation | An internal error has occurred while attempting to process the lazyEnlist method. |
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 | Normally this indicates an error with the resource adapter implementation. The resource adapter called lazyEnlist with a null ManagedConnection. |
Action | Contact the resource adapter provider for assistance. 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 | Avoid using the fully qualified names of resources when looking up resources through Java Naming Directory Interface (JNDI). The J2EE programming model recommends the use of resource references and the local JNDI java:comp/env context. |
Action | Modify the application to use the preferred J2EE programming model with resource references and the local JNDI java:comp/env context. |
Explanation | Normally this 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 which may include the line numbers of the code in question - this can help to narrow down the search. If the line numbers are not found (the code has been jit compiled or otherwise obfuscated), you may want to instrument the code with System.out.println() statements to help find the problem area. If the problem cannot be found contact support. |
Explanation | No configuration properties were supplied for the ActivationSpec. This may be normal, however, if a value is required not having a value could cause a failure. |
Action | If a value is required please supply one. |
Explanation | There was a mismatch between the configured isEnableHASupport boolean and the HACapability. Processing continues with HA disabled. |
Action | Make sure the Resource adapter is configured correctly and implements the getHACapability() method and has the isEnabledHASupport property. |
Explanation | Normally this indicates an unsupported setting. HACapability greater than 1 (one) is not supported. |
Action | Make sure the Resource adapter is configured with HACapability of 0 or 1. |
Explanation | Normally this indicates a suspend/resume operation was attempted while HA is enabled. Only outbound portions of the RA will be suspended or resumed. |
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 | No value was supplied for the [activation-config-property]. This may be normal. If a value is required, not having a value could cause a failure. |
Action | If a value is required please supply one. |
Explanation | The value provided for the custom property WAS_EndpointInitialState is not valid. Hence this property will be ignored. |
Action | Use the administrative console or the wsadmin tool to provide a valid value for the custom property [ACTIVE or INACTIVE]. |
Explanation | If this message is logged it means that the 'connErrorAlert' has been enabled for this ConnectionFactory or DataSource. The configuration has optional parameters for indicating a time interval and a threshold for the alert such that if the number of connection errors observed by the ConnectionFactory or DataSoure during the time interval exceeds the threshold the alert is issued. |
Action | If you believe that the frequency of connection errors is unexpectedly excessive then you should investigate the root cause of connection errors. The first place to look would be in the error log. |
Explanation | You have configured the monitoring of individual connections for low usage efficiency. Efficiency is measured from the time the connection is gotten to the time it is released for unshareable connections, and the from the time it is gotten to the time the sharing boundary ends (typically the end of a transaction or component method). The usage efficiency is the amount of time the connection is used to interact with the back end divided by the total amount of time the connection has been held (expressed as a percent). |
Action | If the efficiency is lower than what you expect you should look at your application to determine why. |
Explanation | You have configured the monitoring of your DataSource/ConnectionFactory for low average connection usage efficiency. The usage efficiency is total amount of time the connections are used to interact with the back end divided by the total amount of time the connections have been held average over the number of connections at any point in time in the pool and expressed as a percent. |
Action | If the efficiency is lower than what you expect you should look at your application to determine why. You may also want to configure the Connection Low Efficiency Alert with callstack capture enabled to further isolate specific application usage which are inefficient. |
Explanation | DataSources and ConnectionFactories can be configured to limit the rate at which new connections are created based on configuration thresholds. If the surge feature has been configured and this alert is enabled, this message indicates that you have entered the surge throttling mode whereby the connection creation rate is governed by the surge configuration parameters. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in surge mode you may want to check to see if the configuration parameters are reasonable or if there is some other underlying cause which needs to be investigated. |
Explanation | DataSources and ConnectionFactories can be configured to decide if operations to the back end are not responding in a timely manor (they are hung) based on configuration thresholds. Once hung mode has been entered the connection manager will block all requests for new connections until it detects that requests to the back end are responding reasonably again. If the hang detection has been configured and this alert is enabled, this message indicates that you have entered the hung connection blocking state whereby new connection creation is not allowed. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if the configuration parameters are reasonable or if there is some other underlying with the back end you are trying to communicate with. |
Explanation | DataSources and ConnectionFactories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can get a functioning connection. If the pre-testing of connections has been configured and this alert is enabled, this message indicates that you have entered the pretest connection blocking state whereby new connection creation is not allowed. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if there is an underlying problem with the back end you are trying to communicate with. |
Explanation | ConnectionFactorys or DataSources can be configured to wait a certain amount of time for a connection to become amiable. If this time is exceeded a ConnectionWaitTimeoutException is issue. This alert can be configure to count the number of ConnectionWaitTimeoutExceptions over a given interval and raise an alert if the threshold is exceeded. |
Action | Check the documentation for ConnectionWaitTimeoutExceptions for more details. |
Explanation | When a ConnectionFactory or DataSource has reached its maxConnection limit and a request comes in for a new connection and it has connections available in its free pool but none of these connections match the needed matching criteria of the request, one of these connections will be destroyed (this is the victim) so that a new connection can be created. This alert notifies you if the rate at which this is occurring is exceeding your configured threshold. |
Action | Excessive claiming of connections is detrimental to performance and may indicate a problem with the whey the application is using connections, however, depending on the usage scenario this may be normal. |
Explanation | A ConnectionFactory or DataSource has a maximum available load equal to all of its connections in continuous use (this would equal its current maxConnections setting). The pool load at any point in time is the number of connections in use plus any threads waiting for a connection. The average pool load is time averaged value of the pool load over the interval configured by this alert. This alert tells you that you have exceeded that pool average load for the last interval. |
Action | Excessive load on the pool may be caused by a number of factors: maxConnnections setting is too low; connection percent efficiency is too low thus causing poor connection utilization; demand is outstripping capacity; etc. Investigate and make appropriate changes. |
Explanation | Unexpected nesting of LTC can have an undesirable side affect of tying up more connections then the user expects. This alert can help detect such situations and provide information that will help with pinpointing the problem. |
Action | For more information consult the documentation. |
Explanation | Any single requesting thread which ties up multiple connections can unexpectedly contribute to rapid pool starvation or inefficient use of connection resources. This alert can help detect such situations and provide information that will help with pinpointing the problem. |
Action | For more information consult the documentation. |
Explanation | When applications manage the interaction with the back end, having two connections to a single managed connection can cause data integrity problems since no one owner is in charge of the commit or rollback calls. This is not allow. If this is attempted, a second managed connection will be returned. If this is unexpected it may caused data integrity problems. I may also cause unexpected additional connections to be used. This alert can help detect such situations and provide information that will help with pinpointing the problem. |
Action | For more information consult the documentation on connection sharing rules for LTCs. |
Explanation | DataSources and ConnectionFactories can be configured to limit the rate at which new connections are created based on configuration thresholds. If the surge feature has been configured and this alert is disabled, this message indicates that you have exited the surge throttling mode whereby the connection creation rate is governed by the surge configuration parameters. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in surge mode you may want to check to see if the configuration parameters are reasonable or if there is some other underlying cause which needs to be investigated. |
Explanation | DataSources and ConnectionFactories can be configured to decide if operations to the back end are not responding in a timely manor (they are hung) based on configuration thresholds. Once hung mode has been entered the connection manager will block all requests for new connections until it detects that requests to the back end are responding reasonably again. If the hang detection has been configured and this alert is enabled, this message indicates that you have exited the hung connection blocking state whereby new connection creation is not allowed. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if the configuration parameters are reasonable or if there is some other underlying with the back end you are trying to communicate with. |
Explanation | DataSources and ConnectionFactories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can get a functioning connection. If the pre-testing of connections has been configured and this alert is enabled, this message indicates that you have exited the pretest connection blocking state whereby new connection creation is not allowed. |
Action | If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if there is an underlying problem with the back end you are trying to communicate with. |
Explanation | Message Endpoints that are activated or stopped cannot be resumed. |
Action | Modify the application to verify the Message Endpoint is inactive before invoking the resume operation. |
Explanation | Message Endpoints that are stopped do not have runtime JMS Properties. |
Action | Modify the application to verify the Message Endpoint is not stopped before invoking the getJMSProperties() method. |
Explanation | The Message Endpoint exists and is enabled to handle incoming messages. |
Action | None. |
Explanation | The Message Endpoint exists and is disabled from handling incoming messages. |
Action | None. |
Explanation | Message Endpoints stop (expire) when their host applications or Resource Adapters stop. Once a Message Endpoint has stopped, getStatus() is the only method supported by its MBean; all other methods will throw an IllegalStateException. |
Action | Restart the application hosting the Message Endpoint and obtain a new MBean reference in order to control the Message Endpoint. |
Explanation | The HA Manager controls the activation of inbound messaging for Resource Adapters having enabled HA Capabilities. The Message Endpoints may be paused and resumed after the HA Manager activates inbound messaging on the Resource Adapter. |
Action | Avoid pausing or resuming Message Endpoints that are not yet activated by the HA Manager. |
Explanation | The message endpoint exists, but has been disabled from handling incoming messages by setting the custom property WAS_EndpointInitialState to INACTIVE. |
Action | Activate the endpoint by invoking the resume operation on the J2CMessageEndpoint MBean. |
Explanation | The attempt to reserve an MCWrapper failed. |
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 | The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool. |
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/. |