IBM Support

PI21685: OutOfMemoryError java.util.concurrent.LinkedBlockingQueue owned by BBDescriptionManager$UpdateThread

Fixes are available

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
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
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
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

  • OutOfMemoryError is running in
    BBDescriptionManager.$UpdateThread.
    
    3XMTHREADINFO      "Thread-15" J9VMThread:0x0000000010DFFF00,
    j9thread_t:0x00007F3880CDCC70,
    java/lang/Thread:0x0000000000BC8328,
    state:R, prio=5
    3XMTHREADINFO1            (native thread ID:0x3B49, native
    priority:0x5,
    native policy:UNKNOWN)
    3XMTHREADINFO2            (native stack address range
    from:0x00007F3886F4A000, to:0x00007F3886F8B000, size:0x41000)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    java/util/Arrays.copyOfRange(Arrays.java:4138(Compiled Code))
    4XESTACKTRACE                at
    java/util/Arrays.copyOf(Arrays.java(Compiled Code))
    4XESTACKTRACE                at
    java/io/ByteArrayOutputStream.write(ByteArrayOutputStream.java:1
    06(Compi
    led Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/Compressor.decompress(Compressor.java:191(Com
    piled
    Code))Page 37 of 41
    4XESTACKTRACE                at
    com/ibm/ws/cluster/topography/DescriptionManagerA.divideMultiple
    Inputs(D
    escriptionManagerA.java:700(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/topography/DescriptionManagerA.update(Descrip
    tionMana
    gerA.java:414(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r.common
    Update(BBDescriptionManager.java:882(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r.access
    $400(BBDescriptionManager.java(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r$Update
    Thread.performUpdate(BBDescriptionManager.java:943(Compiled
    Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r$Update
    Thread.run(BBDescriptionManager.java:922)
    
    BBDescriptionManager$UpdateThread lacks a try/catch for this
    type of
    exception so the thread running this code terminates.  However
    BBDescriptionManager continues to queue work to the
    LinkedBlockingQueue
    associated with this thread.  Thus the LinkedBlockingQueue grows
    indefinitely causing subsequent memory problems.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: BBDescriptionManager continues to       *
    *                      queue work elsewhere after              *
    *                      OutOfMemoryError                        *
    *                      causing indefinite queue growth.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After the OutOfMemoryError is thrown, the related thread
    terminates
    but BBDescriptionManager continues to queue work on
    LinkedBlockingQueue. This queue will continue to grow
    indefinitely
    as BBDescriptionManager processes work, causing further
    memory problems. The following thread failure is observed:
    OutOfMemoryError is running in
    BBDescriptionManager.$UpdateThread.
    3XMTHREADINFO      "Thread-15" J9VMThread:0x0000000010DFFF00,
    j9thread_t:0x00007F3880CDCC70,
    java/lang/Thread:0x0000000000BC8328,
    state:R, prio=5
    3XMTHREADINFO1            (native thread ID:0x3B49, native
    priority:0x5,
    native policy:UNKNOWN)
    3XMTHREADINFO2            (native stack address range
    from:0x00007F3886F4A000, to:0x00007F3886F8B000, size:0x41000)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    java/util/Arrays.copyOfRange(Arrays.java:4138(Compiled Code))
    4XESTACKTRACE                at
    java/util/Arrays.copyOf(Arrays.java(Compiled Code))
    4XESTACKTRACE                at
    java/io/ByteArrayOutputStream.write(ByteArrayOutputStream.java:1
    06(Compi
    led Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/Compressor.decompress(Compressor.java:191(Com
    piled
    Code))Page 37 of 41
    4XESTACKTRACE                at
    com/ibm/ws/cluster/topography/DescriptionManagerA.divideMultiple
    Inputs(D
    escriptionManagerA.java:700(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/topography/DescriptionManagerA.update(Descrip
    tionMana
    gerA.java:414(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r.common
    Update(BBDescriptionManager.java:882(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r.access
    $400(BBDescriptionManager.java(Compiled Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r$Update
    Thread.performUpdate(BBDescriptionManager.java:943(Compiled
    Code))
    4XESTACKTRACE                at
    com/ibm/ws/cluster/propagation/bulletinboard/BBDescriptionManage
    r$Update
    Thread.run(BBDescriptionManager.java:922)
    

Problem conclusion

  • A try/catch was added to handle OutOfMemoryError so the thread
    does not terminate.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.37, 8.0.0.10, 8.5.5.4 .  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

    PI21685

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-09

  • Closed date

    2014-08-25

  • Last modified date

    2014-08-25

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

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 #: PI21685

Modified date: 25 August 2014