PM70231: UNHANDLED EXCEPTION THROWN FROM WITHIN AN EXTERNALIZER METHOD CAUSES INCORRECT/INCOMPLETE SQL TO BE GENERATED/EXECUTED.

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• The exception is thrown due to an incorrect generation of the
  SQL statement with a missing WHERE clause for the case when an
  exception occurs in an Externalizer method.
  
  This problem is to include the fix for OPENJPA-2095
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0.0, V8.0.0 and V8.5.0 who make   *
  *                  use of a JPA Externalizer method.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unhandled exception thrown from         *
  *                      within an Externalizer method causes    *
  *                      incorrect/incomplete SQL to be          *
  *                      generated/executed.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an Externalizer method (i.e. the method listed in the
  @Externalizer) causes/throws an exception, OpenJPA generates,
  and executes, incorrect/incomplete SQL. To better explain,
  please take the following test code snippets.
  First, take this entity:
  @Entity
  public class TestItem implements Serializable {
  @org.apache.openjpa.persistence.Persistent
  @org.apache.openjpa.persistence.Externalizer("check")
  private TestExternal ext;
  .....
  And take the following class TestExternal:
  public static class TestExternal {
  .....
  public String check() throws Exception {
  throw new PersistenceException("test exception
  externalizer");
  .....
  With this code, take the case where a persist of a new
  TestItem occurs, and the case where we update an existing one.
  When a new TestItem is created and persisted, OpenJPA
  generates and executes the following SQL:
  INSERT INTO TESTITEM (data) VALUES (?)
  However, this SQL should be generated:
  INSERT INTO TESTITEM (iref, data, ext, name) VALUES (?, ?, ?,
  ?)
  When an update is made to an existing TestItem, OpenJPA
  generates, and executes, the following SQL:
  UPDATE TESTITEM SET data = ?
  However, this SQL should be generated:
  UPDATE TESTITEM SET data = ? WHERE iref = ?
  Because an unhandled exception is thrown by the Externalizer
  method, the transaction will be rolled back. However, if the
  SQL were to actually commit, every row in TestItem would be
  updated with the value in 'data'. Furthermore, in the case
  where there are hundreds/thousands of rows in the DB, the
  execution of the SQL may take a long time to complete and will
  maintain a lock on the TestItem table during the execution,
  possibly locking out other clients.
  

Problem conclusion

• With this fix, code has been added to ensure that OpenJPA
  properly handles an exception thrown from an Externalizer
  method.
  
  The fix for this APAR is currently targeted for
  inclusion in Service Levels (Fix Packs) 7.0.0.25, 8.0.0.5 and
  
  8.5.0.1 of WebSphere Application Server versions 7.0.0, 8.0.0
  and 8.5.0.
  
  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:

  PM62998

• 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