PM33319: OpenJPA cache plug-in not reading 'REMOTE' configuration correctly.

PM37461; 7.1.0.2: FIX THREAD SAFETY ISSUE WHEN RUNNING SAME QUERY CONCURRENTLY
Download WebSphere eXtreme Scale V6.1.0 Fix Pack 5 compatibility fix

APAR status

• Closed as program error.

Error description

• OpenJPA cache plug-in not reading 'REMOTE' configuration
  correctly. REMOTE configuration is being read as EMBEDDED.
  Properties defined in persistence.xml, as shown below may
  be read as EMBEDDED.
  
   <property name="openjpa.DataCache"
  value="com.ibm.websphere.objectgrid.openjpa.ObjectGridDataCache(
  objectGridName=MyGrid,
  objectGridType=REMOTE)"/>
  
         <property name="openjpa.RemoteCommitProvider"
  value="sjvm"/>
  
         <property name="openjpa.QueryCache"
  value="com.ibm.websphere.objectgrid.openjpa.ObjectGridQueryCache
  ()"/>
  

Local fix

• Remove or comment out
  
  property name= openjpa.QueryCache
  
  in the persistence.xml
  
  
  That should not start the embedded container in client jvm
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere eXtreme Scale that   *
  *                  use WebSphere eXtreme Scale as level        *
  *                  2 cache for either OpenJPA or Hibernate     *
  *                  Java ¢â€ž ¢ Persistence API (JPA) providers.
  ****************************************************************
  * PROBLEM DESCRIPTION: If an application is configured to      *
  *                      use REMOTE, the configuration           *
  *                      is ignored and EMBEDDED is used         *
  *                      instead.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The code expects the properties to be in  certain
  order: the DataCache property first, followed by the QueryCache
  property. A problem occurs if the properties are not in this
  order.
  

Problem conclusion

• A future cumulative fix will correct this problem in WebSphere
  eXtreme Scale Version 7.0 and 7.1.
  

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

  XD EXTREME SCAL

• Fixed component ID

  5724J3402

Applicable component levels

• R700 PSY

     UP

• R710 PSY

     UP