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: Repoprting Server
Section: Messaging
Valid values: An integer followed by a measurement unit (b, kb, mb, gb). Maximum value is 1024mb, but the system must have available memory for the increase.
Default value: 256mb
Takes effect: at start/restart
Use this parameter to limit the reserved memory for messages handled by the ActiveMQ broker.

 

NOTE: When MCP/RM components experience a high call volume / load environment, you can observe the following log messages/ exceptions in their logs due to no free space on BROKER (RS). 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).

Here are some actions that you can take to prevent it:

• Ensure there is better consumption of messages on RS side ? Hence good performance of RS database/ host and network;
• Increase the storage limits to smooth out peaks in load;
• Increase the memory limit for messages handled by the ActiveMQ BROKER (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:

Update the RS application properties-> Options -> messaging -> activemq.memoryUsageLimit -> 1024 mb (Increase the value from 256 mb to 1024 mb). And then restart the RS service during the maintenance period.