Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
APAR status
Closed as program error.
Error description
Two replicas are configured in an inconsistent manner that will prevent them from working together. replica A defines itself as the entire replica set and isInitial=true replica B defines itself as the entire replica set and isInitial=true Now the user wants to join these two. The problem is, both of them think they are the original replica set. The system is in a confused state then, where it has 2 replicas claiming to be the authoritative replica set, but only one can be.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile 8.5.5 collective * * controller. * **************************************************************** * PROBLEM DESCRIPTION: Joining together replicas created * * separately creates a failure as the * * configuration of them is incompatible * * due to both indicating * * isInitialReplicaSet true. * **************************************************************** * RECOMMENDATION: * **************************************************************** Joining together replicas created separately creates a failure as the configuration of them is incompatible due to both indicating isInitialReplicaSet true. Both of the replicas will assume they contain the master information for the new replica set, where only one can have this master information, so the configuration is not valid.
Problem conclusion
Added the use of a message to indicate the incompatible configuration of the collective repository replicas. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.1. 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
PM92785
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-11
Closed date
2013-07-29
Last modified date
2013-07-29
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
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
12 January 2022