IBM Support

PM91049: CHECK XSI:NIL ATTRIBUTES DURING EAGER LOADING.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MTOM Export with xs:nil=true does not work. Getting the error
    below:
    
    java.io.IOException: Error reading XML
    at
    
    com.ibm.ws.box.service.BOXMLSerializerImpl.load(BOXMLSerializer
    Impl.java:161)
    at
    com.ibm.ws.box.service.BOXMLSerializerSPIImpl.readXMLDocumentWi
    thOptions(BOXMLSerializerSPIImpl.java:58)
    at
    com.ibm.ws.bo.delegate.BOXMLSerializerDelegate.readXMLDocumentW
    ithOptions(BOXMLSerializerDelegate.java:104)
    at com.mytest.PMR139114.testReadXMLDocument(PMR139114.java:68)
    at com.mytest.PMR139114.main(PMR139114.java:32)
    
    Caused by: java.io.IOException: java.lang.NumberFormatException:
    For
    input string: ""
    at
    com.ibm.ws.box.util.SerializerUtil$2.run(SerializerUtil.java:184
    )
    at
    java.security.AccessController.doPrivileged(AccessController.ja
    va:251)
    at
    com.ibm.ws.box.util.SerializerUtil.privilegedLoad(SerializerUti
    l.java:178)
    

Local fix

  • No known work around.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: During eager loading we are not         *
    *                      checking for the xsi:nil attribute      *
    *                      before constructing an                  *
    *                      InvalidEmptyCData.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During eager loading, we identify empty CData types with
    xsi:nill attributes as an invalid CData type. This caused a BO
    failure as described in the "Error Description".
    

Problem conclusion

  • The algorithm has now been corrected to not flag empty CData
    types as invalid CData.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.8 and 8.5.5.1.  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

    PM91049

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-06-13

  • Closed date

    2013-07-10

  • Last modified date

    2013-10-01

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 January 2022