You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Dominic Evans (JIRA)" <ji...@apache.org> on 2014/11/18 15:16:33 UTC

[jira] [Created] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error

Dominic Evans created PROTON-751:
------------------------------------

             Summary: [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error
                 Key: PROTON-751
                 URL: https://issues.apache.org/jira/browse/PROTON-751
             Project: Qpid Proton
          Issue Type: Bug
          Components: proton-c
    Affects Versions: 0.8
            Reporter: Dominic Evans


If I attempt to put and send a message using messenger to a unresolvable DNS name, messenger just blocks indefinitely (or until timeout if one is set) and the getaddrinfo failure is never exposed to the user via messenger->error
```
e.g.,
$ bundle exec ruby send.rb -a madeup.example.com
```

The fix is to update pn_messenger_resolve to copy the error set on messenger->io to messenger->error in the event that PN_INVALID_SOCKET is returned by the pn_connect call (in the same way as we already do for pn_listener_ctx)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)