We will try it. Thanks for the advice!
-Original Message-
From: Justin Bertram
Sent: Thursday, November 21, 2024 7:44 AM
To: users@activemq.apache.org
Subject: Re: Warning around reconnect attempt
*** [Caution] This email is from an external source. Please use caution
responding
Unfortunately the thread dump didn't provide any meaningful information.
Did you acquire it during the 60-second window while the client was
attempting to reconnect to the broker? There were essentially no active
threads in the thread dump.
I'd recommend a few adjustments to your connection settin
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
> We want to shorten this one-minute reconnect interval, ideally to < 30
> seconds. What combination of settings will do this?
>
> Thanks
> john
>
> -----Original Message-
> From: Justin Bertram
> Sent: Tuesday, November 19, 2024 2:52 PM
> To: users@activemq.
m
Sent: Tuesday, November 19, 2024 2:52 PM
To: users@activemq.apache.org
Subject: Re: Warning around reconnect attempt
*** [Caution] This email is from an external source. Please use caution
responding, opening attachments or clicking embedded links. ***
> 1- Should we
> 1- Should we be setting connectionFactory.setConfirmationWindowSize()?
The docs for confirmationWindowSize are here [1]. Whether you should set
this parameter is really up to you and the behavior you want for your
application.
> 2- Are the retry settings reasonable?
"Reasonable" is hard to jud
2024-11-19 14:19:51,426 WARN [org.apache.activemq.artemis.core.server]
AMQ222066: Reattach request from 10.147.133.72:53082 failed as there is no
confirmationWindowSize configured, which may be ok for your system
This was issued by the broker at the same time that our JMS client issued this
wa
