[JAVA-433] DBPortPool is not reusing sockets once maxSize is reached. Created: 14/Sep/11 Updated: 25/Jun/13 Resolved: 24/Oct/11 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | connections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
A report has come in that connections/sockets are not being reused by other threads, than last used them, once the max size of the DBPortPool is reached. The report says that by removing the thread-id check the problem goes away. DBPortPool.java:164 – "if ( p._lastThread == id )" |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 24/Oct/11 ] |
|
test checked in which tests this and it works |