[
https://issues.apache.org/jira/browse/QPIDJMS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPIDJMS-439.
------------------------------------
Resolution: Fixed
> distinguish sessions and connections better in the protocol trace logging
> -------------------------------------------------------------------------
>
> Key: QPIDJMS-439
> URL: https://issues.apache.org/jira/browse/QPIDJMS-439
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.40.0
>
>
> If protocol trace logging is enabled via the connection URI using the 'frame
> tracer' method, it is sometimes not possible to distinguish which of multiple
> sessions on a connection a frame relates to since the channel number isn't
> logged. Also, it is only possible to distinguish connections through use of
> the provider thread name detail, which sometimes is omitted. We should log
> the channel number and a connection/transport identifier (in line with that
> used for the proton-j transport trace logging) to allow better understanding
> the activity being described.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
