[JAVA-3761] ConcurrentPool doesn't release semaphore permit properly after com.mongodb.MongoSocketException:<host_name_of_read_replica> Created: 11/Jun/20 Updated: 03/Aug/20 Resolved: 03/Aug/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Async |
| Affects Version/s: | 3.11.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anastasiya Kaluzhonak | Assignee: | Jeffrey Yemin |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
One of our application's node was faced with some network issues, yet the node did not completely restore its operation after the issue was gone. During network issues connections were closed because of com.mongodb.MongoSocketReadTimeoutException: Timeout while receiving message. After network issues were gone opening new connections were failed for only one of two read replicas with Mongo Async driver v3.11.2 ClusterSettings: ConnectionOptions: maxPoolSize=10&minPoolSize=10&w=1&wtimeoutMS=500&j=0&connectTimeoutMS=500&socketTimeoutMS=2000&readPreference=secondaryPreferred&waitQueueMultiple=5&waitQueueTimeoutMS=2000&replicaSet=rs0 Issue: Please see the attached stacktrace with some obfuscation for more detailes. |
| Comments |
| Comment by Jeffrey Yemin [ 16/Jul/20 ] |
|
Hi anastasiya.kaluzhonak@gmail.com It looks like this duplicates Let me know if you can test out that release. We can also consider backporting that fix to a 3.12 patch release. |