[ 
https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish updated AMQ-4335:
------------------------------

    Attachment: max-frame-size-test.zip

Here is a simple maven project that will build and run everything for you.  
Just extract run mvn compile exec:java and it will start an embedded broker 
using a configuration file similar to your own.  Note that there is no 
difference here between embedded and standalone broker, sae code, same config.  
Test send the large message and receives and outputs the size. 
                
> Cannot set maxFrameSize greater than 100MB
> ------------------------------------------
>
>                 Key: AMQ-4335
>                 URL: https://issues.apache.org/jira/browse/AMQ-4335
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: Windows 2008 R2
>            Reporter: Pat Flaherty
>         Attachments: AMQ4335Test3_WithLargeGeneratedString.zip, 
> AMQ4335_Test4_regularRunThroughOurApplication.zip, AMQ4335Test.java, 
> AMQ4335Test.java, AMQ4335Test.java, amq4335.xml, amq4335.xml, 
> BugInActivemq.zip, max-frame-size-test.zip
>
>
> Trying to send JSON messages greater then 100MB and I receive the error:
> Transport Connection to: tcp://192.168.10.1:55823 failed: 
> java.io.IOException: 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://192.168.10.1:61616?maximumConnections=1000&amp;wireformat.maxFrameSize=157286400"/>
>             <transportConnector name="amqp" 
> uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;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: http://www.atlassian.com/software/jira

Reply via email to