Oracle Documaker MQ Message contains Null Values Causing Errors (Doc ID 2096785.1)

Last updated on JANUARY 14, 2016

Applies to:

Oracle Documaker - Version 11.3 and later
Information in this document applies to any platform.


On Documaker 11.3 version, Docupresentment version 1.8

There is an issue with the MQ interface. Users are setting a MQ message id that is unique in the final 8 bytes - these bytes contain the store clock value - a system timer.
When the message id is copied to the correlation id, the copy appears to terminate at the first occurrence of a null byte (hex 00).
This causes the requesting application to fail to get its reply message, since the correlation id is not what is expected.

ERROR - example

request message id = hex ( D00032ADA170BFCB )

After Oracle software copies the message id into the reply correlation id

reply correlation id = hex ( D00000000000000000 )

Appears to terminate the copy after the hex D0

(Possibly strcpy() or strcat() isbbeing used instead of memcpy() or similar line of thought.)

The issue has the following business impact:
Transactions are not retrieved from the queue successfully.


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