PM75886: OPENJPA CLASS COLLISION WITH PREVIOUS APP LIFECYCLE

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• After application restart it is possible for Classes from the
  application's previous lifecycle to be inapproprately processed
  should something prevent the stopped application classloader
  from being garbage collected.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: OpenJPA's metadata repository must not  *
  *                      process classes from other              *
  *                      applications.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  By design, OpenJPA's PCRegistry maintains a static list of
  persistent capable types where entries are registered when
  such a type is first loaded, and removed when the type is
  unloaded. This list, and updates to the list, are dispatched
  to the metadata repository of active EntityManager instances.
  A problem was encountered with the logic involved in the first-
  pass processing of the registered classes that resulted in an
  unexpected Exception that caused JPA operations to fail.
  

Problem conclusion

• The first-pass processing now first validates that each type
  contained in the dispatch message belong to the application
  before undergoing any further processing.  This removes any
  risk of error involved with the metadata repository
  inappropriately instantiating a class belonging to another
  application.
  
  This updated processing behavior must be enabled by
  configuring a Compatibility option in the persistence unit,
  for example:
  
  <property name="openjpa.Compatibility"
            value="FilterPCRegistryClasses=true"/>
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.6 and 8.5.0.2.  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:

  PM80437

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP