We will try it. Thanks for the advice! -----Original Message----- From: Justin Bertram <jbert...@apache.org> 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, opening attachments or clicking embedded links. *** 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 settings. First, it's recommended that clientFailureCheckPeriod be significantly lower than connectionTTL [1] (e.g. half). Second, I'd recommend increasing connectionTTL to be more than callTimeout. Lastly, I recommend you make all your connection-related settings in the same place rather than split between code & configuration. Putting all this together, you might try something like this: (tcp://dm-activemq-live-svc:61616,tcp://dm-activemq-backup-svc:61617)?ha=true&reconnectAttempts=200&initialConnectAttempts=200&clientFailureCheckPeriod=7500&connectionTTL=15000&callTimeout=10000&retryInterval=1000&retryIntervalMultiplier=1.5&maxRetryInterval=4000 Justin [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__activemq.apache.org_components_artemis_documentation_latest_connection-2Dttl.html-23detecting-2Dfailure-2Dfrom-2Dthe-2Dclient&d=DwIFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=VpU5fPwEQ8wKbKY5SBkV1DYypS_WKWolD9Eue6u6sYo&m=uk5DBLChLtwQrj_ZnjtJ9xolF5pa7gRhP8DSCRwFwy8_k9nEYCXhko9064nne9xH&s=lZ6nJ0O9HDSzLYx07BxK56BdZ6ZH4rqEp7LiRMTqllU&e= On Wed, Nov 20, 2024 at 4:31 PM John Lilley <https://urldefense.proofpoint.com/v2/url?u=http-3A__john.lilley-40redpointglobal.com&d=DwIFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=VpU5fPwEQ8wKbKY5SBkV1DYypS_WKWolD9Eue6u6sYo&m=uk5DBLChLtwQrj_ZnjtJ9xolF5pa7gRhP8DSCRwFwy8_k9nEYCXhko9064nne9xH&s=WAwgV2yiJaYeN8Gvn5vyxSqmUhVehv3s6GJ6Oiq-MQ0&e=> wrote: > 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 the request when it is > received, which is right about when the client reports the warning at the > 1-second mark.. > > >> Do you have any idea what's happening during this 60-second window? > Have you, for example, gathered any thread dumps from the client > during this time to see exactly what it's doing? If so, what did they > show? If not, could you? > > I attached the thread dump for our "client", which is the thing seeing > the timeout issues. Unfortunately I am not able to make much of it, > not knowing Artemis driver internals and there are a LOT of artemis threads. > > >> That said, it would be worth knowing *all* the connection-related > parameters you're setting on the client. Can you provide that info? > > These are the only things being set on the connection factory: > connectionFactory.setRetryInterval(1000); > connectionFactory.setRetryIntervalMultiplier(1.5); > connectionFactory.setMaxRetryInterval(4000); > > But we also set these on the client connection URL > clientFailureCheckPeriod=10000&connectionTTL=10000&callTimeout=10000 > > The overall connection URL is > > (tcp://dm-activemq-live-svc:61616,tcp://dm-activemq-backup-svc:61617)? > ha=true&reconnectAttempts=200&initialConnectAttempts=200&clientFailure > CheckPeriod=10000&connectionTTL=10000&callTimeout=10000 > > Thanks > john > PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is > confidential and is intended solely for the use of the individual(s) > to whom it is addressed. If you believe you received this e-mail in > error, please notify the sender immediately, delete the e-mail from > your computer and do not copy, print or disclose it to anyone else. If > you properly received this e-mail as a customer, partner or vendor of > Redpoint, you should maintain its contents in confidence subject to > the terms and conditions of your agreement(s) with Redpoint. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org For > further information, visit: > https://urldefense.proofpoint.com/v2/url?u=https-3A__activemq.apache.o > rg_contact&d=DwIFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=Vp > U5fPwEQ8wKbKY5SBkV1DYypS_WKWolD9Eue6u6sYo&m=uk5DBLChLtwQrj_ZnjtJ9xolF5 > pa7gRhP8DSCRwFwy8_k9nEYCXhko9064nne9xH&s=HrIqZWlKmtxk4HYX6DDbCJT46uPEW > rjRhrjmIejfKZg&e= > ---------- This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam: https://us5.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5fca03f960214c74da99a142ea77479aae4171c3d501b081d0f149a046817985b058c0810768c9312001ffdea453a1415fabdc91d9ec66a95857c5c336c19b34a79bc8702947e98e64cbc3b19f41091069f1b2b7df4a250e15520475336fff0d4242b1d6beb08ae0dd0a17668ba33f2dc055c6e273f8bd321281e47e642c005535279b4bad1389935599222b59a40ad8ead68e92346c199cd8
