Alex Rudyy created QPID-4943:
--------------------------------
Summary: [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: Alex Rudyy
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: [email protected]
For additional commands, e-mail: [email protected]
