IBM Support

PM33312: OUTOFMEMORY DURING STARTUP OF DEFAULT MESSAGING PROVIDER MESSAGING ENGINE

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
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

  • Websphere Application Server v6.1.x Service Integration Bus
    Messaging Engine takes approximately 50 minutes to start.
    Also during the messaging engine failover, hung threads
    messages(WSVR0605W) and CPU starvation(HMGR0152W)
    messages are logged in the SystemOut.log. In some cases it
    may even lead to OutOfMemory errors.
    
    Javacores show HA manager callback thread is in blocked
    state waiting on the SIB Action thread .
    
    HAManager.thread.pool :
    at com/ibm/ws/sib/admin/impl/HAManagerMessagingEngineImpl.
      membershipChanged(HAManagerMessagingEngineImpl.java:653)
    at com/ibm/ws/hamanager/impl/HAGroupImpl.doMembership
      Changed(HAGroupImpl.java:815)
    at com/ibm/ws/hamanager/impl/HAGroupImpl$HAGroupUserCallback.
      doCallback(HAGroupImpl.java:1361)
    at com/ibm/ws/hamanager/impl/Worker.run(UserCallbacks.java:
      288(Compiled Code))
    at com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:
      1497(Compiled Code))
    
    SIB Activation Thread :
     at java/util/Collections$UnmodifiableMap$UnmodifiableEntrySet
       $1.next(Collections.java:1362(Compiled Code))
    at java/util/Collections$UnmodifiableMap$UnmodifiableEntrySet
      $1.next(Collections.java:1364(Compiled Code))
    at com/ibm/ws/cluster/topography/KeyRepositoryImpl.exportTo
      Stream(KeyRepositoryImpl.java:174(Compiled Code))
    at com/ibm/ws/cluster/topography/IdentityMapImpl.writeOut
      (IdentityMapImpl.java:394(Compiled Code))
    at com/ibm/ws/cluster/topography/IdentityMapImpl.exportTo
      Stream(IdentityMapImpl.java:345(Compiled Code))
    at com/ibm/ws/cluster/topography/DescriptionManagerA.getData
      tFromDescription(DescriptionManagerA.java:757(Compiled Code))
    at com/ibm/ws/cluster/topography/DescriptionManagerA.publish
      (DescriptionManagerA.java:324(Compiled Code))
    at com/ibm/websphere/cluster/topography/DescriptionA.update
      Memento(DescriptionA.java:159(Compiled Code))
    at com/ibm/ws/cluster/topography/IdentityMapImpl.putAll
      (IdentityMapImpl.java:208)
    at com/ibm/ws/cluster/service/ClusterMemberServiceImpl.
      addToActiveClusterSet(ClusterMemberServiceImpl.java:704
      (Compiled Code))
    at com/ibm/ws/cluster/service/ClusterMemberServiceImpl.
      joinCluster(ClusterMemberServiceImpl.java:526(Compiled
      Code))
    at com/ibm/ws/sib/trm/wlm/server/Join.join(Join.java:211
      (Compiled Code))
    at com/ibm/ws/sib/trm/wlm/server/Join.toDestination(Join.
      java:184(Compiled Code))
    at com/ibm/ws/sib/trm/wlm/server/DestEventQueue.register
      Destination(DestEventQueue.java:368(Compiled Code))
    at com/ibm/ws/sib/trm/wlm/server/DestEventQueue.deQueue
      DestinationEvents(DestEventQueue.java:649)
    at com/ibm/ws/sib/trm/wlm/server/Manager.start(Manager.
      java:135)
    at com/ibm/ws/sib/trm/TrmMeMainImpl.start(TrmMeMainImpl.
      java:235)
    at com/ibm/ws/sib/admin/impl/JsMessagingEngineImpl.start
      (JsMessagingEngineImpl.java:543)
    at com/ibm/ws/sib/admin/impl/HAManagerMessagingEngineImpl.
      activate(HAManagerMessagingEngineImpl.java:978)
    at com/ibm/ws/sib/admin/impl/JsActivationThread.run
      (JsActivationThread.java:92)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: HA Manager callback thread is held      *
    *                      for duration of messaging engine        *
    *                      startup.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the HA Manager requests a messaging engine to start via
    the HA Manager callback thread, the messaging engine would keep
    hold of that thread for the duration of the startup. This can
    cause an OutOfMemory error as HA Manager has only limited
    capacity to process any further work.
    

Problem conclusion

  • The code has been altered to ensure that the messaging engine
    startup code will only hold the HA Manager callback thread as
    required, not for the duration of startup.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.39.  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

    PM33312

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-22

  • Closed date

    2011-03-31

  • Last modified date

    2011-03-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

    PLAT MSG COM

  • Fixed component ID

    620600101

Applicable component levels

  • R200 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.1

Reference #: PM33312

Modified date: 31 March 2011