The correlationID and messageID in the Response Do Not Match Those in the Request When Using Docupresentment (IDS) 2.3 or Later with MQ Queues (Doc ID 1599142.1)

Last updated on DECEMBER 02, 2024

Applies to:

Symptoms

When a message is placed on an MQ queue by a third party application with a null correlation ID the message is picked up and processed, but the reply message from IDS has a different message ID and correlation ID to the request. See IDS log below:

When the correlationID is null the messageID should be copied to the correlationID for the response message.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.