1. As I said in my earlier email, you can download the code, change that constant, and recompile, or you can split your messages and make your clients handle that properly (which may be problematic since you need to ensure that all parts of a given message are consumed, in order, by the same consumer). Maybe someone else has a way to do this without doing one of those, but I think you'd have heard it by now if someone had an answer for you. 2. I can't answer that, but maybe someone else can. 3. Sounds like a great idea, and it sounds like it'll be an easy fix for someone. (Maybe even you? You've clearly looked at this code enough to know it better than most people.) Too bad it missed the cutoff for 5.11.0, though.
Tim On Wed, Feb 4, 2015 at 7:21 AM, khandelwalanuj <khandelwal.anu...@gmail.com> wrote: > Another concern here: > > As Tim mentioned : > > You need to configure a large maxFrameSize on the STOMP > transportConnector > > in your Broker > > configuration, see: http://activemq.apache.org/xml-configuration.html > > I looked into the source code of ActiveMQ. I don't think changing the > 'maxFrameSize' will work here. From the stack trace I posted I can clearly > see that 'MAX_DATA_LENGTH' and 'MAX_COMMAND_LENGTH' is exceeded when I try > to send more than 100MB of data. And these are constants defined in > StompWireFormat.java. I didn't find any way to modified these parameters in > entire ActiveMQ source code. > > *My Questions: > * > 1. Is there any way I can send more than 100MB of data from STOMP (python > and perl) producers? > 2. What is the difference between 'MAX_DATA_LENGTH' and > 'MAX_COMMAND_LENGTH' > ? > 3. These parameters should be configurable. Should I log a JIRA for this ? > > Thanks, > Anuj > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Stomp-producer-messages-size-limitation-tp4689847p4691050.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
