I am using ActiveMQ 5.3.1 and running into a scenario where consumers will
sometimes stop reading from the socket, leaving the transport write in a
blocked state (known issue). I have configured the transport.soWriteTimeout
in the transport URI and the socket does close after the timeout period, but
it leaves the connection to the consumer open. Is there a way to confugre
the broker to close the consumer connection after such a timeout?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Remove-consumer-from-broker-if-socket-is-closed-due-to-write-timeout-tp2537877p2537877.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
