Direct links to fixes
APAR status
Closed as program error.
Error description
Updating a WSRR cluster deployment with a fix pack or iFix might fail when the deployment manager and a managed node share the same host.
Local fix
N/A <br/>
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Service and Repository Server Version 7.5 and 8.0. **************************************************************** PROBLEM SUMMARY: When applying a fix pack or iFix to the deployment manager host that also hosts one of the managed nodes, the update might fail during execution of the ANT scripts that update the WAS profiles. The following messages can appear in the <WAS_HOME>/logs/WSRRProfileUpgrade.ant.log: [wsadmin] ADMA5105E: Updates to the server index entry failed for the last node in [wsadmin] com.ibm.websphere.management.exception.AdminException: ADMA5029E: Cluster member <CLUSTER_MEMBER_NAME> that is defined in the cluster configuration for <CLUSTER_NAME> cannot be found as a server. The scripts appear to successfully update the deployment manager profile, but then fail when attempting to update the managed (custom) profile.
Problem conclusion
The update code should only attempt to update deployment manager or stand-alone WAS profiles. Unfortunately, the code used to establish the type of WAS profile did not reliably handle the case when two profiles of different types exist within the same WAS installation on the same host. This code has now been modified to guarantee that it will only attempt to update WSRR on WSRR augmented deployment manager and stand-alone server WAS profiles. This fix is targeted for inclusion in fix pack 2 for WSRR v8.0 and fix pack 3 for WSRR v7.5.
Temporary fix
Comments
APAR Information
APAR number
IV28477
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-09-21
Closed date
2012-09-24
Last modified date
2012-09-26
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
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
26 September 2012