CWSPX

CWSPX0001W: Problems occurred while creating error logs.

Explanation

No logging will occur due to the unhandled event.

Action

Make sure the specified log file name(s) are valid and accessible.

CWSPX0002W: Caught unhandled exception from initFilterConfig in SipClusterSelectorRequestFilter exception={0}.

Explanation

The SipClusterSelectorRequestFilter filter failed to be initialized from the ProxyConfig.

Action

Make sure that the configuration for cluster routing rules is correct.

CWSPX0003W: Caught unhandled exception from doFilter in SipClusterSelectorRequestFilter exception={0}.

Explanation

The SipClusterSelectorRequestFilter filter has a possible configration problem.

Action

Make sure that the configuration for cluster routing rules is correct.

CWSPX0004W: Unable to find least loaded server for request in cluster {0}.

Explanation

There are no available servers in the cluster.

Action

Make sure that there are servers in the cluster running.

CWSPX0005W: Unable to find partition id {0} in clusters {1}. The call id for the message is [{2}].

Explanation

The partition id is not available in the available clusters.

Action

None.

CWSPX0006W: Invalid SIP message received. Header in question [{0}] for call id [{1}].

Explanation

An non valid Session Initiation Protocol (SIP) message was received. The message is missing a required header.

Action

None.

CWSPX0007W: Unable to retrieve configuration data.

Explanation

Configuration error, the SipViaHeaderRequestFilter is unable to retrieve the configuration information.

Action

None.

CWSPX0008W: Invalid VIA header in SIP response message.

Explanation

The topmost VIA header in the Session Initiation Protocol (SIP) response message is not valid.

Action

None.

CWSPX0009W: Unable to route message due to invalid VIA header in SIP response message.

Explanation

The address in the VIA header is not valid.

Action

None.

CWSPX0010W: Unable to find least loaded server for request in cluster {0} repeated {1} times with last failure {2}.

Explanation

There are no available servers in the cluster.

Action

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}.

Explanation

The partition id is not available in the available clusters.

Action

None

CWSPX0012I: SIP Proxy detected server down {0} in cluster {1}.

Explanation

The proxy determined that a server has went down in a cluster that the proxy was using.

Action

None

CWSPX0013I: SIP Proxy detected server up {0} in cluster {1}.

Explanation

The proxy determined that a server has been started in a cluster that the proxy is using.

Action

None

CWSPX0014I: SIP Proxy detected partition id added {0} to server {1}.

Explanation

The proxy determined that a partition has been added to a server.

Action

None

CWSPX0015I: SIP Proxy detected partition id removed {0} from server {1}.

Explanation

The proxy determined that a partition has been removed from a server.

Action

None

CWSPX0016W: SIP Proxy detected overloaded server {1} for request in cluster {0}.

Explanation

The server that was selected, was overloaded.

Action

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}.

Explanation

The server that was selected, was overloaded.

Action

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.

Explanation

The server that was overloaded is now not overloaded.

Action

None

CWSPX0019I: SIP Proxy detected server {0} that has a MMAP {1} with AP {2} with calculated MMAP {3}.

Explanation

This is the Maximum Messages per Averaging Interval for this server instance.

Action

None

CWSPX0020I: Stateless SIP Proxy Startup Successful.

Explanation

Indicates that the Session Initiation Protocol (SIP) Proxy has successfully started.

Action

None.

CWSPX0021I: Stateless SIP Proxy Shutdown Successful.

Explanation

Indicates that the Session Initiation Protocol (SIP) Proxy has terminated normally.

Action

None.

CWSPX0022W: Connection retries exhausted, unable to connect to target: address = {0}.

Explanation

We cannot connect to the address

Action

None.

CWSPX0023W: Transport Error, unable to send message to target. address = {0}.

Explanation

Transport Error, unable to send message to target.

Action

None.

CWSPX0025I: Outbound client connection successful: address = {0}.

Explanation

Indicates that an outbound connection to a client was successful.

Action

None.

CWSPX0026I: Inbound client connection successful: address = {0}.

Explanation

Indicates that a new inbound connection from a client was successful.

Action

None.

CWSPX0027W: Error on client connection: address = {0}.

Explanation

A connection to a client has been broken.

Action

None.

CWSPX0028I: Server connection successful: address = {0}.

Explanation

The Session Initiation Protocol (SIP) Proxy Server has made a successful connection to a SIP Container.

Action

None.

CWSPX0029W: Error on server connection: address = {0}.

Explanation

A connection to a Session Initiation Protocol (SIP) Container has been broken. This may be caused by a container going down, but could also be caused by a network device or networking timeout in the operating system. If it is not a container outage, it is likely the connection will be recreated and this message can be ignored.

Action

Check that the container is still up and running. If not, restart it. If so, then no action is required as the connection will be recreated automatically.

CWSPX0030W: Unable to connect to client: address = {0}.

Explanation

An attempt to connect to a client failed.

Action

None.

CWSPX0031W: Unable to connect to server: address = {0}.

Explanation

An attempt to connect to a server failed.

Action

None.

CWSPX0032I: SIP Proxy is not configured to start.

Explanation

The Session Initiation Protocol (SIP) Proxy did not find any associated channel chains.

Action

None.

CWSPX0033I: SIP Proxy quiesce started.

Explanation

The Session Initiation Protocol (SIP) Proxy received a start quiesce request.

Action

None.

CWSPX0034I: SIP Proxy quiesce completed.

Explanation

The Session Initiation Protocol (SIP) Proxy quiesce is completed.

