Fixes are available
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
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
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
APAR status
Closed as program error.
Error description
Admin Console cannot determine status of some of the Node Agents after remote clone migration completes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WASPostUpgrade Clone process * **************************************************************** * PROBLEM DESCRIPTION: The NODE_DISCOVERY_ADDRESS of certain * * Federated nodes are not being * * migrated properly. The port is set * * to 0. * **************************************************************** * RECOMMENDATION: * **************************************************************** A clone migration temporarily sets the port for the NODE_DISCOVERY_ADDRESS for all federated nodes to 0 during the Deployment Manager migration process. These are reset back to a valid port as each federated node is migrated. However, under certain conditions these are not being handled correctly and are left as zero. This causes the Dmgr and nodeagent to fail to communicate status properly.
Problem conclusion
Added fix to code to properly determine owning node of the serverindex.xml being migrated to see if it matches the actual node being migrated. This allows the NODE_DISCOVERY_ADDRESS's port number to be set correctly. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.10. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Fix the NODE_DISCOVERY_ADDRESS for problem node in the Dmgr by hand after migration and sync it to the Federated node. This should be done before starting the nodeagent.
Comments
APAR Information
APAR number
PH02468
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
2018-09-07
Closed date
2018-10-15
Last modified date
2018-10-15
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
R900 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":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021