Hi Team, We are using activemq-client-jakarta 5.18.0, activemq-broker 5.18.0 with spring boot 3.0 and jdk 17. We are consuming messages using @JmsListener initially having 1-5 concurrency. We are consuming mostly 2500-3000 messages from the queue as the part of some campaigns.
Now it works fine most of the days but once or twice in a week, we found that some of the messages got stuck in the queue which are not consumed but messages which pushed later got consumed successfully. We have to restart the pod every time in such cases to receive stuck messages. We tried some solution like not to use PooledConnectionFactory for consumers, also we changed concurrency setting to 5-5 so that consumer could not be killed but nothing worked. Could you please help me to find out the solution or is it a known ActiveMQ issue ? (please note that in JMS configuration, we are using ActiveMQConnectionFactory, DefaultJmsListenerContainerFactory, with JmsTemplate) Mit freundlichen Grüßen Gorav Singh externe Fachkraft von der Firma Coforge Limited im Auftrag der DB Systel GmbH SEZ Developer Unit Plot No. TZ-2 & 2A, Sector Tech Zone, Greater Noida, UP 201308 E-Mail: gorav.singh-ext...@deutschebahn.com<mailto:gorav.singh-ext...@deutschebahn.com> ________________________________ Pflichtangaben anzeigen<https://www.deutschebahn.com/pflichtangaben/20230607> Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: https://www.deutschebahn.com/de/konzern/datenschutz
