Leiste mit Community-Erfolgen erweitern.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.

GELÖST

Polling config / scheduler stopped importing

Avatar

Level 4

Hi, in our AEM application we have a poll config used to import a stockquote into our repo. simple.  It is scheduled to trigger each 300 sec. (5 minutes) However, for some reason, the process got stuck, and it stopped importing.  I looked in the log files, I found no trace of an error that could have caused the stoppage.

I restarted the scheduler bundle, and it fixed my problem. Data is now coming in.

Do you guys have an opinion on what may have caused the scheduler to stop triggering?

Thank you.

1 Akzeptierte Lösung

Avatar

Korrekte Antwort von
Level 10

JS Bournival wrote...

Hi, in our AEM application we have a poll config used to import a stockquote into our repo. simple.  It is scheduled to trigger each 300 sec. (5 minutes) However, for some reason, the process got stuck, and it stopped importing.  I looked in the log files, I found no trace of an error that could have caused the stoppage.

I restarted the scheduler bundle, and it fixed my problem. Data is now coming in.

Do you guys have an opinion on what may have caused the scheduler to stop triggering?

Thank you.

 


Most of the cases I have seen is happening due to job gets blacklisted if custom implementation throws an uncaught exception.  To identify set the log level to DEBUG on org.apache.sling.commons.scheduler  & when issue reoccur you could find the cause for it.

Lösung in ursprünglichem Beitrag anzeigen

2 Antworten

Avatar

Korrekte Antwort von
Level 10

JS Bournival wrote...

Hi, in our AEM application we have a poll config used to import a stockquote into our repo. simple.  It is scheduled to trigger each 300 sec. (5 minutes) However, for some reason, the process got stuck, and it stopped importing.  I looked in the log files, I found no trace of an error that could have caused the stoppage.

I restarted the scheduler bundle, and it fixed my problem. Data is now coming in.

Do you guys have an opinion on what may have caused the scheduler to stop triggering?

Thank you.

 


Most of the cases I have seen is happening due to job gets blacklisted if custom implementation throws an uncaught exception.  To identify set the log level to DEBUG on org.apache.sling.commons.scheduler  & when issue reoccur you could find the cause for it.

Avatar

Level 4

will look into this. thanks for the advice.