OK, so I managed to fire up a local broker that requires SSL and everything works fine... I can open sessions, senders, receivers, send a message etc.
So it seems that the problem is specific to Azure, although not sure why it works with the non connection_engine build, but not with the connection_engine. I'm guessing there's something I'm not doing in relation to SSL setup that Azure requires, but have not yet found what it is. Also find it a little strange that the connection can be opened, sessions opened, but things fall apart when links are opened. Anyway, seems not to be a fundamental problem with using libcurl to deal with all the SSL side of things, which is good. Toby -- View this message in context: http://qpid.2158936.n2.nabble.com/qpid-proton-0-12-2-connection-engine-and-ssl-tp7647090p7647803.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
