Memory leak in CLS when using FML-style messaging or double pointers (Doc ID 832871.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

UNIX and NT only

Goal

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.

This problem was reproduced using MessageQ 5.0 versions of dmqperftest and dmqclperftest utilities. Since double-pointers and FML were new in MessageQ 5.0, these utilities didn't contain double pointers in MessageQ 4.0a. The 4.0A versions of the performance test utilities didn't reproduce the problem in MessageQ 5.0

Also this issue is reproduced on Windows NT and Unix. Although tested on OpenVMS, the OpenVMS version of MessageQ 5.0 didn't exhibit a memory leak.

To reproduce the problem, run version 5.0 of dmqclperftest as a server. For example,

 

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