Direct links to fixes
APAR status
Closed as program error.
Error description
During your load test, when multiple threads serialize the same business object to XML, the serialized XML data might be incorrect. As a result, you see the following failure in the FFDC log file when the incorrect XML data is deserialized: com.ibm.xml.xci.errors.XCIDynamicErrorException: Attribute "xsi:type" was already specified for element "p:SampleType". at com.ibm.xml.xci.adapters.xlxp.scanner.XCIScanner.produceFatalErr orEvent(XCIScanner.java:720) at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner.reportFatalErr or(DocumentScanner.java:5050) at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner.reportFatalErr or(DocumentScanner.java:1340) at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner.duplicateAttri bute(DocumentScanner.java:4751) This error occurs only in lazy parsing mode.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: IBM Business Process Manager (BPM) Advanced * * IBM BPM Express * **************************************************************** * PROBLEM DESCRIPTION: During your load test, when multiple * * threads serialize the same business * * object to XML, the serialized XML * * data might be incorrect. As a result, * * you see the following failure in the * * FFDC log file when the incorrect XML * * data is deserialized: * * com.ibm.xml.xci.errors.XCIDynamicErrorE * * xception: Attribute "xsi:type" was * * already specified for element * * "p:SampleType". * * at * * com.ibm.xml.xci.adapters.xlxp.scanner.X * * CIScanner.produceFatalErrorEvent(XCISca * * nner.java:720) * * at * * com.ibm.xml.xlxp.internal.s1.scan.Docum * * entScanner.reportFatalError(DocumentSca * * nner.java:5050) * * at * * com.ibm.xml.xlxp.internal.s1.scan.Docum * * entScanner.reportFatalError(DocumentSca * * nner.java:1340) * * at * * com.ibm.xml.xlxp.internal.s1.scan.Docum * * entScanner.duplicateAttribute(DocumentS * * canner.java:4751) * * This error occurs only in lazy * * parsing mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** Because business object serialization is not thread safe in lazy parsing mode, when multiple threads serialize the same business object to XML the xsi:type attribute might be added to the XML twice, which causes the failure.
Problem conclusion
A fix is available for IBM BPM V8.5.5.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 JR52456: 1. Select IBM Business Process Manager with your edition 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 JR52456, 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
JR52456
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-02-04
Closed date
2015-04-14
Last modified date
2015-06-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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 August 2023