bangali
September 7, 2018, 7:54pm
1296
if you are seeing this error in the logs:
java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 87907337909179 @line -1 (error)
this is currently happening for many apps not just rooms manager apps. i am finding the same error for other apps including many of my existing pistons.
so very likely there is a ST platform issue ongoing. something similar to this:
I caught it this morning completely by accident killing a scheduled job that was scheduled for 9:00:07. That time was purely coincidental, just something that happened testing something. That job was killed for running over 20 seconds. So what they’re doing is queuing things up when there is a flood of events, which I understand and doesn’t matter much. But then they kill the job as it goes stale in the queue. I bet that most of the scheduling problems arise from this one thing. Why in the world they kill a job that’s in a queue that they use to buffer high event loads is beyond me. Maybe they don’t know how to distinguish a genuinely bad app that’s in an infinite loop from one that they’ve stuck in a queue.
If they would address this one failing, a lot might improve. @Jim , @Ben ,…