WWLM

WWLM0001E: Could not notify {0} in the {1} method because the server was not found in the cluster. {2}
WWLM0019W: Method {0} found no usable cluster member in the cluster member list. {1}
WWLM0022E: Cannot find an affinity object with ID {0} in the {1} method.
WWLM0023E: No transaction available getting {0} from {1}. {2}
WWLM0024E: [Interop] Could not retry call to retrieve server group information. {0}
WWLM0025E: Unable to resume transaction. {0}
WWLM0028E: Method {0} encountered an unexpected exception. {1}
WWLM0036E: An unexpected exception occurred when updating cluster {0} with new cluster information. {1}
WWLM0043E: Method {0} was unable to access the servlet request object. {1}
WWLM0044E: Method {0} encountered an unexpected exception while reading the servlet request object. {1}
WWLM0045E: Method {0} was unable to parse the servlet request XML. {1} {2}
WWLM0046E: Method {0} was unable to find {1} attribute in servlet request XML.{2} {3}
WWLM0047E: Method {0} was unable to convert {1} value {2} to a number. {3} {4}
WWLM0048E: Method {0} was unable to send response to client. {1} {2}
WWLM0049W: Method {0} was unable to send error to client. {1} {2}
WWLM0050E: Method {0} was unable to find the LSDSelector.
WWLM0051W: Unable to activate the ClusterMgr MBean. {0}
WWLM0052W: Unable to activate the {0} Cluster MBean. {1}
WWLM0053W: The Cluster MBean for cluster {0} was not found. {1}
WWLM0054I: Cluster {0} controlled by {1}.
WWLM0055I: Control for cluster {0} has changed. Prior controller: {1}. New controller: {2}.
WWLM0056E: Unable to register for node agent notifications. {0}
WWLM0057W: The node agent for cluster member {0} is not started. This cluster member will not be started.
WWLM0058E: Cluster member {0} did not start properly. {1}
WWLM0059W: Cluster member {0} could not be stopped. {1}
WWLM0060W: The operation {0} failed for cluster "{1}". {2}
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}
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}
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.
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}
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}
WWLM0066W: An error was encountered attempting to update cluster {0} with information from cluster {1}.
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}
WWLM0068W: Unable to initialize affinity modules, no affinity enabled. {0}
WWLM0069E: No CFEndPoint associated with the chain {0} will not be available for selection.
WWLM0070E: The Channel Framework Service is 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}.
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.
WWLM0073I: Attempting to contact backup cluster using domain boot strap information: cluster {0} host {1} port {2}.
WWLM0074I: Successfully connected to the backup cluster using domain boot strap information: cluster {0} host {1} port {2}.
WWLM0075I: operation failed because another administrative operation:
WWLM0076I: is already in progress.
WWLM0077I: There are no cluster members to
WWLM0078I: All members of the cluster {0} must exist on a node contained in the node group {1}.
WWLM0079I: Received {0} for transactionLogRecovery. The value must be either be enabled or disabled.
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.
WWLM0081W: The rule with start time {0} and end time {1} is not valid and will be ignored.
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.
WWLM0083W: During Ripplestart for cluster {0} the {1} operation exceeded the time-out of {2} milliseconds for member {3} on node {4}.
WWLM0084I: The WLM Custom Property {0} has been configured with a value of {1}.
WWLM0085I: The {1} member on the {2} node is set to the available state for the {0} cluster.
WWLM0086I: The {1} member on the {2} node is set to the unavailable state for the {0} cluster.
WWLM1001E: An exception occurred while setting the property {0}. {1}
WWLM1002E: The value for the key {0} in the implfactory.properties file must implement the interface {1}.
WWLM1003W: Unable to activate the {0} Cluster MBean. {1}
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}
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.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.wlm.resources.WLMNLSMessages.dita
File name: com.ibm.ws.wlm.resources.WLMNLSMessages.html