You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2016/11/28 21:50:58 UTC

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

Alan Conway created DISPATCH-578:
------------------------------------

             Summary: 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: Alan Conway
            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