[
https://issues.apache.org/jira/browse/QPID-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec closed QPID-5252.
-------------------------------
I agree, I havent realized the behaviour of command line precedence applies
also to the `log-enable` option that can be specified multiple times.
> [C++ broker] log-enable option ignored in config file when used also in
> command line
> ------------------------------------------------------------------------------------
>
> Key: QPID-5252
> URL: https://issues.apache.org/jira/browse/QPID-5252
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.24
> Reporter: Pavel Moravec
> Assignee: Ted Ross
> Priority: Minor
> Labels: easytest
>
> Description of problem:
> When specifying "log-enable" option both in command line and in configuration
> file, the option in command line is silently ignored.
> This is low severity but high priority bug, as it delays customer problem
> investigation due to troubleshooting why adding the option to config file
> does not enable the desire logging.
> Version-Release number of selected component (if applicable):
> any (checked on 0.22-19 and 0.18-14)
> How reproducible:
> 100%
> Steps to Reproduce:
> echo "log-enable=trace+" > qpidd.conf
> qpidd --config qpidd.conf --log-enable info+ 2>&1 | grep trace
> Actual results:
> no output
> Expected results:
> trace logs like:
> 2013-10-23 06:44:00 [Model] trace Mgmt create memory. id:amqp-broker
> to appear
> Additional info:
> moving the option from config.file to command line causes it is applied
> properly
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
