Fixes are available
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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
WAS 9.0.0.10 on Linux AdminTask.moveClusterToCoreGroup, which is used to move servers between core groups, fails to update the hamanagerservice.xml template file carried by dynamic clusters: [WAS_PROFILE_ROOT]/config/cells/[cellName]/dynamicclusters/[dcNa me]/servers/[dcName]/hamanagerservice.xml While the dynamic cluster members themselves are moved to the expected core group, the value of the core group name in the dynamic cluster's server-template (hamanagerservice.xml) does not get updated. This can cause issues when the dynamic cluster scales up/down or when another modification is made to that dynamic cluster's server template files.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server with * * dynamic clusters associated with old * * core group. * **************************************************************** * RECOMMENDATION: * **************************************************************** The dynamic cluster's server template is not updated to a new core group when the dynamic cluster members are moved. The coreGroupName within the [WAS_PROFILE_ROOT]/config/cells/ [cellName]/dynamicclusters/[dynamic cluster name]/servers/ [dynamic cluster name]/hamanagerservice.xml file will contain the original coreGroupName for the dynamic cluster. This may cause problems with dynamic cluster scaling or future template updates.
Problem conclusion
Code has been modified to update the dynamic cluster's server template's coreGroupName value to reflect the new core group when the cluster is moved to a new core group. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.16. 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
PH08584
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-14
Closed date
2019-02-28
Last modified date
2019-02-28
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
28 April 2022