WLMKEY_ATTEMPTING_TO_CONTACT_BACKUP_CLUSTER=WWLM0073I: Attempting to contact backup cluster using domain boot strap information: cluster {0} host {1} port {2}. 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. Look for message WWLM0074I in the log file. NLSKEY_UNABLE_TO_ACCESS_REQUEST=WWLM1009E: Method {0} was unable to access the servlet request object. {1} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_UPDATE_ERROR=WWLM0066W: An error was encountered attempting to update cluster {0} with information from cluster {1}. 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. No action is required. The problem should correct itself. WLMKEY_ACTIVATED_CLUSTER_MBEAN_NOT_FOUND=WWLM0053W: The Cluster MBean for cluster {0} was not found. {1} A cluster managed bean (MBean) was activated, but a query could not find it. 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/ . WLMKEY_CLUSTER_MEMBER_STOP_FAILED=WWLM0059W: Cluster member {0} could not be stopped. {1} A cluster member cannot be stopped. Either the cluster member could not be contacted, or the cluster member is already stopped. 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. NLSKEY_UNABLE_TO_PARSE_REQUEST=WWLM1011E: Method {0} was unable to parse the servlet request XML. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . NLSKEY_POST_LOCAL=WWLM0087I: The workload management component is configured in local posting mode. This configuration prevents workload management cluster data from being propagated outside of this JVM and should be used only when distributed workload management services are not required. If you want to enable full workload management behavior, ensure the cell level custom property IBM_CLUSTER_WLM_POST_LOCAL is set to false, or remove the custom property from the cell. WLMKEY_UNABLE_TO_RETRY_GET_SERVERGROUP=WWLM0024E: [Interop] Could not retry call to retrieve server group information. {0} [Interop]Workload management cannot obtain the server group information from the ADMIN server that was running on a previous version of the product. [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. NLSKEY_UNABLE_TO_INSTALL_DWLM_APP=WWLM1004W: Errors have been encountered attempting to install the dWLM Application to cluster {0}. During the installation of the dWLM application, an error occurred that prevented the dWLM application from being installed. Make sure that the wlmservlet.ear file is located in the <install root>/installableApps directory for the deployment manager. WLMKEY_SERVER_MARKED_AVAILABLE=WWLM0072W: Cluster member {0} was previously determined to be unreachable from this process but now the member is reachable and has been marked usable for future requests to the cluster. Requests can now be sent to this cluster member. No action is required. WLMKEY_IMPROPER_CUSTOM_PROPERTY_VALUE=WWLM0082W: The custom property {0} was set to have a value of {1}. Note that this value is outside the recommended range of {2} for this property. The value of the custom property is outside the recommended range. Ensure that the value was entered as intended, refer to the WLMConstants javadoc if necessary to determine if the value entered is appropriate. NLSKEY_UNABLE_TO_ACTIVATE_CLUSTER_MBEAN=WWLM1003W: Unable to activate the {0} Cluster MBean. {1} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_SERVER_MARKED_UNUSABLE=WWLM0061W: An error was encountered sending a request to cluster member {0} and that member has been marked unusable for future requests to the cluster {1}, because of exception: {2} A cluster member has been marked unusable for normal operational reasons, such as a ripple start. 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.. WLMKEY_NOTIFICATION_ERROR=WWLM0056E: Unable to register for node agent notifications. {0} 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. 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/ . WLMKEY_UNABLE_TO_ACTIVATE_CLUSTER_MBEAN=WWLM0052W: Unable to activate the {0} Cluster MBean. {1} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_LSD_MARKED_UNUSABLE=WWLM0063W: An error was encountered attempting to use the Location Service Daemon {0} to resolve an object reference for host:port {1} and has been marked unusable for future requests to that cluster. A Location Service Daemon has been marked unusable because the node agent is either unusable or cannot be reached. 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. NLSKEY_CANNOT_FIND_XML_ATTRIBUTE=WWLM1012E: Method {0} was unable to find {1} attribute in servlet request XML.{2} {3} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_WLC_REGISTRATION_UPDATE=WWLM0055I: Control for cluster {0} has changed. Prior controller: {1}. New controller: {2}. A workload controller has registered to control the cluster. This workload controller replaces the previously registered controller. No user action is required. NLSKEY_REQUEST_NUMBER_FORMAT_EXCEPTION=WWLM1013E: Method {0} was unable to convert {1} value {2} to a number. {3} {4} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_RIPPLESTART_TIMEOUT=WWLM0083W: During Ripplestart for cluster {0} the {1} operation exceeded the time-out of {2} milliseconds for member {3} on node {4}. The stop or start operation on a member could not be completed in the allotted time. Determine the reason why a member fails to stop or start in the allotted time or increase the time-out by updating the IBM_CLUSTER_RIPPLESTART_NOTIFICATION_TIMEOUT custom property. WLMKEY_UNEXPECTED_EXCEPTION=WWLM0028E: Method {0} encountered an unexpected exception. {1} This exception is unexpected. The cause is not immediately known. 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/ . NLSKEY_UNABLE_TO_SEND_RESPONSE=WWLM1007E: Method {0} was unable to send response to client. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_COMMAND_INVALID_TRANSACTION_LOG_RECOVERY_VALUE=WWLM0079I: Received {0} for transactionLogRecovery. The value must be either be enabled or disabled. transactionLogRecovery must either be enabled or disabled. Correct the transactionLogRecovery value. WLMKEY_SERVER_MARKED_UNAVAILABLE=WWLM0071W: Cluster member {0} was determined to be unreachable from this process and that member has been marked unusable for future requests to the cluster {1}. 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. 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. WLMKEY_SUCCESSFULLY_CONTACTED_BACKUP_CLUSTER=WWLM0074I: Successfully connected to the backup cluster using domain boot strap information: cluster {0} host {1} port {2}. Workload management successfully connected to the backup cluster. No user action is required. WLMKEY_NO_USEABLE_PROXIES=WWLM0019W: Method {0} found no usable cluster member in the cluster member list. {1} 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. 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. WLMKEY_AFFINITY_NOT_FOUND=WWLM0022E: Cannot find an affinity object with ID {0} in the {1} method. Affinity was unexpectedly removed. 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/ . WLMKEY_CLUSTER_MBEAN_SETUNAVAILABE=WWLM0086I: The {1} member on the {2} node is set to the unavailable state for the {0} cluster. This message is sent when the setUnavailable method on the Cluster MBean has been invoked. No action is required. WLMKEY_UNABLE_TO_UPDATE_SERVER_GROUP=WWLM0036E: An unexpected exception occurred when updating cluster {0} with new cluster information. {1} Workload management could not parse the cluster information. 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/ . NLSKEY_CANNOT_SEND_ERROR=WWLM1006W: Method {0} was unable to send error to client. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_MARKED_UNUSABLE=WWLM0064W: Errors have been encountered attempting to send a request to all members in the cluster {0} and all of the members have been marked unusable for future requests that cluster, because {1} All of the servers in a cluster have either been marked unusable, or cannot be reached. 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. WLMKEY_CANNOT_SEND_ERROR=WWLM0049W: Method {0} was unable to send error to client. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CANNOT_FIND_XML_ATTRIBUTE=WWLM0046E: Method {0} was unable to find {1} attribute in servlet request XML.{2} {3} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_SERVER_MARKED_UNUSABLE_TWOORMORETIMES=WWLM0062W: An error was encountered sending a request to cluster member {0} and that member has been marked unusable, for future requests to the cluster {1}, two or more times, because of exception: {2} A cluster member has been marked unusable two or more times when it should have been usable. 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. NLSKEY_DYNAMIC_LOAD_ERROR=WWLM1002E: The value for the key {0} in the implfactory.properties file must implement the interface {1}. The implementation classes must be contained in the implfactory.properties file because these classes are dynamically loaded. Make sure that the implementation classes for the object are contained in the implfactory.properties file. WLMKEY_COMMAND_CLUSTER_NODE_MISSING_IN_NODEGROUP=WWLM0078I: All members of the cluster {0} must exist on a node contained in the node group {1}. All nodes containing members in the cluster must also be members of the node group. Verify that all nodes in the cluster are also members of the node group. If not, correct the node group and retry the operation. WLMKEY_SERVER_UNREACHABLE_FROM_DEPLOYMENTMANAGER=WWLM0065W: An error was encountered attempting to update a cluster member {0} in cluster {1}, as it was not reachable from the deployment manager, because {2} While attempting to refresh cluster information to servers thought to be active within a cluster, the deployment manager could not reach the specified server. 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. WLMKEY_CONSOLE_OPERATION_FAILURE=WWLM0075I: operation failed because another administrative operation: This message is issued by the console. No action is required. WLMKEY_CLUSTER_OPERATION_FAILED=WWLM0060W: The operation {0} failed for cluster "{1}". {2} An administrative operation, that was being performed on a cluster, could not be completed. Check the log files to see if you can determine why the administrative operation 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. WLMKEY_COREGROUPBRIDGESERVICE_UNAVAILABLE=WWLM0080W: Server {0} on node {1} in cell {2} could not start the coregroup bridge service. Refer to other messages to discover the problems associated with the coregroup bridge service. The coregroup bridge service did not start. Refer to other messages to discover the problems associated with the coregroup bridge service. WLMKEY_CONSOLE_NO_CLUSTER_MEMBER=WWLM0077I: There are no cluster members to This message is issued by the console. No action is required. WLMKEY_NODEAGENT_NOT_STARTED=WWLM0057W: The node agent for cluster member {0} is not started. This cluster member will not be started. A cluster member cannot be started if its node agent is not running. Start the node agent for this cluster member. WLMKEY_UNABLE_TO_ACTIVATE_CLUSTERMGR_MBEAN=WWLM0051W: Unable to activate the ClusterMgr MBean. {0} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_MBEAN_SETAVAILABE=WWLM0085I: The {1} member on the {2} node is set to the available state for the {0} cluster. This message is sent when the setAvailable method on the Cluster MBean has been invoked. No action is required. WLMKEY_UNEXPECTED_EXCEPTION_READING_REQUEST=WWLM0044E: Method {0} encountered an unexpected exception while reading the servlet request object. {1} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_CUSTOM_PROPERTY_LOADED=WWLM0084I: The WLM Custom Property {0} has been configured with a value of {1}. A WLM Custom property has been configured. None, informational message only. WLMKEY_UNABLE_TO_PARSE_REQUEST=WWLM0045E: Method {0} was unable to parse the servlet request XML. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_SERVER_SIGNAL_RETRY=WWLM0067W: Client is signalled to retry a request: for a server at host: {0} on port: {1}. The request could not be transparently retried by WLM, because of exception:{2} While attempting to service a request, workload management 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. 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. NLSKEY_UNEXPECTED_EXCEPTION=WWLM1008E: Method {0} encountered an unexpected exception. {1} This exception is unexpected. The cause is not immediately known. 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/ . NLSKEY_UNEXPECTED_EXCEPTION_READING_REQUEST=WWLM1010E: Method {0} encountered an unexpected exception while reading the servlet request object. {1} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_TRANSACTION_UNAVAILABLE=WWLM0023E: No transaction available getting {0} from {1}. {2} Workload management was unable to get the transactional coordinator from the controller. 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/ . NLSKEY_CFS_UNAVAILABLE=WWLM0070E: The Channel Framework Service is unavailable. For some unexpected reason, the Channel Framework Service is not available. 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. WLMKEY_CONSOLE_IN_PROGRESS=WWLM0076I: is already in progress. This message is issued by the console. No action is required. NLSKEY_UNABLE_TO_REGISTER_WLMSERVLETLISTENER=WWLM1005W: An errors has been encountered attempting to register the dWLM application Listener to Deployment Manager. During the registration of the dWLM application listener, an error occurred that prevented the dWLM application from being installed. 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/ . WLMKEY_WLC_REGISTRATION_NEW=WWLM0054I: Cluster {0} controlled by {1}. A workload controller has registered to control the cluster. No user action required. WLMKEY_UNABLE_TO_RETRIEVE_CFENDPOINT=WWLM0069E: No CFEndPoint associated with the chain {0} will not be available for selection. The channel framework protocol notified workload 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. No action is required. WLMKEY_COULD_NOT_RESUME_TRANSACTION=WWLM0025E: Unable to resume transaction. {0} Workload management runtime suspended the specified user transaction and was not able to resume the transaction. Rollback the transaction and retry it. WLMKEY_UNABLE_TO_SEND_RESPONSE=WWLM0048E: Method {0} was unable to send response to client. {1} {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_MALFORMEDTIMEPERIODRULE=WWLM0081W: The rule with start time {0} and end time {1} is not valid and will be ignored. The rule is incorrectly configured. 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. WLMKEY_SERVER_NOT_FOUND_IN_SERVERGROUP=WWLM0001E: Could not notify {0} in the {1} method because the server was not found in the cluster. {2} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_NO_LSDSELECTOR=WWLM0050E: Method {0} was unable to find the LSDSelector. This exception is unexpected. The cause is not immediately known. 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/ . NLSKEY_HAMAMAGERFUNCTION_UNAVAILABLE=WWLM1014E: Server {1} on node {0} in cell {2} is not included in the distribution of work for the applications running in server {1}. This is because the HAManager service is not available on server {1}. Refer to other messages to discover the problems associated with the HAManager service. This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_CLUSTER_MEMBER_START_FAILED=WWLM0058E: Cluster member {0} did not start properly. {1} The specified cluster member did not start. 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. NLSKEY_UNABLE_TO_SET_PROPERTIES=WWLM1001E: An exception occurred while setting the property {0}. {1} The specified workload management property is set to an unsupported value. Change the value of the specified workload management property to a supported value. WLMKEY_UNABLE_TO_INITIALIZE_AFFINITY=WWLM0068W: Unable to initialize affinity modules, no affinity enabled. {0} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_REQUEST_NUMBER_FORMAT_EXCEPTION=WWLM0047E: Method {0} was unable to convert {1} value {2} to a number. {3} {4} This exception is unexpected. The cause is not immediately known. 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/ . WLMKEY_UNABLE_TO_ACCESS_REQUEST=WWLM0043E: Method {0} was unable to access the servlet request object. {1} This exception is unexpected. The cause is not immediately known. 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/ .