My Oracle Support Banner

OSB Adds Hex Characters When Writing To The JMS Queue (Doc ID 1083410.1)

Last updated on MARCH 27, 2020

Applies to:

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

Goal

Oracle Service Bus (OSB) Product Information Center  > Index Master Note for Oracle Service Bus > Master Note for Troubleshooting Oracle Service Bus JMS Proxy and Business Services Issues > Note 1083410.1


A problem was observed with the XML that gets written to JMS queue on an OSB process that takes a SOAP input and sends it to the JMS queue.

The problem is that in addition to the XML, it also writes hex representation of this XML, and it creates problems for the consumers of this queue.
An example of the message written to the queue looks like the following:

00000000: 3c3f 786d 6c20 7665 7273 696f 6e3d 2231 .?xml version."1
00000010: 2e30 2220 656e 636f 6469 6e67 3d22 5554 .0" encoding."UT
etc.





Solution

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
Goal
 Oracle Service Bus (OSB) Product Information Center  > Index Master Note for Oracle Service Bus > Master Note for Troubleshooting Oracle Service Bus JMS Proxy and Business Services Issues > Note 1083410.1
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.