CLS generates PAMS__INTERNAL with pams_get_msgw (Doc ID 836628.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle MessageQ - Version 5.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
5.0

Goal

When pams_get_msg for large messages is tested with RP20 and RP21, all seemed well.

However, with pams_get_msgw (any timeout reading a multireader queue), the CLS (server) returns PAMS__INTERNAL in the CLS header. Normally, the client side (eg, DMQCL32.DLL), checks only the client task ID, and since that is not filled in, it reports:

 
It is interesting to note that the CLS processes the get message correctly - it dequeues the message the message and writes a trace into its log as if everything is OK. However, the data transmitted back to the client is garbled, except for the PAMS__INTERNAL status in the header. The last 20 bytes of the CL header are overwritten by the first 20 bytes of the message that should have been received.

Solution

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