Hi, I'm experiencing an issue with the connection_engine variant of qpid-proton 0.12.2 when connected to Azure. The problem does not exist in the non connection_engine build.
The remote end (Azure) is terminating the connection after 315 seconds of inactivity. Setting PN_TRACE_FRM=1 I get the following output: [0x2b3904006300]:0 <- @close(24) [error=@error(29) [condition=:"amqp:connection:forced", description="The connection was inactive for more than the allowed period of time."]] Looking at Wireshark traces of both the connection_engine and non connection_engine builds when connected to Azure I can see the difference: non connection_engine build sends a heartbeat every 120 seconds, whereas the connection_engine build never sends a heartbeat (although it does respond to the ones that Azure sends). It seems like the connection_engine build is not setting up whatever timers are necessary to send periodic heartbeats based on the idle_timeout reported in the connect frame coming back from the remote broker. I'd like to fix this and wonder whether anyone could point me in the right direction please? This thread http://qpid.2158936.n2.nabble.com/Azure-Service-Bus-receiver-timing-out-with-electron-go-binding-td7651057.html posted to the wrong list contains additional information. Thanks, Toby -- View this message in context: http://qpid.2158936.n2.nabble.com/qpid-proton-0-12-2-connection-engine-remote-idle-timeout-tp7651556.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]
