[jira] [Updated] (DISPATCH-786) Message annotations transmitted on wire incorrectly

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Updated] (DISPATCH-786) Message annotations transmitted on wire incorrectly

JIRA jira@apache.org

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

Kim van der Riet updated DISPATCH-786:
--------------------------------------
    Attachment: dispatch-jms.pcapng

Attached is the pcapng file showing the above scenario.

*Frame 35:* The client sends 67 messages to dispatch.

*Frame 37:* Dispatch returns 10 messages to the client. These are the transfers containing the AMQP errors.

*Frame 40:* Dispatch closes the connection.

*Frame 41:* Client sends TCP RST

*Frame 42:* Dispatch sends flow/disposition

*Frame 44:* Dispatch sends heartbeat

Detail of one of the bad transfers (cut from amqpAnalyze):
{noformat}
[37] 0.016493s  2040 bytes
  TCP: ::1:5672 -> ::1:33848 [PSH ACK] ci=2
  0000   00 00 00 be 02 00 00 00  00 53 14 d0 00 00 00 18 |........ .S......|
  0010   00 00 00 08 52 00 52 00  a0 08 00 00 00 00 00 00 |....R.R. ........|
  0020   00 00 52 00 42 42 40 40  00 53 70 d0 00 00 00 0b |..R.BB@@ .Sp.....|
  0030   00 00 00 05 42 50 04 40  42 52 00 00 53 72 d1 00 |....BP.@ BR..Sr..|
  0040   00 00 1a 00 00 00 02 a3  12 78 2d 6f 70 74 2d 6a |........ .x-opt-j|
  0050   6d 73 2d 6d 73 67 2d 74  79 70 65 51 03 73 2d 6d |ms-msg-t ypeQ.s-m|
                                                 ^^                      ^
  0060   73 67 2d 74 79 70 65 51  03 00 53 73 d0 00 00 00 |sg-typeQ ..Ss....|
  0070   3b 00 00 00 0d 40 40 40  40 40 40 a3 18 61 70 70 |;....@@@ @@@..app|
  0080   6c 69 63 61 74 69 6f 6e  2f 6f 63 74 65 74 2d 73 |lication /octet-s|
  0090   74 72 65 61 6d 40 83 00  00 00 00 00 00 00 00 83 |tream@.. ........|
  00a0   00 00 00 00 00 00 00 00  40 52 00 40 00 53 74 d1 |........ @R.@.St.|
  00b0   00 00 00 04 00 00 00 00  00 53 75 a0 01 01 00 00 |........ .Su.....|
  AMQP: [0000] f AMQP frame: size=0xbe doff=0x2 type=0x0 (AMQP) chnl=0x0:
        [0008] p transfer:6/8: [handle:handle(0x0)
                                delivery-id:transfer-number(0x0)
                                delivery-tag:delivery-tag:8(00 00 00 00 00 00 00 00)
                                message-format:uint(0x0)
                                settled:boolean(false)
                                more:boolean(false)]
        [0028] s header:4/5: [durable:boolean(false)
                              priority:ubyte(0x4)
                              first-acquirer:boolean(false)
                              delivery-count:uint(0x0)]
        [003b] s message-annotations:1: {{symbol:18("x-opt-jms-msg-type"): byte(0x3)}}
        [005d] e Decoder::decodeSection(): Unexpected leading frame byte: expected 0x0, found 0x73
{noformat}


> Message annotations transmitted on wire incorrectly
> ---------------------------------------------------
>
>                 Key: DISPATCH-786
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-786
>             Project: Qpid Dispatch
>          Issue Type: Bug
>            Reporter: Kim van der Riet
>         Attachments: dispatch-jms.pcapng
>
>
> Using today's master of dispatch router, qpid-interop-test's JMS messages test hangs. A look at a capture of the wire during this test shows the following:
> 1. Once the message annotations section is sent, a fragment of the annotation just sent is repeated, which is not correctly interpreted on the wire by the receiver.
> 2. Dispatch then closes the connection with a "amqp:connection:framing-error" the client follows with a TCP RST. However, dispatch appears to then continue and sends a flow, disposition and heartbeats to the closed connection.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Loading...