Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.7
-
None
Description
This issue occurs in the version 1.7.4177, where if a user has a job_chain with a shell job as its first node and has only one repeating order i.e. repeat="00:02", the order will run a first time and second time it will just hang without giviing out an error or a warning.
To reproduce the problem (see also attached example file)
- create a job_chain i.e. job_chain1
- create a shell job i.e. job1 shell command echo "hello world"
- create an order i.e. order id 1, everyday begin="00:00", end="24:00", repeat="00:02"
The order will run first time but second time It will just hang.
Some workarounds :
- Recommended solution
Change microscheduling to old microscheduling engine for the JobScheduler .
For this add the following parameter into the ./config/scheduler.xml and restart the JobScheduler.... <params> ... <param name="scheduler.old_microscheduling.enable_for_jobs" value="true"/> </params> ...
- Make the first job node an API job or give the shell job a monitor script.
<?xml version="1.0" encoding="ISO-8859-1"?> <job order="yes" stop_on_error="no"> <script language="shell"><![CDATA[ echo "Hello World!!!" ]]></script> <monitor name="js-1172-workaround" ordering="0"> <script language="javascript"><![CDATA[ function spooler_task_before() { return true; } ]]></script> </monitor> <run_time /> </job>
- Create more than one order with a run_time assigned to the job_chain.
Attachments
Issue Links
- mentioned in
-
Page Loading...