Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1078936 - "csharp.example.server" cannot read connection options
"csharp.example.server" cannot read connection options
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
Development
Unspecified Windows
medium Severity medium
: 3.1
: ---
Assigned To: Chuck Rolke
Petra Svobodová
: EasyFix, Patch
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-20 10:58 EDT by Petra Svobodová
Modified: 2015-04-14 09:47 EDT (History)
1 user (show)

See Also:
Fixed In Version: qpid-cpp-0.30-2
Doc Type: Bug Fix
Doc Text:
An issue with how the `csharp.map.receiver` example application command line processing code looked for arguments prevented users from getting the correct result for argument two. The code has been improved so the program argument list is now parsed correctly, which allows users to pass values to argument two correctly.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-04-14 09:47:39 EDT
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA QPID-5840 None None None Never
Red Hat Product Errata RHEA-2015:0805 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.1 Release 2015-04-14 13:45:54 EDT

  None (edit)
Description Petra Svobodová 2014-03-20 10:58:49 EDT
Description of problem:
Example application "csharp.example.server" has two optional arguments "url" (as the first) and "connectionOptions" (as the third). The second argument is omitted (it is reserved for an address and it is not used in this example). 

But when the example is started, the "connectionOptions" argument is not read without some senseless argument on the second position.

Current part of csharp.example.spout.cs:
...
static int Main(string[] args) {
            string url = "amqp:tcp:127.0.0.1:5672";
            string connectionOptions = "";

            if (args.Length > 0)
                url = args[0];
            // address args[1] is not used in this example
            if (args.Length > 2)
                connectionOptions = args[2];
...

Should be:
...
static int Main(string[] args) {
            string url = "amqp:tcp:127.0.0.1:5672";
            string connectionOptions = "";

            if (args.Length > 0)
                url = args[0];
            // address is not used in this example
            if (args.Length > 1)
                connectionOptions = args[1];
...

Version-Release number of selected component (if applicable):
qpid-cpp-win-3.22.36.1-1

How reproducible:
100%

Steps to Reproduce:
1. Unpack the qpid-cpp-win package and build C# examples.
2. Run a qpid broker with authentication requirement.
3. Try to run the server example: csharp.example.server.exe <broker_hostname> "{sasl-mechanisms:PLAIN,username:<user>,password:<password>}"

Actual results:
csharp.server.example cannot connect to the broker due authentication failure (the connection options are ignored).

Expected results:
csharp.server.example should be able to connect the broker.
Comment 1 Chuck Rolke 2014-06-24 11:40:23 EDT
Fixed upstream at commit r1605112.
Comment 3 Petra Svobodová 2014-11-03 09:36:09 EST
Now the "csharp.example.server" client is able to accept the broker url and connection options.

Verified on qpid-cpp-win-0.30.3.1-1 on WindowsXP-x86, Windows7-x86 and x64, Windows Server2003-x86, x64 and Windows Server2008-x86, x64 and R2.

--> VERIFIED
Comment 5 errata-xmlrpc 2015-04-14 09:47:39 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0805.html

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