HangfireIO / HangfireIO/Hangfire
Too many sql server connection in RecurringJobScheduler for both (1.6.6 & 1.6.8)
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Asp.net Core WebApi running on CentOS 7.2
SQL Server 2008 R2 sp3
=====================================================
[deploy@uatvmgxxxx v2]$ netstat -apn | grep 172.21.101.XXX -c
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
**2422**
==================================================
"ConnectionStrings": {
"DefaultConnection": "Data Source=172.21.101.xxx,xxxxx;Initial Catalog=PiaoDB;Persist Security Info=True;User ID=xxxxx;Password=xxxxxxxx"
},
Contributor guide
Research direction
Start by investigating the RecurringJobScheduler behavior described in the issue and reproduce the excessive connection count against the stated SQL Server setup. Use the reported netstat command and connection string as the baseline; done means identifying the cause and verifying that the scheduler no longer creates excessive connections in both reported versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100