IBM Support

PM09761: MISSING PARAMETERS WHEN BATCHLIMIT=-1

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In WebSphere Application Server 7.0.0.7 when batchLimit=-1 ,
    the key debugging parameters in the "[params" statement are
    missing as opposed to when the batchLimit=1.
    

Local fix

  • fix provided.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM ‚ ® WebSphere ‚ ® Applicatio
    *                  Server V7.0.0 who make use of the Java      *
    *                  Persistence API (JPA) batchLimit property.  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When batchLimit=-1 or >1 and an         *
    *                      exception is caused, the params and     *
    *                      'FailedObject' are missing from the     *
    *                      resultant exception.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Exception reporting is different depending on the value of
    batchLimit. To describe and demonstration this problem, lets
    take the following Entitiy:
    
    @Entity
    public class Ent1 {
     ‚   ‚   ‚   ‚  @Id
     ‚   ‚   ‚   ‚  private int pk;
     ‚   ‚   ‚   ‚  private String name;
    .....
    }
    
    As a test, lets assume that we have an Ent1 with pk=200
    already defined in the DB and our test will attempt to create
    and persist another Ent1 with pk=200 (i.e. a duplicate key).
    In so doing we get the following exception as indicated by the
    batchLimit settings:
    
    batchLimit=0 or batchLimit=1
    Caused by: <openjpa-1.2.2-SNAPSHOT-r422266:889769M nonfatal
    store error>
    org.apache.openjpa.persistence.EntityExistsException: The
    statement was aborted because it would have caused a duplicate
    key value in a unique or primary key constraint or unique
    index identified by 'SQL100301111328870' defined on 'ENT1'.
    {prepstmnt 33038075 INSERT INTO Ent1 (pk, name) VALUES (?, ?)
    [params=(int) 200, (String) twohundred]} [code=20000,
    state=23505]
    FailedObject: Ent1@19d0e0b
    
    
    when batchLimit=-1 or >1
    Caused by: <openjpa-1.2.2-SNAPSHOT-r422266:889769M nonfatal
    store error>
    org.apache.openjpa.persistence.EntityExistsException: The
    statement was aborted because it would have caused a duplicate
    key value in a unique or primary key constraint or unique
    index identified by 'SQL100301111328870' defined on 'ENT1'.
    FailedObject: prepstmnt 33038075 INSERT INTO Ent1 (pk, name)
    VALUES (?, ?)
    [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedS
    tatement]
    
    
    Notice that when batchLimit=[0,1], the exception lists the
    prepared statement used along with the params which caused the
    failure, as well as the 'FailedObject'. Furthermore, calling
    'getFailedObject' on the resultant exception will give the
    caller the entity which caused the failure. In contrast, when
    batchLimit=-1 or a value greater than 1, we can see that the
    exception message is missing the prepared statement info,
    however, it is presented in the 'FailedObject'. The params are
    also missing from the prepared statement. A call to
    'getFailedObject' on the resultant exception will NOT give the
    caller the entity which caused the exception.
    

Problem conclusion

  • With this fix, code will be added to ensure that the params
    and 'FailedObject' are included when an exception occures
    during batch processing where batchLimit=1 or >1.
    
    The fix for this APAR is currently targeted for inclusion in
    Service Level (Fix Pack) 7.0.0.13 of WebSphere Application
    Server version 7.0.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

    PM09761

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-11

  • Closed date

    2010-04-07

  • Last modified date

    2010-07-19

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM09761

Modified date: 19 July 2010