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 > what are the results when using message priorities? Does it work in most > cases or rarely? I suppose it would work in most cases because priority support is also implemented at the cursors and in the consumers. However, KahaDB has explicit support for priority levels at the persistence level and messages can be pulled off disk with some notion of priority. This is the part missing in LevelDB AFAIK
> > I'm using ActiveMQ 5.8 und have LevelDB activated. Should I go back to > KahaDB? > > Thanks, > Tom > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/LevelDB-in-ActiveMQ-5-9-0-tp4673129p4679750.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
