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

Kim van der Riet commented on DISPATCH-566:
-------------------------------------------

This error was noted on a 2-node dispatch router configuration:
{noformat}
[sender] --> [node1/9001] --> [broker/5672] --> [node2/9002] --> [receiver]
{noformat}
The error is noted for transfers of messages through node1. A test in which a 
single message containing a JMS annotation {{x-opt-jms-msg-type}} is sent 
(frame 51) from the sender to node 1. This is immediately forwarded on the 
linkRoute to the broker (frame 52), but the annotation is absent.
{noformat}
◊  ◊◊ 2.370179  Frame 30  [::1]:60148  -> [::1]:5672  ->   begin [0,null], 
attach [0,0] receiver link_0 (source: endpoint_0, target: null), flow [0,0] 
(0,10)
◊  ◊◊ 2.383967  Frame 35  [::1]:37874  -> [::1]:9001  ->   init AMQP (0): 
(1.0.0), open [0], begin [0,null], attach [0,0] sender link_1 (source: null, 
target: endpoint_0)
◊  ◊◊ 2.384075  Frame 37  [::1]:37874 <-  [::1]:9001 <-    init AMQP (0): 
(1.0.0)
◊  ◊◊ 2.384221  Frame 39  [::1]:37874 <-  [::1]:9001 <-    open [0], begin [0,0]
◊  ◊◊ 2.384403  Frame 41  [::1]:60146  -> [::1]:5672  ->   begin [0,null], 
attach [0,0] sender link_1 (source: null, target: endpoint_0)
◊  ◊◊ 2.414587  Frame 43  [::1]:60148 <-  [::1]:5672 <-    begin [0,0], attach 
[0,0] sender link_0 (source: endpoint_0, target: null)
◊  ◊◊ 2.414760  Frame 45  [::1]:60294 <-  [::1]:9002 <-    attach [0,0] sender 
link_0 (source: endpoint_0, target: null)
◊  ◊◊ 2.423239  Frame 47  [::1]:60146 <-  [::1]:5672 <-    begin [0,0], attach 
[0,0] receiver link_1 (source: null, target: endpoint_0), flow [0,0] (0,100)
◊  ◊◊ 2.423452  Frame 49  [::1]:37874 <-  [::1]:9001 <-    attach [0,0] 
receiver link_1 (source: null, target: endpoint_0), flow [0,0] (0,100)
◊  ◊◊ 2.426887  Frame 51  [::1]:37874  -> [::1]:9001  ->   transfer [0,0] (0)
   ◊  transfer [0,0] (0)
        Length: 160
        Doff: 2
        Type: AMQP (0)
        Channel: 0
        Performative: transfer (20)
        Arguments
             Handle: 0
             Delivery-Id: 0
             Delivery-Tag: 0100000000000000
             Message-Format: 0
             Settled: False
             More: False
        Message-Header
             Durable: False
             Priority: 4
             First-Acquirer: False
             Delivery-Count: 0
        Message-Annotations (map of 1 element)
             x-opt-jms-msg-type (byte): 0
        Message-Properties
             Content-Type: application/octet-stream
             Expiry-Time: Jan 1, 1970 00:00:00.000000000 UTC
             Creation-Time: Jan 1, 1970 00:00:00.000000000 UTC
             Group-Sequence: 0
◊  ◊◊ 2.427223  Frame 52  [::1]:60146  -> [::1]:5672  ->   transfer [0,0] (0)
   ◊  transfer [0,0] (0)
        Length: 126
        Doff: 2
        Type: AMQP (0)
        Channel: 0
        Performative: transfer (20)
        Arguments
             Handle: 0
             Delivery-Id: 0
             Delivery-Tag: 0100000000000000
             Message-Format: 0
             Settled: False
             More: False
        Message-Header
             Durable: False
             Priority: 4
             First-Acquirer: False
             Delivery-Count: 0
        Message-Properties
             Content-Type: application/octet-stream
             Expiry-Time: Jan 1, 1970 00:00:00.000000000 UTC
             Creation-Time: Jan 1, 1970 00:00:00.000000000 UTC
             Group-Sequence: 0
◊  ◊◊ 2.444970  Frame 53  [::1]:60146 <-  [::1]:5672 <-    disposition [0] 
(receiver 0-0)
◊  ◊◊ 2.445221  Frame 54  [::1]:37874 <-  [::1]:9001 <-    disposition [0] 
(receiver 0-0)
◊  ◊◊ 2.445331  Frame 55  [::1]:37874  -> [::1]:9001  ->   close [0]
◊  ◊◊ 2.445387  Frame 56  [::1]:37874 <-  [::1]:9001 <-    close [0]
◊  ◊◊ 2.445619  Frame 59  [::1]:60146  -> [::1]:5672  ->   detach [0,0]
◊  ◊◊ 2.450018  Frame 61  [::1]:60146 <-  [::1]:5672 <-    detach [0,0]
◊  ◊◊ 2.450211  Frame 62  [::1]:60146  -> [::1]:5672  ->   end [0]
◊  ◊◊ 2.451333  Frame 63  [::1]:60146 <-  [::1]:5672 <-    end [0]
◊  ◊◊ 2.453602  Frame 64  [::1]:60148 <-  [::1]:5672 <-    transfer [0,0] (0)
◊  ◊◊ 2.456369  Frame 66  [::1]:60294 <-  [::1]:9002 <-    transfer [0,0] (0)
◊  ◊◊ 2.457292  Frame 69  [::1]:60294 <-  [::1]:9002 <-    close [0]
◊  ◊◊ 2.457464  Frame 71  [::1]:60148  -> [::1]:5672  ->   detach [0,0]
◊  ◊◊ 2.463800  Frame 73  [::1]:60148 <-  [::1]:5672 <-    detach [0,0]
◊  ◊◊ 2.464002  Frame 74  [::1]:60148  -> [::1]:5672  ->   end [0]
◊  ◊◊ 2.465783  Frame 75  [::1]:60148 <-  [::1]:5672 <-    end [0]
{noformat}

> Message annotations are not propagated to brokers on a linkRoute
> ----------------------------------------------------------------
>
>                 Key: DISPATCH-566
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-566
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 0.7.0
>            Reporter: Kim van der Riet
>            Assignee: Ganesh Murthy
>             Fix For: 0.8.0
>
>
> When a message containing a custom annotation (such as is used for JMS 
> messages) is passed to a broker on a linkRoute, the annotation is not 
> attached to the message.
> This issue is similar to that in DISPATCH-160, but the case for a single-node 
> dispatch router in which the message is passed directly from one client to 
> another works correctly.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to