qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Ross (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-148) Strip qpid-dispatch-specific delivery properties on ingress
Date Thu, 13 Aug 2015 19:40:45 GMT

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

Ted Ross commented on DISPATCH-148:
-----------------------------------

Possible solution:

Add an attribute 'preserveDa' to listener and connector with type ["no", "in", "out", both"],
optional and defaults to "no".

On connections with "no", strip delivery annotations both inbound and outbound.  "in" means
strip outbound only, "out" means strip inbound only, "both" means don't strip.


> Strip qpid-dispatch-specific delivery properties on ingress
> -----------------------------------------------------------
>
>                 Key: DISPATCH-148
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-148
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Router Node
>            Reporter: Ted Ross
>             Fix For: 0.5
>
>
> Messages that ingress from endpoints outside of the router should have any x-opt-qd headers
removed from the delivery properties.
> Occasionally developers will re-use received messages for transmit and not clear the
delivery properties.  This can result in mysterious dropping of messages due to anti-looping
(i.e. the x-opt-qd-trace header shows the message passing through the router already and the
message is dropped).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message