Don't empty connection pool on every RuntimeException (JAVA-589)

[JAVA-1003] 2.12: Don't empty connection pool on every RuntimeException Created: 11/Oct/13  Updated: 03/Apr/14  Resolved: 26/Nov/13

Status: Closed
Project: Java Driver
Component/s: Connection Management
Affects Version/s: None
Fix Version/s: 2.12.0

Type: Sub-task 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   

Implement in 2.12.



 Comments   
Comment by Githook User [ 26/Nov/13 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: JAVA-1005, JAVA-1003, JAVA-1007, JAVA-1009: Ported PooledConnectionProvider from 3.0.x, and refactored DBPort to work with it by extracting a Connection interface that it implements. This new connection pool is non-blocking, and supports enforcement of max idle time, max life time, and minimum size. It also abstracts the JMX monitoring into an implementation of the ConnectionPoolListener interface, which the connection pool fires events to.

Conflicts:
src/main/com/mongodb/BaseCluster.java
src/main/com/mongodb/Clusters.java
src/main/com/mongodb/DBTCPConnector.java
src/main/com/mongodb/DefaultServer.java
src/main/com/mongodb/Server.java
src/main/com/mongodb/ServerStateNotifier.java
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/eb6a74247e54ca5855f6b729242b0f360f47dbdf

Generated at Thu Feb 08 08:53:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.