PI12307: ConcurrentModificationException exceptions in FFDC incorrectly being created.

APAR status

• Closed as program error.

Error description

• For applications running grids with XIO and COPY_TO_BYTES maps
  that are using the Dynacache plugin or that are modifying
  collections while trying to serialize the object containing the
  collection a ConcurrentModificationException will be thrown.
  
  In some situations it is normal for a
  ConcurrentModificationException to be thrown if the application
  is modifying a collection while another thread is attempting to
  serialize the value.  The thread performing the serialization
  will report an exception and this is normal.  The XDF code will
  also generate FFDC records for some scenarios but it should not
  be creating an FFDC in this situation.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Applications running grids with XIO and     *
  *                  COPY_TO_BYTES maps that are using the       *
  *                  Dynacache plugin or that are modifying      *
  *                  collections while trying to serialize the   *
  *                  object containing the collection.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: ConcurrentModificationException FFDC    *
  *                      is created in the file system when a    *
  *                      collection is serialized.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some situations it is normal for a
  ConcurrentModificationException to be thrown if the
  application is modifying a collection while another thread is
  attempting to serialize the value.  The thread performing the
  serialization will report an exception and this is normal.
  The XDF code will also generate FFDC records for some
  scenarios, but it should not be creating an FFDC in this
  situation since this becomes noise for the system administrator
  

Problem conclusion

• Added logic to avoid the logging of the
  FFDC when trace debug is disabled.  When trace is enabled, the
  FFDC will be generated in this situation in order to aid with
  debugging unexpected ConcurrentModificationException errors.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP