Fixes are available
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
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
Document Information
Modified date:
28 April 2022