WebSphere Process Server messages     Operating Systems: All supported

CWSCT

CWSCT0001I: SIP Container initialization completed.
Problem The SIP container is up and ready to receive messages from the network.
User response This is an informational message. No user action is necessary.
CWSCT0002I: SIP Container {0}
Problem Version number of the SIP container component.
User response This is an informational message. No user action is necessary.
CWSCT0003W: SIP Container MBean unable to start.
Problem SIP Container MBean unable to start. JMX operations will not be available for the SIP Container.
User response No action is required.
CWSCT0004E: The following exception has occurred:
Problem An exception was caught by the SIP container.
User response No action is required.
CWSCT0006I: Failover started. Number of received objects {0} for logical name {1}.
Problem One of the servers in the cluster has terminated, and some of its logical names are transferred to this server. The session objects associated with these logical names are now being activated on this server.
User response No action is required.
CWSCT0008I: Failover ended.
Problem Finished activation of session objects that are associated with a logical name. See "Failover started" for the logical name and the number of objects.
User response No action is required.
CWSCT0010E: Error configuring sip.xml parser.
Problem An error has occurred while trying to initialize the XML parser. This does not indicate an error in the sip.xml document.
User response No action is required.
CWSCT0011E: Parser not available; unable to load application configuration.
Problem The SIP container cannot load an application from the sip.xml file because there is no XML parser.
User response Look for an earlier error message in the log that reads "Error configuring sip.xml parser".
CWSCT0012E: Parse exception; failed to parse sip.xml {0}.
Problem The SIP container cannot load an application from the sip.xml file because of an error in the sip.xml document.
User response Check for errors in the sip.xml file. You can find information about the standard sip.xml format in JSR 116 (SIP Servlet API) chapters 11 (Mapping Requests to Servlets) and 15 (Deployment Descriptor).
CWSCT0013E: Listener Class: {0} not found for application: {1}.
Problem The class loader could not find the listener class.
User response Check your sip.xml and verify that the listener class name is correct. Make sure the listener class is included in the class path.
CWSCT0014E: Failed to create Listener Class: {0} for application: {1}.
Problem The SIP container could not instantiate the listener class.
User response Check your sip.xml and verify that the listener class name is correct. Make sure the listener class has a public constructor that expects no arguments.
CWSCT0015E: Invalid XML - more than one Timer Listener assigned to application {0}.
Problem The sip.xml document defines more than one TimerListener for the same application.
User response Check your sip.xml and make sure there is only one TimerListener class for the application.
CWSCT0016E: Error parsing session TTL for Sip Application: {0}.
Problem The sip.xml document contains an invalid application session timeout value.
User response Check your sip.xml to make sure the session-timeout setting is expressed in whole number of minutes.
CWSCT0017E: Mapping for nonexisting siplet: {0}, Application: {1}.
Problem The sip.xml document contains a servlet mapping for an undefined servlet
User response Check your sip.xml and make sure that all servlet-name tags under servlet-mapping correspond to an existing servlet, and make sure there is a pattern definition for the servlet mapping.
CWSCT0018E: Invalid Condition Type in sip.xml: {0}.
Problem The sip.xml document contains an invalid type of servlet matching condition.
User response Check your sip.xml to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) 11.3 (Conditions).
CWSCT0019E: Error parsing {0} condition, var: {1} ,value: {2}.
Problem The sip.xml document contains an invalid servlet matching rule.
User response Check your sip.xml to make sure the matching rules are compliant with JSR 116 (SIP Servlet API) chapter 11 (Mapping Requests to Servlets).
CWSCT0020E: Error parsing AND condition; subelements not found.
Problem The sip.xml document contains an AND condition with no sub elements.
User response Check your sip.xml to make sure there are matching rules under the AND tag.
CWSCT0021E: Error in xml definition for sip-app.
Problem The sip.xml document contains zero or multiple sip-app sections. There may only be one.
User response Check your sip.xml to make sure there is exactly one sip-app section.
CWSCT0022E: Error - local SIP DTD document not found.
Problem There is no local definition for /javax/servlet/sip/sip-app_1_0.dtd
User response No action is required.
CWSCT0023I: Server is no longer overloaded.
Problem The SIP container is no longer considered overloaded, and is now ready to handle new sessions
User response No action is required.
CWSCT0024I: New server weight set to {1} by {0}
Problem The server weight was changed, due to a change in SIP activity
User response No action is required.
CWSCT0025E: Failed to create SIP stack.
Problem The internal SIP stack failed to initialize.
User response No action is required.
CWSCT0026E: Exception in SIP stack.
Problem An exception was caught in the SIP stack layer. The stack will attempt to continue running normally.
User response No action is required.
CWSCT0028I: SIP Container Listening Point {0}:{1}/{2}
Problem This is an informational message printed for each host address, port number, and transport protocol, that the SIP container listens to, for incoming SIP traffic.
User response No action is required.
CWSCT0029E: SIP failed to forward; response request is {0}
Problem The SIP container failed to forward a SIP message.
User response No action is required.
CWSCT0030E: SIP failed proxying to branch; URI is {0}
Problem The SIP container, acting as a proxy, failed to forward a request to one of the destinations.
User response No action is required.
CWSCT0031E: SIP failed to create record route {0}
Problem The SIP container, acting as a proxy, failed to create a Record-Route header.
User response No action is required.
CWSCT0032E: SIP cannot change proxy to parallel after proxyTo
Problem The SIP servlet code called Proxy.setParallel() after calling Proxy.proxyTo()
User response Change the application code so Proxy.setParallel() is not called after Proxy.proxyTo()
CWSCT0033E: SIP cannot recurse with stateless proxy.
Problem The SIP servlet code called Proxy.setRecurse() on a stateless Proxy.
User response Change the application code so it doesn't call Proxy.setRecurse() on a stateless Proxy.
CWSCT0034E: SIP cannot change proxy to stateful after proxyTo
Problem The SIP servlet code called Proxy.setStateful() after calling Proxy.proxyTo()
User response Change the application code so Proxy.setStateful() is not called after Proxy.proxyTo()
CWSCT0035E: SIP failed cancellation request in proxy; cancel request: {0}
Problem The SIP container failed sending out a CANCEL request.
User response No action is required.
CWSCT0036E: SIP failed to send response upstream; response: {0}
Problem The SIP container failed to send a response upstream (upstream is the direction that responses flow from the UAS back to the UAC)
User response No action is required.
CWSCT0037E: SIP cannot set record route after proxyTo
Problem The SIP servlet code called Proxy.setRecordRoute() after calling Proxy.proxyTo()
User response Change the application code so Proxy.setRecordRoute() is not called after Proxy.proxyTo()
CWSCT0040E: SIP failed to create request; request: {0}
Problem The SIP container failed creating a SIP request message.
User response No action is required.
CWSCT0041E: Failed to get route header.
Problem The SIP container failed getting a Route header in a request.
User response No action is required.
CWSCT0042E: Failed to resolve internet address.
Problem Failed resolving an internet address from host name to IP address.
User response No action is required.
CWSCT0043E: Unable to set record route for a non dialog request: {0}
Problem The SIP servlet code called Proxy.setRecordRoute() on a request that does not create a dialog.
User response Change the application code so it doesn't call Proxy.setRecordRoute() on requests that don't create a dialog. Examples of requests that do create dialogs are INVITE, REFER, and SUBSCRIBE.
CWSCT0044E: Proxy has reached an unexpected function call.
Problem The SIP container received a message where it does not expect it.
User response No action is required.
CWSCT0045E: Unable to proxy subsequent requests without route header: {0}
Problem The SIP container cannot proxy a subsequent request on a dialog, because the incoming request has no Route header.
User response No action is required.
CWSCT0046E: Unknown URI type; unable to access parameters from header: {0}
Problem The SIP container cannot process a message because the URI is not a sip or sips URI.
User response No action is required.
CWSCT0048E: Error processing Strict Routing; request URI does not contain session ID. {0}
Problem The SIP container received a request on a dialog from a strict router, and the session ID parameter in the Request-URI was missing, or had the wrong value.
User response No action is required.
CWSCT0049E: Error sending response
Problem The SIP container failed to send out a response.
User response No action is required.
CWSCT0051E: Unable to find a siplet for invocation; default handler not available.
Problem There is no matching SIP servlet for handling a request.
User response Check the matching rules of the installed SIP applications and make sure that at least one of them can be matched to the request.
CWSCT0052E: Unable to find dialog for received BYE request. Call-Id is {0}
Problem The SIP container received a BYE request that is not matched to any existing dialog.
User response No action is required.
CWSCT0053E: Invalid variable in operator; var: {0}
Problem The sip.xml document contains an invalid variable.
User response Check your sip.xml to make sure the variable is valid according to JSR 116 (SIP Servlet API) 11.2 (SIP Request Object Model)
CWSCT0054E: Failed to evaluate operator {0}; subelements not available.
Problem The sip.xml document contains a condition with no sub-elements.
User response Check your sip.xml to make sure that pattern matching is valid according to JSR 116 (SIP Servlet API) 11.3 (Conditions).
CWSCT0055E: IPAuthenticator failed parsing configuration
Problem The SIP container failed to parse the list of trusted IP addresses from configuration.
User response Check the configuration property com.ibm.ws.sip.security.trusted.iplist
CWSCT0056E: IPAuthenticator failed, unknown host
Problem The list of trusted IP addresses for SIP authentication contains a host name that fails to resolve.
User response Check the list of trusted IP addresses in the configuration property com.ibm.ws.sip.security.trusted.iplist
CWSCT0057E: IPAuthenticator failed parse header
Problem The SIP container failed to parse a Via header for IP authentication.
User response No action is required.
CWSCT0058E: IPAuthenticator header problem.
Problem The SIP container failed to find a Via header in the message for IP authentication.
User response No action is required.
CWSCT0059E: SIP failed to get expirations; not properly formatted: {0}
Problem The application call to Address.setExpires() failed because the message's address header contains a malformed expires parameter value.
User response No action is required.
CWSCT0060E: SIP failed to set display name; name: {0}
Problem The application call to Address.setDisplayName() failed.
User response Check the application code to make sure the display name is valid and not null.
CWSCT0061E: SIP failed to set expirations; seconds: {0}
Problem The application call to Address.setExpires() failed.
User response No action is required.
CWSCT0062E: SIP failed to set parameters; name: {0}, value: {1}
Problem The application call to Address.setParameter() or SipURI.setParameter() failed.
User response Check the application code to make sure the parameter's name and value are valid.
CWSCT0063E: SIP failed to set q; value: {0}
Problem The application call to Address.setQ() failed.
User response Check the application code to make sure the priority value is valid.
CWSCT0064E: SIP failed to get method from submitted request: {0}
Problem The application call to SipServletMessage.getMethod() failed.
User response No action is required.
CWSCT0065E: SIP failed to get request URI from submitted request: {0}
Problem The application call to SipServletRequest.getRequestURI() failed.
User response No action is required.
CWSCT0066E: SIP failed to create response to request: {0}
Problem The SIP container failed to create a response to the request.
User response No action is required.
CWSCT0067E: SIP failed to send request using JAIN; URI: {0}
Problem The SIP container failed sending out a request.
User response No action is required.
CWSCT0069E: SIP failed to add header; name: {0}, value: {1}
Problem The SIP container failed to add a header to the message.
User response No action is required.
CWSCT0070E: SIP failed to send response, {0}
Problem An error occurred while the SIP container was trying to send out a response.
User response No action is required.
CWSCT0071E: SIP failed to set header; name: {0}, value: {1}
Problem The SIP container failed to set a header value in the message.
User response No action is required.
CWSCT0072E: SIP failed to set host; host: {0}
Problem The application call to SipURI.setHost() failed.
User response Check the application code to make sure the host name is valid and not null.
CWSCT0073E: SIP failed to set port; port: {0}
Problem The application call to SipURI.setPort() failed.
User response No action is required.
CWSCT0074E: SIP failed to set secure; value: {0}
Problem The application call to SipURI.setSecure() failed.
User response No action is required.
CWSCT0075E: SIP failed to set user; user: {0}
Problem The application call to SipURI.setUser() failed.
User response Check the application code to make sure the user name is valid and not null.
CWSCT0076E: SIP failed to set user password; password: {0}
Problem The application call to SipURI.setUserPassword() failed.
User response Check the application code to make sure the user password is valid and not null.
CWSCT0077E: SIP failed to get accepted language, {0}
Problem The application call to SipServletMessage.getAcceptLanguage() failed.
User response No action is required.
CWSCT0078E: SIP failed to get accepted languages, {0}
Problem The application call to SipServletMessage.getAcceptLanguages() failed.
User response No action is required.
CWSCT0079E: SIP failed to get address header; name: {0}
Problem The application call to SipServletMessage.getAddressHeader() failed.
User response No action is required.
CWSCT0080E: SIP failed to get address headers; name: {0}
Problem The application call to SipServletMessage.getAddressHeaders() failed.
User response No action is required.
CWSCT0081E: SIP failed to get character encoding {0}
Problem The application call to SipServletMessage.getCharacterEncoding() failed.
User response No action is required.
CWSCT0082E: SIP failed to get content length {0}
Problem The application call to SipServletMessage.getContentLength() failed.
User response No action is required.
CWSCT0083E: SIP failed to get content type {0}
Problem The application call to SipServletMessage.getContentType() failed.
User response No action is required.
CWSCT0084E: SIP failed to get header; name: {0}
Problem The application call to SipServletMessage.getHeader() failed.
User response No action is required.
CWSCT0085E: SIP failed to get header; names {0}
Problem The application call to SipServletMessage.getHeaderNames() failed.
User response No action is required.
CWSCT0086E: SIP failed to get headers; name: {0}
Problem The application call to SipServletMessage.getHeaders() failed.
User response No action is required.
CWSCT0087E: SIP failed to set content; content: {0}, content type: {1}
Problem The application call to SipServletMessage.setContent() failed.
User response Check the application code to make sure the message content is valid and not null.
CWSCT0088E: SIP failed to get via headers {0}
Problem The application call to SipServletMessage.getViaHeaders() failed.
User response No action is required.
CWSCT0089E: SIP failed to get contact header {0}
Problem The application call to SipServletMessage.getContactHeader() failed.
User response No action is required.
CWSCT0090E: SIP failed to get JAIN SIP headers {0}
Problem The SIP container failed getting one or more headers from the internal JAIN message object.
User response No action is required.
CWSCT0091E: SIP failed to get maximum forwards {0}
Problem The application call to SipServletRequest.getMaxForwards() failed.
User response No action is required.
CWSCT0092E: SIP failed to get reason phrase {0}
Problem The application call to SipServletResponse.getReasonPhrase() failed.
User response No action is required.
CWSCT0093E: SIP failed to get status {0}
Problem The application call to SipServletResponse.getStatus() failed.
User response No action is required.
CWSCT0094E: SIP failed to set status; status: {0}, reason phrase: {1}
Problem The application call to SipServletResponse.setStatus() failed.
User response Check the application code to make sure the status code is valid. If you also supplied a reason phrase, make sure it is not null and not empty.
CWSCT0095E: SIP failed to create address; URI: {0}, display name: {1}
Problem The application call to SipFactory.createAddress() failed.
User response Check the application code to make sure the URI and display name are valid.
CWSCT0097E: SIP failed to create SIP URI; user: {0}, host: {1}
Problem The application call to SipFactory.createSipURI() failed.
User response Check the application code to make sure the user and host parameters are valid and not null.
CWSCT0098E: SIP failed to create URI; URI: {0}
Problem The application call to SipFactory.createURI() failed.
User response Check the application code to make sure the URI string represents a valid URI.
CWSCT0099E: Failed to push route; URI: {0}
Problem The application call to SipServletRequest.pushRoute() or SipServletRequest.pushRecordRoute() failed.
User response Check the application code to make sure the SipURI is valid.
CWSCT0100E: SIP failed to set URI; URI: {0}
Problem The application call to Address.setURI() failed.
User response Check the application code to make sure the URI is valid.
CWSCT0101E: Failed to send an ACK request.
Problem The SIP container failed to send out an ACK request.
User response No action is required.
CWSCT0102E: Failed to send a CANCEL request.
Problem The SIP container failed to send out a CANCEL request.
User response No action is required.
CWSCT0103E: Failed to generate a timeout response.
Problem A request that was sent out from the SIP container was not responded for 32 seconds, and the SIP container failed to generate a timeout response to the application.
User response No action is required.
CWSCT0104E: Failed to clone address.
Problem Internal error in the SIP container cloning an Address object.
User response No action is required.
CWSCT0105E: Invalid Telephony URL: {0}
Problem The SIP container failed to create a tel URL.
User response Check that the raw URL string is at least 4 bytes long (3 for the scheme plus 1 for the colon character).
CWSCT0106E: Error on sending a 487 response {0}
Problem While canceling a request, the SIP container failed sending the 487 (Request Terminated) response to the original request.
User response No action is required.
CWSCT0108E: Error setting character encoding: {0}
Problem The application call to SipServletMessage.setCharacterEncoding() failed.
User response Check the application code to make sure the encoding parameter is valid and not null.
CWSCT0109E: Error setting tag value: {0}
Problem The application call to Address.setTag() failed.
User response Check the application code to make sure the tag parameter is valid.
CWSCT0113I: SIP Session sequence logger is enabled, level: {0}
Problem The logger for SIP session/dialog sequence is enabled.
User response No action is required.
CWSCT0115E: Expected SIP URI but received: {0}
Problem
User response No action is required.
CWSCT0116I: SIP Container is using standalone configuration.
Problem The SIP container is not running as a Websphere service.
User response No action is required.
CWSCT0117E: Failed to initialize siplet {0}
Problem The SIP container failed loading or instantiating a SIP servlet class.
User response Check your sip.xml to make sure the class name is correct and has a public constructor that expects no arguments.
CWSCT0118E: Service siplet failed {0}
Problem An exception was thrown by the SIP servlet code.
User response No action is required.
CWSCT0119E: Invoke siplet failed; servlet unavailable: {0}, {1}
Problem The SIP servlet does not exist.
User response Check your sip.xml to make sure the servlet class name is correct.
CWSCT0120E: Error initializing the SIP container
Problem Error initializing the SIP container; additional details can be found in trace file.
User response Enable diagnostic tracing for the SIP container, restart the server to recreate the problem, and then pull the trace log.
CWSCT0122W: Error dispatching timer event; timer listener not available for: {0}
Problem The SIP servlet timer was triggered, but no listener is associated with it.
User response No action is required.
CWSCT0124W: TimerServiceImpl is unavailable !!!
Problem All timers are disabled in the SIP container
User response Check the SIP container configuration and remove the "enable.timers" property, or set its value to "true".
CWSCT0125E: Transaction ID already set for transaction; current {0}, new {1}
Problem The SIP transaction is already initialized with a transaction ID, and cannot be changed.
User response No action is required.
CWSCT0139E: SIP Failed to invoke request; message is {0}
Problem An exception was thrown while the SIP container tried to invoke a request.
User response No action is required.
CWSCT0140E: SIP failed to send response to prepare to write.
Problem The SIP container failed to send out the response from within the call to prepareHeadersForWrite().
User response No action is required.
CWSCT0142E: Error dispatcher has not completed dispatching previous message.
Problem The SIP container cannot dispatch a message because the previous message dispatching has not completed yet.
User response No action is required.
CWSCT0145E: Received a {0} request while expecting javax.servlet.http.HttpServletRequest
Problem The SIP container received a request from the web container that is not a javax.servlet.http.HttpServletRequest.
User response No action is required.
CWSCT0146E: failed to register {0} collaborator
Problem The SIP container failed to register itself as a listener to Websphere.
User response No action is required.
CWSCT0185E: Error - The cache algorithm does not exist.
Problem The cache algorithm requested by the SIP container session manager does not exist.
User response No action is required.
CWSCT0186E: Error - Replicator exception
Problem Replication exception caught by the SIP container session manager.
User response No action is required.
CWSCT0187I: SIP HA {0}
Problem The SIP container high availability component initialized.
User response No action is required.
CWSCT0188E: Error - Class Not Found Exception; unable to deserialize.
Problem The SIP container caught an exception of type ClassNotFoundException during object serialization.
User response No action is required.
CWSCT0189E: Error - IO exception; unable to serialize / deserialize.
Problem The SIP container caught an exception of type IOException during object serialization.
User response No action is required.
CWSCT0219E: error - drs exception
Problem Exception caught in the SIP container during DRS replication.
User response No action is required.
CWSCT0220E: error - admin JMX exception
Problem Exception caught in the SIP container while activating the MBean for the session manager.
User response No action is required.
CWSCT0222E: Error - DRS multibroker exception.
Problem Exception caught in the SIP container using the DRS multi broker.
User response No action is required.
CWSCT0224E: Error - DRS mode is not BOTH_CLIENT_SERVER (peer to peer)
Problem The DRS mode is not suitable for data replication in the SIP container.
User response No action is required.
CWSCT0225E: Info - DRS not set
Problem Replication in the SIP container is disabled because DRS is not set.
User response Make sure to configure the WebContainer SessionManager to use memory-to-memory replication.
CWSCT0226I: Info - SIP container failover disabled.
Problem SIP container failover disabled.
User response Use the "enable.replication" custom property (for sip container) to enable.
CWSCT0227I: Info - SIP container High Availability component enabled.
Problem The SIP container High Availability component is enabled for load balancing and failover.
User response No action is required.
CWSCT0228E: Error - HAGroupLeftException
Problem The SIP container caught an exception of type HAGroupLeftException while being activated as a group member.
User response No action is required.
CWSCT0229E: Error - HAParameterRejectedException
Problem The SIP container caught an exception of type HAParameterRejectedException while being activated as a group member.
User response No action is required.
CWSCT0231E: Error - IO exception; unable to deserialize.
Problem Data serialization failed in the SIP container.
User response No action is required.
CWSCT0232E: Error - HA exception
Problem An exception was caught in the SIP container High Availability component.
User response No action is required.
CWSCT0233E: Error - Datastack exception
Problem A DataStackException was caught in the SIP container High Availability component.
User response No action is required.
CWSCT0237E: error - IO excpetion
Problem A IOException was caught in the SIP container.
User response No action is required.
CWSCT0238E: Error - UCF Exception; no cluster defined.
Problem The SIP container cannot join or depart from cluster because no cluster is defined.
User response No action is required.
CWSCT0240E: Error - no cluster member service.
Problem The SIP container cannot start or stop the High Availability component because an exception occurred while trying to access the cluster service.
User response No action is required.
CWSCT0241E: Error - UCF Exception - no member available.
Problem The SIP container failed getting SIP proxy endpoint information from UCF.
User response No action is required.
CWSCT0243E: Error - Class not found exception.
Problem A ClassNotFoundException was caught in the SIP container.
User response No action is required.
CWSCT0244E: Error - cannot obtain ORB object
Problem The SIP container cannot publish its logical names due to an error obtaining ORB object.
User response No action is required.
CWSCT0245E: Error - ORB class cast exception
Problem The SIP container cannot publish its logical names due to a ClassCastException.
User response No action is required.
CWSCT0246E: Error - invalid ORB name request
Problem The SIP container cannot publish its logical names due to InvalidName exception.
User response No action is required.
CWSCT0259E: Error - class not found
Problem The SIP container TAI failed to initialize due to a ClassNotFoundException
User response No action is required.
CWSCT0260E: Error - instantiation exception
Problem The SIP container TAI failed to initialize due to InstantiationException.
User response No action is required.
CWSCT0261E: Error - illegal access exception.
Problem The SIP container TAI failed to initialize due to IllegalAccessException.
User response No action is required.
CWSCT0262E: Error - file not found.
Problem The SIP container security cannot open passwords file.
User response No action is required.
CWSCT0264E: Error - Login Context - failed
Problem A LoginException was caught by the SIP container TAI while getting the user subject.
User response No action is required.
CWSCT0266E: Error - naming exception
Problem A NamingException was caught in the SIP container security.
User response No action is required.
CWSCT0267E: Error - parse exception.
Problem A parse exception was caught in the SIP container TAI (Trust Association Interceptor).
User response No action is required.
CWSCT0315E: Exception in SIP Stack.
Problem An exception was caught initializing the SIP stack.
User response No action is required.
CWSCT0316I: SIP Stack {0}
Problem The SIP stack is initializing
User response No action is required.
CWSCT0317E: Unknown host exception; unable to resolve hostname.
Problem An UnknownHostException was caught in the SIP stack while trying to resolve a host name to IP address.
User response No action is required.
CWSCT0318E: Parser exception; failed to write to output stream.
Problem The SIP stack failed writing to output stream.
User response No action is required.
CWSCT0321I: SIP stack init configuration
Problem The SIP stack configuration is initialized.
User response No action is required.
CWSCT0322I: SIP stack init transport.
Problem The SIP stack transport is initialized.
User response No action is required.
CWSCT0323I: SIP stack init finished.
Problem The SIP stack initialization is complete.
User response No action is required.
CWSCT0324I: SIP Stack, Timer B Set to {0} milliseconds.
Problem The SIP stack timer B is set. More information on timer B in RFC 3261.
User response No action is required.
CWSCT0328I: SIP starting to listen on {0}.
Problem The SIP stack is starting to listen on specified listening point.
User response No action is required.
CWSCT0332I: SIP Container was launched successfully but will only be initialized when first SIP application is loaded.
Problem SIP Container was launched successfully. It will only be initialized when first SIP application is loaded.
User response No action is required.
CWSCT0333E: Replication failed.
Problem Exception occurred in the SIP container during replication.
User response No action is required.
CWSCT0334E: Failed to deserialize replication.
Problem Exception occurred in the SIP container replication during object deserialization.
User response No action is required.
CWSCT0335E: Failed to reactivate objects after failover.
Problem Exception occurred in the SIP container during session activation after failover.
User response No action is required.
CWSCT0336E: VirtualHostAlias.init: cannot lookup host {0}
Problem The SIP container failed resolving the host name of a virtual host alias to an IP address.
User response No action is required.
CWSCT0337W: Display name in sip.xml ({0}) is different from display name in web.xml ({1}).
Problem The application's display name in sip.xml is different from the display name in web.xml. This is not compliant with JSR-116 section 15.2.
User response Change the deployment descriptors to match the application display name.
CWSCT0338W: Failed to dispatch SIP message to thread pool. Message= {0}, Call ID= {1}, Error code= {2}.
Problem The SIP container failed to dispatch a message to the thread pool.
User response No action is required.
CWSCT0339E: Deserialize: Cannot identify object type.
Problem The SIP container cannot identify object type for deserialization.
User response No action is required.
CWSCT0340E: Error - cannot retrieve password attribute.
Problem Authentication failed because the SIP container cannot retrieve the userPassword attribute from the person entry in the directory.
User response Change the LDAP configuration settings so the server has access to the userPassword attribute in the directory.
CWSCT0341W: The server is overloaded.
Problem The Session Initiation Protocol (SIP) server cannot accept any more incoming messages while it is overloaded.
User response Reduce the incoming messages, or reduce any other possible sources of stress on the server machine.
CWSCT0342W: The server is overloaded because there are too many application sessions.
Problem The SIP server cannot accept any more incoming messages while it is overloaded. Too many application sessions are active.
User response Reduce the number of application sessions that are created or set a higher value for the maximum application sessions on the Session Initiation Protocol (SIP) container.
CWSCT0343W: The server is overloaded because too many messages were received during an averaging period.
Problem The SIP server cannot accept any more incoming messages while it is overloaded. The messages traffic is too high.
User response Reduce the message load or set the maximum messages per averaging period value to a higher value on the Session Initiation Protocol (SIP) container.
CWSCT0344W: The server is overloaded because the server response time is too slow.
Problem The SIP server cannot accept any more incoming messages while it is overloaded.
User response Reduce the incoming messages traffic or reduce any other possible source of stress on the server machine. If the maximum response time value is enabled and set on the Session Initiation Protocol (SIP) container, consider modifying it to a higher value.
CWSCT0345W: The messages dispatching limit value has been exceeded. New messages will be dropped.
Problem The SIP server cannot accept any more incoming messages while the dispatch queue is overloaded.
User response Reduce the message load or set the maximum dispatch queue size value to a higher value on the Session Initiation Protocol (SIP) container.
CWSCT0346E: The dispatch queue is overloaded. The following message has been rejected: {0}
Problem The SIP container threads cannot handle the current load of tasks.
User response Reduce any possible sources of stress on the server machine, especially Session Initiation Protocol (SIP) messages traffic. In addition, review the amount of resources that are consumed by the SIP application code.
CWSCT0347I: Bootstrap replication has started.
Problem The Session Initiation Protocol (SIP) container is replicating its sessions data to a newly connected peer.
User response No action is required.
CWSCT0348I: Bootstrap replication has finished.
Problem The Session Initiation Protocol (SIP) container has finished replicating its sessions data to the newly connected peer.
User response No action is required.
CWSCT0349I: SIP stack timer [{0}] value set to [{1}]
Problem The timer value is modified in configuration
User response No action is required
CWSCT0350I: Entering quiesce mode
Problem The SIP container MBean received an administrative quiesce command. In this mode, new calls are not serviced on this container instance.
User response No action is required
CWSCT0351I: Exiting quiesce mode
Problem The SIP container MBean received an administrative de-quiesce command.
User response No action is required
CWSCT0360I: Server quiesce ended successfully
Problem The SIP container quiesce operation has ended and all application sessions have been invalidated.
User response No action is required
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.sip.util.log.messages.html

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