[JAVA-1475] Every connection should determine for itself the version of the server Created: 23/Sep/14 Updated: 31/Mar/15 Resolved: 29/Sep/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
If a Connection relies on the containing Server instance to determine its description, there is a race whereby the MongoDB server could have been restarted since the last refresh of the Server's description, and the Connection could end up reporting an incorrect version. This is important because clients use the server description to determine what operation to send to a server (e.g., write command vs. opcodes), so it's important that this information always be correct. |
| Comments |
| Comment by Jeffrey Yemin [ 31/Mar/15 ] |
|
Closing all resolved 3.0.0 issues, as 3.0.0 has been tagged and released. |
| Comment by Githook User [ 30/Jan/15 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: Add ServerDescription as a property of InternalConnection and use it to implement Connection.getDescription.
|
| Comment by Githook User [ 29/Sep/14 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: Add ServerDescription as a property of InternalConnection and use it to implement Connection.getDescription.
|