IBM Support

JR52630: CONCURRENT PROBLEMS OCCUR WHEN YOU SERIALIZE A BUSINESS OBJECT IN EAGER PARSING MODE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During your load test, when multiple threads serialize the
    same business object to XML, the serialization might fail. You
    see the following exception in the FFDC log file:
    
    org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsExce
    ption
    SourceId:org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfB
    oundsException caught trying to serialize BO
    {http://sample/nameSpace, SampleBO} ProbeId:214
    org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsExce
    ption: index=0, size=0
     at
    org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:512)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.writeTopObjects(XMLSa
    veImpl.java:658)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.
    java:553)
     at
    org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java
    :233)
     at
    com.ibm.ws.bo.bomodel.util.BOResourceImpl.doSave(BOResourceImpl.
    java:107)
     at
    org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceIm
    pl.java:993)
     at
    com.ibm.ws.bo.bomodel.util.SerializerUtil$1.run(SerializerUtil.j
    ava:144)
     at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:327)
     at
    com.ibm.ws.bo.bomodel.util.SerializerUtil.privilegedSave(Seriali
    zerUtil.java:135)
     at
    com.ibm.ws.bo.service.BOXMLSerializerImpl.save(BOXMLSerializerIm
    pl.java:575)
    
    This error occurs only in eager parsing mode.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Process Server                *
    *                  IBM Business Process Manager (BPM)          *
    *                  Advanced                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: During your load test, when multiple    *
    *                      threads serialize the same business     *
    *                      object to XML, the serialization        *
    *                      might fail. You see the following       *
    *                      exception in the FFDC log file:         *
    *                      org.eclipse.emf.common.util.BasicEList$ *
    *                      BasicIndexOutOfBoundsException          *
    *                      SourceId:org.eclipse.emf.common.util.Ba *
    *                      sicEList$BasicIndexOutOfBoundsException *
    *                      caught trying to serialize BO           *
    *                      {http://sample/nameSpace, SampleBO}     *
    *                      ProbeId:214                             *
    *                      org.eclipse.emf.common.util.BasicEList$ *
    *                      BasicIndexOutOfBoundsException:         *
    *                      index=0, size=0                         *
    *                      at                                      *
    *                      org.eclipse.emf.common.util.BasicEList. *
    *                      get(BasicEList.java:512)                *
    *                      at                                      *
    *                      org.eclipse.emf.ecore.xmi.impl.XMLSaveI *
    *                      mpl.writeTopObjects(XMLSaveImpl.java:65 *
    *                      8)                                      *
    *                      at                                      *
    *                      org.eclipse.emf.ecore.xmi.impl.XMLSaveI *
    *                      mpl.traverse(XMLSaveImpl.java:553)      *
    *                      at                                      *
    *                      org.eclipse.emf.ecore.xmi.impl.XMLSaveI *
    *                      mpl.save(XMLSaveImpl.java:233)          *
    *                      at                                      *
    *                      com.ibm.ws.bo.bomodel.util.BOResourceIm *
    *                      pl.doSave(BOResourceImpl.java:107)      *
    *                      at                                      *
    *                      org.eclipse.emf.ecore.resource.impl.Res *
    *                      ourceImpl.save(ResourceImpl.java:993)   *
    *                      at                                      *
    *                      com.ibm.ws.bo.bomodel.util.SerializerUt *
    *                      il$1.run(SerializerUtil.java:144)       *
    *                      at                                      *
    *                      java.security.AccessController.doPrivil *
    *                      eged(AccessController.java:327)         *
    *                      at                                      *
    *                      com.ibm.ws.bo.bomodel.util.SerializerUt *
    *                      il.privilegedSave(SerializerUtil.java:1 *
    *                      35)                                     *
    *                      at                                      *
    *                      com.ibm.ws.bo.service.BOXMLSerializerIm *
    *                      pl.save(BOXMLSerializerImpl.java:575)   *
    *                      This error occurs only in eager         *
    *                      parsing mode.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Because business object serialization is not thread safe in
    eager parsing mode, when multiple threads serialize the same
    business object to XML the concurrent problem might occur.
    

Problem conclusion

  • A fix is available for IBM WebSphere Process Server V7.0.0.5
    and IBM BPM V7.5.1.2, V8.0.1.3, V8.5.0.1, V8.5.5.0, and
    V8.5.6.0 that synchronizes the business object when
    serializing it to avoid the multiple-threads issue.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52630:
    
    1. Select IBM WebSphere Process Server or IBM Business Process
    Manager Advanced from the product selector, the installed
    version to the fix pack level, and your platform, and then
    click Continue.
    2. Select APAR or SPR, enter JR52630, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR52630

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-02-25

  • Closed date

    2015-04-22

  • Last modified date

    2015-04-22

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R750 PSY

       UP

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 April 2015