[jira] [Created] (PROTON-2380) frame tracing issues/improvements

["Robbie Gemmell (Jira)" <ji...@apache.org>]

Robbie Gemmell created PROTON-2380:
--------------------------------------

             Summary: frame tracing issues/improvements
                 Key: PROTON-2380
                 URL: https://issues.apache.org/jira/browse/PROTON-2380
             Project: Qpid Proton
          Issue Type: Bug
          Components: protonj2
    Affects Versions: protonj2-1.0.0-M1
            Reporter: Robbie Gemmell
            Assignee: Timothy A. Bish


Running the HelloWorld example against Broker-J 8.0.4 with PN_TRACE_FRM=true style frame trace enabled shows some areas for improvement.

* Nothing distinguishes the connection it applies to (e.g in other cases we log include the memory address), limiting value in multi-connection use cases. 
* The run ultimately resulted in exposing a broker bug (QPID-8523), causing connection closure with explanation, but the attach frame trace itself didnt show the issue at all, instead implying a value was sent (printing initialDeliveryCount=0). Some way of distinguishing actual vs default (in code terms) values received, and possibly how many fields were populated, would be useful. 
* Some binary bits will just print out the buffer class/sizes etc.
* The initial SASL header is prefixed 'AMQP' which is debatable (both ways, since its only a header). May be simpler to say SASL to show transition. Or drop the prefix.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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