PI07368: NullPointerException exception during deserialization of hashtable may occur if hashtable was modified during

APAR status

• Closed as program error.

Error description

• During serialization with XDF the Hashtable, Vector and Stack
  collections, the objects were not locked by the serialization
  process and as a result other threads would have access to
  manipulate the collections if the application had a reference
  to the object.  A NullPointerException is one of the errors,
  but other errors such as seeing inconsistent data in the
  collection ( due to other threads changing it ) may be possible.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Applications that have COPY_TO_BYTES maps   *
  *                  with                                        *
  *                  IBM eXtremeIO (XIO) and sharing access to   *
  *                  Vector, Hashtable or Stack collections in   *
  *                  multiple threads.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: A NullPointerException occurs during    *
  *                      deserialization of the Hashtable, if    *
  *                      the                                     *
  *                      Hashtable was modified during           *
  *                      serialization.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During serialization with eXtreme data format (XDF) of the
  Hashtable, Vector and Stack
  collections, the objects were not locked by the serialization
  process. As a result, other threads have access to
  manipulate the collections, if the application had a reference
  to the object.  A NullPointerException is one error that might
  occur. Other errors, such as inconsistent data in the
  collection due to other threads changing the data, might also
  occur.
  

Problem conclusion

• Corrected the logic to hold a lock on these collection types.
  Other threads are blocked from making changes during the
  serialization process.
  

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