Description of problem: Applications "qpid-perftest.exe" and "qpid-latency-test.exe" with option "--tcp-nodelay" exit with error messages; see the command line transcript below, please: C:\qpid_VS2008\bin\Release>qpid-perftest.exe -b <broker_IP_address> --count 100 --tcp-nodelay An operation was attempted on something that is not a socket. (..\..\qpid\cpp\s rc\qpid\sys\windows\Socket.cpp:279) C:\qpid_VS2008\bin\Release>qpid-latency-test.exe -b 10.34.37.202 --tcp-nodelay An operation was attempted on something that is not a socket. (..\..\qpid\cpp\s rc\qpid\sys\windows\Socket.cpp:279) Version-Release number of selected component (if applicable): qpid-cpp-win-3.0.0.2-1 How reproducible: 100% Steps to Reproduce: 1. Unpack the package. 2. Run "qpid-perftest.exe" or "qpid-latency-test.exe". Actual results: "qpid-perftest.exe" and "qpid-latency-test.exe" exit with exception. Expected results: "qpid-perftest.exe" and "qpid-latency-test.exe" should run without exceptions.
Fix applied upstream r1339927. see https://issues.apache.org/jira/browse/QPID-4008
Tools "qpid-perftest.exe" and "qpid-latency-test.exe" work with "--tcp-nodelay" option now; this exception did not occur. Verified on packages qpid-cpp-win-3.1.0.1-1 on Windows platforms: - XP-x86 and x64 - 7-x86 and x64 - Server2003-x86 and x64 - Server2008-x86 and x64 - Server2008 R2 --> VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The Windows specific code for Socket::setTcpNoDelay tries to set the property before the connection is open, resulting in an exception. The fix remembers the request and delays its operation until after the socket is open (which matches the Posix implementation).
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. http://rhn.redhat.com/errata/RHSA-2012-1277.html
Removing external tracker bug with the id '4008' as it is not valid for this tracker