Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
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.
Gelöst! Gehe zu Lösung.
Zugriffe
Antworten
Likes gesamt
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.
Zugriffe
Antworten
Likes gesamt
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.
Zugriffe
Antworten
Likes gesamt
will look into this. thanks for the advice.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Like
Antworten