[
https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007152#comment-13007152
]
Alan Conway commented on QPID-3144:
-----------------------------------
Those log statements are in a precarious position, during plugin loading before
things have been properly initialized. IMO they have little to no value and
should be removed given that they're causing useful functionality (qpidd
--check) to fail in some situations. If we want to log an init message for
plugins it should be at plugin _initialization_ (not loading) when things are
better set up. Most plugins have their own init logging already, it would be
easy to do a global "plugin foo initialized" message as well.
> qpidd --check does not work with info logging and --log-to-stdout=yes
> ---------------------------------------------------------------------
>
> Key: QPID-3144
> URL: https://issues.apache.org/jira/browse/QPID-3144
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.9
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Minor
> Fix For: 0.10
>
>
> qpidd --check is supposed to print the PID of a running qpidd --daemon, for
> use in scripts and the like. However with info logging and log-to-stdout
> enabled this does not work because log messages of the form:
> 2011-03-14 16:21:05 info Loaded Module: /usr/lib64/qpid/daemon/cluster.so
> precede the port number.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
