What does "Periodically check and repair data connections for idle instances" do in Arcgis Server Manager.

IkeJia

I had already read this page about Checking for invalid data connections section.

 https://enterprise.arcgis.com/en/server/latest/publish-services/windows/tuning-and-configuring-services.htm#ESRI_SECTION1_7D909BF9345747769D22CCE316213F95 

 

I am using SQL Server as geodatabase, could someone explain for me more about this option?

I had DynamicMappingHost service running 6, using 0, max instance 6.

And I checked "Periodically check and repair data connections for idle instances" for this service , config value is 5 minutes.

Is this meaning that all idle instance will reconnect to DB after a connection failure?
For test, I restart my SQL Server, but I don't see any ArcGis DB connection session reconnect in 5 minutes.
So I wonder to know what does this option do? How can I test the functionality to confirm it works?

34d72b82-a99b-4d59-97a7-6c8f2e0056f1.png

MattHowe_0-1744275658864.png

GlenterpriseUK

Hi @IkeJia,

The option "Periodically check and repair data connections for idle instances" does not actively reconnect all idle instances to the database every 5 minutes.

Q: "Is this meaning that all idle instance will reconnect to DB after a connection failure".

Not exactly. Idle instances are not automatically reconnecting on a timer. Instead ArcGIS Server validates the connection and only repairs it if its needed.

Q: "For test, I restart my SQL Server, but I don't see any ArcGis DB connection session reconnect in 5 minutes."

This is expected because the check runs but it does not necessarily create a visible SQL session immediately or force a reconnection unless its required. The process is silent and most probably you won't see much evidence in the logs or in SQL Server activity unless the service is actively used.

You can attempt a quick test:

1. Make sure that a service has at least one minimum pooled instance

2. Call the service to establish the initial connection

3. Let it go idle and restart the SQL Server once it goes idle

4. Wait longer than 5 minutes (or whatever value is configured) and call the service again

The call request should succeed and a new sql connection will likely be created at the moment of the request.

To sum it up, that setting is to protect users from stale or broken connections in idle pooled instances so that when they are reused they don't fail. Its not a keep-alive or automatic reconnection mechanism that runs in the bakground.

Regards,

Glen