You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tobias Duckworth (JIRA)" <ji...@apache.org> on 2016/07/19 14:54:20 UTC

[jira] [Commented] (PROTON-1261) Qpid-Proton 0.12.2 unable to open link with Azure when using connection_engine

    [ https://issues.apache.org/jira/browse/PROTON-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384281#comment-15384281 ] 

Tobias Duckworth commented on PROTON-1261:
------------------------------------------

Use the filter ip.addr == 13.69.192.43 to see the pertinent information in the wireshark traves

> Qpid-Proton 0.12.2 unable to open link with Azure when using connection_engine
> ------------------------------------------------------------------------------
>
>                 Key: PROTON-1261
>                 URL: https://issues.apache.org/jira/browse/PROTON-1261
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: cpp-binding
>    Affects Versions: 0.12.2
>         Environment: Linux
>            Reporter: Tobias Duckworth
>            Assignee: Cliff Jansen
>         Attachments: AzureWithQpidProton_FAILonOpenSender.pcapng, AzureWithQpidProton_SUCCESS.pcapng
>
>
> Since proton's built in SSL does not work when running as a connection_engine I used libcurl to achieve an SSL connection.
> I have tested this against a local broker and am able to connect, open sessions, senders and receivers fine.
> However, on connecting to a Microsoft Azure IoTHub I find that whilst I am able to connect and open a session, when attempting to open a sender or receiver the remote (Azure) end immediately closes it again.
> The problem does not occur with a reactor/messenger build of the same program, which uses proton's built in SSL support. However I don't think that the use of internal or external SSL is the cause of the problem. (It's tricky to prove this as I haven't found a way to do the io_reads and io_writes with a reactor build, which is why I'm using connection_engine/socket_engine in the first place - However, I did hack around in connection_options.cpp and convinced ssl_init to get called and found that the connection_engine build fails in the same way when using built in SSL).
> I'll try to attach wireshark traces from both sample programs to this bug.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org