I'm struggling with configuring for coping with broken connections. I'm getting the impression that MQ removes inactive connections._I assume the following happens_: When a destination does not receive any message for a long time -> the consumer connection is not active for a long time and eventually removed on MQ.so I try to send heartbeats so the connection is always active and won't be removed. And set a grace period so It won't have unnecessary disconnections.I find a few words about this configuration on ActiveMQ documentation but that just won't work for me. Maybe it's because AWS managed AMQ is slightly different.... (https://activemq.apache.org/stomp)Does anyone have any good direction for me ? Maybe another way of avoiding a dead connection on consumer ?
-- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
