|
WebSphere WLM Client messages |
|
WWLM0001E: Could not notify {0} in the {1} method because the server was not found in the cluster. {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0002W: An exception occurred while setting Workload Management properties. {0}
Explanation:
One of the Workload Management properties was invalid.
User Response:
Make sure that the Workload Management properties are set correctly. In particular com.ibm.websphere.wlm.UnusableInterval must be valid number.
WWLM0019W: Method {0} found no usable cluster member in the cluster member list. {1}
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.
User Response:
Workload Management resumes when servers become available again. Check the availability of the cluster members or communications between the client and the cluster members.
WWLM0022E: Cannot find an affinity object with ID {0} in the {1} method.
Explanation:
Affinity was unexpectedly removed.
User Response:
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/.
WWLM0023E: No transaction available getting {0} from {1}. {2}
Explanation:
Workload Management was unable to get the transactional coordinator from the controller.
User Response:
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/.
WWLM0024E: [Interop] Could not retry call to retrieve server group information. {0}
Explanation:
[Interop]Workload Management was unable to communicate with the previous versions admin server to get the server group information.
User Response:
[Interop] Make sure the previous versions admin server is running.
WWLM0025E: Unable to resume transaction. {0}
Explanation:
Workload Management runtime suspended the user transaction and was unable to resume it.
User Response:
Rollback and retry the transaction.
WWLM0028E: Method {0} encountered an unexpected exception. {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0036E: An unexpected exception occurred when updating cluster {0} with new cluster information. {1}
Explanation:
Unable to parse cluster information.
User Response:
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/.
WWLM0043E: Method {0} was unable to access the servlet request object. {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0044E: Method {0} encountered an unexpected exception while reading the servlet request object. {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0045E: Method {0} was unable to parse the servlet request XML. {1} {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0046E: Method {0} was unable to find {1} attribute in servlet request XML.{2} {3}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0047E: Method {0} was unable to convert {1} value {2} to a number. {3} {4}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0048E: Method {0} was unable to send response to client. {1} {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0049W: Method {0} was unable to send error to client. {1} {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0050E: Method {0} was unable to find the LSDSelector.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0051W: Unable to activate the ClusterMgr MBean. {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0052W: Unable to activate the {0} Cluster MBean. {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM0053W: The Cluster MBean for cluster {0} was not found. {1}
Explanation:
A cluster MBean was activated, but a query can't find it.
User Response:
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/.
WWLM0054I: Cluster {0} controlled by {1}.
Explanation:
A workload controller has registered to control the cluster.
User Response:
No user action required.
WWLM0055I: Control for cluster {0} has changed. Prior controller: {1}. New controller: {2}.
Explanation:
A workload controller has registered to control the cluster and replaced the previously registered controller.
User Response:
No user action required.
WWLM0056E: Unable to register for node agent notifications. {0}
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.
User Response:
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/.
WWLM0057W: The node agent for cluster member {0} is not started. This cluster member will not be started.
Explanation:
A cluster member can not be started if its node agent is not running.
User Response:
Start the node agent for this cluster member.
WWLM0058E: Cluster member {0} did not start properly. {1}
Explanation:
The cluster member did not start.
User Response:
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.
WWLM0059W: Cluster member {0} could not be stopped. {1}
Explanation:
A cluster member can not be stopped. Either an error occurred trying to reach the cluster member or it is already stopped.
User Response:
Verify if the cluster member process is stopped. Stop it manually using stopserver. Check the logs for additional information.
WWLM0060W: The rippleStart function failed for cluster "{0}". {1}
Explanation:
A cluster could not be ripple started.
User Response:
Either manually restart each member in the cluster or stop the cluster and restart it.
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}
Explanation:
A cluster member that has been marked unusable for normal operational reasons (i.e. a ripple start).
User Response:
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.
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}
Explanation:
A cluster member has been marked unusable two or more times that was thought to be reachable,
User Response:
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.
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.
Explanation:
A Location Service Daemon has been marked unusable. In this case a Node Agent is either unusable or is unreachable.
User Response:
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.
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}
Explanation:
All servers in a cluster have been either marked unusable or are not reachable.
User Response:
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.
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}
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.
User Response:
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.
WWLM0066W: An error was encountered attempting to update cluster {0} with information from cluster {1}.
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.
User Response:
No action is required. The problem should correct itself.
WWLM0067W: Client is signalled to retry a request: a server request could not be transparently retried by WLM, because of exception:{0}
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.
User Response:
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.
WWLM0068W: Unable to initialize affinity modules, no affinity enabled. {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM1001E: An exception occurred while setting the property {0}. {1}
Explanation:
One of the Workload Management properties was invalid.
User Response:
Make sure that the Workload Management properties are set correctly.
WWLM1002E: The value for the key {0} in the implfactory.properties file must implement the interface {1}.
Explanation:
Some classes are dynamically loaded, the implementation classes are specified in the implfactory.properties file.
User Response:
Fix the implfactory.properties file to include the correct implementation for the object.
WWLM1003W: Unable to activate the {0} Cluster MBean. {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WWLM1004W: Errors have been encountered attempting to install the dWLM Application to cluster {0}.
WWLM1005W: An errors has been encountered attempting to register the dWLM application Listener to Deployment Manager.
WWLM1006W: Method {0} was unable to send error to client. {1} {2}
WWLM1007E: Method {0} was unable to send response to client. {1} {2}
WWLM1008E: Method {0} encountered an unexpected exception. {1}
WWLM1009E: Method {0} was unable to access the servlet request object. {1}
WWLM1010E: Method {0} encountered an unexpected exception while reading the servlet request object. {1}
WWLM1011E: Method {0} was unable to parse the servlet request XML. {1} {2}
WWLM1012E: Method {0} was unable to find {1} attribute in servlet request XML.{2} {3}
WWLM1013E: Method {0} was unable to convert {1} value {2} to a number. {3} {4}
Explanation:
During the installation of the dWLM application, an error occurred resulting in the dWLM application not being installed.
User Response:
Check that the wlmservlet.ear file is located in the
Explanation:
During the registration of the dWLM application listener, an error occurred resulting in the dWLM application listener not being installed.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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/.
Last updated:
Library |
Support |
Trademarks |
Feedback