HangfireIO / HangfireIO/Hangfire

Hangfire.SqlServer throws System.ObjectDisposedException on SqlServerDistributedLock release

Open
#1,201 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
10.1k
Forks
1.8k
Avg merge
1h 19m
Merged PRs (30d)
1

Description

![image](https://user-images.githubusercontent.com/11006239/41093398-7c2d386a-6a4b-11e8-9790-c2b3e4531a46.png)

The blocks that call the Release method check connection state (different from Open), but this isn't indicative of a disposed connection.

Contributor guide

Open the contributing guide

Research direction

Start by locating SqlServerDistributedLock and its Release method, then inspect the blocks that check connection state before releasing the lock. Reproduce the ObjectDisposedException if possible; done means releasing the lock no longer throws when its connection has already been disposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, sql
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.