You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2016/11/29 18:42:58 UTC

[jira] [Comment Edited] (DISPATCH-578) Dispatch trace logging forces all proton tracing on

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

Andrew Stitcher edited comment on DISPATCH-578 at 11/29/16 6:42 PM:
--------------------------------------------------------------------

Unless I misremember the proton-c code {{PN_TRACE_(FRM|DRV|RAW)}} will be active whatever dispatch does.

All that dispatch can do is to change the destination/handling of the logging by implementing the specific pn_trace_t function and passing it to pn_transport_trace().

Perhaps this is what you mean, but I'd say that as you can specify the trace function on a per transport basis, you can probably make this a per connection setting.


was (Author: astitcher):
Unless I misremember the proton-c code PN_TRACE_{FRM|DRV|RAW} will be active whatever dispatch does.

All that dispatch can do is to change the destination/handling of the logging by implementing the specific pn_trace_t function and passing it to pn_transport_trace().

Perhaps this is what you mean, but I'd say that as you can specify the trace function on a per transport basis, you can probably make this a per connection setting.

> Dispatch trace logging forces all proton tracing on
> ---------------------------------------------------
>
>                 Key: DISPATCH-578
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-578
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Container
>    Affects Versions: 0.7.0
>            Reporter: Alan Conway
>            Assignee: Ganesh Murthy
>            Priority: Minor
>             Fix For: 0.8.0
>
>
> Presently enabling TRACE logging for the SERVER module forces all proton PN_TRACE_* logging on and sends it to the router log. This makes trace logs hard to read, in particular the PN_TRACE_RAW output is verbose and rarely wanted.
> Make dispatch respect the PN_TRACE_* environment variables: it will still log proton traces as SERVER trace logs but only if the relevant env vars are turned on (and SERVER trace is enabled)



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

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