WARN: Frame size errors in the data collector activemq.log

Products

• Network Observability
• CA Performance Management

Issue/Introduction

The following WARN is repeatedly being seen in the data collector's activemq.log

 

<DATE> 08:40:56,378 | WARN  | Transport Connection to: tcp://<HOST-IP>:53068 failed: Frame size of 1 GB is larger than max allowed 100 MB | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///<HOST-IP>:53068@61616

 

Environment

DX NetOps Performance Management : All Supported Versions

Cause

The value for framesize was set lower than optimal to prevent DoS attacks.  This has been known to cause the broker to stop consuming messages, causing the data collector (karaf) to hold onto all JMS messages in memory

Resolution

To resolve edit DC activemq.xml: /opt/IMDataCollector/broker/apache-activemq-5.18.6/conf/activemq.xml (path may vary)

 

• Change <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=100&amp;wireFormat.maxFrameSize=104857600"/> to <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=100&amp;wireFormat.maxFrameSize=1024857600"/> 

 

*****

Also, this setting relates to mitigating Denial-of-Service attacks. So, if the DC isn't on the open internet, or if firewalls are configured correctly, this setting should not even be necessary.  In that case, we can remove the "maxFrameSize" commands entirely.

We can remove the selection in red/orange noted above:

<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=100"/>

 ******

 

After making either of the above modifications. then recycle activemq

• systemctl stop activemq .... it should restart on its own, if it doesn't then restart it
• systemctl start activemq

Additional Information

These changes will NOT persist through any upgrades to ActiveMQ and will need to be reimplemented post upgrade.