[CSHARP-649] The driver should be strict about honoring MaxConnectionIdleTime and MaxConnectionLifeTime Created: 18/Dec/12  Updated: 20/Mar/14  Resolved: 24/Dec/12

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 1.7
Fix Version/s: 1.7.1

Type: Bug Priority: Major - P3
Reporter: Sridhar Nanjundeswaran Assignee: Craig Wilson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently the driver is not strict about honoring the above 2 values. The connection pool maintainer removes 1 expired connection (lifetime or idle time) per maintenance run. Hence users can acquire connections from the connection pool which are either past their max idle time or max life time.
When acquiring connections from the pool, only connections which are not past their max idle or life time should be given. Connections that are past their max idle or life time should be closed



 Comments   
Comment by auto [ 12/Feb/13 ]

Author:

{u'date': u'2013-02-12T16:40:54Z', u'name': u'rstam', u'email': u'robert@10gen.com'}

Message: CSHARP-649: Enforce MaxConnectionIdleTime and MaxConnectionLifeTime strictly.
Branch: v1.7.1
https://github.com/mongodb/mongo-csharp-driver/commit/4fdd8cc91627d9584e0021ea611f4297cc646622

Comment by auto [ 22/Dec/12 ]

Author:

{u'date': u'2012-12-22T19:15:10Z', u'name': u'Craig Wilson', u'email': u'craiggwilson@gmail.com'}

Message: CSHARP-649: MaxConnectionLifeTime and MaxConnectionIdleTime are now strictly enforced.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/275bf49fd12b2f5d360d7095fac2eff257b4079b

Generated at Wed Feb 07 21:37:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.