Details
-
Test Case
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Pre Test
- Setup a JobScheduler / Agent configuration for v1.8.x
- Put configuration of js1188.zip (see attachment) into the live folder
- Change the adresses of remote_scheduler in my-agents.process_class.xml to adress the installed agent (the first process_class is to adress the master itself).
- Start both JobScheduler (Master & Agent)
Test
- start the job js-1188
- check task log to be sure that the task was executed at the master
- start the job js-1188 again
- check task log to be sure that the task was executed at the agent
- start the job js-1188 again
- check task log to be sure that the task was executed at the master
- shut down the agent
- start the job js-1188 again
- check task log to be sure that the task was executed at the master
- check that task log contains a message like this:
SCHEDULER-488 This remote JobScheduler ... is not accessible.
Attachments
Issue Links
- tests
-
JS-1188 A process_class can reference multiple JobScheduler instances
- Released