[jira] Commented: (QPID-154) Logging/tracing for C++.

["Alan Conway (JIRA)" <qp...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463281 ] 

Alan Conway commented on QPID-154:
----------------------------------

qpid::Exception should  provide a method to log the exception and constructor that logs the exception during creation.

Low-level tracing should provide function entry-exit logging via a macro+guard object that logs in constructor/destructor.  (BOOST_FUNCTION_NAME gives the current function name in a macro)

> Logging/tracing for C++.
> ------------------------
>
>                 Key: QPID-154
>                 URL: https://issues.apache.org/jira/browse/QPID-154
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Broker, C++ Client
>            Reporter: Alan Conway
>
> Qpid needs logging infrastructure for user logging and debug tracing.
> Performance is critical, in particular the descision *not* to log a disabled messages must be extremely cheap so that disabled logging statements have no significant performance impact.
> Ideally a single system for both user logging and debug tracing so that debug tracing can be left in release builds and enabled to diagnose  problems in the users's environment.
> Only if we can't get acceptable performance should we consider a separate debug tracing facility that is compiled out of release builds for tracing critical code.
> Highly desirable to use an existing open source solution rather than reinvent the wheel provided we can find one that is acceptable, need some research & discussion on dev list before selecting and implementing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira