gtully wrote
The only known caveat atm is priority support, levelDb does not
respect JMS priority in the same way as kahaDB or JDBC does.
Hi Gary,
can you please expain a little more? Not the same is not not at all, so
what are the results when using message priorities? Does it work in most
On Mon, Mar 31, 2014 at 12:06 PM, Tom_Z tomatgooglec...@arcor.de wrote:
gtully wrote
The only known caveat atm is priority support, levelDb does not
respect JMS priority in the same way as kahaDB or JDBC does.
Hi Gary,
can you please expain a little more? Not the same is not not at all, so
leveDB also does not support multiple kahaDB instance (persistent adapters)
similar to kahaDB.
With the Mulitple KahaDB persistence adapter, destination partitioning
across journals is possible. but there is no support in levelDB for this.
Please correct me if I am wrong !!
Thanks,
Anuj
Gary:
I just tried to use 5.9 with replicated levelDB and my test failed epically...
The specific problem I have is that after about 1700 messages the whole
thing slows down to a crawl. It doesn't seem to be the case if I am
using plain leveldb, but when using replication I come across
there has been a bunch of work in that area for 5.10 so my first
suggestion is to give a 5.10-SNAPSHOT a whirl. If that shows the same
behaviour we can get on the job of sorting out what the problem is.
A fresh snapshot was minted today -
Per Claus Ibsen's blog post:
Over time level db is planned to be default out of the box persistent
store, instead of the current kahadb store. Though we are not there
yet, so kahadb is still the default store.
What does we are not there yet mean? What are the caveats regarding
LevelDB usage?
of the ~3k unit tests - many use the default store and we have not
switched the default store. Until we do, and work through any issues
we won't know for sure. We plan to do that before we make it the
default.
The only known caveat atm is priority support, levelDb does not
respect JMS priority in
Does level db have support for that scheduled persistent store?
http://activemq.apache.org/delay-and-schedule-message-delivery.html
Or maybe I am mistaking or remembering wrong that the scheduler has a
separate store from the regular store for its scheduled messages.
On Tue, Oct 22, 2013 at
There is a separate store for scheduled messages.
KahaDB is implemented.
There is no impl for leveldb yet.
On Tue, Oct 22, 2013 at 9:09 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Does level db have support for that scheduled persistent store?
true but in fact, the scheduler has its own 'home grown' kahadb like
store - and really needs to be layered over the existing persistence
adapters - https://issues.apache.org/jira/browse/AMQ-3758 - on the
todo list for 5.10
On 22 October 2013 17:30, Christian Posta christian.po...@gmail.com
10 matches
Mail list logo
