Replies: 2 comments 1 reply
-
@lahma Do you have any suggestions? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Could be many things, like
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are intermittently getting the Couldn't determine job existence exception while running the Immediate job. I can't precisely reproduce it.
It occurs when calling this method.
I am passing whenOptions as an empty string.
var result = await scheduler.ScheduleJob(job, trigger);
Trigger and Job format:
Exception Details:
Message: Couldn't determine job existence (schedule_generic_job_immediate_busmessagejob_11111111-1111-1111-1111-84ba20252626.job_46ee9029-9f58-4b37-b3cd-475009073171_70f23160-6818-4864-8d04-755325f460eb): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
problemId: System.ComponentModel.Win32Exception at Quartz.Impl.AdoJobStore.JobStoreSupport+d__161.MoveNext
type: System.ComponentModel.Win32Exception
Inner Exception: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. / Unknown error 258
trace:at Quartz.Impl.AdoJobStore.JobStoreSupport.JobExists(ConnectionAndTransactionHolder conn, JobKey jobKey, CancellationToken cancellationToken)
at Quartz.Impl.AdoJobStore.JobStoreSupport.StoreJob(ConnectionAndTransactionHolder conn, IJobDetail newJob, Boolean replaceExisting, CancellationToken cancellationToken)
at Quartz.Impl.AdoJobStore.JobStoreSupport.<>c__DisplayClass156_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Quartz.Impl.AdoJobStore.JobStoreSupport.ExecuteInNonManagedTXLock[T](String lockName, Func
2 txCallback, Func
3 txValidator, Nullable1 requestorId, CancellationToken cancellationToken) at Quartz.Impl.AdoJobStore.JobStoreSupport.ExecuteInNonManagedTXLock[T](String lockName, Func
2 txCallback, Func3 txValidator, Nullable
1 requestorId, CancellationToken cancellationToken)at Quartz.Impl.AdoJobStore.JobStoreSupport.StoreJobAndTrigger(IJobDetail newJob, IOperableTrigger newTrigger, CancellationToken cancellationToken)
at Quartz.Core.QuartzScheduler.ScheduleJob(IJobDetail jobDetail, ITrigger trigger, CancellationToken cancellationToken)
at Automation.Management.Adapters.Repositories.GenericScheduler.GenericScheduler`1.Schedule(String whenOptions, String payload, String serviceId) in /src/Management/Automation.Management.Adapters/Repositories/GenericScheduler/GenericScheduler.cs:line 109
at Automation.Management.Adapters.Repositories.BusMessageSchedulerRepository.Schedule(ScheduleType scheduleType, String whenOptions, String payload, String serviceId) in /src/Management/Automation.Management.Adapters/Repositories/BusMessageSchedulerRepository.cs:line 49
at Automation.Management.Quartz.Service.Controllers.SchedulerController.Generic(ScheduleType when, String serviceId, String payload, String whenOptions) in /src/Management/Automation.Management.Quartz.Service/Controllers/SchedulerController.cs:line 81
Quartz version: 3.5.0
.Net framework: .Net 6
Below are the quartz-related configuration details.
I also checked there was not much load on the database when the exception occurred.
Beta Was this translation helpful? Give feedback.
All reactions