PM89377: CONCURRENCY ISSUE IN APPLICATIONCONFIGURATOR.

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

• ApplicationConfigurator used ConcurrentMaps to permit
  simultaneous access to data. But the ConcurrentMap contains
  unprotected ArrayLists, and is at risk of iterating over one
  while modifying it. When the unfortunate timing occurred, our
  regression tests were reporting a FileNotFoundException
  reported during WABTestUtils.getHTTPResponse(). The problem
  could also arise in normal (non-testing) operation.
  
  Timing-dependent, intermittent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Intermittent FileNotFoundException      *
  *                      failures during application             *
  *                      configuration.                          *
  ****************************************************************
  * RECOMMENDATION:  Apply this APAR                             *
  ****************************************************************
  One of the datastructures we use to hold application
  configuration data was less than perfectly reentrant. Under
  certain circumstances, applying a configuration change while
  the current configuration was being read could result in bad
  data being retrieved.
  This failure mode would be very uncommon under normal use, but
  was exposed during intensive testing.
  

Problem conclusion

• The datastructure has been modified so it not only uses a
  ConcurrentMap, but uses concurrently-accessible objects within
  that map.
  
  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