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.
Fixed upstream at commit r1605112.
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
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