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] [Updated] (DISPATCH-148) Strip qpid-dispatch-specific message annotations on ingress/egress
Date Fri, 14 Aug 2015 15:47:45 GMT

     [ https://issues.apache.org/jira/browse/DISPATCH-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Ross updated DISPATCH-148:
------------------------------
    Summary: Strip qpid-dispatch-specific message annotations on ingress/egress  (was: Strip
qpid-dispatch-specific delivery properties on ingress)

> Strip qpid-dispatch-specific message annotations on ingress/egress
> ------------------------------------------------------------------
>
>                 Key: DISPATCH-148
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-148
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Router Node
>            Reporter: Ted Ross
>            Assignee: Ganesh Murthy
>             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