[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587235#comment-13587235 ] Lucille Wilson commented on AMQ-4335: - Dear Christian, I had the 5.6.0 jar in my client application. I switch that out and put in the activemq-all-5.8.0.jar. Now I can properly send TextMessage whose payload is over 100MB. The two changes I had to make were: 1. spell wireFormat correctly in the activemq.xml 2. add the activemq-all-5.8.0.jar to my project. Thank you, Thank you, Thank you! However, I have two suggestions for changes, please. 1. When the activemq project is distributed, the conf/activemq.xml spells wireformat with a small 'f'. Please fix this, because if you use the small 'f' then the maxFrameSize is not set to a number other than the default. (I tested this). So activemq.xml should read: 2. Please document this a bit better. On this page: http://activemq.apache.org/configuring-wire-formats.html Please mention that the default value is NOT max long, but 104857600 (i.e. 100MB), that the value is the number of bytes (not megabytes, gigabytes or any other thing). Thank you and thank Timothy for all your help. Lucille Wilson > 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: AMQ4335SmallPayloadTest.java, > AMQ4335SmallPayloadTest.java, amq4335-small.xml, > AMQ4335Test3_WithLargeGeneratedString.zip, > AMQ4335_Test4_regularRunThroughOurApplication.zip, > AMQ4335Test4_With2mbMessage.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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[
https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586285#comment-13586285
]
Lucille Wilson commented on AMQ-4335:
-
I changed the spelling of "wireFormat" to capitalize the "F".
Then I went back to running AMQ4335Test3_WithLargeGeneratedString.
What I saw in my activemq.log was:
2013-02-25 15:57:45,818 | DEBUG | localhost adding destination:
topic://ActiveMQ.Advisory.Producer.Queue.TEST.LARGE.FILE |
org.apache.activemq.broker.region.AbstractRegion | ActiveMQ Transport:
tcp:///192.168.2.106:55568@61616
2013-02-25 15:57:46,476 | DEBUG | Transport Connection to:
tcp://192.168.2.106:55568 failed: java.io.IOException: Frame size of 100 MB
larger than max allowed 100 MB |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport:
tcp:///192.168.2.106:55568@61616
java.io.IOException: Frame size of 100 MB larger than max allowed 100 MB
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:277)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:662)
But what I hadn't noticed before was lines in the activemq.log file which
looked like this:
2013-02-25 15:57:45,783 | DEBUG | Sending: WireFormatInfo { version=9,
properties={MaxFrameSize=157286400, CacheSize=1024, CacheEnabled=true,
SizePrefixDisabled=false, MaxInactivityDurationInitalDelay=1,
TcpNoDelayEnabled=true, MaxInactivityDuration=3, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} |
org.apache.activemq.transport.WireFormatNegotiator | ActiveMQ
BrokerService[localhost] Task-2
2013-02-25 15:57:45,784 | DEBUG | Using min of local: WireFormatInfo {
version=9, properties={MaxFrameSize=157286400, CacheSize=1024,
CacheEnabled=true, SizePrefixDisabled=false,
MaxInactivityDurationInitalDelay=1, TcpNoDelayEnabled=true,
MaxInactivityDuration=3, TightEncodingEnabled=true,
StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} and remote: WireFormatInfo {
version=9, properties={CacheSize=1024, MaxFrameSize=104857600,
CacheEnabled=true, SizePrefixDisabled=false, TcpNoDelayEnabled=true,
MaxInactivityDurationInitalDelay=1, MaxInactivityDuration=3,
TightEncodingEnabled=true, StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} |
org.apache.activemq.transport.InactivityMonitor | ActiveMQ Transport:
tcp:///192.168.2.106:55568@61616
2013-02-25 15:57:45,784 | DEBUG | Received WireFormat: WireFormatInfo {
version=9, properties={CacheSize=1024, MaxFrameSize=104857600,
CacheEnabled=true, SizePrefixDisabled=false, TcpNoDelayEnabled=true,
MaxInactivityDurationInitalDelay=1, MaxInactivityDuration=3,
TightEncodingEnabled=true, StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]} |
org.apache.activemq.transport.WireFormatNegotiator | ActiveMQ Transport:
tcp:///192.168.2.106:55568@61616
2013-02-25 15:57:45,784 | DEBUG | tcp:///192.168.2.106:55568@61616 before
negotiation: OpenWireFormat{version=9, cacheEnabled=false,
stackTraceEnabled=false, tightEncodingEnabled=false, sizePrefixDisabled=false,
maxFrameSize=157286400} | org.apache.activemq.transport.WireFormatNegotiator |
ActiveMQ Transport: tcp:///192.168.2.106:55568@61616
2013-02-25 15:57:45,784 | DEBUG | tcp:///192.168.2.106:55568@61616 after
negotiation: OpenWireFormat{version=9, cacheEnabled=true,
stackTraceEnabled=true, tightEncodingEnabled=true, sizePrefixDisabled=false,
maxFrameSize=104857600} | org.apache.activemq.transport.WireFormatNegotiator |
ActiveMQ Transport: tcp:///192.168.2.106:55568@61616
I think it may be that maxFrameSize is overriden in some code, but then set
back to the default of 100MB in other code. There is a discrepancy between
values in maxFrameSize in the lines labeled 'Using min of local', 'Received
WireFormat', 'before negotiation', and 'after negotiation'.
I still think there is a bug.
Lucille Wilson
> 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: AMQ4335SmallPayloadTest.java,
> AMQ4335SmallPayloadTest.java, amq4335-small.xml,
> AMQ4335Test3_WithLargeGeneratedString.zip,
> AMQ4335_Test4_regularRunThroughOurApplication.zip,
> AMQ4335Test4_With2mbMessage.zip, AMQ4335Test.java, AMQ4335Test.java,
> AMQ4335Test.java, amq4335.xml, amq4335.xml, BugInActivemq.zip,
> max-frame-size-test.zip
>
>
> Trying
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586124#comment-13586124 ] Lucille Wilson commented on AMQ-4335: - Dear Christian, I used the AMQ4335SmallPayloadTest.java and the amq4335-small.xml. I renamed the xml to activemq.xml. When I ran the AMQ4335SmallPayloadTest.java the Junit test showed green (which is what has been happening all along) but the message was not enqueued on the TEST.SMALL.MESSAGE queue. In addition whatever setting there is in the amq4335-small.xml which enables the admin/queue.jsp, that setting was not enabled. So my test did not show the "frame size of 2 mb is larger than max allowed 1 mb message" I was expecting. I am running on Windows 7 Professional 64 bit operating system. Since I can readily and easily reproduce the problem showing that the max frame size is always the default of 100MB what would you like from me in order to show you this bug? In the meantime, if there is any configuration or action we should take to override the default of 100mb to a larger number, please advise. Lucille Wilson > 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: AMQ4335SmallPayloadTest.java, amq4335-small.xml, > AMQ4335Test3_WithLargeGeneratedString.zip, > AMQ4335_Test4_regularRunThroughOurApplication.zip, > AMQ4335Test4_With2mbMessage.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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Updated] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucille Wilson updated AMQ-4335: Attachment: AMQ4335Test4_With2mbMessage.zip The max frame size is set to 1mb, however the message is 2mb. The expected result is an error. However, the message goes through. All overrides of maxFrameSize are ignored. Only the default maxFrameSize is respected. > 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, > AMQ4335Test4_With2mbMessage.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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585896#comment-13585896 ] Lucille Wilson commented on AMQ-4335: - I set the maxFrameSize in ACTIVEMQ_HOME/conf/activemq.xml to 1 mb. Then I created a junit test class which created a 2 mb message. I expect that if my setting of maxframesize is respected the message will produce an error saying frame size of 2mb is larger than the max allowed of 1mb. However, the message was enqueued. Please see AMQ4335Test4_With2mbMessage.zip. I believe I have proven that Activemq has hard-coded a 100mb limit in the maxframesize and that any overrides set are ignored. We'd like Activemq to fix this bug, please. Please let us know when the bug is fixed and where to download the software. Lucille Wilson > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585879#comment-13585879 ] Lucille Wilson commented on AMQ-4335: - tcp://0.0.0.0:61616 > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585116#comment-13585116 ] Lucille Wilson commented on AMQ-4335: - Dear Tim, We have increased the heap size for activemq. We have configured activemq.xml just as you say. We have changed the log4j settings to debug so that is why you can see the debug messages in the activemq.log I have sent you. > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584748#comment-13584748 ] Lucille Wilson commented on AMQ-4335: - Dear Mr. Bish, I think we should restart this conversation. Perhaps I can fill in some details. The problem, simply stated, is I want to produce a TextMessage whose message size is over 100MB. I seem to be prevented from doing so by the DEFAULT MAX FRAME SIZE parameter. In order to effect this change, I made the following changes to activmq and to my application: 1. I am running Activemq 5.8.0. We are using a native broker, not an embedded broker. We must use TextMessage, not BytesMessage. In ACTIVEMQ_HOME/conf/activemq.xml I made the follwowing changes: and also: (I increased this to 20mb) And also: (I changed this to true) And also ( I changed this to 950mb) 2. When I start activemq (in a cmd line console), I inspect the activemq.log and see: 2013-02-22 14:28:14,333 | DEBUG | Publishing: tcp://Lucille-Win7-PC:61616 for broker transport URI: tcp://Lucille-Win7-PC:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400 | org.apache.activemq.broker.TransportConnector | main 2013-02-22 14:28:14,333 | DEBUG | Publishing: amqp://0.0.0.0:5672 for broker transport URI: amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400 | org.apache.activemq.broker.TransportConnector | main This leads me to believe that activemq will accept a message larger than 100MB. 3. Next I run my application (not my unit tests). When I do, my RSIProducerToClient producer.send(TextMessage) does send the TextMessage. My application does not detect any exceptions. My client application (waiting for this message) does not get the message at all. My client application times out while waiting on this message. We look on the queue and we do not see the message either enqueued or dequeued. When we inspect the activemq.log we see: 2013-02-22 14:30:20,692 | DEBUG | Transport Connection to: tcp://192.168.2.106:50385 failed: java.io.IOException: Frame size of 140 MB larger than max allowed 100 MB | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///192.168.2.106:50385@61616 java.io.IOException: Frame size of 140 MB larger than max allowed 100 MB at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:277) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:221) at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:213) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196) at java.lang.Thread.run(Thread.java:662) 4. It seems to us, that Activemq is allowing the possibility of sending a message over 100MB when Activemq starts up. When we put the maxFrameSize in the activemq.xml and then we see that value (which is 157286400) parroted back when we start up Activemq in a console, we believe that ActiveMQ will be able to allow us to send a message of up to 150MB. But when we actually DO send such a large message, the message is not allowed. Please help us to figure out how to send a TextMessage which is over 100mb long. Thank you. Lucille Wilson > 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 > > > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584697#comment-13584697 ] Lucille Wilson commented on AMQ-4335: - The default value is 100MB. I'm trying to override the default and replace the default with a larger size. I know absolutely that my largest message is OVER 100MB. So I thought that in order to override the default max frame size, I had to modify the /conf/activemq.xml and replace the transportConnector. NO? I certainly do NOT want a 100MB max size. I want to produce a TextMessage whose size is greater than 100MB. Lucille > 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 > > > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584625#comment-13584625 ] Lucille Wilson commented on AMQ-4335: - If we aren't using /conf/activemq.xml how can we tell? We seem to be using it, because we only changed the wireformat.maxFrameSize in /conf/activemq.xml and when we bring up activemq.xml, we see that the transportConnector parameters are parroted back to us in the activemq.log. We changed /conf/activemq.xml transportConnectors to say: If we are to change the wireformat.maxFrameSize to LONG.MAX_VALUE, do we spell it just this way? : ? Lucille > 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 > > > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584605#comment-13584605 ] Lucille Wilson commented on AMQ-4335: - Dear Mr. Bish, Test3: When I used your second Unit test I get socket exceptions. So I tried another unit test which I made, to try and stuff a string whose size is over 100MB into a TextMessage and I still got a SocketException. To view the SocketException, please unzip AMQ4335Test3_WithLargeGeneratedString.zip. When you do, you'll see that I tried to overcome the socket exception by adding the socketBufferSize=157286400 parameter to the activemq.xml 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 > > > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Updated] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucille Wilson updated AMQ-4335: Attachment: AMQ4335_Test4_regularRunThroughOurApplication.zip > 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 > > > 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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Updated] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lucille Wilson updated AMQ-4335: Attachment: AMQ4335Test3_WithLargeGeneratedString.zip > 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, > AMQ4335Test.java, AMQ4335Test.java, AMQ4335Test.java, amq4335.xml, > amq4335.xml, BugInActivemq.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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
[jira] [Commented] (AMQ-4335) Cannot set maxFrameSize greater than 100MB
[ https://issues.apache.org/jira/browse/AMQ-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583205#comment-13583205 ] 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: https://issues.apache.org/jira/browse/AMQ-4076 Sincerely, Lucille Wilson > 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: AMQ4335Test.java, amq4335.xml, BugInActivemq.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: > > > uri="tcp://192.168.10.1:61616?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireformat.maxFrameSize=157286400"/> > -- 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
