You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hariharan (Commented) (JIRA)" <ji...@apache.org> on 2011/12/07 05:31:40 UTC
[jira] [Commented] (AMQ-3610) sharedDeadLetterStrategy is not
discarding the DLQ messages.
[ https://issues.apache.org/jira/browse/AMQ-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164131#comment-13164131 ]
Hariharan commented on AMQ-3610:
--------------------------------
Can somebody please help me with this?
> sharedDeadLetterStrategy is not discarding the DLQ messages.
> ------------------------------------------------------------
>
> Key: AMQ-3610
> URL: https://issues.apache.org/jira/browse/AMQ-3610
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0
> Reporter: Hariharan
> Labels: activemq, broker
>
> Hi,
> Am using AMQ 5.5. I would like to disable the option of sending dead letters to ActiveMQ.DLQ destination and completely discard (automatically) the messages that would be sent there otherwise. To do this I had configured the broker as below:
> {code:xml}
> <amq:destinationPolicy>
> <amq:policyMap>
> <amq:policyEntries>
> <amq:policyEntry topic=">" producerFlowControl="false" >
> <amq:deadLetterStrategy>
> <amq:sharedDeadLetterStrategy processExpired="false" />
> </amq:deadLetterStrategy>
> </amq:policyEntry>
> <amq:policyEntry queue=">" producerFlowControl="false">
> <amq:deadLetterStrategy>
> <amq:sharedDeadLetterStrategy processExpired="false" />
> </amq:deadLetterStrategy>
> </amq:policyEntry>
> </amq:policyEntries>
> </amq:policyMap>
> </amq:destinationPolicy>
> {code}
> However, I still see that the messages are getting stored in DLQ. Can you please let me know what could be causing this?
> Do I need to fix anything in the config?
> Thanks
> Hari
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply:[jira] [Commented] (AMQ-3610) sharedDeadLetterStrategy is not
discarding the DLQ messages.
Posted by SuoNayi <su...@163.com>.
There has been a broker plugin which does what you want .
You can add the plugin to plugins section like this:
<amq:plugins>
<amq:discardingDLQBrokerPlugin dropAll="true"/>
</amq:plugins>
At 2011-12-07 12:31:40,"Hariharan (Commented) (JIRA)" <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/AMQ-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164131#comment-13164131 ]
>
>Hariharan commented on AMQ-3610:
>--------------------------------
>
>Can somebody please help me with this?
>
>> sharedDeadLetterStrategy is not discarding the DLQ messages.
>> ------------------------------------------------------------
>>
>> Key: AMQ-3610
>> URL: https://issues.apache.org/jira/browse/AMQ-3610
>> Project: ActiveMQ
>> Issue Type: Bug
>> Components: Broker
>> Affects Versions: 5.5.0
>> Reporter: Hariharan
>> Labels: activemq, broker
>>
>> Hi,
>> Am using AMQ 5.5. I would like to disable the option of sending dead letters to ActiveMQ.DLQ destination and completely discard (automatically) the messages that would be sent there otherwise. To do this I had configured the broker as below:
>> {code:xml}
>> <amq:destinationPolicy>
>> <amq:policyMap>
>> <amq:policyEntries>
>> <amq:policyEntry topic=">" producerFlowControl="false" >
>> <amq:deadLetterStrategy>
>> <amq:sharedDeadLetterStrategy processExpired="false" />
>> </amq:deadLetterStrategy>
>> </amq:policyEntry>
>> <amq:policyEntry queue=">" producerFlowControl="false">
>> <amq:deadLetterStrategy>
>> <amq:sharedDeadLetterStrategy processExpired="false" />
>> </amq:deadLetterStrategy>
>> </amq:policyEntry>
>> </amq:policyEntries>
>> </amq:policyMap>
>> </amq:destinationPolicy>
>> {code}
>> However, I still see that the messages are getting stored in DLQ. Can you please let me know what could be causing this?
>> Do I need to fix anything in the config?
>> Thanks
>> Hari
>
>--
>This message is automatically generated by JIRA.
>If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>