Reason for socket errors not reported correctly on Windows
----------------------------------------------------------
Key: AMQCPP-44
URL: https://issues.apache.org/activemq/browse/AMQCPP-44
Project: ActiveMQ C++ Client
Issue Type: Bug
Affects Versions: 1.1
Reporter: Albert Strasheim
Assigned To: Nathan Mittler
Fix For: 2.0
Socket errors aren't reported correctly on Windows. When the broker is down and
the TcpTransport fails to connect, I get an exception saying "Socket::connect -
No error". strerror of errno might not be the right way to get the error
description for socket errors on Windows. Maybe one needs to look at what
WSAGetLastError returns, but I'm not sure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
