The error has nothing to do with the messages or fields in them. It is
saying that a client connection is trying to use the same AMQP
container-id as another existing client connection. The broker treats
the connection container-id as the ClientID in JMS terms, only
allowing one connection to use
I’m using ActiveMQ, Broker Engine Version 5.15.6 on AWS. The instance
size is mq.t2.micro, in Single-instance broker deployment mode.
A Golang application that has been working for years started
misbehaving. The calling application is getting error messages:
time="2023-02-23 21:35:17.1885"
