IBM Support

JR62785: INVOKING AN ADVANCED INTEGRATION SERVICE (AIS) WITH AN SCA BINDING COULD FAIL INTERMITTENTLY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • When there are heavy loads for an Advanced Integration service
    (AIS) that has an SCA binding and you set the business object
    parsing mode as Eager, you could get the following error:
    
    An error occurred while parsing native data: The error message
    is: java.lang.RuntimeException: Error reading XML.
    Caused By: java.lang.RuntimeException: Error reading XML
    at
    com.ibm.ws.sca.internal.message.impl.SCANativeDataHolder.getHead
    ers(SCANativeDataHolder.java:325)
    at
    com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.getSafeH
    eadersEx(ManagedMessageImpl.java:1086)
    ... 80 more
    Caused by: java.lang.RuntimeException: Error reading XML
    at
    com.ibm.ws.bo.service.BOXMLSerializerImpl.load(BOXMLSerializerIm
    pl.java:377)
    at
    com.ibm.ws.bo.service.BOXMLSerializerImpl.readXMLDocumentWithOpt
    ions(BOXMLSerializerImpl.java:650)
    at
    com.ibm.ws.sca.internal.sdo.impl.BOXMLSerializerDelegatorImpl.lo
    ad(BOXMLSerializerDelegatorImpl.java:96)
    at
    com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl$1.run(XMLFil
    eServiceImpl.java:576)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:694)
    at
    com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.load(XMLFile
    ServiceImpl.java:573)
    at
    com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.load(XMLFile
    ServiceImpl.java:318)
    at
    com.ibm.wsspi.sca.sdo.XMLFileService$1.load(XMLFileService.java:
    111)
    at
    com.ibm.ws.sca.internal.message.impl.EMFMessageSerializer.load(E
    MFMessageSerializer.java:68)
    at
    com.ibm.ws.sca.internal.message.impl.SCAMessageNativeDataHolder.
    performHeaderDeserialization(SCAMessageNativeDataHolder.java:123
    )
    at
    com.ibm.ws.sca.internal.message.impl.SCANativeDataHolder.getHead
    ers(SCANativeDataHolder.java:318)
    ... 81 more
    Caused by: java.lang.NullPointerException
    at
    org.eclipse.emf.ecore.util.EcoreEList.resolveProxy(EcoreEList.ja
    va:192)
    at
    org.eclipse.emf.ecore.util.EcoreEList.resolve(EcoreEList.java:15
    2)
    at
    org.eclipse.emf.ecore.util.EObjectContainmentWithInverseEList$Re
    solving.resolve(EObjectContainmentWithInverseEList.java:94)
    at
    org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:514)
    at
    org.eclipse.emf.ecore.util.BasicExtendedMetaData$EPackageExtende
    dMetaDataImpl.getType(BasicExtendedMetaData.java:2090)
    at
    org.eclipse.emf.ecore.util.BasicExtendedMetaData.getType(BasicEx
    tendedMetaData.java:115)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getType(XMLHelperIm
    pl.java:812)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject(XMLHel
    perImpl.java:832)
    at
    com.ibm.ws.bo.bomodel.util.BOXMLHandler.createObjectFromFactory(
    BOXMLHandler.java:1706)
    at
    com.ibm.ws.bo.bomodel.util.BOXMLHandler.validateCreateObjectFrom
    Factory(BOXMLHandler.java:1636)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTypeNa
    me(XMLHandler.java:1871)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHandle
    r.java:1802)
    at
    com.ibm.ws.bo.bomodel.util.BOXMLHandler.handleFeature(BOXMLHandl
    er.java:802)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHand
    ler.java:898)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandle
    r.java:873)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandle
    r.java:641)
    at
    org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
    Source)
    at
    org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement
    (Unknown Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
    ntentDispatcher.dispatch(Unknown Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
    Source)
    at
    org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
    Source)
    at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java
    :193)
    at
    org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourc
    eImpl.java:179)
    at
    org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceIm
    pl.java:1094)
    at
    com.ibm.ws.bo.bomodel.util.SerializerUtil$2.run(SerializerUtil.j
    ava:184)
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:694)
    at
    com.ibm.ws.bo.bomodel.util.SerializerUtil.privilegedLoad(Seriali
    zerUtil.java:175)
    at
    com.ibm.ws.bo.service.BOXMLSerializerImpl.load(BOXMLSerializerIm
    pl.java:340)
    ... 91 more
    

Local fix

Problem summary

  • The Eclipse Modeling Framework (EMF) model of the header for AIS
     communication with an SCA binding in the message was not
    pre-initialized when the invocation occurred, possibly leading
    to multiple threads trying to access the EMF model, which EMF
    doesn't support.
    

Problem conclusion

  • A fix that pre-initialize the EMF model of the header for AIS
    communication with an SCA binding is available for IBM BPM
    V8.6.0.0 cumulative fix 2018.03.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62785

  • Reported component name

    BPM

  • Reported component ID

    5737A5700

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-08

  • Closed date

    2020-10-30

  • Last modified date

    2020-10-30

  • 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

  • Fixed component ID

    5737A5700

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0"}]

Document Information

Modified date:
14 September 2022