WebSphere Process Server messages     Operating Systems: All supported

CWSPX

CWSPX0001W: Problems occurred while creating error logs.
Problem No logging will occur due to the unhandled event.
User response Make sure the specified log file name(s) are valid and accessible.
CWSPX0002W: Caught unhandled exception from initFilterConfig in SipClusterSelectorRequestFilter exception={0}.
Problem The SipClusterSelectorRequestFilter filter failed to be initialized from the ProxyConfig.
User response Make sure that the configuration for cluster routing rules is correct.
CWSPX0003W: Caught unhandled exception from doFilter in SipClusterSelectorRequestFilter exception={0}.
Problem The SipClusterSelectorRequestFilter filter has a possible configration problem.
User response Make sure that the configuration for cluster routing rules is correct.
CWSPX0004W: Unable to find least loaded server for request in cluster {0}.
Problem There are no available servers in the cluster.
User response Make sure that there are servers in the cluster running.
CWSPX0005W: Unable to find partition id {0} in clusters {1}.
Problem The partition id is not available in the available clusters.
User response None.
CWSPX0006W: Invalid SIP message received. Header in question [{0}] for call id [{1}].
Problem An invalid SIP message was received. The message is missing a required header.
User response None.
CWSPX0007W: Unable to retrieve configuration data.
Problem Configuration error, the SipViaHeaderRequestFilter is unable to retrieve the configuration information.
User response None.
CWSPX0008W: Invalid VIA header in SIP response message.
Problem The topmost VIA header in the SIP response message is not valid.
User response None.
CWSPX0009W: Unable to route message due to invalid VIA header in SIP response message.
Problem The address in the VIA header is invalid.
User response None.
CWSPX0010W: Unable to find least loaded server for request in cluster {0} repeated {1} times with last failure {2}.
Problem There are no available servers in the cluster.
User response Make sure that there are servers in the cluster running.
CWSPX0011W: Unable to find partition id {3} in cluster {0} repeated {1} times with last failure {2}.
Problem The partition id is not available in the available clusters.
User response None
CWSPX0012I: SIP Proxy detected server down {0} in cluster {1}.
Problem The proxy determined that a server has went down in a cluster that the proxy was using.
User response None
CWSPX0013I: SIP Proxy detected server up {0} in cluster {1}.
Problem The proxy determined that a server has been started in a cluster that the proxy is using.
User response None
CWSPX0014I: SIP Proxy detected partition id added {0} to server {1}.
Problem The proxy determined that a partition has been added to a server.
User response None
CWSPX0015I: SIP Proxy detected partition id removed {0} from server {1}.
Problem The proxy determined that a partition has been removed from a server.
User response None
CWSPX0016W: SIP Proxy detected overloaded server {1} for request in cluster {0}.
Problem The server that was selected, was overloaded.
User response Check the server logs to see what caused the server to be overloaded.
CWSPX0017W: SIP Proxy detected overloaded server {3} for request in cluster {0} repeated {1} times with last failure {2}.
Problem The server that was selected, was overloaded.
User response Check the server logs to see what caused the server to be overloaded.
CWSPX0018I: SIP Proxy detected that previously overloaded server {0} is now okay.
Problem The server that was overloaded is now not overloaded.
User response None
CWSPX0019I: SIP Proxy detected server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
Problem This is the Maximum Messages per Averaging Interval for this server instance.
User response None
CWSPX0050I: SIP Proxy detected SIP Proxy server up in cluster {4}, recalculating server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
Problem This is the Maximum Messages per Averaging Interval for this server instance.
User response None
CWSPX0051I: SIP Proxy detected SIP Proxy server down in cluster {4}, recalculating server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.
Problem This is the Maximum Messages per Averaging Interval for this server instance.
User response None
CWSPX0052W: SIP Proxy detected overloaded server {1} for request due to MMAP in cluster {0}.
Problem The server that was selected, was overloaded.
User response None
CWSPX0053W: SIP Proxy detected overloaded server {3} for request due to MMAP in cluster {0} repeated {1} times with last failure {2}.
Problem The server that was selected, was overloaded.
User response None
CWSPX0054W: SIP Proxy detected SIP heartbeat failure for server {0}.
Problem This server is not responding to SIP heartbeats.
User response Check the server logs to see if the server is up.
CWSPX0055I: SIP Proxy detected previously down server {0} is now responding to SIP heartbeats.
Problem This server is now responding to SIP heartbeats.
User response None
CWSPX0056I: SIP Proxy has informed the load balancer of readiness.
Problem The Proxy is successfully responding to load balancer inquiries.
User response None
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.proxy.filter.resources.sipfilters.html

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