{"action":"created","issue":{"url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/346","repository_url":"https://api.github.com/repos/alanxz/rabbitmq-c","labels_url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/346/labels{/name}","comments_url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/346/comments","events_url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/346/events","html_url":"https://github.com/alanxz/rabbitmq-c/issues/346","id":145192045,"number":346,"title":"amqp_socket_open to port without listener appears to block forever","user":{"login":"sigiesec","id":16757805,"avatar_url":"https://avatars.githubusercontent.com/u/16757805?v=3","gravatar_id":"","url":"https://api.github.com/users/sigiesec","html_url":"https://github.com/sigiesec","followers_url":"https://api.github.com/users/sigiesec/followers","following_url":"https://api.github.com/users/sigiesec/following{/other_user}","gists_url":"https://api.github.com/users/sigiesec/gists{/gist_id}","starred_url":"https://api.github.com/users/sigiesec/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sigiesec/subscriptions","organizations_url":"https://api.github.com/users/sigiesec/orgs","repos_url":"https://api.github.com/users/sigiesec/repos","events_url":"https://api.github.com/users/sigiesec/events{/privacy}","received_events_url":"https://api.github.com/users/sigiesec/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-01T14:13:51Z","updated_at":"2016-04-04T13:26:29Z","closed_at":null,"body":"In librabbitmq-c 0.5.2, trying to amqp_socket_open to a port where no one was listening, resulted in an AMQP_STATUS_SOCKET_ERROR (unfortunately, the exact socket error could not be determined, cf. https://github.com/alanxz/rabbitmq-c/issues/236, but it should probably have been WSAECONNREFUSED (10061) ).\r\n\r\nIn librabbitmq-c 0.7.1, this behavior has changed, amqp_socket_open now appears to block forever, and amqp_socket_open_noblock completes with a AMQP_STATUS_TIMEOUT\r\n \r\nThis is unfortunate, as the condition can no longer be distinguished from a real timeout, and the operation only fails after the timeout period.\r\n\r\nHas the behaviour changed for a reason? Can the original behaviour be restored?"},"comment":{"url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/comments/205295507","html_url":"https://github.com/alanxz/rabbitmq-c/issues/346#issuecomment-205295507","issue_url":"https://api.github.com/repos/alanxz/rabbitmq-c/issues/346","id":205295507,"user":{"login":"sigiesec","id":16757805,"avatar_url":"https://avatars.githubusercontent.com/u/16757805?v=3","gravatar_id":"","url":"https://api.github.com/users/sigiesec","html_url":"https://github.com/sigiesec","followers_url":"https://api.github.com/users/sigiesec/followers","following_url":"https://api.github.com/users/sigiesec/following{/other_user}","gists_url":"https://api.github.com/users/sigiesec/gists{/gist_id}","starred_url":"https://api.github.com/users/sigiesec/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sigiesec/subscriptions","organizations_url":"https://api.github.com/users/sigiesec/orgs","repos_url":"https://api.github.com/users/sigiesec/repos","events_url":"https://api.github.com/users/sigiesec/events{/privacy}","received_events_url":"https://api.github.com/users/sigiesec/received_events","type":"User","site_admin":false},"created_at":"2016-04-04T13:26:29Z","updated_at":"2016-04-04T13:26:29Z","body":"I checked it with the current master branch, and it seems to be back to the previous behaviour with AMQP_STATUS_SOCKET_ERROR. Still, I cannot determine the socket error code, but it is reasonable to assume that there is no other socket error."}}