Action

None.

CWSPX0035I: Custom property {0} with value {1} has overridden server configuration property with value {2}.

Explanation

A Custom property has overridden a server configuration property.

Action

Administrator should check configuration to ensure it is configured correctly.

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}.

Explanation

This is the Maximum Messages per Averaging Interval for this server instance.

Action

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}.

Explanation

This is the Maximum Messages per Averaging Interval for this server instance.

Action

None

CWSPX0052W: SIP Proxy detected overloaded server {1} for request due to MMAP in cluster {0}.

Explanation

The server that was selected, was overloaded.

Action

None

CWSPX0053W: SIP Proxy detected overloaded server {3} for request due to MMAP in cluster {0} repeated {1} times with last failure {2}.

Explanation

The server that was selected, was overloaded.

Action

None

CWSPX0054W: SIP Proxy detected SIP heartbeat failure for server {0}.

Explanation

This server is not responding to Session Initiation Protocol (SIP) heartbeats.

Action

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.

Explanation

This server is now responding to Session Initiation Protocol (SIP) heartbeats.

Action

None

CWSPX0056I: SIP Proxy has informed the load balancer of readiness.

Explanation

The Proxy is successfully responding to load balancer inquiries.

Action

None

CWSPX0057W: The Session Initiation Protocol (SIP) logic in the control region encountered an error when it attempted to contact the SIP Container to start the failover process.

Explanation

The SIP logic in the control region is attempting to notify the container to to start the failover process. However, the container is not responding.

Action

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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

CWSPX0058W: The last Session Initiation Protocol (SIP) Container has failed. The failover process has been canceled.

Explanation

A SIP Container has failed. The SIP logic in the control region attempted to notify an existing container to handle the failover, but containers are not running.

Action

CWSPX0059I: The Session Initiation Protocol (SIP) logic in the control region will start routing new requests to a new logical server name named {0}.

Explanation

A SIP Container has registered a new logical server name. The SIP logic in the control region will add that name to its load balancing list.

Action

No action is required.

CWSPX0060I: The Session Initiation Protocol (SIP) logic in the control region will stop routing new requests to the {0} logical server name.

Explanation

A SIP Container is unregistering a logical server name. The SIP Router will remove the name from its load balancing list.

Action

No action is required.

CWSPX0061I: Network heartbeat from a new proxy {0} timeout {1} limit {2}

Explanation

The Session Initiation Protocol (SIP) logic in the control region detected a new SIP proxy in the cluster, and SIP network outage detection is enabled.

Action

No action is required

CWSPX0062W: Network heartbeat limit exceeded with Session Initiation Protocol (SIP) proxy {0}. {1} heartbeats missed.

Explanation

The SIP logic in the control region has not received heartbeat messages from the front-end proxy within the pre-configured timeout value.

Action

Verify that the SIP proxy is still running, and the SIP network line between the proxy and the container is in order.

CWSPX0063E: Session Initiation Protocol (SIP) container failed to restart

Explanation

The SIP container attempted to restart itself as a result of network outage, but this action failed.

Action

Please restart the application server manually.

CWSPX0064E: Session Initiation Protocol (SIP) logic in the control region detected network outage, and will restart itself.

Explanation

The SIP logic in the control region has lost touch with all front-end proxies in the cluster. It is now restarting itself. Active sessions will migrate to a backup container, if one is present in the replication domain.

Action

Determine the cause for SIP network outage. Focus on the network line between the proxy and the application server. You can use a network sniffer to trace the SIP KEEPALIVE messages between the proxy and the container.

CWSPX0065I: SIP Proxy startup delay is enabled for {0} milliseconds.

Explanation

The SIP Proxy startup delay is used to allow for the replication of all data from all the configured clusters before processing of any messages.

Action

None.

CWSPX0066I: SIP Proxy startup delay is completed.

Explanation

The SIP Proxy startup delay is completed and is now processing SIP messages.

Action

None.

CWSPX0067I: Session Initiation Protocol (SIP) proxy detected server {0} being quiesced.

Explanation

The SIP Proxy recieved notification that the server has started its quiesce sequence.

Action

No action is required

CWSPX0068I: Session Initiation Protocol (SIP) proxy detected server {0} coming out of a quiesce.

Explanation

The SIP Proxy recieved notification that the server has gone from being quiesced to active.

Action

No action is required

CWSPX0069W: DNS lookup for {0} took {1} milliseconds.

Explanation

The proxy did a DNS lookup took a long time to complete. This can cause the SIP Proxy to run at a slow rate.

Action

Consider disabling dynamic DNS lookups.

CWSPX0070I: SIP Proxy is communicating with the Load Balancer at address {0}.

Explanation

The SIP Proxy received a message from the Load Balancer.

Action

No action is required

CWSPX0071W: SIP Proxy is no longer communicating with the Load Balancer at address {0}.

Explanation

The SIP Proxy has not received a message from the Load Balancer recently.

Action

No action is required

CWSPX0072W: The write queue is approaching capacity. The connection to the remote site is congested. The address of the remote site is {0}.

Explanation

The remote site has stopped reading packets or the network is congested.

Action

Check the network for congestion problems or check the remote site for insufficient resources.

CWSPX0073E: The write queue has reached capacity. The connection to the remote site is closed. The address of the remote site is {0}.

Explanation

The remote site has stopped reading packets or the network is congested. The connection to the remote site is closed to free resources.

Action

Check the network for congestion problems or check the remote site for insufficient resources.