Are messages being added to the queue at a rate of 10 per second? If not, the algorithm will take that into account and it won't close consumers because in situations like that every consumer would be disconnected with message production slows down which is generally not desirable.
Also, consumers can be hung in terms of message consumption but can still be sending/receiving heartbeats to/from the broker. If your consumers are hung you need to determine why they are hung and fix the problem. If you think there's a bug in the implementation (which I don't rule out) please provide some kind of test-case to reproduce the problem. Justin On Fri, May 25, 2018 at 3:40 AM, Egiptman <gvv_h...@inbox.ru> wrote: > 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 >
