Hi, Just some clarification for the below story. The events-dispatcher is a service we use for publishings messages, its the only container containing publishers. We use spring-boot-starter-amqp for communicating with both RMQ and AMQ.
Our problem is simple: AMQ just drops messages and our producer doesnt care about it. Of course as you said we should set syncronous mode to deal with it, but it had some negative effect on performance (I'm still trying to figure out how could RMQ be fast enough on quorum queues no less) Either way, even if its async, it shouldn't drop messages "randomly". The producer doesn't log any errors and we are running on INFO level. AMQ itself only logs the below line, even tho we tried to add the DEBUG options. Any idea is welcome at this point, as I only left with two choices: - Switch to sync producers for AMQ - Switch to RMQ Thank you! Mátyás [cid:image001.png@01DC0ACF.4C097AF0]<http://www.scientificgames.com/> Mátyás SZOMBATHY Lead DevOps Engineer (UPAM) Scientific Games M: +36 30 950 6846 HAVE FUN. DO GOOD. PLAY HEALTHY. May be privileged. May be confidential. Please delete if not the addressee. [cid:SGlogo_f3831c59-1ff5-46dd-9228-397252e47acd.png]<http://www.scientificgames.com/> Mátyás SZOMBATHY Lead DevOps Engineer Scientific Games M: +36 30 950 6846 HAVE FUN. DO GOOD. PLAY HEALTHY. Scientific Games Kft., 1011 Budapest, Fő utca 14-18, Hungary May be privileged. May be confidential. Please delete if not the addressee. From: KASSA Máté <mate.ka...@scientificgames.hu> Sent: Monday, August 11, 2025 2:47 PM To: users@activemq.apache.org Cc: UPAM_DEVOPS <upam_dev...@scigames.at> Subject: Issue with Lost Events in ActiveMQ Classic 6.1.X Dear Support, I'm reaching out regarding an issue with an ActiveMQ instance where certain events are reported as published but are never consumed - indicating they were never actually received. Each time this occurs, we observe the only following warning in the AMQ log: * 2024-04-01 10:25:18,236 | WARN | Async error occurred | org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: tcp:///11.11.111.11:58808@61515 Notably, the event dispatcher does not raise any errors when this happens, which suggests the issue may be internal to ActiveMQ. In a previous response, I was informed that: - This error is caused by any process that fails on the broker side and is handled by the serviceException method. The resulting behavior is that the exception is sent to the client. - You can try disabling sendAsync and rely on client acknowledgments instead, if you're currently using sendAsync on the producer. Could you please help clarify what might be causing this issue and suggest any further steps (guide) to resolve it? Thank you in advance. Best regards, Máté
