[
https://issues.apache.org/jira/browse/QPIDJMS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955758#comment-15955758
]
Timothy Bish commented on QPIDJMS-274:
--------------------------------------
Implemented this feature using a similar pattern as that of the Message based
ACK where the outcome supplied by the policy is returned as an int value
mapping to the outcomes in the following manner
{code}
int ACCEPTED = 1
int REJECTED = 2
int RELEASED = 3
int MODIFIED_FAILED = 4
int MODIFIED_FAILED_UNDELIVERABLE = 5
{code}
The policy is configured from the URI as follows:
{code}
?jms.redeliveryPolicy.outcome=5
{code}
> Be able to REJECT messages in JmsRedeliveryPolicy
> -------------------------------------------------
>
> Key: QPIDJMS-274
> URL: https://issues.apache.org/jira/browse/QPIDJMS-274
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.21.0
> Reporter: Fredrik Jönsson
> Assignee: Timothy Bish
>
> This is a placeholder for discussion right now, I believe I could implement
> it myself, but would like suggestions as to how to do so in an acceptable
> manner for inclusion in the project in that case if there are opinions about
> it.
> I would like to optionally (by configuration) *reject* messages with
> JmsRedeliveryPolicy/DefaultJmsRedeliveryPolicy, rather than respond with
> modify_undeliverable.
> The particular use case I have is a client reading from Azure Service Bus. I
> want it to be able to reject messages that it knows to be undeliverable to
> explicitly dead-letter them immediately.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
