Hi Kassa- Please note that the ‘dev@‘ mailing list is for conversation about making coding changes to ActiveMQ itself. A question, such as this, about using ActiveMQ should be on the ‘users@‘ mailing list.
This error is caused by any process that the broker-side fails and is handled by this serviceException method. The resulting behavior is that the exception is sent to the client. The log should include a more detailed message that would help identify what is causing this. Do you have more detailed log messages? Thanks, Matt > On Jun 23, 2025, at 2:56 AM, KASSA Máté <mate.ka...@scientificgames.hu> wrote: > > Hi everyone! > > I hope you are doing well. I would like to ask for some support in the > following topic: > > I have a running Active MQ instance (Apache ActiveMQ Classic 6.1.6) in which > some events are lost (notified as published but never consumed because never > received) and each time it happens we can see in the AMQ log the following > message: Async error occurred | > org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: > tcp:///11.11.111.11:58808@61515. The events dispatcher doesn't trigger any > error when it happens so it look at an internal AMQ error. > > Based on my recent findings, the problem can be resolved in 2 possible ways: > Broker constraint and configuration (such as message dispatching settings, > etc.) > Combining Application-level hooks (handling shutdown signals) and > Orchestrator configurations (grace period settings) > > Could someone please confirm these solutions or give me explanation about the > problem? > > Thank you in advance. > > Best, > Mate > <http://www.scientificgames.com/> Máté KASSA > Junior DevOps Engineer > Scientific Games > M: +36 30 094 1373 > > 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.
