Disable ActiveMQ.DLQ

[varoa <an...@gmail.com>]

Hi,

I'm using a couple of topics with the configuration shown at the bottom of
this msg. There is 1 client consuming from each topic, both run the same
code, create a connection like this:

    ActiveMQConnectionFactory factory = new
ActiveMQConnectionFactory(this.url);
    this.connection = factory.createConnection();     
    this.session = this.connection.createSession(false, this.sessionType);
    this.topic = this.session.createTopic(this.topicName);
    MessageConsumer consumer = session.createConsumer(this.topic,
this.messageSelector, this.noLocal);
    consumer.setMessageListener(this);
    this.connection.setExceptionListener(this);
    this.connection.start();

And are fast enough to consume all messages comfortably. We were using 5.0.0
and recently migrated to 5.1.0 After a couple of weeks, our disk was full
with a few gigs in the apache-activemq-5.1.0/data folder, that I assume were
coming from an "ActiveMQ.DQL" queue with a *lot* of messages. They seemed to
be all messages from the ACT topic below, and none from the other. For some
reason, our server keeps adding messages in bursts to this queue (none,
until it suddenly sends a few). I've been reading about the usage of that
queue, exceded redeliveries, etc. 

1. I am not consuming messages from that queue, nor do I want to, so I'd
prefer to discard them when redeliveries fail, rather than filling the DQL.
How can i set this up? 

2. As I said both topics have practically the same configuration, both
clients use the same code above, both are fast consumers, and the ACT topic
has a lot less traffic than SUBS. Why are all these redeliveries failing
only in the ACT one?

Thanks,

My topics conf. in activemq.xml is:

            <policyEntry topic="SUBS.>" producerFlowControl="false"
memoryLimit="24mb">
              <dispatchPolicy>
                <strictOrderDispatchPolicy />
              </dispatchPolicy>
              <subscriptionRecoveryPolicy>
                <timedSubscriptionRecoveryPolicy recoverDuration="30000" />
              </subscriptionRecoveryPolicy>
              <pendingMessageLimitStrategy>
                <prefetchRatePendingMessageLimitStrategy multiplier="2.5"/>
              </pendingMessageLimitStrategy>
            </policyEntry>

            <policyEntry topic="ACT.>" producerFlowControl="false"
memoryLimit="24mb" >
              <dispatchPolicy>
                <strictOrderDispatchPolicy />
              </dispatchPolicy>
              <subscriptionRecoveryPolicy>
                <timedSubscriptionRecoveryPolicy recoverDuration="30000" />
              </subscriptionRecoveryPolicy>
              <pendingMessageLimitStrategy>
                <prefetchRatePendingMessageLimitStrategy multiplier="2.5"/>
              </pendingMessageLimitStrategy>
            </policyEntry>
-- 
View this message in context: http://www.nabble.com/Disable-ActiveMQ.DLQ-tp18108569p18108569.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.