Hello Justin,
Could you please share your point of view regarding.
"Based on the "retry-interval" frequency, there is a connection tentative from
the primary server which turns out in this ERROR message AMQ214016 and flooding
logs
When not using SSL, there is a WARNING reported in logs at sa
Justin,
Thanks again for taking a look at this,.
I've attached the thread dump, as well as our broker configuration file.
>> What logging do you see that indicates the packet was sent?
We have a "client" side and a "server" side of the app. Each packet has a
unique ID, and our "server" logs t
> After ten seconds, the packet appears to be sent, but we log its delivery
in our service.
What logging do you see that indicates the packet was sent?
To be clear, if the client doesn't receive an acknowledgement from the
broker (e.g. due to a network issue, broker crash, etc.) that the message
Hi Justin,
I appreciate you taking the time.
We've been hitting this issue in various forms for a while. There appear to be
two conditions in which we see this:
- The active member of our HA broker pair is moved by Kubernetes and fails over
to the backup
- The connection between our AMQ client
