AMQ219010 is an error that comes from the Core client when an application is attempting to use a connection (e.g. to send a message) which has already been closed. If the connection worked fine when the broker was first started but then failed later that suggests to me some kind of infrastructure problem (e.g. firewall closing the idle connection).
It's not clear what you mean by, "we tried restart." Did you restart the broker or the client or both? Were you able to establish the connection initially after restart and then it failed eventually like before or were you not able to connect at all. Please clarify the details of your use-case otherwise we won't be able to help much. Justin On Tue, Oct 22, 2024 at 8:01 AM Rai, Pratheeka <pratheeka....@capgemini.com.invalid> wrote: > I have issues with Artemis Active MQ where I get the error "AMQ219010: > Connection is destroyed". After installing Artemis Active MQ 2.29.0 version > to Linux VM for a client, we are able to reach the MQ immedietly after > setup. But the MQ is not used frequently as we are still setting up our > infrastructure. When we try to reach the MQ after several days it throws > this error without any changes from our end. We tried restart, but that did > not help. > Please let me know if there are some changes in the configuration > This message contains information that may be privileged or confidential > and is the property of the Capgemini Group. It is intended only for the > person to whom it is addressed. If you are not the intended recipient, you > are not authorized to read, print, retain, copy, disseminate, distribute, > or use this message or any part thereof. If you receive this message in > error, please notify the sender immediately and delete all copies of this > message. >
