When submitting any jobs, such as editing a service configuration, the runAsync parameter is defaulted to false. However, code examples in the documentation are starting to include a runAsync=true paramater without explanation.
ArcGIS Server does not currently perform any job management to ensure that the server does not run itself into the ground. This has been confirmed in case 04154139 as being due to the fact that additional ArcSOC processes will be started up.
When there are multiple users (i.e. nearly every installation) it is then possible to use up all resources resulting in service unavailability. This additionally appears to be an issues when the services recycling (by default at 00:00) which causes additional ArcSOC processes to be started up above the maximum capability of the server (cases 03793148, 03788078)
ArcGIS Server should perform management of the job queue and not just allow these all to run directly. Any enforced limits of resources should be possible to define, or be derived from system statistics.
