Last updated on NOVEMBER 03, 2016
Applies to:Oracle MessageQ / MessageQ / 5.0
Information in this document applies to any platform
The dmqcls process can leak memory when the client uses FML-style messaging or double pointers. A client connects to a MessageQ 5.0 CLS, attaches to a permanent queue, and then does pams_get_msgw in a loop, waiting for messages to arrive. Each time the client receives an FML-style message, the CLS process grows larger. The CLS will not stop growing until the client detaches from MessageQ.
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