Hi Jitesh,

On Fri, 2024-02-02 at 13:26 +0530, Jitesh Shetty wrote:
> Dear Apache Sling Team,
> 
> I hope this email finds you well. I wanted to reach out regarding
> some
> issues I've encountered while working with the Sling scheduler. Below
> are
> the points I'd like to address:
> 
> *1. Scheduler Process Issues:* While working with the Sling
> scheduler, I've
> encountered issues with its scheduler process. Despite having the
> correct
> cron expression, it seems to not be functioning as expected.

I think this is the root cause for your problems, and 2 and 3 are very
much related. I would encourage you to generate a reproducible scenario
where the Scheduler does not work as expected and create an issue at
https://issues.apache.org/jira/browse/SLING .

> 
> *2. Scheduler Behavior After Server Restart:* Additionally, there's a
> peculiar scenario where after restarting the server, the scheduler
> works
> for a certain period but then stops working. This behavior persists
> for
> sometimes even a day post-restart.
> 
> *3. Lack of Logging When Scheduler Stops Working:* One notable
> observation
> is that when the scheduler stops working automatically, there are no
> logs
> printed in the log file indicating whether it has been disabled or
> enabled.
> However, I do notice similar logs in the sling-scheduler.logs file.
> 
> *4. Discrepancy in Timestamps:* Furthermore, despite finding logs in
> sling-scheduler, they do not reflect the correct time I have
> specified. I
> suspect this might be due to server timestamp issues, but I'm having
> trouble pinpointing the exact cause.

Logs timestamps by default are generated by slf4j/logback, so any
issues should be traced back to those libraries. As you mentioned
though, I would first start with checking the server time accuracy
using the preferred tools for your OS.

Thank,
Robert

> 
> I'm reaching out to seek assistance and guidance on resolving these
> issues.
> Any insights or suggestions you could provide would be greatly
> appreciated.
> 
> Thank you for your attention to this matter.
> 

Reply via email to