[
https://issues.apache.org/jira/browse/DISPATCH-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-178.
------------------------------------
Resolution: Fixed
Introduced qd_transport_tracer() which is set as the pn_transport->tracer and
is invoked when proton tries to write the log message to pn_transport->tracer.
Also added a connection id to qd_connection_t which helps in easy
identification for a connection.
The trace message will show up in the log if the mode is enabled to trace+
> Route proton trace messages to the dispatch router log file instead of console
> ------------------------------------------------------------------------------
>
> Key: DISPATCH-178
> URL: https://issues.apache.org/jira/browse/DISPATCH-178
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 0.5
> Reporter: Ganesh Murthy
> Priority: Minor
>
> Steps to reproduce -
> 1. Turn on proton frame level logging by doing the following on the command
> line
> export PN_TRACE_FRM=1
> 2. Add the following line to the dispatch router config file
> (qdrouterd.conf). This will enable trace level logging on the dispatch router
> and send log messages to qdrouterd.log.
> log {
> module: DEFAULT
> enable: trace+
> output: qdrouterd.log
> }
> 3. Now start the dispatch router and receive and send messages using proton's
> simple_receive.py and simple_send.py respectively.
> You will notice that the AMQP frame level trace is shown on the console. The
> frame level traffic handled/generated by the router should appear in the
> qdrouterd.log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
