Thanks for the quick fix!
@ssewell, I don’t like the fix introduced in Hangfire 1.3.3 that solves a problem with stucked enqueued jobs when using MSMQ. I even couldn’t imagine why this problem occurs at all, but was able to reproduce this problem recently by enabling snapshot isolation.
Does your database use the
I’ve already added a note to the documentation that snapshot isolation isn’t supported by Hangfire, and want to rollback the fix. The problem is that we can’t efficiently handle non-existing background jobs with the fix, and a number of wrong identifiers in a queue may cause background job processing to stuck.
My database has (and always has) both READ_COMMITTED_SNAPSHOT and AlLOW_SNAPSHOT_ISOLATION set to false.
What SQL Server version are you using?