Dear Qpid-Users, I'm using the Qpid JMS (0.6.0). The provider of the service my client application connects to has informed me that it has changed it's message plattform from JBoss A-AMQ 6.1 to A-MQ 6.2:
/Please note AMQ 6.2 comes with an automatic heartbeat / connectivity monitoring built in [https://issues.jboss.org/browse/ENTMQ-763 ]. Connections timing out will result in an InactivityIOException if no data is received for a given time (defined by wireFormat.maxInactivityDuration). / I currently have configured the Qpid JMS API with "amqp.idleTimeout=-1" to prevent that idle connections are dropped by the client. Do I also need to set "transport.tcpKeepAlive=true" or something else to prevent that the connection will be dropped because of inactivity (by the broker)? Regards, Erik -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-Idle-timeout-inactivity-handling-tp7632838.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]
