Hex 16 (SYN) Character Causes Composite Service To Fail, Thus Message Gets Stuck In 'Routing' State

(Doc ID 2380307.1)

Last updated on MARCH 29, 2018

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


On : version, BPEL Service Engine

When a SOA composite is attempting to process Hex 16 characters, it fails and
the following error occurs. This message also causes rest of the messages in queue to be backed up.

[2017-06-14T10:36:58.860-05:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: DaemonWorkThread: '1081' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: 4c3401d0d16ea8c1:-324eaa9c:15c9b5e05e6:-7ffd-000000000007f651,0] [APP: soa-infra] [composite_instance_id: 19520006] [composite_name: FLJAC_CO_CerMil_ADT_OneCare!1.0] [component_name: FLJAC_MD_RR_CerMil_ADT_OneCare] JMSAdapter TXWAC_CO_Omnicell_OMN [[
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.

at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:626)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:413)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1193)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1073)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)


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