[JAVA-1969] Wrong reason for closing a connection supplied in log message in some cases Created: 17/Sep/15 Updated: 07/Oct/15 Resolved: 24/Sep/15 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management, Monitoring |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | 3.1.0 |
| Type: | Bug | 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 |
|
The check for connection.isClosed() should come before the check for previous generation. If a connection is closed, the generation will be incremented when that happens, so the check for connection.isClosed() will never be reached. |
| Comments |
| Comment by Jeffrey Yemin [ 07/Oct/15 ] |
|
Released in 3.1.0 |
| Comment by Githook User [ 24/Sep/15 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |