Hi Ivan, No, the broker does not impose any message size limits. You might want to run a tcp packet snooper on your traffic to make sure that the STOMP protocol is actually being preserved. You also might want to enabled debug logging on the broker side so that you can see when the broker killed the stomp connection.
Regards, Hiram On Wed, May 14, 2008 at 6:29 AM, Ivan Jovanovic <[EMAIL PROTECTED]> wrote: > > I have installed ActiveMQ 5.1 as broker and I'm using PHP Stomp client (not > one from codehouse but self made) to communicate with the broker. I have no > problems for messages that are with the size below 42KB, with messages that > are bigger than that broker resets the connection after 42KB written with > fwrite() to tcp socket while sending message > > Is this connection reset normal behavior of the broker if its internal > settings are that 42KB is the message size it can accept? > > I use persistent storage and I'm not sure that it should complain about the > message size at all? I tried to find a way to control the message size but > it seems that memory settings are important when not using persistent > storage, otherwise it should be no issue. > > Thanks for your help in advance > > Cheers > Ivan > -- > View this message in context: > http://www.nabble.com/Connection-reset-by-broker-with-messages-greater-than-42KB-tp17228015s2354p17228015.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
