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 to [Release AS10gR3]
Oracle ESB - Version to [Release AS10gR3]
Information in this document applies to any platform.


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(
at oracle.tip.esb.server.dispatch.JMSDequeuer.processMessage(
at oracle.tip.esb.server.dispatch.agent.JavaDeferredMessageHandler.handleMessage(
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$
Caused by: oracle.xml.parser.v2.XMLParseException: Invalid char in text.
at oracle.xml.parser.v2.XMLError.flushErrors1(
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(
at oracle.xml.parser.v2.XMLParser.parse(
at oracle.tip.esb.utils.XmlUtils.getXmlDocument(
at oracle.tip.esb.utils.XmlUtils.getDocumentElement(
at oracle.tip.esb.server.dispatch.BusinessEvent.setDataAsString(



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