Bug 725998
| Summary: | Windows C++/.NET client sometimes does not inform about exceptions on stderr | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Petra Svobodová <psvobodo> |
| Component: | qpid-sdk | Assignee: | messaging-bugs <messaging-bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0 | CC: | jross |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:14:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Chuck, comments? This looks like a race condition between the message emitted to stderr by the qpid C++ library code (2011-07-26 10:23:54 warning Broker closed connection: 320, connection-forced:Authentication failed) and the text printed to stdout by the .NET application (Exception Org.Apache.Qpid.Messaging.QpidException...). The problem still needs more investigation. This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Description of problem: If an exception caused by failed authentication on a broker occurs the std error is in some cases empty; see the Windows Command line transcriptions bellow: Correct output: --------------- C:\>C:\qpid\bin\csharp.example.spout.exe --broker dh cp-lab-187.englab.brq.redhat.com:5672 --content "HI" --connection-options {usern ame:guestY,password:guestY,sasl-mechanism:PLAIN} --count 1 "yy;{create:sender,de lete:receiver}" 2011-07-26 10:23:54 warning Broker closed connection: 320, connection-forced: Au thentication failed Exception Org.Apache.Qpid.Messaging.QpidException: Failed to connect (reconnect disabled) at Org.Apache.Qpid.Messaging.Connection.Open() at Org.Apache.Qpid.Messaging.Examples.Spout.Main(String[] args) in c:\qpid\do tnet_examples\examples\csharp.example.spout\csharp.example.spout.cs:line 73. Incorrect output with empty stderr: ----------------------------------- C:\>C:\qpid\bin\csharp.example.spout.exe --broker dh cp-lab-187.englab.brq.redhat.com:5672 --content "HI" --connection-options {usern ame:guestY,password:guestY,sasl-mechanism:PLAIN} --count 1 "yy;{create:sender,de lete:receiver}" Exception Org.Apache.Qpid.Messaging.QpidException: Failed to connect (reconnect disabled) at Org.Apache.Qpid.Messaging.Connection.Open() at Org.Apache.Qpid.Messaging.Examples.Spout.Main(String[] args) in c:\qpid\do tnet_examples\examples\csharp.example.spout\csharp.example.spout.cs:line 73. Version-Release number of selected component (if applicable): qpid-cpp-x86-2.0.0.7 Rhel5-1.3.3 and Rhel6-2.0 How reproducible: 10 - 30 % Steps to Reproduce: 1. Set authentication request in the broker configuration file. 2. Restart the qpidd service on the broker. 3. Run the "spout" command in loop: C:\qpid\bin\csharp.example.spout.exe --broker dh cp-lab-187.englab.brq.redhat.com:5672 --content "HI" --connection-options {usern ame:guestY,password:guestY,sasl-mechanism:PLAIN} --count 1 "yy;{create:sender,de lete:receiver}" Actual results: The std error is sometimes empty. Expected results: The std error should contain a message about the occurred exception.