Describe the bug
The antivirus scan is done by a java job. This job is affected by a XWiki issue https://jira.xwiki.org/browse/XWIKI-14494 , which means that after the antivirus app upgrade the scan job will not work anymore until a manual unschedule / schedule is done. So, as part of #32 an automatic unschedule / schedule was added.
Now, on another app that uses the same 'trick', a bug was reported as this isn't actually working all the time xwikisas/application-licensing#177
Even if we haven't received reports that this has happened on antivirus as well, most probably users haven't checked the job status. It's hard to reproduce on our side since it's not happening all the time.
Steps to reproduce
- Have antivirus app
- Check
Antivirus Job scheduler job status, since this should be scheduled
- Trigger job and check that it is executed correctly
- Upgrade antivirus app
- Check again the job status
- Trigger job and check that it is executed correctly
Expected behavior
Job is scheduled after upgrade and triggering it works as expected
Actual behavior
Just sometimes, after an upgrade, the job remains in a broken state. This might means that it is not marked as scheduled, or even if it is scheduled, triggering it will throw errors
Additional context
Please apply the same suggestions as on xwikisas/application-licensing#177 (comment)
Describe the bug
The antivirus scan is done by a java job. This job is affected by a XWiki issue https://jira.xwiki.org/browse/XWIKI-14494 , which means that after the antivirus app upgrade the scan job will not work anymore until a manual unschedule / schedule is done. So, as part of #32 an automatic unschedule / schedule was added.
Now, on another app that uses the same 'trick', a bug was reported as this isn't actually working all the time xwikisas/application-licensing#177
Even if we haven't received reports that this has happened on antivirus as well, most probably users haven't checked the job status. It's hard to reproduce on our side since it's not happening all the time.
Steps to reproduce
Antivirus Jobscheduler job status, since this should be scheduledExpected behavior
Job is scheduled after upgrade and triggering it works as expected
Actual behavior
Just sometimes, after an upgrade, the job remains in a broken state. This might means that it is not marked as scheduled, or even if it is scheduled, triggering it will throw errors
Additional context
Please apply the same suggestions as on xwikisas/application-licensing#177 (comment)