-
1. Re: Message Broker Error
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
-
2. Re: Message Broker Error
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
-
3. Re: Message Broker Error
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.
-
4. Re: Message Broker Error
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.