Frame size errors in the DC activemq.log

Products

• Network Observability
• CA Performance Management

Issue/Introduction

We are seeing these errors in the DC activemq.log repeatedly:

 

<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 : 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 DC (karaf) to hold onto all JMS messages in memory ..... which will cause the DC to fallover.

 

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"/> 

 

The recycle activemq

E.G.

• systemctl stop activemq .... it should restart on its own.  If for some reason that is not the case 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.