Hi all,
I have a scheduled service that did not run. Its next run time is stuck at 0.0 with a status set to Active. Has anyone else come across this issue and have found a way to resolve? or found reasons to why this happens?
thanks
-Cory
Hi all,
I have a scheduled service that did not run. Its next run time is stuck at 0.0 with a status set to Active. Has anyone else come across this issue and have found a way to resolve? or found reasons to why this happens?
thanks
-Cory
Yes that behavior is there. but to troubleshoot / resolve this you first need to restart the IS and also may need to raise the JDBC Pool max connections or check db connection resources available for the main IS DB connection during any time before this scheduler job hang happened.
Also make sure the Settings–> Resource page the server thread pool how many maximum threads were allocated to handle the load.
HTH,
RMG
thanks rmg for the help.
off topic, do you know if/how I can check available resources from the past within a time frame?
Please check the logs and see if you find any errors related to it and there is no way to look at it unless you have more monitoring component like OFI etc… or try to parse/read the stats.log it gives the resource threads info with the timestamp duration sort of things.
HTH,
RMG
Hi Cory,
if this happens, you can just edit and save the affected scheduler without any changes.
This will reset the next run value to a meaningful value.
Regards,
Holger
Yes, I’ve encounter this before, the flow service is running, and it might take longer time to complete or the service has hang somewhere, there are few ways you can try to work on it