Hmmm, Maybe I spoke too soon.
I'm testing my SSL workaround against a Microsoft Azure IoTHub using amqps. What I find is that the connection opens fine, I can open many sessions (after fixing the bug with session opening in qpid-proton-0.12.2), but as soon as I try to open a link (sender or receiver) on any session I get the following: on_link_open on_link_error So I take a look at the local and remote conditions and find the following: local name = local description = local str = No error condition remote name = amqp:internal-error remote description = Object reference not set to an instance of an object. remote str = amqp:internal-error: Object reference not set to an instance of an object. At this stage I'm not sure whether this is something specific to Azure, or whether it's a general problem with the way I'm doing the SSL, although it seems unlikely as a lot of communication takes place to open the connection and the various sessions. If anyone has any ideas they would be most welcomely received. I think I need to try to fire up a local broker that needs SSL in order to get further with this. Toby -- View this message in context: http://qpid.2158936.n2.nabble.com/qpid-proton-0-12-2-connection-engine-and-ssl-tp7647090p7647767.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]
