Explanation | The server has driven a native method that encountered an out of memory condition. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The server has driven a native method that called the referenced WLM service. The reason code from the WLM service indicates the reason for the failure. |
Action | Use the WLM reason code to determine the reason for the failure. |
Explanation | The server has driven a native method that called the referenced WLM service. The errno from the WLM service indicates the reason of the failure. |
Action | Use the errno value to determine the reason for the failure. |
Explanation | The server has driven a native method that failed. The target WebSphere Application Server service and return code are provided. The target WLM service with return and reason codes are also provided. |
Action | Use the return and reason codes to determine the reason for the failure. |
Explanation | The server has driven a native method to perform an authorized service call. It received a non-zero return code from the authorized Program Call (PC). |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The server has driven a native method to perform an authorized service call. It successfully completed the native WLM service invocation, but failed to register the WLM Enclave in the native registry. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The supplied token representing a WLM Enclave failed validation in the native registry. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | A native service needed to process the service call was not found. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | An attempt to drive a service call using the native service BPX4IPT failed. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The value supplied for collectionName attribute has exceeded the maximum of eighteen characters. The first eighteen characters will be used. |
Action | Update the server configuration to specify a correct value for the collectionName attribute. |
Explanation | The value supplied for collectionName attribute is either null or empty. |
Action | Update the server configuration to specify a value for the collectionName attribute. |
Explanation | A classification rule was specified containing a transaction class of greater than 8 characters. It has been truncated to be only 8 characters. |
Action | Update the associated classification rule to specify a correct value for the transactionClass attribute. |
Explanation | A classification rule was specified containing a resource string that uses wildcard characters incorrectly. The specified resource string contains too many consecutive wildcard characters. (Up to two may be used consecutively) |
Action | Update the associated classification rule to specify a valid resource string by correcting the use of wildcarding. |
Explanation | A classification rule was specified containing a resource string that uses wildcard characters incorrectly. The specified resource string contains an incorrect use of double wildcards. |
Action | Update the associated classification rule to specify a valid resource string by eliminating the incorrect use of double wildcards. |