I have the same problem as here <http://activemq.2283324.n4.nabble.com/Artemis-Messages-stuck-in-quot-Delivering-quot-state-infinitely-td4716589.html>
Sometimes there is a situation when the queue "hang" messages. In the JMX console, the image is as follows: <http://activemq.2283324.n4.nabble.com/file/t379073/Queue_with_stuck_messages_in_JMX_console.jpg> It is evident that this queue has consumers, but messages are not consumed. Most likely, consumers are "hung". If you force the JMX console to close the session or the entire connection, an automatic reconnect will occur and the work will continue as usual. In the configuration of the broker, the policy "slow consumer" is configured to 10 messages per second, and also, the parameter <connection-ttl-override> is set to 30000. However, automatically the broker does not close the "hung" connections and they will be there for a very long time. How to configure automatic closing of such connections? -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
