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 2011/03/14 21:23:29 UTC
[jira] Created: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "michael j. goulish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007476#comment-13007476 ]
michael j. goulish commented on QPID-3144:
------------------------------------------
good point about the inappropriate position of these log statements in any case.
and especially because of teensyness of change -- i withdraw my objection.
nihil obstat.
imprimatur.
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "michael j. goulish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007042#comment-13007042 ]
michael j. goulish commented on QPID-3144:
------------------------------------------
Fixing this in the code seems too heavy-handed.
Also, the log message that is getting in the way is presumably useful in other contexts.
Wouldn't it be better to simply do something like the following in the affected scripts?
my_pid=`qpidd --check | grep -v "Loaded"`
I would propose that we leave this small change out.
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "Justin Ross (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007477#comment-13007477 ]
Justin Ross commented on QPID-3144:
-----------------------------------
Approved for 0.10. Reviewed by Mick Goulish.
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006622#comment-13006622 ]
Alan Conway commented on QPID-3144:
-----------------------------------
Comitted to trunk r1081548, awaiting permission to merge to 0.10 release branch.
> 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:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-3144) qpidd --check does not work with info
logging and --log-to-stdout=yes
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-3144.
-------------------------------
Resolution: Fixed
> 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:dev-subscribe@qpid.apache.org