My Oracle Support Banner

Parsing XML Cause STUCK Thread or java.lang.OutOfMemoryError: Java heap space in OSB 12.2.1.3.0 (Doc ID 2688941.1)

Last updated on JULY 10, 2020

Applies to:

Oracle Service Bus - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, OSB Core Functionality

When attempting to parse XML either a stuck thread occurs or java.lang.OutOfMemoryError: Java heap space.

ERROR
-----------------------
Caused By: java.lang.OutOfMemoryError: Java heap space
at org.apache.xmlbeans.impl.store.CharUtil.allocate(CharUtil.java:397)
at org.apache.xmlbeans.impl.store.CharUtil.saveChars(CharUtil.java:506)
at org.apache.xmlbeans.impl.store.CharUtil.saveChars(CharUtil.java:419)
at org.apache.xmlbeans.impl.store.CharUtil.saveChars(CharUtil.java:489)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.text(Cur.java:2927)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.stripText(Cur.java:3130)
at org.apache.xmlbeans.impl.store.Cur$CurLoadContext.text(Cur.java:3143)
at org.apache.xmlbeans.impl.store.Locale$SaxHandler.characters(Locale.java:3278)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportCdata(Piccolo.java:992)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXMLNS(PiccoloLexer.java:1290)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.parseXML(PiccoloLexer.java:1261)
at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:4812)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3466)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1277)
at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1251)
at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:747)
at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:266)
at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:287)
at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:138)
at com.bea.wli.sb.sources.MetaTransformerImpl.doTransform(MetaTransformerImpl.java:152)
at com.bea.wli.sb.sources.MetaTransformerImpl.transform(MetaTransformerImpl.java:93)
at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1246)
at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1191)
at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:997)
at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:255)
at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:155)
at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:33)
at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:53)


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.