If there is an errant/inactive consumer on a destination, the best practice is to locate and remove/correct that consumer. Any actions taken to work-around its impact will be imperfect. For example, considering a timeout, what time period would be good to use? Too short and there's a risk of impacting a perfectly functioning consumer. Too long and the errant consumer causes some message processing to be delayed for a long time. Also, automatically termining the errant consumer doesn't prevent the consumer from be recreated, so it could only buy a very short reprieve.
There are ways to track down the errant consumer. Can you locate that consumer and resolve it? -- View this message in context: http://activemq.2283324.n4.nabble.com/Inactive-Expired-CONSUMER-tp4676865p4676914.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
