[
https://issues.apache.org/jira/browse/QPID-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-28:
---------------------------------
Fix Version/s: (was: M2)
M3
Affects Version/s: M2
M1
Moving unresolved JIRAs from M2 to M3, in preparation for M2 release
> Allow user to select policy for undeliverable message handling
> --------------------------------------------------------------
>
> Key: QPID-28
> URL: https://issues.apache.org/jira/browse/QPID-28
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker, Java Client
> Affects Versions: M1, M2
> Environment: All
> Reporter: Marnie McCormack
> Fix For: M3
>
>
> Currently an undeliverable message is returned to the sender, via the
> ExceptionListener registered for the MessageProducer implementation. However,
> a more common model for other messaging applications is to route
> undeliverable messages to a dead letter queue, or similar.
> I believe there has been previous discussion on the AMQP mailing lists about
> possible options for handling undeliverable messages, including the provision
> of a dead letter queue. This discussion is relevant to this tasks and should
> be reviewed first to determine status and options in terms of the qpid
> implementation.
> Ideally, we should allow users to specify how they want undeliverable
> messages to be handled i.e. returned, sent to an dead letter queue, sent to
> another queue which they specify etc. (The onException method is not the
> ideal place for apps to manage this scenario.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
