[JAVA-483] MongoException$Network on stale connection pool for selection queries only Created: 05/Dec/11 Updated: 25/Jun/13 Resolved: 10/Mar/12 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | 2.7.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Nick Matheson | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OSX Lion |
||
| Description |
|
Steps to reproduce 1. Establish connection to mongo (i.e.: execute a single query) This may be the expected behavior in this scenario but was surprising since inserts do not exhibit the behavior. Exception: com.mongodb.MongoException$Network: can't call something : /127.0.0.1:27017/connection_test |
| Comments |
| Comment by Nick Matheson [ 20/Dec/11 ] |
|
Jeff- Thanks for the clarification. Nick |
| Comment by Jeffrey Yemin [ 15/Dec/11 ] |
|
This is expected behavior when a connection goes stale. You'll get the same result on insert if you use WriteConcern.SAFE. |
| Comment by Jeffrey Yemin [ 14/Dec/11 ] |
|
Do you have sample code? I assume you're not doing slaveOk reads. |