You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ganesh Murthy (JIRA)" <ji...@apache.org> on 2015/10/20 23:33:27 UTC
[jira] [Commented] (DISPATCH-182) Introduce new logging levels or
modules to print proton PN_TRACE_DRV and PN_TRACE_RAW messages to the
dispatch router log
[ https://issues.apache.org/jira/browse/DISPATCH-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965814#comment-14965814 ]
Ganesh Murthy commented on DISPATCH-182:
----------------------------------------
Proton has three logging options (not logging levels)
PN_TRACE_RAW (1) (001) (Log raw binary data into/out of the transport)
PN_TRACE_FRM (2) (010) (Log frames into/out of the transport)
PN_TRACE_DRV (4) (100) (Log driver related events, e.g. initialization, end of stream, etc)
Each of the above options can be independently turned on (one or two or all options can be turned on). For example, all three options can be turned on like this -
pn_transport_trace(tport, PN_TRACE_RAW | PN_TRACE_FRM | PN_TRACE_DRV);
The problem is that proton's callback function has the following signature -
static void qd_transport_tracer(pn_transport_t *transport, const char *message) - this does not tells us if the message is a PN_TRACE_RAW or a PN_TRACE_FRM or PN_TRACE_DRV
Because of this, we are unable to independently introduce new modules called PN_RAW, PN_FRM, PN_DRV in the qdrouter.json.
for the time being, we are going to turn on all proton logging options, like so in server.c -
if (qd_log_enabled(qd_server->log_source, QD_LOG_TRACE)) {
pn_transport_trace(tport, PN_TRACE_FRM | PN_TRACE_DRV | PN_TRACE_RAW);
pn_transport_set_tracer(tport, qd_transport_tracer);
}
> Introduce new logging levels or modules to print proton PN_TRACE_DRV and PN_TRACE_RAW messages to the dispatch router log
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: DISPATCH-182
> URL: https://issues.apache.org/jira/browse/DISPATCH-182
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 0.5
> Reporter: Ganesh Murthy
> Priority: Minor
>
> Enhance dispatch router logging so that proton's PN_TRACE_DRV and PN_TRACE_RAW messages can be included in the dispatch router log. Right now only PN_TRACE_FRM print in the log.
> PN_TRACE_DRV and PN_TRACE_RAW messages print out valuable information that can be used to debug router issues and it would be good to have these messages in the dispatch router log
--
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