Explanation | A property could not be configured on the specified resource due to an error. |
Action | Make corrections to the configuration of the specified resource and retry. |
Explanation | A property could not be found on the specified resource. |
Action | Make corrections to the configuration of the resource. |
Explanation | The type of configuration properties list is incorrect for the specified configuration element. |
Action | Update the configuration to use a configuration properties list that corresponds to the desired type of resource. |
Explanation | It is taking longer than expected to create the timer. |
Action | Verify if there is a high load on the system and consider decreasing it. |
Explanation | The attempt to start the work has timed out. |
Action | Verify if there is a high load on the system and consider decreasing it, or contact the resource adapter vendor to consider if they should increase the work timeout that they use when submitting work to the JCA work manager. |
Explanation | There is a conflict between thread context propagation specified via the WorkContextProvider and the ContextService. |
Action | Consider disabling propagation of this type of context on the ContextService of this resource adapter. |
Explanation | The resource adapter submitted work that implements WorkContextProvider and also specified an ExecutionContext. It is not valid to do both. |
Action | The resource adapter needs to be updated to choose between WorkContextProvider or ExecutionContext. |
Explanation | The resource adapter submitted work with multiple WorkContext instances of the same type. |
Action | The resource adapter needs to be updated to eliminate duplicate WorkContext instances from the WorkContextProvider. |
Explanation | The type of work context is either not supported by the application server or the feature that supports it is not enabled. |
Action | Verify if the work context type is supported. If so, verify the feature that supports it is enabled. |
Explanation | The resource adapter should return only one XA resource for the provided activation specification. |
Action | Contact the resource adapter vendor to have them correct their implementation of the getXAResources API so that it complies with the JCA specification. |
Explanation | The message endpoint has been activated, and it is ready to handle incoming messages. |
Action | No action is required. |
Explanation | The specified exception was generated during message endpoint activation. |
Action | Check the specified exception to help in determination of the cause of the error. |
Explanation | The specified exception was generated during message endpoint deactivation. |
Action | Check the specified exception to help in determination of the cause of the error. |
Explanation | The message endpoint has been deactivated, and it will no longer handle incoming messages. |
Action | No action is required. |
Explanation | The lookup of the administered object failed, possibly because (1) The administered object referred to by the specified JNDI name has not been configured, or (2) the JNDI name specified on the message driven bean is incorrect. |
Action | Verify that the administered object is configured correctly and the JNDI name specified in the server configuration matches the JNDI name specified for the message driven bean configuration. |
Explanation | The service that provides RRS transactional support is not active. Resource registration attempts with the transaction manager are rejected. |
Action | Verify that the angel process is active. Verify that MVS user ID of the Liberty process has the appropriate SAF authority to invoke the set of authorized services used for RRS integration. Verify that the feature that provides RRS integration has been configured. |