WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS


WWLM

WWLM5000E: While reading the PROXY configuration an exception occurred {0}.
Explanation The configuration of an URI group and routing rules for one or more of the generic sever clusters may not be configured properly.
Action Make sure that the URI groups and routing rules for all configured generic server clusters are configured correctly.
WWLM5001E: When creating the runtime Generic Server Cluster, an unexpected exception occurred {0}}.
Explanation An internal, unrecoverable error occurred.
Action If this problem persists, contact your service representative.
WWLM5002E: When trying to register the GenericClusterConfigChangeListener with the FilterManager an unexpected exception occurred {0}}.
Explanation An internal error occurred which prevents runtime updates of Generic Server Cluster configuration information.
Action If this problem persists, contact your service representative.
WWLM5003W: The following unexpected exception occurred while attempting to create cluster data from ODC: {0}
Explanation An error occurred which prevented all necessary cluster data from being created.
Action Examine the ODC logs for further details.
WWLM5004E: While reading the PROXY configuration, the configuration data for custom advisor {0} could not be found.
Explanation One or more of the custom advisors may not be configured properly.
Action Make sure configuration is correct for all the custom advisors.
WWLM5005E: When starting or stopping a custom advisor, an unexpected exception occurred {0}}.
Explanation An internal, unrecoverable error occurred.
Action If this problem persists, contact your service representative.
WWLM5006E: The required custom advisor class {0} could not be found in Java ARchive (jar) {1}.
Explanation The custom advisor class specified in the advisor-class element of the advisor-context.xml was not found in the Java ARchive (jar).
Action Include this custom advisor class in the Java ARchive (jar) or remove this advisor-class element from the advisor-context.xml.
WWLM5007E: The required custom advisor element(s) {0} could not be found in {1}.
Explanation When parsing the advisor-context.xml, one or more of the required elements were not found.
Action Make sure that the advisor-name and advisor-class elements are correct in the advisor-context.xml.
WWLM5008W: A CustomAdvisorException was received from the custom advisor {0}. The exception received was {1}.
Explanation A CustomAdvisorException indicates that the custom advisor code is having a problem.
Action Examine the exception details and the custom advisor log (if there is one) to diagnose the problem with the custom advisor code.
WWLM5009W: An unexpeted exception was received from the custom advisor {0}. The exception received was {1}.
Explanation The exception was unexpected and very likely a runtime exception. It indicates that the custom advisor code is having a problem.
Action Examine the exception details and the custom advisor log (if there is one) to diagnose the problem with the custom advisor code.
WWLM5010W: The server cookie names for the {4} cluster do not match. The server cookie name previously set for the cluster is {3}. The server cookie name for the {1} process on the {2} node was defined as {0}. All server cookies in the cluster now have the default name of JSESSIONID.
Explanation The server cookie names must be the same for all members of a cluster.
Action Ensure that the server cookie names are the same for all members of the cluster. Export the updated configuration and transfer the configuration archive file to the secure proxy server node.
WWLM5011W: The {0} cluster member on the {1} node and in the {2} cluster has two different different server cookies defined on it. The cookies are {3} and {4}.
Explanation The non-default server cookie names must be the same for all members of a cluster. Having two different cookies defined on the same cluster member can cause routing problems for defined sessions.
Action Ensure that all server cookie names are the same for all members of the cluster.
WWLM5012W: When the proxy server started and processed the {0} application, the proxy server defined two different non-default cookies of {1} and {2}. Session affinity to this application might not be honored.
Explanation The non-default cookie names must be the same for all members of a cluster the application is installed to.
Action Ensure that all server cookie names are the same for all members of the cluster. Restart all processes in the cell if a change is made.
WWLM5013W: The {0} cluster member on the {1} node is using the default cookie name of JSESSIONID, but other members of its cluster are using the non-default cookie name of {2}. The {0} cluster member has been marked as unavailable for all future requests.
Explanation The cookie names must be the same for all members of a cluster.
Action Ensure that the cookie name of the new specified cluster member is set properly and restart the cluster member.
WWLM5014I: When processing the {0} application with the {1} cookie, a new non-default cookie value of {2} was found. The new cookie value will be used for all new sessions
Explanation The non-default cookie name for this application has changed.
Action If the non-default cookie name is being changed, no action is necessary. Otherwise, check the configuration of the cluster members this application is installed on to ensure that all defined cookies match.
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:56:37 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.proxy.wlm.resources.WLMPROXYNLSMessages.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)