Consumer count is zero in AMQ console even if consumer application is up and running
We have deployed replicated fail-over AMQ in our environment. There are 3 queues are listening to consumer application. Consumer count for one of the queue becomes zero. This issue is happening intermittent.
Client connected JNDI settings
connectionFactory.ConnectionFactory=(tcp://127.0.0.1:61616,tcp://127.0.0.1:61617)?ha=true&reconnectAttempts=-1
AMQ deployed in replicated HA,
master in 127.0.0.1:61616, slave in 127.0.0.1:61617
Noticed following log in artemis.log
16:30:30,261 WARN [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /127.0.0.1:38052 within the 60,000ms connection TTL. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
16:30:30,261 WARN [org.apache.activemq.artemis.core.server] AMQ222061: Client connection failed, clearing up resources for session
appreciate your response in advance. Thanks and Regards Rony
Attachments
Responses
Hi Torsten,
we are facing this issue, and we are using the version 7.8.0.
2021-11-29 05:48:45,033 WARN [org.apache.activemq.artemis.core.client] (Thread-10 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@5b03b9fe)) AMQ212037: Connection failure to /10.20.2.235:38402 has been detected: AMQ229014: Did not receive data from /10.20.2.235:38402 within the 30,000ms connection TTL. The connection will now be closed. [code=CONNECTION_TIMEDOUT
Thanks & Regards
Rajesh
We are also facing this issue:
2022-01-23 14:06:02,518 WARN [org.apache.activemq.artemis.core.client] (Thread-886 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@53deafe1)) AMQ212037: Connection failure to /169.177.230.245:35738 has been detected: AMQ229014: Did not receive data from /169.177.230.245:35738 within the 60,000ms connection TTL. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
@Rony, Is the issue resolved? We have seen similar issue where the consumer count is reduced to 0. We are using AMQ 7.8.6.
@Thulasi was the consumer count reduced to 0 but message got still consumed? Or did you not see any message consumption? Some messaging clients (such as Camel-JMS or Spring JMS) when configured incorrectly may re-create new JMS consumer (and JMS session and connection) for every single message. As consumers get registered and unregistered all the time, the brokers statistics (which only refresh every 5 seconds or so) may report a 0 consumer count. But messages would still get processed.
If you don't find messages getting processed either, then please check broker and client logs for errors.