You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by John Smith <jo...@gmail.com> on 2007/12/21 12:17:55 UTC

Which version and persistence combination to use?

Hi,

Does anyone have the perfect combination of ActiveMQ release that has been
working for a longer period of time with large (>=10MB) and durable
messages?

We have tried various combinations of AMQ4.0, 4.1.1 and 5.0 with the default
old file storage, MySQL, Derby and Kaha, but we have not been lucky. All the
errors have been identified in Jira issues, and have been fixed to the next
release. But in the next release, there has been something else that did not
work out well.

One of the tests that we use and usually fail on, is to take the example
that comes with the distribution, change nothing but the build.xml to send
100 of 10000000 byte messages, and setting durable to "true".

We are using activemq extensively for smaller messages, and we changed some
of our applications that should need bigger messages to send many more
smaller messages, using mapmessage instead of xml in text messages, but that
does not seem quiet right.

Thanks,
John

Re: Which version and persistence combination to use?

Posted by Rob Davies <ra...@gmail.com>.
Please keep try the latest 5.0-SNAPSHOT - as we are working our way  
through any issues you find

On Dec 21, 2007, at 11:17 AM, John Smith wrote:

> Hi,
>
> Does anyone have the perfect combination of ActiveMQ release that  
> has been
> working for a longer period of time with large (>=10MB) and durable
> messages?
>
> We have tried various combinations of AMQ4.0, 4.1.1 and 5.0 with the  
> default
> old file storage, MySQL, Derby and Kaha, but we have not been lucky.  
> All the
> errors have been identified in Jira issues, and have been fixed to  
> the next
> release. But in the next release, there has been something else that  
> did not
> work out well.
>
> One of the tests that we use and usually fail on, is to take the  
> example
> that comes with the distribution, change nothing but the build.xml  
> to send
> 100 of 10000000 byte messages, and setting durable to "true".
>
> We are using activemq extensively for smaller messages, and we  
> changed some
> of our applications that should need bigger messages to send many more
> smaller messages, using mapmessage instead of xml in text messages,  
> but that
> does not seem quiet right.
>
> Thanks,
> John