Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Workload Management was unable to find an available cluster member in the cluster list because either they are all marked as unuseable or all of the cluster members are stopped. |
Action | Workload Management resumes when servers become available again. Check the availability of the cluster members or communications between the client and the cluster members. |
Explanation | Affinity was unexpectedly removed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Workload Management was unable to get the transactional coordinator from the controller. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | [Interop]Workload Management was unable to communicate with the previous versions admin server to get the server group information. |
Action | [Interop] Make sure the previous versions admin server is running. |
Explanation | Workload Management runtime suspended the user transaction and was unable to resume it. |
Action | Rollback and retry the transaction. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Unable to parse cluster information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A cluster MBean was activated, but a query can't find it. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A workload controller has registered to control the cluster. |
Action | No user action required. |
Explanation | A workload controller has registered to control the cluster and replaced the previously registered controller. |
Action | No user action required. |
Explanation | When registering for node agent's notifications an error occurred. When starting or stopping a cluster, the state will not progress to its desired started or stopped state. This is not an expected error. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A cluster member can not be started if its node agent is not running. |
Action | Start the node agent for this cluster member. |
Explanation | The cluster member did not start. |
Action | Check the logs for information on why the cluster member did not start. If this is a newly created cluster, verify that the configuration was synchronized to the remote nodes. If the error log indicates that the server is not found, the configuration is probably not synchronized. |
Explanation | A cluster member can not be stopped. Either an error occurred trying to reach the cluster member or it is already stopped. |
Action | Verify if the cluster member process is stopped. Stop it manually using stopserver. Check the logs for additional information. |
Explanation | A cluster could not be ripple started. |
Action | Either manually restart each member in the cluster or stop the cluster and restart it. |
Explanation | A cluster member that has been marked unusable for normal operational reasons (i.e. a ripple start). |
Action | No user action is required. However, if the problem persists, check the server status (stopped/start/running/etc). If the cluster member is down, restart and continue. If the server is still running, check that it is reachable across the network, and then check that the weights assigned to the server are in the accepted range. If the weight assigned is valid, check the server logs for possible errors. |
Explanation | A cluster member has been marked unusable two or more times that was thought to be reachable, |
Action | Check the cluster member status (stopped/start/running/etc). If the cluster member is down, restart and continue. If the cluster member is running, check that it is reachable across the network, and then check that the weights assigned to the cluster member are in the accepted range. If the weight assigned is valid, check the cluster members logs for possible errors. |
Explanation | A Location Service Daemon has been marked unusable. In this case a Node Agent is either unusable or is unreachable. |
Action | Check the status of the Node Agent. If the Node Agent had stopped for some reason, restart and continue. Else, if the Node Agent is still running, check that it is reachable across the network, and then check its logs for possible errors. |
Explanation | All servers in a cluster have been either marked unusable or are not reachable. |
Action | Check the status of the cluster servers (stopped/start/running/etc), if the cluster has stopped for some reason, restart and continue. Else, if the servers are still running, check that they are reachable across the network, and then check their SystemOut/Err for possible errors. |
Explanation | In an attempt to refresh cluster information to servers thought to be active within a cluster, we found a server is unreachable from the deployment manager. |
Action | Check the server status (stopped/start/running/etc). If the server is down, restart and continue. If the server is still running, check that it is reachable across the network, and then check the server's SystemOut/Err for possible errors. |
Explanation | During an attempt to refresh cluster information, the cluster being refreshed did not match the cluster associated with the available cluster information. The update did not occur. |
Action | No action is required. The problem should correct itself. |
Explanation | In attempting to service a request, WLM encountered a condition that would not allow the request to be transparently resubmitted. The originating exception is being caught, and a new CORBA.TRANSIENT with minor code 0x49421042 (SERVER_SIGNAL_RETRY) is being thrown to the client. |
Action | Client should, upon receipt of the CORBA.TRANSIENT minor code:SERVER_SIGNAL_RETRY, determine if the call can be retried after appropriate actions are taken by the client. If the call can be retried, the call may be successful. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The Channel Framework notified WLM that a chain was being started or stopped. When WLM attempted to retrieve the CFEndPoint from the Channel Framework Service with the given name, none could be found. |
Action | None. |
Explanation | For some unexpected reason the Channel Framework service is not available. |
Action | Check the logs for information about any failure of the Channel Framework. Stopping and restarting the process that received the error may be required. |
Explanation | Requests sent to this cluster member are not possible at this time. There can be various reasons for this state, for example, the communication path from this process to the cluster member is down. |
Action | None is probably required, requests will be routed to other members until the member becomes available. However, one may check the cluster member's status (stopped/start/running/etc). If the cluster member is down, restart and continue. If the member is still running, check that it is reachable across the network. |
Explanation | Requests can now be sent to this cluster member. |
Action | None. |
Explanation | One of the Workload Management properties was invalid. |
Action | Make sure that the Workload Management properties are set correctly. |
Explanation | Some classes are dynamically loaded, the implementation classes are specified in the implfactory.properties file. |
Action | Fix the implfactory.properties file to include the correct implementation for the object. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | During the installation of the dWLM application, an error occurred resulting in the dWLM application not being installed. |
Action | Check that the wlmservlet.ear file is located in the <install root>/installableApps directory on the Deployment Manager. |
Explanation | During the registration of the dWLM application listener, an error occurred resulting in the dWLM application listener not being installed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |