Can you please hack up a unit test that shows this behavior? It would be
great to see what's going on in your use case.

Maybe take a look at this and use LevelDB instead:

https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/JMSUsecaseTest.java


On Wed, Oct 30, 2013 at 6:41 AM, kal123 <kpfininf...@gmail.com> wrote:

> I didn't understand why leveldb had the impact either, same conf. works
> when
> we us kahadb..
> For now we changed the nonpersistence queues to use vmcursors and it seem
> much better..
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/non-persistence-msgs-very-slow-with-levedb-tp4673159p4673447.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Reply via email to