IBM Support

PI32705: Large number of TickRange instances under GuaranteedTargetStream consumes more memory and may create

Fixes are available

PI32705;8.5.5: JVM Heapspace and High cpu usage observed when large number of TickRange instances are in one GuaranteedTargetStream instance
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
PI32705;8.5.5: Large number of TickRange instances under GuaranteedTargetStream cause performance problems
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Large number of TickRange instances under one
    GuaranteedTargetStream instance occupies a major portion of
    JVM heapspace observed under heapdump. High CPU also may be
    observed because of this.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  versions 7.0, 8.0 and 8.5.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unnecessary TickRange instances         *
    *                      occupy more heapspace and may create    *
    *                      High CPU.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using Publish Subscribe in Service Integration Bus in a
    multi Messaging Engine scenario, Heapdump shows large number
    of TickRange instances under GuaranteedTargetStream which may
    lead to unnecessary consumption of memory and considerable CPU
    cycles. One possiblility of having large number of TickRange
    instances is when there are a lot of silence messages which
    are consecutive are not getting consolidated. So it is not
    necessary to have these TickRange instances which belong to
    consecutive silence messages.
    

Problem conclusion

  • Source code has been modified by consolidating the silence
    ticks and sending an acknowledgement for those ticks so that
    all "TickRange" instances will be deleted.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.6.
    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

    PI32705

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-14

  • Closed date

    2015-02-17

  • Last modified date

    2015-02-17

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 8.0

Reference #: PI32705

Modified date: 17 February 2015