New Parameter helps RS ActiveMQ Component Handle high Call Volume/Load
SUMMARY: In some situations, Media Control Platform and Resource Manager will terminate due to no free space on BROKER (Reporting Server). 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
ADD TO: Table 36: Selected Reporting Server Configuration Options (Messaging section on pages 281-282)
Parameter: activemq.memoryUsageLimit
Application: Reporting Server
Section: Messaging
Valid values: An integer followed by a measurement unit (b, kb, mb, gb). Maximum value is 1024mb, and the system must have available memory for the increase.
Default value: 256mb
Takes effect: at start/restart
Use this parameter to specify the memory that is reserved for messages handled by the ActiveMQ broker.
NOTE: You can observe the following log messages and exceptions, generated in MCP and RM in call logs due to no free space on their BROKER (Reporting Server), when these components experience a high call volume / load environment
MCP/RM Example log Traces:
- Reporting Client failed to send message to RS. Exception trace: *** BEGIN SERVER-SIDE STACK TRACE ***
- Message: Usage Manager Store is Full. Producer (ID:pbrm01.cct.tatasky.com-39117-1411158990620-0:53127:0:0) stopped to prevent flooding queue: //rs.queue.cdr. See http://activemq.apache.org/producer-flow-control.html for more info
- Exception Class javax.jms.ResourceAllocationException
When a BROKER (Reporting Server) runs out of memory, the producer (MCP/RM) is blocked until enough memory is cleared. When no space is free on the BROKER, an exception is thrown on the client side (RM/MCP-RC).
Actions that you can take to prevent it:
- Ensure there is better consumption of messages on RS side. STEVE ASKS: how to accomplish this?
- Increase the storage limits to smooth out peaks in the work load.
- Increase the memory limit for messages handled by the ActiveMQ BROKER (specififed in the activemq.memoryUsageLimit option).
Genesys recommends frequent monitoring of MCP and RM logs, to identify system overloads and act accordingly. Also: increase the value of the Reporting Server configuration parameter activemq.memoryUsageLimit to 1024mb: