IBM Support

PM72572: SIP CONTAINER DOESN'T GET OUT OF OVERLOAD DUE TO EXCEPTION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Component:  WAS.sip.container
    Sametime SIP proxy showing overloaded messages in log:
    "CWSPX0017W: SIP Proxy detected overloaded server RTCGWServer
    for request in cluster SametimeGatewayCluster "
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM Websphere Application Server        *
    *                  Feature Pack for Communications Enabled     *
    *                  Applications (CEA) Session Initiation       *
    *                  Protocol (SIP) users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SIP Container doesn't get out of    *
    *                      overload condition.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following exception occurs which prevents from the SIP
    Container to get out of the overload condition:
    java.lang.NullPointerException
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.hamanagment.io.ReplicationBytes.recycle(Replicati
    onBytes.java:267)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.RepCommand.recycle(RepCommand.
    java:168)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.ServiceReplicationData.recycle
    Commands(ServiceReplicationData.java:248)
    [8/8/12 7:18:30:999 EDT] 000000c5 FfdcProvider  W
    com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
    Incident emitted on
    D:\IBM\STGWWebSphere\AppServer\profiles\RTCGW_Profile1\logs\ffdc
    \RTCGWServer_3ed63ed6_12.08.08_07.18.30.99914074221870699248.txt
    com.ibm.ws.drs.message.DRSBuffWrapper.storeObject 1
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.ServiceReplicationData.clearSt
    ructures(ServiceReplicationData.java:209)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.ServiceReplicationData.execute
    Replication(ServiceReplicationData.java:194)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.ReplicationHandler.serviceFini
    shed(ReplicationHandler.java:622)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.ReplicationHandler.serviceFini
    shed(ReplicationHandler.java:653)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.failover.FailoverMgrImpl.reportEndOfSer
    vice(FailoverMgrImpl.java:1565)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.appqueue.AppQueueHandler.reportToFailov
    erServiceEnded(AppQueueHandler.java:344)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.appqueue.AppQueueHandler.finishToExecut
    eRunnable(AppQueueHandler.java:123)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.was.ContextBasedQueue.finishedToExecute
    Task(ContextBasedQueue.java:163)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.sip.container.was.SignalingEndOfTask.run(SignalingEnd
    OfTask.java:82)
    [8/8/12 7:18:30:999 EDT] 000000c5 SystemErr     R    at
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613)
    

Problem conclusion

  • The exception that prevented the container getting
    out of the overload is now caught, so the code that would take
    the next task from the queue to the pool to be processed by
    another thread, or mark the queue as free, will be proccessed.
    In addition, in order to fix the root cause of the exception
    the dialog usages set in DialogState was synchronized.
    
    The fix for this APAR is currently targeted for inclusion in
    Feature Pack for CEA fix pack 1.0.0.15. Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM72572

  • Reported component name

    CEA FEATUREPACK

  • Reported component ID

    5724J0855

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-11

  • Closed date

    2012-10-29

  • Last modified date

    2012-10-29

  • APAR is sysrouted FROM one or more of the following:

    PM70768

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CEA FEATUREPACK

  • Fixed component ID

    5724J0855

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2022