JAVA-2034: Stop interrupting the wait queue handler in BaseCluster, as it's possible that the interrupt flag will be checked somewhere else besides the wait queue handler itself.

Additionally, ensure that exceptions thrown in DefaultConnectionPool.getAsync are propagated to the callback.

Author: jyemin

driver-core/src/main/com/mongodb/connection/BaseCluster.java

@@ -429,8 +429,6 @@ private synchronized void notifyWaitQueueHandler(final ServerSelectionRequest re
                 waitQueueHandler = new Thread(new WaitQueueHandler(), "cluster-" + clusterId.getValue());
                 waitQueueHandler.setDaemon(true);
                 waitQueueHandler.start();
-            } else {
-                waitQueueHandler.interrupt();
             }
         }
     }
@@ -466,9 +464,7 @@ public void run() {
                 try {
                     currentPhase.await(waitTimeNanos, NANOSECONDS);
                 } catch (InterruptedException e) {
-                    // Either we were interrupted because the wait queue has been added to, or because the cluster has been
-                    // closed.  If the latter, the while loop will exit.  If the former, we check all waiters, since we don't know which
-                    // one was added
+                    // The cluster has been closed and the while loop will exit.
                 }
             }
             // Notify all remaining waiters that a shutdown is in progress

driver-core/src/main/com/mongodb/connection/DefaultConnectionPool.java

@@ -124,6 +124,9 @@ public void getAsync(final SingleResultCallback<InternalConnection> callback) {
             connection = getPooledConnection(0, MILLISECONDS);
         } catch (MongoTimeoutException e) {
             // fall through
+        } catch (Throwable t) {
+            callback.onResult(null, t);
+            return;
         }
 
         if (connection != null) {