Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Admin - Scheduler |
| Version | 14.0 |
Product: Aqua Data Server
Version: 13.0.5
Build #: 33675
Build Date: 2013-Aug-21 09:33:30 AM
Operating Environment: Linux (3.2.0-29-generic, amd64) / UTF-8 / en / US / Sun Microsystems Inc. 1.6.0_27-b07
Memory: Max=477,233,152; Total=99,876,864; Free=19,980,392;
Server Info: Apache Tomcat/6.0.33
DB Version: 2.220
Custom Scheduled Job Doesn't Respect Occurence Frequency
1. Create a sample AquaScript with 1 line which will print name
2. Created a scheduled job with properties
Occurence = Custom
Every 240 minutes
3. If you look at the execution history of the newly created job, you can see that the job is executed every 1 minutes which is incorrect.
|
|
148 KB
|
|
60 KB
|
|
101 KB
@Tariq, did you attach the correct screenshot? The screenshot doesn't match the description of this issue. It says:
Occurrence: Every 2400 minute(s)
But the execution history on the screenshot shows the jobs were executed every 1 minute.
I have attached the correct screenshot for the job with 240 minutes. Yes, the jobs are executed every 1 minute.
I have attached the correct screenshot for the job with 240 minutes. Yes, the jobs are executed every 1 minute.
The schedule controller uses the repeat code of 'm' (same as "Every Minute") as the unit and the period for the number of units. However, the schedule service manager expected a repeat code of 'c' (custom) which is never set. The fix is to change the schedule service manager to check for a non-null period to mean a custom repeat code.
The schedule controller uses the repeat code of 'm' (same as "Every Minute") as the unit and the period for the number of units. However, the schedule service manager expected a repeat code of 'c' (custom) which is never set. The fix is to change the schedule service manager to check for a non-null period to mean a custom repeat code.
Can you port this to AD Server for v13 as well ?
Can you port this to AD Server for v13 as well ?
Verified in ADServer-17.0.0-GA-21. Refer updated screenshot '2904_ADS-17-GA-21.png'
Verified in ADServer-17.0.0-GA-21. Refer updated screenshot '2904_ADS-17-GA-21.png'
Issue #2904 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
@Tariq, did you attach the correct screenshot? The screenshot doesn't match the description of this issue. It says:
Occurrence: Every 2400 minute(s)
But the execution history on the screenshot shows the jobs were executed every 1 minute.