활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
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.
해결되었습니다! 솔루션으로 이동.
조회 수
답글
좋아요 수
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.
조회 수
답글
좋아요 수
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.
조회 수
답글
좋아요 수
will look into this. thanks for the advice.
조회 수
답글
좋아요 수