You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2015/11/30 15:59:11 UTC

[jira] [Resolved] (PROTON-986) [C] proton-dump assumes one AMQP header

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

Chuck Rolke resolved PROTON-986.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11

> [C] proton-dump assumes one AMQP header
> ---------------------------------------
>
>                 Key: PROTON-986
>                 URL: https://issues.apache.org/jira/browse/PROTON-986
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>    Affects Versions: 0.10
>         Environment: C 
>            Reporter: Chuck Rolke
>             Fix For: 0.11
>
>
> Proton-dump discards the leading 8 bytes of data in all cases. I have two uses where this is a nuisance. They are generated by wireshark the same way:
>  * Start wireshark trace
>  * Find stream of interest
>  * Follow TCP stream
>  * Save As type raw
>  * Feed the raw file to proton-dump
> Case 1. The raw saved file has a complete AMQP connection startup. The binary data has two AMQP headers and proton-dump fails.
> Case 2. The raw saved file starts midstream in the AMQP content. The binary data has no AMQP headers and proton-dump fails.
> With the wireshark dissector one usually does not need proton-dump. But sometimes wireshark complains about a frame format or a decoding issue. Proton-dump as an AMQP decoder is a higher authority than wireshark and fixing proton-dump a little improves its utility.



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