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

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?