Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.9.11, 1.10, 1.10.1, 1.10.2, 1.10.3, 1.10.4
-
None
Description
As of Now Situation
- If any of the JITL job is executed
- a new scheduler.log file is created
- scheduler.log is renamed as scheduler-old.log
Observation
- This issue is not observed in the release 1.9.3
- This issue started from release 1.9.4
- There was issue
JS-1455related with API method API method spooler_log.start_new_file(), which was fixed in release 1.9.4.
How to reproduce
- Let run job1
<job name="job1"> <script language="javax.script:ecmascript"> <![CDATA[ function spooler_process() { spooler_log.info( " start_new_file "); spooler.log().start_new_file(); } ]]> </script> <run_time /> </job>
- Let run job2
<job name="job2"> <script language="javax.script:ecmascript"> <![CDATA[ function spooler_process() { spooler_log.info( " hello world : "); } ]]> </script> <run_time /> </job>
- Check $SCHEDULER_DATA/log folder, scheduler.log will have same start date as the task start date and there will be a scheduler-old.log file.
Desired Behavior
- JITL jobs should not trigger rotate of scheduler.log
Attachments
Issue Links
- relates to
-
JS-1455 API method spooler_log.start_new_file() deactivates the log category {scheduler}
- Released