PM95664: UNEXPECTED RESULTS OF TRANSACTION RECOVERY SERVICE IN RELATION TO HA MGR.

Fixes are available

APAR status

Closed as program error.

Error description

If a member of a CoreGroup is in a problematic state which
cannot be determined as up or down,
services that rely on a defined state of the entire CoreGroup
have to wait until the problematic server is either up or down.
Getting the warning below as:

CWRLS0030W: Waiting for HAManager to activate recovery
processing...

Although distributed transaction recovery is not enabled at all
(it is also not enabled by default), there should be no such
check of the CoreGroup status. Problematic server would be
ignored and the server process could start up.

Local fix

```
No know work around at this time.
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Network Deployment                          *
****************************************************************
* PROBLEM DESCRIPTION: Network issues may cause server         *
*                      restart to hang with message            *
*                      CWRLS0030W even though transaction      *
*                      peer recovery not enabled.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an application server running in a cluster starts the
recovery log service registers with the HA Manager regardless
of whether the cluster has been configured to enable
failover of transaction log recovery.  This is a defensive
measure so that if failover is later enabled but only part
of the cluster is restarted the HA Manager will already have
all cluster members registered.
If the environment is experiencing networking problems then
this registration step may not be possible until the network
issues have been resolved, however the application server will
not start until registration has been successfully performed
and hence not be available to process work.

Problem conclusion

When the application server is not a member of a cluster that
has failover of transaction log recovery enabled it is not
necessary for the recovery log service to register
with the HA Manager.  Such behaviour does however provide a
safe-guard in the event that failover is later enabled and
only a partial restart of the cluster occurs.

In this scenario the default behaviour remains unchanged but the
following JVM System property can be set to a value of 'true'
so that the recovery log service does not register with the
HA Manager:

com.ibm.ws.recoverylog.disableNonHARegistration

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.8 and 8.5.5.2 .  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
PM95664
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-22
Closed date
2013-11-11
Last modified date
2013-11-11

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM98647

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PM95664: UNEXPECTED RESULTS OF TRANSACTION RECOVERY SERVICE IN RELATION TO HA MGR.

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?