On Mon, 2016-07-18 at 02:03 -0700, Tobias Duckworth wrote: > 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 am very curious about that, if there are interop issues in the engine I want to fix them. Can you get a couple of wireshark traces, one from a working session with the reactor and another from the failed session with the connection engine? Stick them on a JIRA and I'll take a look. The reactor and the engine have separate mechanisms for generating AMQP container and link-ids, that is my first suspect. > 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. Me too. It is possible that there is some data (e.g. auth username) that the reactor is getting from SSL which the engine is not, and Azure is expecting it - but I would expect that to fail during connection setup. My guess is SSL is not the issue here, some AMQP difference in the engine is. > > Anyway, seems not to be a fundamental problem with using libcurl to > deal > with all the SSL side of things, which is good. > Thanks for pressing forward with this. I promise to make it easier in future :) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
