Additional Overload Information If you set the queue length as an incoming call

8-16 Oracle WebLogic Communications Server Administration Guide There should be only one PID for each WebLogic Server instance running on the machine. 2. After identifying the affected PID, use the following command to kill the process: kill -3 [pid] 3. This command generates the actual thread dump. If the process is not immediately killed, repeat the command several times, spaced 5-10 seconds apart, to help diagnose potential deadlock problems, until the process is killed. 4. Attempt to restart Oracle WebLogic Communication Services immediately. 5. Make a backup copy of all SIP logs on the affected server to aid in troubleshooting. The location of the logs varies based on the server configuration. 6. Copy each log to assist Tier 4 support with troubleshooting the problem. 7. Notify Tier 4 support and include the log files with the trouble ticket. 8. Monitor the server closely over next 24 hours. If the source of the problem cannot be identified in the log files, there may be a hardware or network issue that will reappear over time.

8.5.2.8.2 Additional Shutdown Information The Administration Console generates SNMP

messages for managed WebLogic Server instances only until the ServerShutDown message is received. Afterwards, no additional messages are generated.

8.5.2.9 sipAppDeployed

Oracle WebLogic Communication Services engine tier nodes generate this alarm when a SIP Servlet is deployed to the container.

8.5.2.9.1 Recovery Procedure This trap is generated during normal deployment

operations and does not indicate an exception.

8.5.2.10 sipAppUndeployed

Oracle WebLogic Communication Services engine tier nodes generate this alarm when a SIP application shuts down, or if a SIP application is undeployed. This generally occurs when Oracle WebLogic Communication Services is shutdown while active requests still exist.

8.5.2.10.1 Recovery Procedure During normal shutdown procedures this alarm should

be filtered out and should not reach operations. If the alarm occurs during the course of normal operations, it indicates that someone has shutdown the application or server unexpectedly, or there is a problem with the application. Notify Tier 4 support immediately.

8.5.2.11 sipAppFailedToDeploy

Oracle WebLogic Communication Services engine tier nodes generate this trap when an application deploys successfully as a Web Application but fails to deploy as a SIP application. Note: Oracle WebLogic Communication Services logs are truncated according to your system configuration. Make backup logs immediately to avoid losing critical troubleshooting information.