A cold start means a complete failure of the entire environment. This is not necessarily feasible for every environment at any time...
So: Thanks
@Pete Wirfs for posting the workaround.
In my eyes, that's a bug in Automic. Unfortunately, it will be difficult to get a permanent solution, because you can't reliably reproduce the error... :-(
------------------------------
Automation Evangelist
Fiducia & GAD IT AG
---
Mitglied des deutschsprachigen Automic-Anwendervereins FOKUS e.V.
Member of the German speaking Automic user association FOKUS e.V.
------------------------------
Original Message:
Sent: 11-20-2019 03:43 AM
From: Thierry Tarrason
Subject: The mqsrv table is not properly maintained(?)
Hi Pete,
I might be mistaken, but if i remember correctly a coldstart will clean up the MQ* tables.
------------------------------
Best regards,
Thierry
Banque de Luxembourg
Original Message:
Sent: 11-18-2019 03:05 PM
From: Pete Wirfs
Subject: The mqsrv table is not properly maintained(?)
This weekend some of our non-prod servers were patched and rebooted. Over the course of the weekend the DEV AE server was also rebooted. This morning we could not get two of the non-prod agents to connect to our DEV AE. I rebooted the AE server and that didn't fix it. I contacted support and they had me delete the related agent rows out of the mqsrv table. Then everything worked.
This seems pretty bad to me, that the product seems to retain an "I'm connected" row to an agent even through a reboot cycle.
Have others encountered this? How do you mitigate the issue?
We are running our AE's on V12.3.0, Windows, SQLServer
------------------------------
Pete
------------------------------