When you create a new service, the default value for the maximum usage time is 600 seconds (10 minutes). In this situation, your choice of time interval may be influenced by firewall timeout settings. The default of 30Įnabling these checks may also help you if firewalls are closing ports to enterprise, workgroup, or desktop geodatabase after your services sit idle for a certain period of time. You also need to specifyĪn interval in minutes at which service connections will beĪutomatically validated (and repaired if needed). You can enable the data connection validity checks by openingĮditor dialog box in either ArcGIS for Desktop or Manager andĬhecking the check box Periodically check and repairĭata connections for idle instances. These checks prevent your service from appearing unresponsive afterĪ connection to enterprise, workgroup, or desktop geodatabase is dropped or interrupted. Mechanisms to check for invalid connections to enterprise, workgroup, or desktop geodatabase geodatabases. Server administrator to determine if connections to the source dataĪre being successfully maintained. When a service instance sits idle, it can be difficult for a If the service's maximum wait time is reached during this period, the logs record the same message that they normally would.
If there are not enough services available during recycling, a request is queued until an instance becomes available. In this way, recycling occurs without interrupting the user of a service. Recycling occurs in random order however, instances of services in use by clients are not recycled until released. Services are recycled one instance at a time to ensure that instances remain available and to spread out the performance hits caused by creating a new instance of each service. From that time forward, recycling will occur each time the recycling interval is reached.
You can also choose the time that the configuration is initially recycled. The default recycling interval is 24 hours, which you can change on the Service Editor dialog box. The time between recycling events is the recycling interval. This custom executable file would take the server name, service name, service type, and whether the service should be started or stopped as command line arguments.
Arcgis server configuration windows#
A good way to automate this process is to create a Python, shell, or Windows batch script that executes a custom ArcGIS Server administrative API command line executable file. To periodically return the number of running instances to the minimum specified, the service must be stopped and restarted. Recycling destroys and re-creates all running instances of a service, whether or not those instances are above the minimum specified. Although you will not see anything on your screen notifying you that recycling is occurring, you can see the events associated with recycling in the log files. Recycling occurs as a background process on the server. Recycling allows you to keep the pool of services fresh and cycle out stale or unusable services.ĭuring recycling, the server destroys, then re-creates, each instance in the service configuration. In some cases, services may become corrupted and unusable. For example, an application may incorrectly modify a service's state, or an application may incorrectly hold a reference to a service, making it unavailable to other applications or sessions. Through reuse, a number of things can happen to a service to make it unavailable for use by applications. Services are typically shared between multiple applications and users of those applications. Service recycling allows services that have become unusable to be destroyed and replaced with fresh services recycling also reclaims resources taken up by stale services.
0 kommentar(er)
