ESB Not Creating Instance When Payload Contains Special Character

(Doc ID 1067243.1)

Last updated on AUGUST 24, 2012

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.4 to 10.1.3.4 [Release AS10gR3]
Oracle ESB - Version 10.1.3.4 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms

A BPEL process polls a database table and sends the resulting message to an ESB routing service. The ESB service in turn invokes a BPEL process with the message.

When a special character is in the payload, such as a control-Z, the ESB service does not create an instance. Instead the following error occurs in the <ORACLE_HOME>/<oc4j container name>/j2ee//log/_default_group_1/oc4j/log.xml file. If the special character is not in the payload, an ESB instance is created as expected.

oracle.tip.esb.server.common.exceptions.BusinessEventRejectionException: Error converting field "data"

at oracle.tip.esb.server.dispatch.BusinessEvent.setDataAsString(BusinessEvent.java:586)
at oracle.tip.esb.server.dispatch.JMSDequeuer.processMessage(JMSDequeuer.java:395)
at oracle.tip.esb.server.dispatch.agent.JavaDeferredMessageHandler.handleMessage(JavaDeferredMessageHandler.java:114)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:178)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:825)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.xml.parser.v2.XMLParseException: Invalid char in text.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:312)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:319)
at oracle.tip.esb.utils.XmlUtils.getXmlDocument(XmlUtils.java:55)
at oracle.tip.esb.utils.XmlUtils.getDocumentElement(XmlUtils.java:62)
at oracle.tip.esb.server.dispatch.BusinessEvent.setDataAsString(BusinessEvent.java:584)

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms