Carsten Ziegeler created SLING-9906:
---------------------------------------
Summary: Avoid retrying to load jobs if classes are missing
Key: SLING-9906
URL: https://issues.apache.org/jira/browse/SLING-9906
Project: Sling
Issue Type: Improvement
Components: Event
Reporter: Carsten Ziegeler
Fix For: Event 4.2.14
When a Sling job is tried to be loaded, it might reference public api classes
provided by bundles - although that is a bad pattern that should be avoid,
sometimes this is used.
While the job engine does not try to reload those jobs for execution - unless
such a new job is created (which is unlikely as the class is missing), the
re-assigning of jobs from a removed instance to a new one suffers from the same
problem. And that is retried over and over again.
So there are probably several possible improvements:
- make sure that jobs are not reloaded when public classes are missing during
job execution (unless bundles have changed)
- reduce log output to a log statement (except of stack trace) if classloading
for jobs fails
- change re-assigning of jobs to not require classes to be available. This can
probably be solved by using ResourceResolver.move
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
