Dequeing Of a Message Fails with ORABPEL-11207 IO Failure in translator When Message Contains Non-Ascii Unicode Characters (Doc ID 745527.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1 to 10.1.3.4
This problem can occur on any platform.

Symptoms

When a message that contains UNICODE characters is dequeued the following error is logged an the message is put in the rejectedMessages folder:

ERROR
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2008-03-02T18:06:44.944+01:00</TSTZ_ORIGINATING>
<COMPONENT_ID>tip</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>nthvsdevpdb01</HOST_ID>
<HOST_NWADDR>172.25.2.37</HOST_NWADDR>
<MODULE_ID>esb.server.service.impl.inadapter</MODULE_ID>
<THREAD_ID>64</THREAD_ID>
<USER_ID>SYSTEM</USER_ID>
</HEADER>
<CORRELATION_DATA>

<EXEC_CONTEXT_ID><UNIQUE_ID>172.25.2.37:82312:1204477604944:48</UNIQUE_ID><SEQ&
gt;0</SEQ></EXEC_CONTEXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>JCA: ORABPEL-11207

IO Failure in translator.
IO failure because the Inbound XSD translator failed to DOM Parse InputStream .
Check the error stack and fix the cause of the error. Contact oracle support if error is not
fixable.
</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[ORABPEL-11207

IO Failure in translator.
IO failure because the Inbound XSD translator failed to DOM Parse InputStream .
Check the error stack and fix the cause of the error. Contact oracle support if error is not
fixable.

at
oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:
199)
at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1328)
at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:570)
at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:217)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
at java.lang.Thread.run(Thread.java:595)
...


To reproduce the issue, follow the steps:

1. Create a BPEL process with an AQ adapter that dequeues messages.
2. Populate the queue with a message like below:

<DequeueMessageRequest xmlns="http://www..../dequeuemessage"><firstname>Robert</firstname><lastname>van Mölken</lastname></DequeueMessageRequest>

Notice the message contains the unicode character 'ö'.

=> No BPEL instance is created, but instead the message is sent to rejectedMessages folder and in domain.log we can see the error: ORABPEL-11207 IO Failure in translator.

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