Thanks for the reply. I don't have the stack trace currently with me and I have not been able to reproduce this issue. In my broker I log hourly destination stats and for this particular topic I observed that the messages consumption doesn't stop immediately rather it happens overtime.
[destName: queue://app.heartBeat | enqueueCount: 160014 | dequeueCount: 160014 | dispatchCount: 160014 | expiredCount: 0 | inflightCount: 0 | msgsHeld: 0 | msgsCached: 0 | memoryPercentUsage: 0 | memoryUsage: 0 | memoryLimit: 134217728 | avgEnqueueTimeMs: 23540.421475620882 | maxEnqueueTimeMs: 3159190 | minEnqueueTimeMs: 1 | currentConsumers: 10 | currentProducers: 0 | blockedSendsCount: 0 | blockedSendsTimeMs: 0 | minMsgSize: 1033 | maxMsgSize: 1074 | avgMsgSize: 1057.1182958991087 | totalMsgSize: 169153727] – all messages consumed till now. [destName: queue://app.heartBeat | enqueueCount: 160408 | dequeueCount: 160274 | dispatchCount: 160274 | expiredCount: 0 | inflightCount: 0 | msgsHeld: 134 | msgsCached: 0 | memoryPercentUsage: 0 | memoryUsage: 0 | memoryLimit: 134217728 | avgEnqueueTimeMs: 23502.23844790796 | maxEnqueueTimeMs: 3159190 | minEnqueueTimeMs: 1 | currentConsumers: 10 | currentProducers: 0 | blockedSendsCount: 0 | blockedSendsTimeMs: 0 | minMsgSize: 1033 | maxMsgSize: 1074 | avgMsgSize: 1057.1288090369558 | totalMsgSize: 169571918] – messages consumed 260/394, held - 134 [destName: queue://app.heartBeat | enqueueCount: 160697 | dequeueCount: 160462 | dispatchCount: 160462 | expiredCount: 0 | inflightCount: 0 | msgsHeld: 235 | msgsCached: 0 | memoryPercentUsage: 0 | memoryUsage: 0 | memoryLimit: 134217728 | avgEnqueueTimeMs: 24854.09577345415 | maxEnqueueTimeMs: 3159190 | minEnqueueTimeMs: 1 | currentConsumers: 10 | currentProducers: 0 | blockedSendsCount: 0 | blockedSendsTimeMs: 0 | minMsgSize: 1033 | maxMsgSize: 1074 | avgMsgSize: 1057.1415956738458 | totalMsgSize: 169879483] – messages consumed 188/289 [destName: queue://app.heartBeat | enqueueCount: 160979 | dequeueCount: 160462 | dispatchCount: 160462 | expiredCount: 0 | inflightCount: 0 | msgsHeld: 517 | msgsCached: 0 | memoryPercentUsage: 0 | memoryUsage: 0 | memoryLimit: 134217728 | avgEnqueueTimeMs: 24854.09577345415 | maxEnqueueTimeMs: 3159190 | minEnqueueTimeMs: 1 | currentConsumers: 10 | currentProducers: 0 | blockedSendsCount: 0 | blockedSendsTimeMs: 0 | minMsgSize: 1033 | maxMsgSize: 1074 | avgMsgSize: 1057.1541691773461 | totalMsgSize: 170179621] – messages consumed 0/282 After this no messages are consumed. Another thing is that the usual hourly heartbeat message rate is 492 messages/hour but it gradually decreases during this time to 282. In my producer, I create a consumer and wait for the acknowledgement using consumer.receive() call with 60s timeout and at listener side I send back the acknowledgement for heartbeat by creating a producer using the same underlying session that I get in session aware listener. I am using selectors for this kind heartbeat messaging and acknowledgement (with persistent messages). I have one question, The producer closes the session on its side under which it sent the heartbeat message once it fails to receive an acknowledgement (may be due to timeout), what will be the behavior of session aware listener on consumer side (which will use same session to send back the ack)? Thanks, Abhi Does this behavior points in some direction I should look for? -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-not-able-to-consumer-messages-from-queue-tp4689594p4689632.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
