-
Hello! In the latest quartznet version, the MaxRetry and RetryPeriod for getting the TRIGGER_ACCESS lock are both configurable (defaults 3 tries and 1000ms, respectively). Ultimately, the behavior we would like to see is for our application to 'fail faster' if we can't get the lock. So we would like the CommandTimeout to be configurable. Thoughts? Is there a configuration I missed, or a workaround to effect this kind of behavior? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Sounds that this is missing. I guess some providers allow this via connection string but maybe not MS SQL Server. If it's "settable" in all providers I guess we can add is as an configuration option, otherwise needs to be injected to specific DB provider. A PR would be great, thank you. |
Beta Was this translation helpful? Give feedback.
Sounds that this is missing. I guess some providers allow this via connection string but maybe not MS SQL Server. If it's "settable" in all providers I guess we can add is as an configuration option, otherwise needs to be injected to specific DB provider.
A PR would be great, thank you.