qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Resolved: (QPID-28) Allow user to select policy for undeliverable message handling
Date Wed, 12 Dec 2007 10:23:43 GMT

     [ https://issues.apache.org/jira/browse/QPID-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Godfrey resolved QPID-28.
-----------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: M3)

Will be part of implementing 0-10 

> 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
>
> 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.


Mime
View raw message