[SERVER-5069] ~ScopedDBConnection is vague and somewhat misleading Created: 24/Feb/12  Updated: 11/Jul/16  Resolved: 24/Feb/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.0.4, 2.1.1

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

... we should say something more interesting here, like "error aborted connection, removed from pool". Also, the message is also thrown from ShardConnections, making it non-obvious what is happening.



 Comments   
Comment by auto [ 06/Mar/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-5069 replace ScopedDBConnection message with something more meaningful
Branch: v2.0
https://github.com/mongodb/mongo/commit/d216bc37c309baa162f3a760ac72f991054703c9

Comment by auto [ 24/Feb/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-5069 replace ScopedDBConnection message with something more meaningful
Branch: master
https://github.com/mongodb/mongo/commit/d9e2eae9cbc84262d799d8736d49e4e32d432170

Generated at Thu Feb 08 03:07:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.