Explanation | This 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Systems Management configuration for the resource adapter. A deployment descriptor does not exist for this resource adapter. |
Action | Check that file resources.xml exists and that it contains a [resourceProviders xmi:type="resources.j2c:J2CResourceAdapter" . . .] element. If the file does not exist, or if the file appears to be incorrect, delete it and re-create the resource adapter through the Integrated Solutions Console. |
Explanation | There is 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 and process. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Systems Management configuration of the connection factory. The properties for connection pooling do exist for the connection factory, but they are not in the right format to read and process. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Systems Management configuration of the connection factory. The properties for connection pooling do not exist for this connection factory. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There was a problem invoking a method on a deployed object. The names of these methods are determined by the name/value pairs contained in the properties of the JavaBean. These are based on the contents of the resource adapter"s ra.xml file and class annotations. Processing will continue because the default values for this property might be sufficient, or this particular property might not be required by the specified deployed object. |
Action | This error could indicate a mismatch between the resource adapter"s XML definition or class annotations and the java class provided for implementation of the JavaBean. Examine the attributes supplied by the resource adapter. It might be necessary to provide this failure notification to the provider of the resource adapter. |
Explanation | There is a missing method on a deployed object. The names of these methods are determined by the name/value pairs contained in the properties of the JavaBean. These are based on the contents of the resource adapter"s ra.xml file and class annotations. Processing will continue because the default values for this property might be sufficient, or this particular property might not be required by the specified deployed object. |
Action | This error could indicate a mismatch between the resource adapter"s XML definition or class annotations and the java class provided for implementation of the JavaBean. Examine the attributes supplied by the resource adapter. It might be necessary to provide this failure notification to the provider of the resource adapter. |
Explanation | There was an exception while attempting to create a ManagedConnectionFactory object. There are several possible reasons for this problem. The connection manager (1) could not find the appropriate class for the ManagedConnectionFactory using the context class loader, (2) could not create a TraceWriter object for the ManagedConnectionFactory, or (3) could not create the ConnectionManager object for the ManagedConnectionFactory. Any of these problems could also be related to an XML definition for the resource adapter that is not valid. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The getObjectInstance method is invoked by the JNDI lookup processing of the resource. The implementation of the JNDI lookup 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. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Reference object that was initially stored in the JNDI name space. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Reference object that was initially stored in the JNDI name space. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | A problem occured creating the ManagedConnectionFactory from the stored Reference in the JNDI name space. |
Action | Refer to the additional information that is provided to find related error messages and information from the activity.log file. |
Explanation | A problem occured 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 | Refer to the additional information that is provided to find related error messages and information from the log file. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 | There was a problem 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 | Refer to the additional information that is provided to find related error messages and information from the log file. |
Explanation | There was a problem with the resource adapter creating the desired connection factory. The exception text provides additional details on the actual problem. |
Action | If the exception text does not indicate a situation that is user controlled, collect diagnostic data and refer to the IBM support site for additional information. |
Explanation | The properties for the ManagedConnectionFactory could not be assembled because of other logged errors. This might cause problems at runtime, depending on the default values of the various properties that are provided by the resource adapter. |
Action | Check for other related messages that could further explain the specific problems with the property data. If your connections appear to work, you may ignore this message. Otherwise, attempt to follow the "User Response" sections in the other error messages. |
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 | This might be a symptom of an incorrectly hand-modified resources.xml document. Alternatively, if you are using an application with an embedded resource adapter, this might 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, check the files for any errors. If you have not edited these files, this could be an internal application server error. |
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 | The set method does not exist for this class; the connection manager expected this method to exist. The resource adapter requires this set method to be run to function properly, so the ManagedConnectionFactory is discarded. The class file for this ManagedConnectionFactory might be out of date, or there might be a miscommunication between WebSphere Systems Management and the connection manager. |
Action | Check that the class files for this resource adapter are up to date. |
Explanation | The set method could not be run. 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 | Check 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error has occurred when reading properties from the namespace. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Check the path string that failed and verify that any non-expanded variables are valid (including their case). |
Action | Fix any variables which are not valid. |
Explanation | The path for the resource adapter has not been configured correctly, or the resources.xml file (or deployment.xml file if you are using an embedded RAR file) is corrupted. |
Action | Correct the path configuration for the resource adapter or repair the XML configuration file. |
Explanation | An internal error occurred when getting a Subject. A container-managed authentication alias might not have been selected on the connection factory or data source. |
Action | Check that a valid container-managed authentication alias is specified on the connection factory or data source. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Properties for specified class are only allowed to be primitives, or one 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 | Ensure the class has implemented the appropriate property type. |
Explanation | The server could not enable transaction recovery for this resource adapter. The possible causes include: errors in the archive, class, or native paths; internal server errors. |
Action | Validate your archive, class, and native paths on the connection factory. |
Explanation | Resource adapters should be stopped only after all message endpoints have been deactivated. Message endpoints are deactivated when the application that is supplying the message endpoint is stopped. Currently, only MDB can be a message endpoint. |
Action | Stop any applications that contain message endpoints that are associated with a particular resource adapter before you stop that resource adapter. |
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 | There is no user action required. |
Explanation | An exception occurred while attempting to stop a resource adapter. |
Action | Take appropriate action based on the exception text. |
Explanation | The JNDI lookup of the activation specification failed. This could be caused by one of the following conditions: 1) the activation specification 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 | Check that the activation specification is configured for the correct resource adapter. Verify that the JNDI Name specified when deploying your MDB matches the name that was specified when creating the ActivationSpec on the resource adapter. |
Explanation | The resource adapter does not support the specified TransactionResourceRegistration setting. The J2C Runtime environment is using the default value. |
Action | There is no user action required. |
Explanation | In order to activate a message endpoint (MDB) a JNDI name to a configured activation specification must be supplied during MDB deployment. |
Action | Check that the activation specification had been configured for the resource adapter you are using. Verify that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An error occurred recreating an XA resource. The resource could not be recovered. |
Action | Check for other related messages that can further explain the problem. |
Explanation | The cleanup operation on a managed connection failed. The connection could not be cleaned up after recovery. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The destroy operation on a managed connection failed after recovery. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This is 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This is 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The resource adapter does not support the getter method as documented. |
Action | Visit the support site for the developer of the resource adapter. |
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 occurred. |
Action | This message is due to an error in the internal connection manager processing. Collect diagnostic data and visit the IBM support site for more information. |
Explanation | An internal error occurred. |
Action | This message is an internal error in the connection manager processing. Collect diagnostic data and visit the IBM support site for more information. |
Explanation | A number of connections are being held by a component. This message typically follows the exception for an unavailable resource unavailable when a getConnection request failed in the application code. |
Action | Check if one or more components are holding connections excessively. The application might not be closing connection. If a number of connections appear to be working, increase the "max pool size." |
Explanation | This might be a error associated with a hand-modified resources.xml document. Alternatively, if you are using an application with an embedded resource adapter, this might be a error associated with a hand-modified deployment.xml document. |
Action | If the resources.xml or a deployment.xml file has been modified by hand, verify that there are no errors. If you have not edited these files, this could be an internal error. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 | Processing requires the presence of a transaction in order to run the current method. The most common cause of a missing transaction context is that the transaction timed out. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 | The resource adapter does not support the specified InactiveConnectionSupport setting. |
Action | Visit the support site the developer of the resource adapter. |
Explanation | The ConnectionHandleManager caught an exception while trying to perform a handle re-association operation. This is expected behavior following a transaction time-out, but in other cases this could be an 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 do not see evidence of a transaction time-out, contact support. |
Explanation | Registration with the transaction service for the recovery of transactions for inbound messages to this resource adapter did not complete successfully. Subsequent transactions with the use inbound transactions might also fail. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | A connector property was not given a value, and it does not have a default. The set method is not called. This could be the cause of a later error. |
Action | No user action is required. |
Explanation | Shareable connections are not allowed within a boundary for local transaction containment. |
Action | The connection was made non-shareable. This might have adverse effects. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The resource adapter created an exception. This could indicate a problem with the resource adapter. |
Action | Check the exception for more information. |
Explanation | The message was not translated. |
Action | See the message text for details. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Message was not translated. |
Action | See the message text for details. |
Explanation | Message was not translated. |
Action | See the message text for details. |
Explanation | The transaction for this operation has failed, possibly due to a transaction timeout. |
Action | See messages from the transaction service for more information. |
Explanation | The MappingModule object could not be read. |
Action | See the FFDC logs for more information. |
Explanation | The attempt to create a new MCWrapper failed, causing a NullPointerException on use. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An unexpected null value was returned from ContainerComponentMetaData.getLocalTran(). |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An attempt to run an EJB component that is incompatible with the application server was detected. |
Action | Evaluate the EJB version and CMP version that is supported by the EJB component. Correct any potential problems and redeploy the components. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The RA miscellaneous configuration object could not be read. |
Action | See the FFDC logs for more information on the error. |
Explanation | An attempt to run an EJB component that is incompatible with the application server. |
Action | Evaluate the EJB version supported by the EJB component, correct any errors that might be present, and redeploy the component. |
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 | The authentication mechanism must be one of those specified in the element [authentication-mechanism-type] in the resource adapter"s ra.xml file. |
Action | Use the administrative console to specify an authentication mechanism that is supported by the resource adapter. |
Explanation | This might be a symptom of a hand-modified resources.xml document. A subject might contain null credentials, or the resource adapter mightnot accept this subject. |
Action | Use the administrative console to specify an authentication mechanism that is supported by the resource adapter. If the resource adapter does not support any authentication mechanism, choose "None." |
Explanation | 5.0 Data sources are only supported for WebModules with servlet level 2.3. |
Action | Evaluate whether the servlet in question can be migrated to level 2.3. If so, migrate the application and redeploy it. If it cannot be migrated, the servlet must use a Websphere Application Server 4.0 data source. |
Explanation | The component is accessing the connection factory or data source with res-auth=Application, but no user name or password is available. This might result in an allocateConnection failure. |
Action | If a valid user name and password in the ConnectionSpec is passed on the getConnection method, or if the backend resource does not require authentication, this error can be ignored. If you are experiencing problems logging in to the backend resource, use the administrative console to specify a component-managed authentication alias for the specified ConnectionFactory or DataSource. |
Explanation | An internal error has occurred. The parent MBean should be created when the connection factory or data source is bound into the namespace. |
Action | Collect diagnostic data and visit the IBM support web site for more information. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error occurred. The ObjectNames that were used on the lookup were not created. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error occurred when trying to obtain a cached instance of J2CPerf. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error has occurred. The MBeans should be created when binding the referenceable object into JNDI and during a JNDI lookup. Both ObjectNames will be set to null and the PMI Data will be created, but will not link with the MBeans. If attempting to look up resources on one server that reside on another, this may be normal behavior. Depending on timing the target server may not have created connection factory MBeans by the time the source server does the JNDI lookup of the connection factory in question. If the MBeans had been created, the PMI data will be created. If the MBeans had not been created, the PMI data will not be created, and the informational message J2CA0112W results. It is also possible that the JNDI name is configured in more than one scope, thus overriding the intended one. |
Action | If attempting to look up resources on one server that reside on another, ensure that the target server is running before doing a JNDI lookup of a connection factory or data source. |
Explanation | An internal error occurred. The MBeans will not be linked correctly. This does not effect the use of the connection factory or the data source, but it might cause an error if you are using PMI. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The component did not specify a login configuration on the resource-reference to the connection factory or data source, and no container-managed authentication alias was specified on the connection factory or data source. A Subject with empty user/pw is constructed. |
Action | In some cases, this error 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. Alternatively, use the Integrated Solutions Console or scripting tools to create the connection factory or data source 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | A properties file was not coded correctly. |
Action | Check that the root element of the XML document is correct. |
Explanation | This is an informational message. |
Action | There is no user action required. |
Explanation | The trace writer was not able to be set on the MCF. You will not see any specific trace entries for the resource adapter, but tracing for the application server will work if it is enabled. |
Action | Check that there are no other exceptions in the FFDC logs. The other exceptions might indicate a problem with the ManagedConnectionFactory or in getting the correct PrintWriter. If there are no other exceptions, visit the support web site for the resource adapter. |
Explanation | Usually this means an internal error has occurred. The MBean for the data source will not have all the information that you might expect (some operations will return bad values). The data source instance managed by the MBean is still useable, and this warning will not adversely effect any applications. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error occurred, but it is not terminal. The connection factory or the data source will work correctly. An MBean might not be created for this object, and if one is it might contain bad data. PMI data might also not be able to link to the MBean. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error occurred and the connection manager was unable to create an MBean. The connection factory or the data source will still function, however statistics cannot be accessed through an MBean. This also effects the PMI data that is linked to the MBean. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error might have occurred, but most likely a direct JNDI lookup was done on a connection factory or data source. Processing will continue using the default resource-ref values. |
Action | There is no user action required. |
Explanation | This is an informational message. |
Action | There is no user action required. |
Explanation | This is an informational message. |
Action | There is no user action required. |
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 an infinite wait time. This thread will sleep until a connection is freed. |
Action | There is no user action required. |
Explanation | An exception occurred trying to start a resource adapter. This occurred during the reading of the configuration properties or during the call to start the class for this resource adapter. |
Action | Check the exception and other error messages for more details. Take action based on the exception or the other errors in the log. |
Explanation | There was a problem attempting to create the ActivationSpec JavaBean instance. There are several possible reasons for this problem. The most common reason is that the connection manager could not find the class for the activation specification using the context class loader. This error could also be related to a resource adapter XML definition which is not valid. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 administrative console, and choose this entry for the component-managed authentication alias on the connection factory or the data source configuration. |
Explanation | A set method does not exist for listed [activation-config-property] on the ActivationSpec JavaBean 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 errors, or reassemble the application with valid [activation-config-property] values. |
Explanation | The method caught an exception that is most likely 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The resource adapter marks certain activation specification properties as required, and the value was not supplied. These properties can be set from two different places: (1) when you create an activation specification configuration object under the installed resource adapter, and (2) from the application itself as an <activation-config-property>, which may be modified using the application assembly tool. |
Action | Supply the required values on the activation specification, which is configured on the installed resource adapter, or in an [activation-config-property] entry within the application. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The BootstrapContext was unable to return a WorkManager to the resource adapter 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 resource adapter. |
Action | See the exception and previous log entries for more details. |
Explanation | The resource adapter has rejected the activation specification as it is currently configured. |
Action | See the exception text from the resource adapter 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 | Ensure that the message endpoint is activated before invoking the pause operation. If the endpoint is activated, check the exception and other log entries for more details. |
Explanation | The transaction service was unable to unregister an activation specification at this time. This might be due to outstanding transactional work involving this activation specification. This might be a transient error. |
Action | Restarting the server should clear up any outstanding transactions. If the error persists, visit the IBM support web site. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 the specified ConnectionFactory or DataSource, or its corresponding CMPConnectorFactory. |
Explanation | The server was unable to start a resource adapter. |
Action | See the 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 | Check that the destination is configured for the resource adapter that you are using. The destination can be configured as part of the activation specification configuration or during the MDB step during deployment of the application. Ensure that the specified JNDI Name matches the name specified when you create the Destination AdminObject on the resource adapter. |
Explanation | If required by the JCA specification, an annotated class must implement the specified interface. |
Action | Change the target of the annotation to implement the required interface. |
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 | The user name, password, or both assigned to the authentication alias that is being used by the MDB is not valid. |
Action | Check that the authentication alias has been properly configured and that it is assigned to either the activation specification configuration or specified as part of the MDB deployment step. |
Explanation | The given resource adapter could not be found to perform the operation. This might be because it was not started or has already been shut down. |
Action | Check that the MBean that you are using is valid. |
Explanation | The given resource adapter could not be found or was not in a started state, so the message endpoint could not be activated. |
Action | Check that the resource adapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid resource adapter. |
Explanation | The given resource adapter could not be found or was not in a started state. The message endpoint could not be deactivated. |
Action | Check that the resource adapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid resource adapter. Also, applications must be stopped before the resource adapter is stopped. |
Explanation | The requested resource adapter was found, but it was not in a started state. This might be because it was stopped by an MBean request, the application server might be shutting down, or the resource adapter might be embedded within an application that has stopped. A resource adapter is not usable in a stopped state. |
Action | Check that the resource adapter is started. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The activation specification in use by the given MDB had an authentication alias which failed to return a valid credential object. |
Action | Check that the authentication alias has been properly configured and assigned to the activation specification configuration, or 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The type of the destination property on the activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. The JNDI name will be ignored. |
Action | Take appropriate action based on the exception text. |
Explanation | The type of the destination property on the activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. 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 activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. The JNDI name will be ignored. |
Action | Supply a destination JNDI name that refers to an adminstered object class that 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 not correct, or (3) some other problem exists that is indicated by the exception. |
Action | Check that the destination had been configured for the resource adapter that is in use. The destination can be configured as part of the activation specification configuration or during the MDB step during application deployment. Ensure that the JNDI name that is specified matches the name that is specified when creating the destination administered object on the resource adapter. |
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 a programming model violation to use a connection handle in a component instance that is different from the component instance that first created the connection. Components consist of servlets, JSPs, EJBs, MDBs, and asynchronous Beans. |
Action | Do not make the connection handle available to any component instance that did not implement the getConnection call. |
Explanation | It is a programming model violation to concurrently access a connection handle from multiple threads. |
Action | Do 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 indicates a problem while attempting to create a connection factory instance because it caught an Exception from the ManagedConnectionFactory. |
Action | Check the exception and contact support for the resource adapter which is throwing the exception. |
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 | 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | At transaction timeout, the transaction manager immediately aborts JDBC connections that are associated with XAResource interfaces that are enlisted with the transaction and that support JDBC version 4.1 or later. When the transaction rolls back, it distributes XAResource.end and XAResource.rollback methods to all XAResource interfaces, including any XAResource interfaces that are associated with the aborted connections. The rollback and any other subsequent attempts to reuse the aborted connection result in XAException errors, which you can ignore. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The connection was aborted by a purge connection instance. No action is required. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This message is issued when an application invokes the java.sql.Connection.abort() method with a connection that supports JDBC version 4.1 or later. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The connection manager was unable to find the given class. |
Action | Check that the associated XA resource provider is configured, and restart the server. The resource can then be unconfigured, and the server can be stopped. |
Explanation | This is an internal system error that is probably caused by a previous error. |
Action | Examine any related messages to determine the cause of the problem. If there are no related messages, or they do not help resolve the problem, visit the IBM support site. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An exception occurred while attempting to stop a resource adapter. |
Action | Take appropriate action based on the exception text. |
Explanation | A resource adapter can be configured to tolerate only one instance of their resource adapter class being instantiated within a JVM. You will receive this message if you have more than one such resource adapter instance configured to run on a given server. This can happen in one of the following circumstances: 1) You deployed more than one Application which embeds the same resource adapter; 2) you have one stand-alone resource adapter deployed in a server and an application embeds the same resource adapter on the same server, or 3) you installed more than one instance of the same resource adapter as stand-alone (shared by all applications). |
Action | Change your configuration such that the two resource adapters are not deployed to the same server. |
Explanation | When the multithreaded access detection option is enabled, the connection manager will detect and indicate whether the usage of a connection handle violates the JCA programming model. Specifically, the connection manager attempts to detect when a handle is used concurrently on multiple threads, and when a handle is shared within a component instance that is different from the component instance that first created the connection. Multithreaded access detection option is only available for DataSource. |
Action | Enable the multithreaded access detection option on the connection factory or data source which created the failing connection handle, restart the application, and recreate the problem. If the server logs or Runtime Messages facility indicates JCA programming model violations, modify the application to not make the connection handle available to any component instance that did not invoke method getConnection(), nor to any code executing on a thread that did not invoke method getConnection(). |
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 | If the connection factory had been created by a JNDI lookup, previous configuration changes do not take effect until the next server restart. |
Action | Check the accuracy of the component-managed authentication alias configured on the connection factory or data source. Re-start the server. |
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 | If you configured a data source with scripting, the relationalResourceAdapter attribute might have not been set correctly. |
Action | Check your configuration script to ensure that relationalResourceAdapter is set to "builtin_rra". |
Explanation | You cannot configure a Version 4 data source under this JDBC provider because the provider is configured to be isolated. |
Action | Set this JDBC provider to not be isolated, or configure this Version 4 data source under a JDBC provider that is not configured to be isolated. |
Explanation | If required by the JCA specification, an annotated entity must be a JavaBean class with a publicly visible, no parameter constructor and getter/setter methods for all public fields. |
Action | Correct the target of the annotation to be a JavaBean class. |
Explanation | An unrecognized field of a supported annotation was encountered while attempting to merge the annotation field values into the deployment descriptor. |
Action | Correct the annotation definition to remove the unrecognized field. |
Explanation | The interface for the administered object must be specified. |
Action | Add the interface to the annotation definition or the deployment descriptor, or change the annotated class to implement the correct interface. |
Explanation | Resource adapter must not submit a Work that implements WorkContextProvider along with a valid ExecutionContext. |
Action | Decide which context to use and either do not submit a Work that implements WorkContextProvider or use a null value for the ExecutionContext parameter in WorkManager methods that take it as argument. |
Explanation | Resource adapter provided multiple WorkContexts that implement the same WorkContext type. |
Action | Eliminate duplicates from a list of WorkContexts returned by a Work that implements WorkContextProvider before submitting the Work. |
Explanation | The WorkContext is not supported by the application server. |
Action | Do not use unsupported WorkContext when submitting a Work the implements WorkContextProvider. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The Transaction Manager cannot be loaded from the class specified in com.ibm.ws390.jta.TransactionManager system property. This will cause a subsequent failure when creating an instance of the Transaction 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The expected system property cannot be found. This may cause subsequent failures. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Only specific JavaBeans may be annotated with @ConfigProperty. |
Action | Change the location of the @ConfigProperty annotation to a supported JavaBean type or reconfigure that JavaBean to meet the specification. |
Explanation | Only a field of one of the allowable Object types (Boolean, String, Integer, Double, Byte, Short, Long, Float, or Character), or the field"s associated mutator method may be annotated with @ConfigProperty. |
Action | Change the location of the @ConfigProperty annotation to a supported field type or the mutator method of a supported field type. |
Explanation | Only a field of one of the allowable Object types (Boolean, String, Integer, Double, Byte, Short, Long, Float, or Character), or the field"s associated mutator method may be annotated with @ConfigProperty. |
Action | Change the location of the @ConfigProperty annotation to a supported field type or the mutator method of a supported field type. |
Explanation | The Java type of a field annotated with @ConfigProperty must be the same as that specified by the annotation type element. |
Action | Change the Java type of the field or the annotation element so that they are the same Java type. |
Explanation | The Java type of the parameter of a method annotated with @ConfigProperty must be the same as that specified by the annotation type element. |
Action | Change the Java type of the method parameter or the annotation element so that they are the same Java type. |
Explanation | Only a mutator method which follows the JavaBeans naming convention may be annotated with @ConfigProperty. |
Action | Change the name of the annotated mutator method to conform to the JavaBeans conventions. |
Explanation | The JCA specfication requires that if more than one class is annotated with @Connector, the deployment descriptor of the resource adapter must explicitly state the resourcedapter-class. |
Action | Annotate only one class of the resoure adapter with @Connector or specify the resourceadapter-class in the deployment descriptor of the resource adapter. |
Explanation | The JCA specification requires that a resource adapter must always return a level of transaction support whose ordinal value is equal to or less than the value specified in the metadata of the resource adapter. |
Action | To override the transaction level value specified in the metadata of the resource adapter, use a transaction level support value that is equal to or less than the metadata value. |
Explanation | The resource adapter returned a level of transaction support whose ordinal value is equal to or less than the value specified in the metadata of the resource adapter. The JCA specification requires in such case the level of transaction support to be changed a value returned by the resource adapter. |
Action | No user action is required. |
Explanation | The value of one or more configuration properties of the JavaBean instance violates the specified Bean Validation constraints. |
Action | Consult the documentation of the Resource Adapter provider to determine valid values for each configuration property indicated by the constraint violations and configure each property accordingly. |
Explanation | The feature is not implemented by the application server. |
Action | No user action is required. |
Explanation | The property is ignored because another property has higher precedence. |
Action | No user action is required. |
Explanation | An error occurred while processing the configuration. |
Action | Correct the configuration error. |
Explanation | The value of the property is not understood by WebSphere Application Server. |
Action | Correct the configuration error. |
Explanation | There is a problem with the Reference object that was initially stored in the JNDI name space. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Reference object that was initially stored in the JNDI name space. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | There is a problem with the Reference object that was initially stored in the JNDI name space. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | An internal error has occurred when reading the administered object from the namespace. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Resource adapter classes compiled with a newer version of Java than the server is running can have class incompatibility issues. |
Action | Verify that the resource adapter is intended to run on the version of Java which the application server is using. |
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 | 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | Configuration properties of a resource adapter or activation specification override their corresponding introspected properties, unless the type does not match. |
Action | Check the type of the configuration property. |
Explanation | User-defined properties of a resource adapter or an activation specification will override their corresponding introspected and configuration properties unless the type does not match. |
Action | Check the type of the user-defined configuration property. |
Explanation | The required property was missing from the activation specification. |
Action | Supply a correct property in the activation specification |
Explanation | An application attempted to lookup a connection factory that is associated with an embedded resource adapter for another application. |
Action | The application should use a connection factory that is associated with its own resource adapter or use a connection factory that is associated with a stand-alone resource adapter. |
Explanation | The property was not found through introspection on the underlying bean. |
Action | Compare this property in the ra.xml file and the JavaBean. |
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 | This connection"s resource adapter does not support the pretest connection function. |
Action | Reconfigure pretest connection to false for this resource adapter. |
Explanation | There is no connection definition that is defined, or there is more than one connection definition that is defined. There could be an internal XML formatting error. |
Action | Ensure that there is only a single connection definition defined. |
Explanation | A pool properties value has changed. |
Action | There is no user action required. |
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 | The application EAR file has supplied an [activation-config-property] that does not exist. |
Action | Fix the application descriptor. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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 | Avoid using the fully qualified names of resources when looking up resources through Java Naming Directory Interface (JNDI). The Java EE programming model recommends the use of resource references and the local JNDI java:comp/env context. |
Action | Modify the application to use the preferred Java EE programming model with resource references and the local JNDI java:comp/env context. |
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 | No configuration properties were supplied for the activation specification. This might be normal, but if a value is required then omitting a value could cause a failure. |
Action | Supply a value if one is required. |
Explanation | There was a mismatch between isEnableHASupport and the HACapability settings that are configured. Processing continued with high availability disabled. |
Action | Check that the resource adapter is configured correctly, that it implements the getHACapability() method, and it has the isEnabledHASupport property. |
Explanation | This indicates a suspend/resume operation was attempted while high availability is enabled. Only outbound portions of the resource adapter will be suspended or resumed. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The resource adapter is configured to be highly available, but the resource adapter implementation class indicates that the resource adapter does not support high availability. |
Action | Ensure that high availability is enabled for this resource adapter. To enable high availability either select Register this resource adapter with the high availability manager on the Resource adapter page of the administrator console, or include the EnableHASupport attribute on the J2CResourceAdapter configuration object in the wsadmin tool. |
Explanation | The application assembler entered a property that does not exist or one that is poorly formatted [activation-config-property]. |
Action | Reassemble the application with a [activation-config-property] that is valid. |
Explanation | No value was supplied for the [activation-config-property]. This may be normal. If a value is required, then not having a value could cause a failure. |
Action | Supply a [activation-config-property] if one is required. |
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 | The high availability capability that is supported by the resource adapter could not be obtained because an unexpected exception occurred when method returnHACapability() was invoked for the specified resource adapter. The connection manager will use the high availability setting that is already configured. |
Action | This is an exception within the resource adapter. See the support Web site for the resource adapter provider for more information. |
Explanation | The resource adapter is configured with a high availability setting that differs from the high availability capability that is supported by the resource adapter. The connection manager will use the high availability capability that is supported by the resource adapter. |
Action | Use the administrative console or the wsadmin tool to configure the resource adapter with a high availability capability that is supported by the resource adapter. |
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 | The BootstrapContext was unable to return a TransactionSynchronizationRegistry to the resource adapter due to an internal problem. The resource adapter cannot directly interact with the Transaction Manager until the problem is resolved. |
Action | Please review the FFDC log files for potential actions to resolve this problem. |
Explanation | The "connErrorAlert" has been enabled for this connection factory or data source. The configuration has optional parameters for indicating a time interval and a threshold for the alert so that the message is issued if the number of connection errors that are observed during the time interval by the connection factory or data source exceeds the threshold. |
Action | If the frequency of connection errors is excessive, investigate the root cause of connection errors, starting with the error log. |
Explanation | You have configured the monitoring of individual connections for low usage efficiency. For connections that are not shared, efficiency is measured from the time the connection is received to the time it is released. For connections that are sharable, efficiency is measured from the time it is received to the time that the sharing boundary ends, which is typically the end of a transaction or component method. The usage efficiency is the amount of time that the connection is used to interact with the backend, divided by the total amount of time the connection has been held. It is expressed as a percentage. |
Action | If the efficiency is lower than expected, examine the application for possible causes. |
Explanation | You have configured the monitoring of your data source or connection factory for low average connection usage efficiency. The usage efficiency is the total amount of time the connections are used to interact with the the backend data source, divided by the total amount of time the connections have been held, and averaged for the number of connections at any point in time in the pool. It is expressed as a percentage. |
Action | If the efficiency is lower than expected, examine the application for possible causes. You might want to configure the Connection Low Efficiency Alert with a callstack capture enabled to further isolate the specific application usage which is not efficient. |
Explanation | Data sources and connection factories 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, and the connection creation rate is governed by the surge configuration parameters. |
Action | If your connection factory or data source is spending excessive time in surge mode, you might want to verify the configuration parameters or investigate for other underlying causes. |
Explanation | Data sources and connection factories can be configured to decide if operations to the backend are not responding in a timely manner (they are hung) based on the configuration thresholds. When hung mode has been entered, the connection manager will block all requests for new connections until it detects that the requests to the backend are responding reasonably. If the hang detection has been configured and this alert is enabled, this message indicates that you have entered the hung connection blocking state, and the creation of new connections is not allowed. |
Action | If your connection factory or data source is spending excessive time in a blocked state, verify the configuration parameters or investigate for other underlying problems with the backend with which you are trying to communicate. |
Explanation | Data sources and connection factories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on the configuration thresholds. If a connection is not responding, the connection manager will block all requests for new connections until it can receive a functioning connection. If the pretesting of connections has been configured and this alert is enabled, this message indicates that you have entered the pretest connection blocking state, and the creation of new connections is not allowed. |
Action | If your connection factory or data source is spending excessive time in a blocked state, you might want to see if there is an underlying problem with the backend with which you are trying to communicate. |
Explanation | Connection factories or data sources can be configured to wait a certain amount of time for a connection to become amenable. If this time is exceeded, a ConnectionWaitTimeoutException is issued. This alert can be configured to count the number of ConnectionWaitTimeoutExceptions over a given interval and raise an alert if the threshold is exceeded. |
Action | Refer to the documentation for on ConnectionWaitTimeoutExceptions for more details. |
Explanation | When a connection factory or data source has reached the maxConnection limit and a request comes in for a new connection, and it has connections available in its free pool that do not match the necessary criteria of the request, one of these connections will be destroyed, which is called the victim, so that a new connection can be created. This alert notifies you if the rate at which this is occurring exceeds the threshold that is configured. |
Action | The excessive claiming of connections is detrimental to performance, and it might indicate a problem with how the application is using connections. In some usage scenarios this might be normal. |
Explanation | A connection factory or data source has a maximum available load that is equal to all of its connections that are in continuous use. This equals its current maxConnections setting. At any point, the pool load is the number of connections in use in addition to any threads that are waiting for a connection. The average pool load is average time of the pool load divided by the interval that is configured by this alert. This alert indicates that you have exceeded the pool average load for the last interval. |
Action | Excessive load on the pool might be caused by a number of factors, including a maxConnnections setting that is too low, a connection percent efficiency that is too low and causes poor connection utilization, or a demand that is outstripping its capacity. Investigate any possible problems and make the appropriate changes. |
Explanation | The nesting of an LTC that is not expected can have side effects of tying up more connections than expected. This alert might help in determining the problem. |
Action | Refer to the error text and support documentation for more information. |
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 interactions with the backend data source, two connections that are mapped to a single managed connection can cause data integrity problems, because there is no owner that is in charge of the commit or rollback calls. If this is attempted, the second managed connection will be returned. If this is unexpected it might cause data integrity problems, and it might cause the use of additional connections. This alert can help detect such situations and provide information that might help determine the problem. |
Action | For more information consult the documentation on the rules for sharing connection with local transaction containment. |
Explanation | Data sources and connection factories can be configured to limit the rate at which new connections are created based on the 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 connection factory or data source is spending excessive time in surge mode you might want to verify the configuration parameters or determine if there are other underlying causes. |
Explanation | Data sources and connection factories can be configured to decide if operations to the backend are not responding in a timely manner (they are hung) based on the configuration thresholds. When hung mode has been entered the connection manager will block all requests for new connections until it detects that the requests to the backend are responding reasonably. If the hang detection has been configured and this alert is enabled, this message indicates that you have exited the hung connection blocking state, and the creation of new connections is now allowed. |
Action | If your connection factory or data source is spending excessive time in a blocked state you might want to verify the configuration parameters or determine if there are other underlying problems with the backend data source. |
Explanation | Data sources and connection factories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on the configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can receive a functioning connection. If the pretesting of connections has been configured and this alert is enabled, this message indicates that you have exited the pretest connection blocking state, and the creation of new connections is now allowed. |
Action | If your connection factory or data source is spending excessive time in a blocked state, you might want to look for underlying problems with the backend with which you are trying to communicate. |
Explanation | Message endpoints that are activated or stopped cannot be resumed. |
Action | Check that the message endpoint is deactivated before invoking the resume operation. If the endpoint is deactivated, see the exception and other log entries for more details. |
Explanation | Message endpoints that are stopped do not have JMS properties at run time. |
Action | Check that the message endpoint is not stopped before invoking the getActivationProperties() method. |
Explanation | The message endpoint exists, and it is enabled to handle incoming messages. |
Action | There is no user action required. |
Explanation | The message endpoint exists, and it is disabled from handling incoming messages. |
Action | There is no user action required. |
Explanation | Message endpoints stop, or 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 that have enabled HA capability. Message endpoints can 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 using the resume method on the J2CMessageEndpoint MBean. |
Explanation | All of the resource adapters compared have compatible deployment descriptors, so they can all be updated using the same new RAR file. |
Action | None |
Explanation | One or more of the resource adapters had differing deployment descriptors. They cannot all be updated using the same RAR file. |
Action | Check the resource adapters entered and make sure that their deployment descriptor are alike, or update each resource adapter individually. |
Explanation | The version of the Resource Adapter you are updating from is specified in the message. This is an informational message only. |
Action | None |
Explanation | The version of the Resource Adapter you are updating to is specified in the message. This is an informational message only. |
Action | None |
Explanation | The new RAR file has a different ResourceAdapter implementation class. This makes the Resource Adapter and RAR incompatible for update. |
Action | None |
Explanation | The new RAR file has removed a ManagedConnectionFactory implementation, and the Resource Adapter currently has at least one configured factory that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. |
Action | To update to the new version of the Resource Adapter, delete the connection factories that use the implementation class that was removed. The configuration for these factories will be lost. |
Explanation | The new RAR file has removed an Administrative Object implementation, and the Resource Adapter currently has at least one configured AdminObject that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. |
Action | Delete the Administrative Objects that use the implementation class that was removed. The configuration for these objects will be lost. |
Explanation | The new RAR file has removed an ActivationSpec implementation, and the Resource Adapter currently has at least one configured ActivationSpec that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. |
Action | Delete the Activation Specifications that use the implementation class that was removed. The configuration for these objects will be lost. |
Explanation | An exception occurred while attempting to retrieve the lists of class names and properties for comparison. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. Make sure that you have enough access privileges to run the command. |
Explanation | The Resource Adapter comparison was unable to complete. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. |
Explanation | The command was unable to retrieve the J2C Resource Adapter from the ObjectName that was provided. |
Action | Make sure that the ObjectName entered is the correct name for a J2C Resource Adapter. Correct ObjectName syntax can be retrieved by invoking the AdminConfig.list("J2CResourceAdapter") command. |
Explanation | An unexpected exception occurred in the Update service. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. |
Explanation | All servers must be stopped on a node while updating Resource Adapters on the node. |
Action | Stop all running servers within the node. |
Explanation | The RAR file either does not exist or is not readable. |
Action | Check the path to the RAR file and make sure that there are no other processes accessing it. |
Explanation | An error occurred during the file transfer process, and the RAR file could not be sent. The update process cannot continue. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. |
Explanation | The FileTransferServer mbean was not able to be found, so the RAR file could not be sent, and the update process cannot continue. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory to see if there are any errors during server startup. |
Explanation | An exception occurred while attempting to extract the rar file to the destination location. The exception information may relate to a remote node if the update was being performed on a remote Resource Adapter. |
Action | Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for the local machine. If attempting to update a resource adapter on a remote node, check the logs on that node as well. |
Explanation | The WebSphere internal resource adapters are not updateable through the RAR Update framework. |
Action | None |
Explanation | When updating a node scoped resource adapter, an update is performed on the configuration and the binary files. A configuration save is automatically done. |
Action | Update any copies of this resource adapter if they have not been updated already. |
Explanation | When updating a resource adapter at a scope other than node scope, only a configuration update is possible. |
Action | To update the binaries, perform an update on the node scoped resource adapter that the specified resource adapter is a copy of, if it has not been updated already. |
Explanation | Resource adapters in other scopes are only copies of node scoped resource adapters. |
Action | Specify a node scoped resource adapter on the command to find copies that need to be updated. |
Explanation | The ra.xml defined a class to be loaded as a Resource Adapter, Connection Factory, Activation Specification or Admin Object, but the class could not be loaded from the rar file. This likely means the RAR file is corrupt or not valid. |
Action | Confirm that the RAR file is not corrupted, then contact your Resource Adapter vendor to make sure that the Resource Adapter provided is valid. |
Explanation | The data source was configured as non-transactional. Connection sharing applies only to connections within a transaction. |
Action | To avoid this message, modify the res-sharing-scope on resource references to the non-transactional datasource to unshareable. |
Explanation | The new RAR file has a different ManagedConnectionFactory implementation class. This makes the JCA 1.0 Resource Adapter and RAR incompatible for update. |
Action | Choose a resource adapter and RAR file which are compatible for update. |
Explanation | Updating to a RAR file that is of a different JCA spec version than the Resource Adapter is not supported. |
Action | Choose a resource adapter and RAR file which are compatible for update. |
Explanation | Updating to a RAR file that is of a different JCA spec version than the Resource Adapter is not supported. |
Action | Choose a resource adapter and RAR file which are compatible for update. |
Explanation | The command executor does not have the monitor privilege for the specified Resource Adapter configuration ID. |
Action | Obtain monitor access privileges from the system administrator for the Resource Adapter that was specified and any related resources. |
Explanation | The command executor does not have configurator privilege for a copy of the resource adapter at the given scope. Copies of a Resource Adapter depend on the given Resource Adapter"s binary files. They must all be updated, but they cannot be updated without the adequate privileges. |
Action | Run the command with a user ID that has configurator access privileges to the resource adapter(s) at the scopes that are listed. |
Explanation | Runtime errors may result from properties whose values are incompatible with their defined type. |
Action | If the default value is not desired, edit the connection factory, activation spec or admin object on which the property is found. |
Explanation | A empty or malformed property name was used as the argument for the managed bean getProperty operation. |
Action | Provide a non-empty, valid string as input for the managed bean getProperty operation. |
Explanation | The connection factory does not have a property with the specified name. Possible reasons for the error are the property name is misspelled or incorrectly capitalized, or the specified property does not apply to the connection factory being configured. |
Action | Verify the property name for the connection factory. Correct any errors in spelling or capitalization. |
Explanation | The attempt to get the value of the custom property 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The JASPIC callback handler of the WorkManager failed to populate the principal or custom credentials of the execution subject because an exception occurred while processing the JASPIC callbacks supplied by the resource adapter. |
Action | Check the FFDC and server logs that were emitted immediately prior to message J2CA0672E to determine the cause. If the cause cannot be determined from the prior error messages, collect diagnostic data and visit the IBM support web site for more information. |
Explanation | The WorkManager could not establish the principal of the caller identity because the resource adapter did not supply an instance of a JASPIC CallerPrincipalCallback necessary for the WorkManager to determine the caller principal, nor did the setupSecurityContext method of the SecurityContext implementation return an execution subject containing either an empty principal set or a principal set containing exactly one principal. |
Action | Contact the resource adapter vendor to determine why the inbound SecurityContext implementation does not satisfy the requirements necessary for the WorkManager to establish the principal of the caller identity. |
Explanation | The security context provided by the work instance contains a user name that does not exist in the realm (user registry) of the security domain associated to the application. The WorkManager obtained the invalid user name from an instance of a JASPIC CallerPrincipalCallback, whenever an instance is supplied by the resource adapter, or from the execution subject returned by method setupSecurityContext. |
Action | In case the user is from the same realm, check if the user exists in the user registry for that realm. In case the user is from a different realm, contact the resource adapter vendor since the WorkManager does not currently support users from different realms. |
Explanation | The WorkManager encountered a problem while establishing and setting up the security context for the inbound Work request. |
Action | Check the FFDC and server logs for messages J2CA0668E and J2CA0669E to determine the cause. |
Explanation | The WorkManager encountered an exception while handling the JASPIC callbacks provided by the resource adapter within the transferred security context. The exception can be of the following cases: 1) A CallerPrincipalCallback provided a principal with a user name that does not exist in the user registry. 2) A PasswordValidationCallback provided a invalid user name or password. 3) A CallerPrincipalCallback and a PasswordValidationCallback provided different user names. 4) The resource adapter provided a callback that the application server does not currently support. 5) The resource adapter provided more than one CallerPrincipalCallback. 6) The WorkManager encountered an unexpected error. |
Action | If the exception message has an error code then check the user action for that error code. If the exception is an UnsupportedCallbackException then contact the resource adapter vendor because the JASPIC callback handler of the WorkManager does not currently support the provided callback. If the exception is not any of the problems mentioned, collect diagnostic data and refer to the IBM support site for additional information. |
Explanation | The instance of the execution subject provided by the WorkManager to establish the security context of the Work instance is not the same instance obtained from the respective callback. The WorkManager ignored the subject obtained from the callback and continued to establish the security context using the instance it provided. |
Action | Contact the resource adapter vendor to modify the JASPIC callback"s getSubject() method to return the execution subject provided to the SecurityContext instance through the call to method setupSecurityContext. |
Explanation | The user name and password do not exist in the user registry of the realm that is configured for the security domain associated with the application. |
Action | Configure the resource adapter and enterprise information system to use a valid user name and password. |
Explanation | User names provided by the PasswordValidationCallback and the CallerPrincipalCallback must match. |
Action | Contact the resource adapter vendor and the system administrator to ensure that the resource adapter is designed and configured to return the same user name from the two callbacks. |
Explanation | The WorkManager expects the security context to supply exactly zero or one instance of a JASPIC CallerPrincipalCallback while establishing the security context of the work instance. |
Action | Contact the resource adapter vendor to determine why the resource adapter provides multiple instances of the CallerPrincipalCallback. |
Explanation | The resource adapter provided an authenticated JAAS subject to the application server along with one or more JASPIC callbacks. The application server supports the in-flow of authenticated JAAS subjects but only individually and not in combination with the JASPIC callbacks. |
Action | Modify the resource adapter configuration or source code to pass in either an authenticated JAAS subject or a valid combination of the JASPIC callbacks and not a combination of both. |
Explanation | The security context transferred with the work instance provided a group name that does not exist in the realm (user registry) of the security domain associated to the application. The WorkManager obtained the invalid group name from an instance of a JASPIC GroupPrincipalCallback, whenever an instance is supplied by the resource adapter. |
Action | Check if the group is from the same realm by confirming the group existence in the user registry for that realm.If the group is from a different realm, contact the resource adapter vendor because the WorkManager does not support groups from different realms. |
Explanation | The security context transferred with the work instance provided a user that does not belong to any of the groups defined in the user registry. |
Action | There is no user action required. |
Explanation | Connection Management has detected that the configured primary resource is unavailable. New requests will be routed to the configured alternate resource. |
Action | Contact your database or system administrator to determine the state of the resource in question. |
Explanation | Connection management has detected that both the configured primary and alternate resources have become unavailable. Requests cannot be rerouted. |
Action | Contact your database or system administrator to determine the state of the resources in question. |
Explanation | The configured primary or alternate resource with the specified JNDI name is now available to process new requests. |
Action | No action is required. |
Explanation | Connection management failed to connect to the specified resource. |
Action | Verify that the JNDI name provided for the resource in question is valid. Verify that the resource is operational. If connection fail-over has been configured for a resource adapter, verify that the version of the resource adapter implements the required infrastructure. |
Explanation | The WorkManager was not able to validate the user name and password that is provided by the PasswordValidationCallback because of a CustomRegistryException. This exception is caused by an invalid password or a problem with the user registry for that application realm. |
Action | If the cause of the CustomRegistryException is an invalid password, configure the resource adapter or enterprise information system to use a valid user name and password combination. Otherwise resolve the problem with the user registry. |
Explanation | The JAAS Subject that was passed in by the resource adapter does not belong to the application realm nor to a realm that is trusted by the application server. |
Action | Add the realm to the list of realms trusted by the application server, or modify the resource adapter configuration or source code to pass in a subject that belongs to the application realm or a trusted realm. |
Explanation | The Application Server supports the following three Work Context types: javax.resource.spi.work.TransactionContext, javax.resource.spi.work.SecurityContext, and javax.resource.spi.work.HintsContext. The RAR failed to deploy because a RequiredWorkContext element, declared in either the RAR deployment descriptor or an @Connector RAR meta-data annotation, specifies a Work Context type that is not supported by the Application Server. |
Action | Contact the resource adapter vendor and obtain a new RAR module that declares only required Work Context types supported by the Application Server. |
Explanation | Connection management failed to connect to the specified resource. |
Action | Verify that the JNDI name provided for the resource in question is valid. If connection fail-over and failure notification action support have been configured for a resource adapter, verify that the version of the resource adapter implements the required infrastructure. |
Explanation | Read the problem description provided as part of the message. |
Action | Verify that the operation is for the correct resource. |
Explanation | Recursive failover to multiple resources is not supported. Failover support for alternate resources that themselves have alternate resources is disabled. |
Action | Read the documentation available on resource routing for correctly enabling failover support. |
Explanation | The specified operation completed with no errors. |
Action | No action is required. |
Explanation | The Application Server supports unique Work Context types. The RAR failed to deploy because two or more RequiredWorkContext elements, declared in either the RAR deployment descriptor or an @Connector RAR metadata annotation, specify the same Work Context type. |
Action | Contact the resource adapter vendor and obtain a new RAR module containing metadata that declares only unique required Work Context types supported by the Application Server. |
Explanation | A value that is not valid was provided for the custom property being defined. The desired behavior will not take effect. |
Action | Verify that the value for the custom property being defined is valid. |
Explanation | A value that is not valid was provided for the custom property being defined. The default value is being used. |
Action | Verify that the value for the custom property being defined is valid. |
Explanation | The custom property is specific to the application server on a z/OS system. Because the system on which the application server is running is not a z/OS system, the custom property being defined is ignored. |
Action | Verify that the custom property being defined has no restrictions. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The node agent for the selected node must be running in order to update a node-scoped resource adapter using the deployment manager. |
Action | Start the node agent, and retry the update operation. |
Explanation | The object identifier of an existing resource adapter must be specified for the update operation. |
Action | Verify the object identifier of the target resource adapter, and retry the update operation. |
Explanation | The given resource adapter could not be found to perform the operation. The resource adapter might not have been installed or the wrong name is being used. |
Action | Check the resource adapter name to make sure it exists. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This indicates an unexpected problem with the BeanValidationService. The cause may not be immediately determined. |
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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The validation.xml file exists, but is unaccessible. The file may be unaccessaible due to insufficient read access priviledge on the file system, the file path is a directory, or the thread lacks permission to read the file. |
Action | Check the FFDC logs. If the file lacks read access priviledge on the file system, add the priviledge to the file. 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This exception is unexpected and indicates a problem with the BeanValidationService, the Bean Validation provider, or the RAR deployment. The cause may not be immediately determined. |
Action | Check the FFDC logs. If the problem appears due to the RAR configuration, reassmeble the RAR per the WebSphere Application Server InfoCenter and redeploy it. If the problem is due to a failure in a Bean Validation implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This exception is unexpected and indicates a problem with the ValidationFactory implementation. The cause may not be immediately determined. |
Action | Check the FFDC logs. If the symptom indicates a failure in a ValidatorFactory implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | This exception is unexpected and indicates a problem with the Validator implementation. The cause may not be immediately determined. |
Action | Check the FFDC and system logs. If the symptom indicates a failure in a Validator implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. 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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
Explanation | The supplied number of reserve pools to generate exceeds the maximum number allowed. |
Action | Change the value of numberOfPoolReserves to be less than or equal to the maximum number of reserve pools allowed. |
Explanation | This occurrs when a connection can not be obtained to a data source. |
Action | No user action required. |
Explanation | This occurrs when a connection can not be obtained to a data source. By enabling a reserve pool, the number of connection wait timeout exceptions could decrease, thus increasing performance. |
Action | No user action required. |
Explanation | To create a JMS Connection Factory, the name(jndi) property should be set in the @JMSConnectionFactoryDefinition annotation or deployment descriptor. |
Action | Set the name(jndi) property in the @JMSConnectionFactoryDefinition annotation or deployment descriptor. |
Explanation | To create a JMS Destination, the name(jndi) property should be set in the @JMSDestinationDefinition annotation or deployment descriptor. |
Action | Set the name(jndi) property in the @JMSDestinationDefinition annotation or deployment descriptor. |
Explanation | Permitted values are javax.jms.ConnectionFactory or javax.jms.QueueConnectionFactory or javax.jms.TopicConnectionFactory. |
Action | Set only the permitted values javax.jms.ConnectionFactory or javax.jms.QueueConnectionFactory or javax.jms.TopicConnectionFactory. |
Explanation | Permitted values are javax.jms.Queue or javax.jms.Topic. |
Action | Set only the permitted values are javax.jms.Queue or javax.jms.Topic. |
Explanation | The connection pools stuck mode switched from false to true or true to false. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode switched from false to true or true to false. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode might switch from false to true or true to false if time spent continues to exceed normal time spent. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode might switch from false to true or true to false if time spent continues to exceed normal time spent. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode might switch from false to true or true to false if time spent continues to exceed normal time spent. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode might switch from false to true or true to false if time spent continues to exceed normal time spent. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |
Explanation | The connection pools stuck mode might switch from false to true or true to false if time spent continues to exceed normal time spent. |
Action | If stuck mode is true, the overall health of the resource in use might be experiencing reduced performance or stopped. Review the health of the resources in use. |