Memory leak in Queue Manager - Erlang Node

Issue dateAugust 29, 2014
Observed behaviorA memory leak causes threads to be unavailable for use. Symptoms vary, but manifest any time Queue Manager attempts to allocate a thread to complete an action and is unable to do so; for example, during a request by EyeQueue to change an operation mode.
Products and versions affectedVirtual Hold Callback version 8.0.1-8.0.6
Components affectedQueue Manager
Applications affectedQueue Manager
SeverityMajor
Root causeMemory leak in Queue Manager when CreateInteraction is called.A memory leak was found in Queue Manager when CreateInteraction is called. It is specific to the communication between Queue Manager and the Erlang Node. The leak is approximately .5KB per call.Monitor server memory using Performance Monitor and restart the server on a schedule that resets memory allocation over an appropriate period of time.
ResolutionVHT code will be edited to ensure memory is removed appropriately.
Expected availability
  • Virtual Hold version 8.0.5 Hotfix 1, which is projected to be release on or around 09/05/2014.
  • Virtual Hold version 8.0.6 Hotfix 1, which is projected to be released on or around 09/05/2014.
  • Virtual Hold version 8.0.7, which is projected to be released in September 2014.
WorkaroundsNone.
Defects related to this issue77745000

Memory leak in QueueManager CreateInteraction