Updating the logger to include the SERVICELOG will provide the stack trace from the broker and the source of the error will help track this down.
org.apache.activemq.TransportConnection.Service = DEBUG -Matt Pavlovich > On Aug 11, 2025, at 7:47 AM, KASSA Máté <[email protected]> wrote: > > 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é > <http://www.scientificgames.com/> Máté KASSA > Junior DevOps Engineer > Scientific Games > M: +36 30 094 1393 > > 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.
