Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Workload management was unable to find an available cluster member in the cluster list. Either all of the cluster members are marked as unuseable, or all of the cluster members are stopped. |
Action | Workload management will start to assign pending work items when a cluster member becomes available. Check the availability of the cluster members, and make sure that the client can properly communicate with the cluster members. |
Explanation | Affinity was unexpectedly removed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Workload management was unable to get the transactional coordinator from the controller. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | [Interop]Workload management cannot obtain the server group information from the ADMIN server that was running on a previous version of the product. |
Action | [Interop]Workload management could not establish communication with the ADMIN server that was running on an earlier version of the product. Make sure that the ADMIN server for the earlier version of the product is running. |
Explanation | Workload management runtime suspended the specified user transaction and was not able to resume the transaction. |
Action | Rollback the transaction and retry it. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Workload management could not parse the cluster information. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A cluster managed bean (MBean) was activated, but a query could not find it. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/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. This workload controller replaces the previously registered controller. |
Action | No user action is required. |
Explanation | An unexpected error occurred while workload management was registering for a node agent's notifications. When starting or stopping a cluster, the state does not progress to its desired started or stopped state. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A cluster member cannot be started if its node agent is not running. |
Action | Start the node agent for this cluster member. |
Explanation | The specified cluster member did not start. |
Action | Check the log files for other messages that might indicate 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 files indicate that the server was not found, the configuration is probably not synchronized. |
Explanation | A cluster member cannot be stopped. Either the cluster member could not be contacted, or the cluster member is already stopped. |
Action | If the cluster member is not already stopped, use the stopServer command to manually stop the cluster member. Check the log files for additional information. |
Explanation | An administrative operation, that was being performed on a cluster, could not be completed. |
Action | Check the log files to see if you can determine why the administrative opeation could not complete. For additional help in determining the cause of the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. After you fix the problem, retry the operation. |
Explanation | A cluster member has been marked unusable for normal operational reasons, such as a ripple start. |
Action | No user action is required. However, if the problem persists, check the cluster member's status. If the cluster member is down, restart the cluster member and continue. If the server is still running, make sure that the server is reachable across the network, and then check that the weight assigned to the server is in the accepted range. If the weight assigned is valid, check the cluster member's log files for error messages that might indicate why the cluster member was marked unusable.. |
Explanation | A cluster member has been marked unusable two or more times when it should have been usable. |
Action | Check the cluster member's status. If the cluster member is down, restart the cluster member and continue. If the server is still running, make sure that the cluster member is reachable across the network, and then check that the weight assigned to the server is in the accepted range.. If the weight assigned is valid, check the cluster member's log files for error messages that might indicate why the cluster member was marked unusable. |
Explanation | A Location Service Daemon has been marked unusable because the node agent is either unusable or cannot be reached. |
Action | Check the status of the node agent. If the node agent has stopped, restart the node agent and continue. If the node agent is still running, make sure that the node agent is reachable across the network, and then check its log files for error messages that might indicate why the node agent is unusable or cannot be reached. |
Explanation | All of the servers in a cluster have either been marked unusable, or cannot be reached. |
Action | Check the status of the cluster servers. If the cluster has stopped, restart the cluster and continue. If the servers are still running, make sure that the servers are reachable across the network, and then check their log files for error messages that might indicate why the servers are marked unusable, or cannot be reached. |
Explanation | While attempting to refresh cluster information to servers thought to be active within a cluster, the deployment manager could not reach the specified server. |
Action | Check the status of the specified server. If the server is stopped, restart the server and continue. If the server is still running, make sure that the server is reachable across the network, and then check the server's log files for error messages that might indicate why the server could not be reached. |
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 | While attempting to service a request, workload managment encountered a condition that would not allow the request to be transparently resubmitted. The originating exception was caught and a org.omg.CORBA.TRANSIENT exception with minor code 0x49421042 (SERVER_SIGNAL_RETRY) was sent to the client. |
Action | After the client takes the action indicated by the minor code, the client should decide whether to retry the call. If the call can be retried, the call might be successful. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The channel framework protocol notified workoad management (WLM) that a transport chain was being started or stopped. When WLM attempted to retrieve the channel framework endpoint from the specified transport chain, it could not find the endpont. Therefore, WLM cannot use this transport chain. |
Action | No action is required. |
Explanation | For some unexpected reason, the Channel Framework Service is not available. |
Action | Check the log files for any messages relating to the failure of the Channel Framework Service. Stopping and restarting the process that received the error might be required. |
Explanation | Requests cannot be sent to this cluster member. The communication path from this process to the cluster member might be down, or there might be some other problem that is causing this situation. |
Action | No action is required. Requests will be routed to other cluster members until this member becomes available. However, you can check the cluster member's status. If the cluster member is down, restart the member and continue. If the member is still running, make sure that the cluster member is reachable across the network. |
Explanation | Requests can now be sent to this cluster member. |
Action | No action is required. |
Explanation | If the backup cluster is successfully contacted, message WWLM0074I will be present in the log file. If message WWLM0074I is not present in the log file, the workload management could not connect to the backup cluster. |
Action | Look for message WWLM0074I in the log file. |
Explanation | Workload management successfully connected to the backup cluster. |
Action | No user action is required. |
Explanation | This message is issued by the console. |
Action | No action is required. |
Explanation | This message is issued by the console. |
Action | No action is required. |
Explanation | This message is issued by the console. |
Action | No action is required. |
Explanation | All nodes containing members in the cluster must also be members of the node group. |
Action | Verify that all nodes in the cluster are also members of the node group. If not, correct the node group and retry the operation. |
Explanation | transactionLogRecovery must either be enabled or disabled. |
Action | Correct the transactionLogRecovery value. |
Explanation | The coregroup bridge service did not start. |
Action | Refer to other messages to discover the problems associated with the coregroup bridge service. |
Explanation | The rule is incorrectly configured. |
Action | Make sure the start time is before the end time, that the hours are in the acceptable range of between 0 and 23 inclusive and that the minutes are in the acceptable range of between 0 and 59 inclusive. |
Explanation | The value of the custom property is outside the recommended range. |
Action | Ensure that the value was entered as intended, refer to the WLMConstants javadoc if necessary to determine if the value entered is appropriate. |
Explanation | The specified workload management property is set to an unsupported value. |
Action | Change the value of the specified workload management property to a supported value. |
Explanation | The implementation classes must be contained in the implfactory.properties file because these classes are dynamically loaded. |
Action | Make sure that the implementation classes for the object are contained in the implfactory.properties file. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | During the installation of the dWLM application, an error occurred that prevented the dWLM application from being installed. |
Action | Make sure that the wlmservlet.ear file is located in the <install root>/installableApps directory for the deployment manager. |
Explanation | During the registration of the dWLM application listener, an error occurred that prevented the dWLM application from being installed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |