Details
-
Test Case
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Pre Test
- Setup a JobScheduler / Agent configuration for v1.7.3
- Start both JobScheduler (Master & Agent)
- Get the test configuration from
JS-1131and put it in the live folder of the master - Change to process-class into the sample pointing to the running agent
- start the test job1_remote
- stop master JobScheduler process will "kill" (e.g. via the task manager) => master JobScheduler will be killed
- be sure that the agent is killed, too.
Pre Test
- Setup a JobScheduler / Agent configuration for v1.7.4
- Start both JobScheduler (Master & Agent)
- Get the test configuration from
JS-1131and put it in the live folder of the master - Change to process-class into the sample pointing to the running agent
- start the test job1_remote
- stop master JobScheduler process will "kill" (e.g. via the task manager) => master JobScheduler will be killed
- the agent should always be running.
Expected behaviour
- the agent should never be killed in case of killing the master
- after restart of the master the job can be started again in a normal way
Attachments
Issue Links
- tests
-
JS-1131 Agent crashes when Master Scheduler process is killed
- Released