This *is* the 4.2-SNAPSHOT (13 march) release. (I did send that info in a followup - sorry for the confusion). Maybe I should file a Jira on this? The initial reason for me using the 4.2 snapshot in the first place, was that I wanted to verify another fix that was done after 4.1.0.
Now, I just re-ran the test (the distributed producer/consumer example configured for 1000 x 1MB message) using the 4.1.0 release. I am happy to say that I don't seem to be able to reproduce the error with that version. Thanks, -Rickard James.Strachan wrote: > > On 3/14/07, RickardS <[EMAIL PROTECTED]> wrote: > > You might wanna try out the recent 4.2-SNAPSHOT builds which include > better support for dealing with this kind of issue by using a cursors > and spooling to disk when the RAM buffer is reached... > > http://cwiki.apache.org/ACTIVEMQ/message-cursors.html > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Large-message-issue-with-default-activemq-config-tf3402080s2354.html#a9482554 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
