Re: Separate kahadb for queues and dead letter queues?

Wildcards aren’t quite that flexible - the docs say “don’t specify any string after ‘>’ on your wildcard express, it will be ignored” http://activemq.apache.org/wildcards.html For what it’s worth - I got around this issue with DLQs by changing the nam

Re: Separate kahadb for queues and dead letter queues?

I just tested by sending messages into a queue test. Unfortunately the filter ">.DLQ" seems to include "test". So it seems everything after ">" is ignored. Is there any way to express that I want all queues that end in DLQ? Christian On 29.04.2016 17:17, Christian Schneider wrote: I took a st

Re: Separate kahadb for queues and dead letter queues?

I took a stab at creating a config with a separate kahadb for the DLQs: Does that make sense? I am unsure

Re: Separate kahadb for queues and dead letter queues?

Using mKahaDB with a separate KahaDB instance for the DLQ is the best idea I know of for dealing with the problem you describe. A JIRA enhancement request exists for compacting KahaDB journals ( https://issues.apache.org/jira/plugins/servlet/mobile#issue/AMQ-3978). You should vote for it, and if

Separate kahadb for queues and dead letter queues?

We have the issue that our journals at a customer are very large. We analyzed the messages in the system and found that most of the time the normal queues stay at a very low number of messages near to 0. The only queues that hold messages for longer periods of time are the dead letter queues.