IBM Support

PM18530: LOADING A FILE AS INPUT STREAM FAILED

Fixes are available

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

  • If uploading a file as Input stream, it fails with the
    following exception:
    
    <openjpa-1.2.3-SNAPSHOT-r422266:907835 nonfatal general error>
    org.apache.openjpa.persistence.PersistenceException: DB2 SQL
    Error:
    SQLCODE=-204, SQLSTATE=42704, SQLERRMC=ADMINISTRATOR.SOMETABLE,
    DRIVER=3.50.152 {prepstmnt 955594997 INSERT INTO
    ADMINISTRATOR.SOMETABLE
    (content) VALUES (?) [params=(InputStream)
    java.io.ByteArrayInputStream@400c400c]} [code=-204,
    state=42704]SQLCA
    OUTPUT[Errp=SQLNQ1FC, Errd=-2145779603, 0, 0, 0, -10, 0]
    DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704,
    SQLERRMC=ADMINISTRATOR.SOMETABLE, DRIVER=3.50.152
    DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098,
    SQLERRMC=2;-204;42704;ADMINISTRATOR.SOMETABLE, DRIVER=3.50.152
    DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098,
    SQLERRMC=2;-204;42704;ADMINISTRATOR.SOMETABLE, DRIVER=3.50.152
    FailedObject: com.ibm.jpa.MyEntity@74037403
    [5/31/10 11:10:37:468 IST] 0000002e SystemErr     R  at
    org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.jav
    a:4246)
    [5/31/10 11:10:37:468 IST] 0000002e SystemErr     R  at
    org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDic
    tionary.
    java:4211)
    [5/31/10 11:10:37:468 IST] 0000002e SystemErr     R  at
    org.apache.openjpa.jdbc.sql.DB2Dictionary.newStoreException(DB2D
    ictionar
    y.java:504)
    

Local fix

  • Fix has identified and resolve the issue. Work around has also
    been provided and avail via detail to this pmr.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM &#130; &#174; WebSphere &#130; &#174; Applicatio
    *                  Server V7.0.0 who make use of InputStreams  *
    *                  in their JPA Entities and use DB2 as their  *
    *                  DataBase.                                   *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: InputStreams not working from within    *
    *                      JPA Entities on DB2.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    OpenJPA does not properly handle InputStreams when DB2 is
    being used.  This fix adds proper support for using
    InputStreams on DB2.
    With this fix applied, a user may see the following issue when
    using a very large Lob:
    
    java.io.IOException:[jcc][10120][11936][3.51.90] Invalid
    operation: Lob is closed.
    
    This exception is not a bug and has to do with the nature of
    DB2 and the way OpenJPA iterates over a results set.
    That is, JCC will automatically use 'progressive streaming' to
    retrieve the LOB data. With 'progressive streaming', the
    InputStream retrieved must be materialized before the next
    iteration and call to 'next' on the ResultSet.
    
    To work with large Lobs (and thus avoid the IOException) is
    to set fullyMaterializedLobData to true (example to follow),
    so that the JCC will materialize the whole Lob data into
    memory.  For example, when defining the
    openjpa.ConnectionProperties, a user would set the DB2
    properties 'fullyMaterializeLobData' and 'progressive
    Streaming' as follows:
    
    <property name="openjpa.ConnectionProperties"
    value="DriverClassName=com.ibm.db2.jcc.DB2Driver,Url=jdbc:db2://
    localhost:50000/demodb3:fullyMaterializeLobData=true;progressive
    Streaming=NO;,Username=joe,Password=123" />
    

Problem conclusion

  • With this fix, code has been added to properly support the use
    of InputStreams in JPA Entities when the backend is DB2.
    
    The fix for this APAR is currently targeted for
    inclusion in Service Level (Fix Pack) 7.0.0.15 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

    PM18530

  • 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-07-15

  • Closed date

    2010-10-18

  • Last modified date

    2010-10-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM24297

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 #: PM18530

Modified date: 18 October 2010