Table of Contents |
---|
Known Issue Status
Occurrence |
| |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Change Management Issue |
|
Behavior
- Passed Test Case
- Starting Situation
- A holidays.xml file is being included into a order for "non working days"
- order.xml and holiday.xml are deploy in to the Jobscheduler
- Jobscheduler read the order.xml and included file holidays.xml
- Jobscheduler suppress the job execution for dates defined as "non working days" in the holidays.xml
- Action
- Check JOC and right click on the order --> show start times --> submit
- Behavior
- Jobscheduler will show all dates jobs will be executed. Jobscheduler will supress execution for "non working days"
- Starting Situation
- Failed Test Case
- Starting Situation
- A holidays.xml file is being included into a order for "non working days"
- User apply changes into the holiday.xml and deploy it in to Jobscheduler.
- Jobscheduler does not read CHANGES from the holiday.xml file.
- Action
- Check JOC and right click on the order --> show start times --> submit
- Behavior
- The Jobscheduler will ignore the changes from holiday.xml file and will execute jobs on "not working days".
- Starting Situation
- Explanation
- Jobscheduler read new or changed job, job chain, order and schedule files as soon as they are deployed in the Jobscheduler live folder. Jobscheduler does not reload changes done in the included files i.e. holidays.xml
Requirement
- The Jobscheduler should auto reload changes done in the include holidays.xml file needed by order.xml.
Workaround
- Solution 1: Restart Jobscheduler
- from JOC Menu
- from command line
$SCHEDULER_HOME/bin/jobscheduler.[cmd/sh] restart
- Solution 2: Reload job configuration
- update all the orders using system command i.e. Linux touch command
touch $(grep -Rl 'bank-holidays.xml' *.order.xml)
- update all the orders using system command i.e. Linux touch command