Description:
Symptom
=======
EMS 4.4.x/5.0.0 tibemsd/tibemsd64 process size growing without bound.
This growth can not be explained by the number of pending messages or number of JMS objects held in memory (connections, sessions, producers, consumers, etc).

Cause
====
A server defect is causing a memory leak when the parameter "server_heartbeat_client" is explicitly configured as "5" (5 seconds).
The memory leak happens when the connection disconnects, and therefore, the importance of the memory growth depends on the number of connections being created/destroyed over time (the individual memory leak represents less than 200 bytes).

Workaround
=========
Change the server_hearbeat_client value (defined in the main configuration file) to a different value than 5 seconds. Note that if this parameter is not defined, you will not be affected by the memory leak.

Impact
=====
Overtime, the process memory usage increasing, the EMS server process may run out of memory, causing a loss of functionality.

Resolution
=======
Will be fixed in the next release.
Symptoms:

Cause:

EMS 4.4.x/5.0.0 tibemsd/tibemsd64 process size growing without bound.