Bug 987498 - no warning for unsupported c++ client options in qpidc.conf
no warning for unsupported c++ client options in qpidc.conf
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
3.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: mick
Messaging QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-23 10:06 EDT by Leonid Zhaldybin
Modified: 2014-11-09 17:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Leonid Zhaldybin 2013-07-23 10:06:32 EDT
Description of problem:
If some unsupported option is passed to the broker (either using qpidd.conf file or from the command line), the broker prints out the error message and does not start:

[root@lzhaldyb-rhel64i ~]# qpidd --foo bar
2013-07-23 16:02:18 [Broker] critical Unexpected error: Error in command line options: unknown option foo
Use --help to see valid options

However, if the unsupported option is added to the c++ client configuration file (/etc/qpid/qpidc.conf), there is no error or warning message. The client just ignores it silently.

Version-Release number of selected component (if applicable):
qpid-cpp-0.22-7

How reproducible:
100%

Steps to Reproduce:
1. Add some unsupported option to the c++ clients configuration file (f.e. "foo=bar").
2. Run a c++ client.
3.

Actual results:
The client does not print out any warning about the unsupported option in the configuration file, just ignores it silently.

Expected results:
The warning about the unsupported option in the configuration file should be printed out.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.