[
https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8062:
-----------------------------
Description:
As per section "2.2.2 Routing Errors" of "Using the Anonymous Terminus for
Message Routing Version 1.0":
{quote}
If the source of the link does not support the rejected outcome, or the message
has already been settled by the sender, then the routing node MUST detach the
link with an error. The error sent by the routing node MUST contain the error
which would have been communicated in the detach sent on attempting to link
directly to the address in the message’s to field. Additionally the info field
of error MUST contain an entry with symbolic key delivery-tag and binary value
of the delivery-tag of the message which caused the failure.
{quote}
The Broker-J does not handle the case when message is sent pre-settled and is
rejected by the destination. We need to add the support for this behaviour.
Additionally, if a pre-settled message is published within a transaction and
cannot be routed by a queue/exchange/whatever then have the transactional
resource
logically mark the transaction as"rollback only" (i.e. failed)
was:
As per section "2.2.2 Routing Errors" of "Using the Anonymous Terminus for
Message Routing Version 1.0":
{quote}
If the source of the link does not support the rejected outcome, or the message
has already been settled by the sender, then the routing node MUST detach the
link with an error. The error sent by the routing node MUST contain the error
which would have been communicated in the detach sent on attempting to link
directly to the address in the message’s to field. Additionally the info field
of error MUST contain an entry with symbolic key delivery-tag and binary value
of the delivery-tag of the message which caused the failure.
{quote}
The Broker-J does not handle the case when message is sent pre-settled and is
rejected by the destination. We need to add the support for this behaviour.
Additionally, if a pre-settled message is published within a transaction and
cannot be fully processed by a queue/exchange/whatever then have the
transactional resource (queue / exchange / whatever) logically mark the
transaction as"rollback only" (i.e. failed), and then reject any attempt to
commit such a transaction.
> [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination
> cannot route received message
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-8062
> URL: https://issues.apache.org/jira/browse/QPID-8062
> Project: Qpid
> Issue Type: Bug
> Affects Versions: qpid-java-broker-7.0.0
> Reporter: Alex Rudyy
> Assignee: Keith Wall
> Priority: Major
> Fix For: qpid-java-broker-7.0.1
>
>
> As per section "2.2.2 Routing Errors" of "Using the Anonymous Terminus for
> Message Routing Version 1.0":
> {quote}
> If the source of the link does not support the rejected outcome, or the
> message has already been settled by the sender, then the routing node MUST
> detach the link with an error. The error sent by the routing node MUST
> contain the error which would have been communicated in the detach sent on
> attempting to link directly to the address in the message’s to field.
> Additionally the info field of error MUST contain an entry with symbolic key
> delivery-tag and binary value of the delivery-tag of the message which caused
> the failure.
> {quote}
> The Broker-J does not handle the case when message is sent pre-settled and is
> rejected by the destination. We need to add the support for this behaviour.
> Additionally, if a pre-settled message is published within a transaction and
> cannot be routed by a queue/exchange/whatever then have the transactional
> resource
> logically mark the transaction as"rollback only" (i.e. failed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
