PM03224: "CWRLS0030W: WAITING FOR HAMANAGER TO ACTIVATE RECOVERY PROCESSING" CAUSED BY HANG IN CSCOPE RECOVERY

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: WebSphere Application Server V6.1 Fix Pack 33 for AIX
6.1.0.33: WebSphere Application Server V6.1 Fix Pack 33 for HP-UX
6.1.0.31: WebSphere Application Server V6.1 Fix Pack 31 for AIX
6.1.0.31: WebSphere Application Server V6.1 Fix Pack 31 for HP-UX
6.1.0.31: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: WebSphere Application Server V6.1 Fix Pack 35 for AIX
6.1.0.35: WebSphere Application Server V6.1 Fix Pack 35 for HP-UX
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
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
6.1.0.37: WebSphere Application Server V6.1 Fix Pack 37
6.1.0.39: WebSphere Application Server V6.1 Fix Pack 39
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: WebSphere Application Server V6.1 Fix Pack 41
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: WebSphere Application Server V6.1 Fix Pack 43
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: WebSphere Application Server V6.1 Fix Pack 45
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During startup of a HA Manager-enabled application server, the
    CScope (Compensation Service) recovery, which runs on one
    thread, is told to stop by the deactivateMember() method call,
    which runs on a separate thread.
    
    It is possible that a hang condition can occur on the thread
    which is running the CScope recovery.  This can result in
    multiple instances of the following message and the application
    server failing to start:
    
    
    CWRLS0030W: Waiting for HAManager to activate recovery
    processing for local WebSphere server
    
    
    This fix will allow the peer recovery thread (the one handling
    the deactivateMember() call) to correctly communicate to the
    CScope recovery thread that it should complete immediately.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server V6.1   *
    *                  and V7.0 users of Compensation Service.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message "CWRLS0030W: Waiting for        *
    *                      HAManager to Activate Recovery          *
    *                      Processing" appeared and the server     *
    *                      failed to start.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Message "CWRLS0030W: Waiting for HAManager to Activate
    Recovery Processing" appeared many times in SystemOut.log and
    the server failed to start. The server was defined in a
    cluster that had been configured with "Enable failover of
    transaction log recovery" selected.
    Another server in the cluster was performing recovery on
    behalf of the failed server, but did not halt processing when
    told to do so by the HAManager. This meant that the server
    being restarted could not complete recovery and so was
    prevented from starting fully.
    The root cause was that the recovery being performed for a
    peer server by the Compensation Service did not test in
    sufficient places in the code to determine that it should halt
    processing and relinquish control of the recovery logs to the
    peer server.
    

Problem conclusion

  • The Compensation Service RecoveryManager has been changed to
    provide additional checks to determine if recovery should
    terminate due to the peer server being started.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.31 and 7.0.0.11.  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

    PM03224

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-10

  • Closed date

    2010-01-20

  • Last modified date

    2010-01-20

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
General

Software version:

6.1

Reference #:

PM03224

Modified date:

2010-01-20

Translate my page

Machine Translation

Content navigation