IBM Support

PM80326: WS-RELIABLEMESSAGING SCALEABILITY ISSUE IN A CLUSTERED ENVIRONMENT.

Fixes are available

7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Large message backlogs on WS-RM sequences can cause memory exhau
    
    In a clustered environment the WS-RM component on one
    application server may attempt to process a sequence associated
    with a different application server.  When this occurs, WS-RM
    will lock the sequence and cause every message on the sequence
    to be read from the WS-RM store even though it will not process
    any of the messages in any further manner.  If WS-RM has been
    configured to provide a persistent quality of service then this
    can have a significant impact on performance.  If a large
    backlog of messages exists on the sequence then the impact on
    performance can cause the rate at which WS-RM can send messages
    to drop below the rate at which new messages are added to the
    sequence, exacerbating the problem further.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  WS-                                         *
    *                  ReliableMessaging                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Large backlogs of messages on WS-RM     *
    *                      sequences causes performance            *
    *                      degradation                             *
    *                      and memory exhaustion causing           *
    *                      OutOfMemory                             *
    *                      errors.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Large message backlogs on WS-RM sequences can cause memory
    exhaustion leading to java.lang.OutOfMemoryError errors.  Large
    backlogs can occur if the destination is unavailable or if the
    application configured with WS-RM is generating messages faster
    than they can be delivered to the destination.
    In addition, in a clustered environment, the WS-RM component's
    algorithm that retrieves the next message to send is highly
    inefficient when the backlog of messages on a sequence is
    large.
    

Problem conclusion

  • The maximum number of messages on an outbound WS-RM sequence can
    be configured using the JVM system property
    com.ibm.websphere.wsrm.MaxSequenceBacklog.  When this limit is
    reached WS-RM will reject any new messages by throwing a
    javax.xml.ws.WebServiceException exception until the backlog
    decreases below the limit.  Clients receiving an exception
    should retry the request.
    
    If WS-Notification Broker is configured with WS-
    ReliableMessaging then the default interval that the WS-
    Notification broker will retry the request is two minutes,
    configurable in minutes by a custom property of the WS-
    Notification service,
    com.ibm.ws.sib.wsn.SubscriptionRetryInterval.  A new custom
    property, com.ibm.ws.sib.wsn.SubscriptionRetryIntervalSeconds,
    of the WS-Notification service is provided by this APAR that
    allows the retry interval to be specified in seconds.
    
    The WS-ReliableMessaging component has also been modified so
    that the algorithm to retrieve the next message to be sent is
    more efficient in a clustered environment.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.6 and the fix pack following 8.5.0.2.
    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

    PM80326

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-10

  • Closed date

    2013-01-31

  • Last modified date

    2013-01-31

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

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

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM80326

Modified date: 31 January 2013