suppress error from Camel Route on slave

I'm running ActiveMQ 5.13 on a leveldb cluster. My ActiveMQ.xml config contains a Camel route in an include file. I route xml from one queue to a topic but when slave is in standby mode I keep getting this error : INFO | jvm 1| 2015/12/28 18:10:26 | ERROR | Could not refresh JMS C

Re: Running as an embedded broker in WildFly

Sent from my iPhone > On Dec 27, 2015, at 7:46 PM, gturner wrote: > > I am looking for GOOD instructions in using ActiveMQ as an embedded broker in > WildFly 10. Can someone provide such instructions. We have waited and > waited on a serious flaw in Artemis to be fixed, and tired of the wait

Running as an embedded broker in WildFly

I am looking for GOOD instructions in using ActiveMQ as an embedded broker in WildFly 10. Can someone provide such instructions. We have waited and waited on a serious flaw in Artemis to be fixed, and tired of the waiting. -- View this message in context: http://activemq.2283324.n4.nabble.com

Re: mKahaDB and durable subscriptions

Multi-KahaDB already separates destinations (if configured that way) into their own KahaDB store, so I'm not really sure what you mean by separate durable subscriptions. If a topic has a bunch of offline durables and that topic is configured to have its own KahaDB instance then it would not affect

Re: Offline durable subscriptions lost when rebuilding kahadb index.

This is the way KahaDB currently works. There is no way to keep around the durable subscriptions (other than the index) because then KahaDB would never be able to GC any files. The main way I can think of to fix this would be to do some sort of compaction, as Tim pointed out in the comments of AM