[OASIS Issue Tracker] (AMQP-140) Make the behaviour of the anonymous terminus clear when faced with transactional pre-settled messages

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/AMQP-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70180#comment-70180 ] 

Keith Wall commented on AMQP-140:
---------------------------------

I think the change appearing in WD04 looks good. I think this issue may be marked as resolved.

> Make the behaviour of the anonymous terminus clear when faced with transactional pre-settled messages
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQP-140
>                 URL: https://issues.oasis-open.org/browse/AMQP-140
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Improvement
>          Components: Anonymous Terminus
>            Reporter: Rob Godfrey
>            Priority: Major
>
> In the routing errors section of the anonymous terminus we discuss how the link to the terminus should be closed with an error if a message cannot be routed to the destination implied in the "to:" field, and the source does not allow for the rejected outcome.  We should clarify this behaviour when messages are being sent within a transaction and have been sent pre-settled.  In this case the behaviour defined for transactions (of essentially marking the transaction as rollback only) should take precedence.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)