Jump to: navigation, search

Increased Memory handles Excessive Loads

SUMMARY: A new configuration option helps MCP and RM handle excessive loads.
The next publication of the GVP 8.5 User's Guide will include this revision:
CHAPTER: Chapter 14: Configuring the Reporting Server
SECTION: Important Reporting Server Configuration Options
ADDto Table 36: Selected Reporting Server Configuration Options, on page 281:

memoryUsageLimit
Section: activemq
Valid values: Any integer followed by a valid measurement unit abbreviation (examples: 64kb, 16mb, 2gb).
Default value: 256mb
Takes effect: At start/restart
Defines the memory limit for messages that are handled by the ActiveMQ broker.

In high volume and high load environments, Media Control Platform or Resource Manager may throw exceptions and terminate due to no free space, and log messages such as "Reporting Client failed to send message to RS…" and "Usage Manager Store is Full…"

An increase would be up to 1028mb (if your installed hardware allows) during maintenance produces these results:

  • Better consumption of messages on the Reporting Server side.
  • Good performance of RS database/ host and network.
  • Balancing of peaks in the RS load.
  • Additional memory available for messages that are handled by the ActiveMQ BROKER.

Genesys recommends regular monitoring of the MCP and RM logs to detect potential problems.

This page was last edited on June 8, 2016, at 01:46.
Comments or questions about this documentation? Contact us for support!