Adaptive Server introduces a Job Scheduler automatic restart feature that is implemented during various states of Job Scheduler Agent (JS Agent) and Job Scheduler Task (JS Task).
This may be as a result of the connection in a pool stopping, or if the target server has stopped while collecting results.
In this situation, both the JS Task and JS Agent are shut down and restarted.
This may be as a result of an inconsistency detected in Job Scheduler tables; alternatively, it may be due to incorrect or missing job callouts.
In this situation, both the JS Task and JS Agent are shut down and restarted.
This may be as a result of JS Agent hitting a fatal signal, JS Agent shutting down due to inconsistency detected in its operation, or an external event, such as the killing of a JS Agent process.
JS Task periodically monitors JS Agent health. If it finds that the JS Agent has stopped, it will restart the JS Agent.
In this situation, you must manually restart Adaptive Server. A new JS Task aborts the existing JS Agent, if any, and starts a new JS Agent.
Default value | 3 |
Range of values | 0 – 10 |
Status | Dynamic |
Display level | 10 |
Required role | System administrator |
Configuration group | SQL Server Administration |
Restricts the number of restart attempts and prevents the Job Scheduler restart feature from going into an infinite loop. The value 0 indicates that the Job Scheduler Auto restart feature is disabled.
Default value | 0 (Job Scheduler logging disabled) |
Range of values | 0, 1 |
Status | Dynamic |
Display level | 10 |
Required role | System administrator |
Configuration group | SQL Server Administration |
Enables or disables diagnostics logging after the restart of Job Scheduler.
Default value | 1 |
Range of values | 1 – 1440 |
Status | Dynamic |
Display level | 10 |
Required role | System administrator |
Configuration group | SQL Server Administration |
The intervals between two JS Agent heartbeat checks, in minutes.