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 - Activation |
| Version | 1.0 |
Assuming you have a long running job.
0. run the long running job.
1. delete the job in the scheduler.
2. now try to view the running jobs.
you'll get a NPE.
2 possible fixes
0. check in the scheduler controller (/app/admin/scheduler?status=RUNNING) to see if the job info is null. If so, don't try to get info for the schdule job (will you can't anyway, it's null, it's really should be checking for nulls)
1. check in the EditScheduleController(/app/home/project/*/scheduled_job/*/delete) to see if there are running jobs scheduled. if there are, tell the users they have to wait for the job to finish before they can delete the scheduled job.
option 0 is an easy fix
option 1 is a more difficult fix but weill result in a better user experience, maybe.
ok, we are going with the easy option.
0. Allow the user to delete the schedule job and when someone tries to view the running jobs don't display the deleted job even when it's running
1. in the schedule job queue, check to see if the job exist before writing to the schedule log to prevent orphan records.
REV:15748
0. Allow the user to delete the schedule job and when someone tries to view the running jobs don't display the deleted job even when it's running
1. In the schedule job queue, check to see if the job exist before writing to the schedule log to prevent orphan records.
related to #1089
REV:15748
0. Allow the user to delete the schedule job and when someone tries to view the running jobs don't display the deleted job even when it's running
1. In the schedule job queue, check to see if the job exist before writing to the schedule log to prevent orphan records.
related to #1089
Null Pointer Exception Not encountered any more , but I was not able to see the job in the Running Tab of ADMIN. Closing the NPE issue - will log another one if I reproduce it correctly
Null Pointer Exception Not encountered any more , but I was not able to see the job in the Running Tab of ADMIN. Closing the NPE issue - will log another one if I reproduce it correctly
you shouldn't see the job anymore in the running tab becuse if it's deleted and it's still running we are not displaying it.
you shouldn't see the job anymore in the running tab becuse if it's deleted and it's still running we are not displaying it.
Issue #1099 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
ok, we are going with the easy option.
0. Allow the user to delete the schedule job and when someone tries to view the running jobs don't display the deleted job even when it's running
1. in the schedule job queue, check to see if the job exist before writing to the schedule log to prevent orphan records.