[
https://issues.apache.org/jira/browse/ARTEMIS-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934383#comment-16934383
]
Keith Wall edited comment on ARTEMIS-2497 at 9/20/19 12:59 PM:
---------------------------------------------------------------
The Broker's current handing of incoming Reject disposition is reasonable. The
reject disposition signals that the target finds the message "message is
invalid and therefore unprocessable" so dropping the message unconditionally is
reasonable. However, Artemis is misusing the Reject disposition to signal that
a queue is full (ARTEMIS-2494) - a transient condition that should not cause a
message to be dropped. This JIRA (really a feature request), requests the
ability to control the behaviour the Broker takes when a Reject disposition is
received. We (EnMasse) would like the ability so that Reject is handled as if
it were Modified (delivery-failed=true). The Broker's default should remain
as it is today.
was (Author: k-wall):
The Broker's current handing of incoming Reject disposition is reasonable. The
reject disposition signals that the target finds the message "message is
invalid and therefore unprocessable" so dropping the message unconditionally is
reasonable. However, Artemis is misusing the Reject disposition to signal that
a queue is full (ARTEMIS-2494) - a transient condition that should not cause a
message to be dropped. This JIRA (really a feature request), requests the
ability to control the behaviour the Broker takes when a Reject disposition is
received. We would like the ability so that Reject is handled as if it were
Modified (delivery-failed=true). The Broker's default should remain as it is
today.
> Allow configuring alternative reject behavior for AMQP
> ------------------------------------------------------
>
> Key: ARTEMIS-2497
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2497
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.10.0
> Reporter: Ulf Lilleengen
> Priority: Major
>
> In EnMasse, we use a broker plugin to forward messages to a remote AMQP
> endpoint. If the remote endpoint responds with a reject, we would like to
> retry the message.
>
> At present, the AMQP implementation will deal with rejects by immediately
> putting the messages on a DLQ (if exists).
>
> It would be nice to have a configuration option to have rejects be treated
> similarly to released by attempting retransmit before moving to DLQ.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
