I am not aware of any plans (at the moment) to support it in ActiveMQ 5.x.
Thanks.
- Original Message -
From: "Krzysztof Sobkowiak"
To: users@activemq.apache.org
Sent: Monday, September 7, 2015 3:20:46 PM
Subject: Re: JMS 2.0 support
Hi
Any plans to support it in ActiveMQ 5.x?
Regards
Not that upgrading to JRE7 would be a bad thing, but I'd say upgrading from
ActiveMQ 5.4.2 to 5.12 is probably the more important of the two. Though
as you said, it appears to still be a problem at least in 5.9, so there's
no guarantee that upgrading ActiveMQ will fix the problem.
My suggestion a
Can someone explain (or understand) why KahaDb implements only three levels of
priority?I wish it'd implement a few more, ideally the 10 levels JMS
specifies.Also, is there an alternative backing store that implements all
levels?
It's not a JVM GC, but executing the broker GC (which you can execute via
JMX) which flushes buffers, etc. And it's flushing of the cursor's prefetch
buffer that does the trick.
The main annoying thing about this problem is that I cannot reproduce it.
And it only happens in our production environm
