Message Broker Error

[veerabathina]

If anyone knows why the MB would throw the following error, please reply.

| WARN  | Transport failed: java.io.IOException: Frame size of 1140 MB larger than max allowed 100 MB | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///192.168.68.246:43527

2012-06-29 10:50:24,371 | WARN  | Transport failed: org.apache.activemq.transport.InactivityIOException: Cannot send, channel has already failed: /192.168.68.246:43527 | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler

[garytully]

There is a limit (maxFrameSize) imposed on the size of a message to avoid OOM trying to unmarshall corrupt data which could be the result of a DOS. More generally, this can happen if a non openwire client tries to connector to an openwire transport. The first packet is expected to be a correctly encoded connection info.

You can increase the limit if you expect to deal with messages > 100MB via a url query parameter on the transport connector: ?wireformat.maxFrameSize=XX

see: http://activemq.apache.org/configuring-wire-formats.html

[veerabathina]

Thanks for the reply. We are on version 5.5.1 and maxFrameSize was added in version 5.6.0. Do you know what the fix is for version 5.5.1?

Edited by: veerabathina on Jul 2, 2012 5:38 PM

[garytully]

That fix was back ported to the fuse 5.5.1 branch for a subscriber, see: MB-894

You can download the current release, it has that fix included.

[veerabathina]

Thanks Gary. Is there a patch that I can apply. It appears that you are suggesting that I reinstall the product which means that I will be loosing the configuration changes I have made over a period of time.