Thanks Robbie, Didn't realise I am on the wrong list, sorry about that.
OK, so comparing what I see in a non connection_engine build to a connection_engine one. >From the Wireshark traces of both I can see that in the connection_engine build the Azure end is sending empty (presumably heartbeat) frames every 70 seconds, but the qpid-proton end is never sending any (although it does respond to the Azure ones). On the non connection_engine build both ends are sending periodic empty frames - The qpid-proton ones are every 120 seconds, which is half the idle_timeout specified in the connect packets coming from Azure. So it looks like I need to convince the connection_engine to send out heartbeat frames and it will be fixed. Toby -- View this message in context: http://qpid.2158936.n2.nabble.com/Azure-Service-Bus-receiver-timing-out-with-electron-go-binding-tp7651057p7651534.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
