| Explanation | No target server is available for the application. |
| Action | Make sure one or more servers are available to run the application. |
| Explanation | An unexpected exception occured. |
| Action | See the problem determination information on the WebSphere Application Server Support Web page: https://ibm.biz/BdztgV for possible causes of this problem. |
| Explanation | A client sent a clone ID that is not valid. The server with the clone id might have been deleted, or the client is in error. |
| Action | No action is required. |
| Explanation | A request was routed to a server, but the server does not have a listening endpoint for the desired protocol. |
| Action | Either configure a transport with the appropriate protocol for the target server, or change the protocol mapping for the proxy or on demand router (ODR). |
| Explanation | A request for an unknown virtual host was received. |
| Action | No action is required. |
| Explanation | A request for an unknown URI was received. |
| Action | No action is required. |
| Explanation | The two specified Web modules have the same virtual host and URI. The routing to one of the Web modules is disabled. |
| Action | Change the context root of one of the Web modules so that no conflict exists. |
| Explanation | Configured multi-cluster routing policy for an application, but the application has not been deployed on the cluster. |
| Action | Check your on demand router customization and deploy the appropriate application. |
| Explanation | No multi-cluster routing policy for the on demand router exists. |
| Action | No action. |
| Explanation | The configured cell and/or generic server cluster is not correct. |
| Action | Correct the configuration in the on demand router and continue. |
| Explanation | The processing of the request took longer than the threshold specified by the ExcessiveServiceTimeThresholdInMs cell custom property. |
| Action | Continue to diagnose why the application, application server, or back end resource took longer than expected. |
| Explanation | An exception occurred during processing. The message may provide additional technical data. |
| Action | Correct the condition that caused the exception, if known; consult IBM Service for help if the problem persists. |
| Explanation | An exception occurred during processing. The description indicates what the exception is, and additional technical data is optionally provided. |
| Action | Correct the condition that caused the exception, if known; consult IBM Service for help if the problem persists. |
| Explanation | Node-based ARFM is enabled. |
| Action | No action. |
| Explanation | Node-based ARFM added the first request to the queue. |
| Action | No action. |
| Explanation | Some properties do not apply to node-based ARFM. |
| Action | No action. |
| Explanation | The value set for the property is invalid. |
| Action | Set the property to a valid value and continue. |
| Explanation | Node-based ARFM is disabled. |
| Action | No action. |
| Explanation | A Node-based ARFM queue has reached the set queue limit. |
| Action | Increase the queue limit in the configuration. |
| Explanation | A host name was provided which could not be resolved to an IP address. |
| Action | Check that the host name is correct, and that it is registered in the DNS and can be resolved. |