qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-4943) [Java Broker] Introduce a feature for 0-8/0-9/0-9-1protocols to close a connection on receiving a mandatory unroutable message in a transacted session
Date Thu, 27 Jun 2013 13:24:21 GMT

    [ https://issues.apache.org/jira/browse/QPID-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694699#comment-13694699
] 

ASF subversion and git services commented on QPID-4943:
-------------------------------------------------------

Commit 1497347 from orudyy@apache.org
[ https://svn.apache.org/r1497347 ]

QPID-4943: Allow setting client connection property 'qpid.close_when_no_route' as string and
boolean
                
> [Java Broker] Introduce a feature for 0-8/0-9/0-9-1protocols to close a connection on
receiving a mandatory unroutable message in a transacted session
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4943
>                 URL: https://issues.apache.org/jira/browse/QPID-4943
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker, Java Client
>    Affects Versions: 0.23
>            Reporter: Alex Rudyy
>            Assignee: Robbie Gemmell
>             Fix For: 0.23
>
>
> With AMQP 0-8/0-9/-9-1 protocols sending a message with a routing key for which no queue
binding exist results in either message being bounced back (mandatory or immediate message)
or discarded on broker side (not mandatory or immediate message).
> When a 'mandatory' message is returned back, an AMQNoRouteException is passes through
the configured ExceptionListener on the Connection. This exception does not cause channel
or connection close. However, it require a special exception handling on client side in order
to deal with AMQNoRouteExceptions. This could potentially be a problem when using various
messaging frameworks and buses (e.g Mule) as they usually close the connection on receiving
any JMSException.
> In order to simplify application handling of scenarios where 'mandatory' messages are
being sent to queues which do not actually exist, the Qpid Java Broker should allow configuring
the client/broker on a global and/or connection-specific basis such that the broker should
respond to this situation by closing the connection rather than returning the unroutable message
to the client. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message