APAR status
Closed as program error.
Error description
Using WebSphere Application Server Network Deployment edition, with Feature Packs SCA 1.0.1.15, XML 1.0.0.13; and Business Process Manager Advanced 7.5.1.1, this exception in FFDC is thrown when a very large Business Object with Russian characters is being processed: bpmServer_7eab7eab_13.03.22_11.24.33.6592787348069323201584.txt FFDC Exception:java.lang.RuntimeException SourceId:com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHelpers aveFailedEvent ProbeId:302 Reporter:com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHelper@ 504e504e java.lang.RuntimeException: Error serializing BO {http://BOSerializerBug,Fault} at com.ibm.ws.box.service.BOXMLSerializerImpl.save(BOXMLSerializerI mpl.java:332) at com.ibm.ws.box.service.BOXMLSerializerImpl.writeDataObject(BOXML SerializerImpl.java:458) at com.ibm.ws.bo.delegate.BOXMLSerializerDelegate.writeDataObject(B OXMLSerializerDelegate.java:120) at com.ibm.wbiserver.manualrecovery.util.FailedEventMessageUtil.con vertParameters(FailedEventMessageUtil.java:1066) at com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHelper.getScaMes sageInfo(RecoveryMDBHelper.java:589) at com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHelper.saveFaile dEvent(RecoveryMDBHelper.java:267) at com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHandler.processM essage(RecoveryMDBHandler.java:187) at com.ibm.wbiserver.manualrecovery.ejb.RecoveryMDBHandler.onMessag e(RecoveryMDBHandler.java:100) at com.ibm.wsspi.sca.async.bean.impl.ServiceSIBusMessageBean.onMess age(ServiceSIBusMessageBean.java:164) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.ws.container.binding.jms.TransactionalMessageEndpoint.in vokeBusinessMethod(TransactionalMessageEndpoint.java:381) at com.ibm.ws.container.binding.jms.TransactionalMessageEndpoint.in voke(TransactionalMessageEndpoint.java:458) at $Proxy177.onMessage(Unknown Source) at com.ibm.ws.sib.ra.inbound.impl.SibRaEndpointInvokerImpl.invokeEn dpoint(SibRaEndpointInvokerImpl.java:157) at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDis patcher.java:900) at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaW ork.run(SibRaSingleProcessListener.java:552) at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646) Caused by: java.lang.ArrayIndexOutOfBoundsException at com.ibm.xml.xml4j.internal.s1.util.XMLChar.isSpace(Unknown Source) at com.ibm.xml.xci.serializer.XSerializer.isAllWhitespace(XSerializ er.java:101) at com.ibm.xml.xci.serializer.XSerializer.addContent(XSerializer.ja va:522) at com.ibm.xml.xci.serializer.fixer.FixerNamespaces.addContent(Fixe rNamespaces.java:609) at com.ibm.xml.xci.adapters.xlxp.scanner.OffsetDataImpl.addContentA sBytes(OffsetDataImpl.java:128) at com.ibm.xml.xci.adapters.xlxp.mediator.XLXPCacheDataFactory$XPSu btreeDataOffset.addContent(XLXPCacheDataFactory.java:410) at com.ibm.xml.xci.dp.cache.dom.mediator.NoMediator$GeneralItemCopi er.copyNode(NoMediator.java:504) at com.ibm.xml.xci.dp.util.copy.CopierDelegate.copyNode(CopierDeleg ate.java:53) at com.ibm.xml.xci.dp.util.copy.Copier.copySequence2Content(Copier. java:390) at com.ibm.xml.xci.dp.util.copy.Copier.copyContents(Copier.java:576 ) at com.ibm.xml.xci.dp.util.copy.Copier.copySequence2Content(Copier. java:381) at com.ibm.xml.xci.dp.util.copy.Copier.copy(Copier.java:238) at com.ibm.xml.xci.dp.util.copy.SerializerCDataDelegate.writeEncode dBytesTo(SerializerCDataDelegate.java:146) at com.ibm.xml.sdo.model.XMLDocumentImpl.save(XMLDocumentImpl.java: 227) at com.ibm.xml.sdo.helper.XMLHelperImpl.save(XMLHelperImpl.java:426 ) at com.ibm.ws.box.util.SerializerUtil$1.run(SerializerUtil.java:105 ) at java.security.AccessController.doPrivileged(AccessController.jav a:277) at com.ibm.ws.box.util.SerializerUtil.privilegedSave(SerializerUtil .java:103) at com.ibm.ws.box.service.BOXMLSerializerImpl.save(BOXMLSerializerI mpl.java:317) ... 20 more
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Feature Pack for XML. * **************************************************************** * PROBLEM DESCRIPTION: Insufficient processing of multi-byte * * characters, such as cyrillic Russian * * characters, during serialization * * caused the error. * **************************************************************** * RECOMMENDATION: * **************************************************************** During the serialization of multi-byte data, incorrect logic was applied that led to an index that was outside the boundaries of the byte array.
Problem conclusion
The serialization algorithm has now been updated to include sufficient processing so that array accesses are within boundaries. The fix for this APAR is currently targeted for inclusion in Feature Pack for XML fix pack 1.0.0.15. 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
PM85914
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-29
Closed date
2013-10-08
Last modified date
2013-10-08
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
XML FEATUREPACK
Fixed component ID
5724J0856
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 February 2022