PM93102: RECONFIGURING REPLICAS IN RAPID SUCCESSION LEADS TO SECOND RECONFIG FAILING.

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

• When the replicas of a set are modified one after another,
  there may be an error.  By modified, this means replicas are
  added or removed from the set.
  
  The following message appears in the FRAPPE trace:
  
  testConfigRelevance : Config will not be proposed due to:
  IRRELEVANT_CONFIG_ID
  
  This is because when the second reconfiguration request was
  processed, it was not up-to-date with the one that had already
  occurred.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile version 8.5.5        *
  *                  collective repository.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When more than one request to           *
  *                      reconfigure the replica set is made     *
  *                      in rapid succession, the second         *
  *                      request fails to complete.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When more than one request to reconfigure the replica set is
  made in rapid succession, the second request fails to complete.
  This is because when the second reconfiguration request was
  processed, it was not up-to-date with the one that had already
  occurred.
  

Problem conclusion

• The code was modified so that the second request uses more
  recent information when it is processed.  This will result in
  the command succeeding, where previously it failed.
  
  
  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 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