[jira] Updated: (QPID-441) .NET Client does not properly handle bounced (undeliverable) messages

["Tomas Restrepo (JIRA)" <qp...@incubator.apache.org>]

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

Tomas Restrepo updated QPID-441:
--------------------------------

    Attachment: QPID-441.diff

This patch creates the missing exception types (AMQInvalidRoutingKeyException, AMQInvalidArgumentException, AMQNoConsumersException, AMQNoRouteException), fixes the method handlers (including creating the proper exceptions from ChannelCloseMethodHandler, like the Java client does) and propagates the exception to the connection.

The patch also fixes UndeliverableTest so that it tests that the exception is getting propagated for all known exchange types.

Note: The SendUndeliverableMessageOnTopicExchange() test is currently failing against the Java broker because of QPID-436.

> .NET Client does not properly handle bounced (undeliverable) messages
> ---------------------------------------------------------------------
>
>                 Key: QPID-441
>                 URL: https://issues.apache.org/jira/browse/QPID-441
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>    Affects Versions: M2
>            Reporter: Tomas Restrepo
>         Attachments: QPID-441.diff
>
>
> Currently the .NET client correctly receives the Basic.Return method from the server when an undeliverable message was sent by the client with the Mandatory flag set. However, the client does not trigger an exception on the connection with the error information and the bounced message, and instead silently ignores it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.