03/21/2023 09:48 AM
I have a job running for two days but nothing executed. it is dead and block running at next execution of scheduled hourly job.
How can stop it totally in order to run it at next scheduled time?
Solved! Go to Solution.
03/21/2023 10:00 AM
03/21/2023 10:12 AM
Thanks Ishan. I want to avoid restart. May I have custom query to remove the job record?
03/21/2023 10:57 AM
Hi @alc , unfortunately it's not a recommended approach to use custom query for it as it's not a standard solution. Restarting the services will be the helpful approach here.
03/21/2023 11:47 AM
I have restarted the server and the job is stopped. but it is stuck there again once I start the job. What is the possible cause for this? how to troubleshoot the issue? This is first time we have this issue to use this Jar connector for a target application.
03/21/2023 02:00 PM
@alc , please raise a FD ticket with all the appropriate details as a detailed analysis is required by checking the logs and configurations pertaining to the application and jobs.