Last updated on NOVEMBER 03, 2016
Applies to:Oracle MessageQ / MessageQ / 4.0A
Information in this document applies to any platform
a pams_get_msg on a Timer message is returning the full msg_area_len of the user buffer rather than a 24 byte timer msg. This causes problems when the user get is configured to receive large messages. Customer reported this problem on Windows NT client. The problem can be reproduced by running the x_timer.c example and increasing the MAX_MESSAGE_SIZE in the code from 50 to a larger number like 5000. Enable Message logging and you will see that all timer messages are 5000 bytes long, they should only be 24 bytes long. This problem is actually a server problem and can be reproduced with an Unix/NT Server and does not require a client app to reproduce.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms