activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lucille Wilson (JIRA)" <>
Subject [jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
Date Thu, 21 Feb 2013 14:08:13 GMT


Lucille Wilson commented on AMQ-4335:

Dear Tim,
I didn't create my own broker.  We do not use an embedded broker.  Also your broker's xml
is set for less than 100MB.  And the unit test message size seems to be set to 131072 bytes,
not 104857600 bytes.

This problem is a problem of getting a message payload whose byte size is greater than 104857600
bytes across a native broker's queue.  From the documentation, it seems as if we set maxFramSize
to greater than 104857600 bytes, we will be able to send a message whose actual size is greater
than 104857600 bytes, but that is not true.  We have tested this in activemq 5.7 and 5.8.

This bug request is related to other bug requests such as:

Lucille Wilson

> Cannot set maxFrameSize greater than 100MB
> ------------------------------------------
>                 Key: AMQ-4335
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: Windows 2008 R2
>            Reporter: Pat Flaherty
>         Attachments:, amq4335.xml,
> Trying to send JSON messages greater then 100MB and I receive the error:
> Transport Connection to: tcp:// failed: Frame
size of 140 MB larger
>  than max allowed 100 MB
> I tried increasing the frame size in 5.8.0 as follows:
>         <transportConnectors>
>             <!-- DOS protection, limit concurrent connections to 1000 and frame size
to 100MB -->
>             <transportConnector name="openwire" uri="tcp://;wireformat.maxFrameSize=157286400"/>
>             <transportConnector name="amqp" uri="amqp://;wireformat.maxFrameSize=157286400"/>
>         </transportConnectors> 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message