Fixes are available
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
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. APAR PM62998 is currently targeted for inclusion in 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 number
PM62998
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-20
Closed date
2012-06-20
Last modified date
2012-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM64827 PM70231
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK81738
UP12/10/04 P F210
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 October 2021