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 beans.xml file in the META-INF directory will be ignored, as CDI Managed Bean Archive Resource Adapters are not supported. |
Action | Remove the beans.xml file from the META-INF directory, as CDI Managed Bean Archive Resource Adapters are not supported. |
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. CMSG0002 |
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 | A destination type was specified that does not match the destination. |
Action | Update the server configuration or the application to specify a destination type that is consistent with the destination. |
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 | 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 hint value specified by the resource adapter is of the wrong data type. |
Action | Contact the resource adapter vendor to correct the data type of the hint. |
Explanation | An error occurred while preparing to run the work item. |
Action | Refer to the cause exception for more information. |
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 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. |
Explanation | An embedded resource adapter, and any of the resources it defines, can be accessed only from the application in which it is embedded. |
Action | Ensure that the application only looks up resources that are defined at the server scope or within the same application. |
Explanation | The endpoint activation failed because it points to an activation specification embedded in another application. |
Action | Update the server configuration so that the endpoint uses an activation specification that is either server scoped or embedded in the same application. |
Explanation | An embedded resource adapter, and any of the resources it defines, can be accessed only from the application in which it is embedded. |
Action | Modify your application or service to look up resources defined at the server scope. |
Explanation | The endpoint activation failed because it points to an activation specification embedded in another application. |
Action | Update the server configuration so that the endpoint uses an activation specification that is defined at the server scope. |
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>. |
Action | Supply the required value on the activation specification in the server configuration or in an activation-config-property entry within the application. |
Explanation | The id attribute of the resourceAdapter element can only contain the '.', '-' and '_' characters in addition to alphanumeric characters. The id specified in the configuration or derived from the module name contains unsupported characters. |
Action | Provide a valid value for the id attribute of the resourceAdapter element in the server configuration. |
Explanation | Multiple resource adapters are configured with or implicitly end up with the same unique identifier (id). |
Action | Assign unique identifiers to one or more of the resource adapters so that there is no longer a conflict. |
Explanation | The id specified in the configuration or derived from the module name is a reserved identifier. Reserved identifiers are for internal use only. |
Action | Provide an unreserved value for the id attribute of the resourceAdapter element or for the module name in the server configuration. |