[ https://issues.apache.org/activemq/browse/AMQCPP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37963 ]
Nathan Mittler commented on AMQCPP-44: -------------------------------------- I've updated trunk to log all socket errors as is appropriate for the platform. Please take a look and see if this solves your problem. > 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. - You can reply to this email to add a comment to the issue online.