fix #467 - call shutdown on ThreadSafeClientConnManager (the HTTP connection pool) to avoid any lingering connections in CLOSE_WAIT

(cherry picked from commit e9499fd)
(cherry picked from commit 62f3bfc)

Author: sammefford

src/main/java/com/marklogic/client/impl/JerseyServices.java

@@ -189,6 +189,7 @@ public void verify(String hostname, String[] cns, String[] subjectAlts)
 
 	private DatabaseClient databaseClient;
 	private String database = null;
+	private ThreadSafeClientConnManager connMgr;
 	private ApacheHttpClient4 client;
 	private WebResource connection;
 	private boolean released = false;
@@ -281,6 +282,10 @@ private void connect(String host, int port, String database, String user, String
 
 		if (connection != null)
 			connection = null;
+		if (connMgr != null) {
+			connMgr.shutdown();
+			connMgr = null;
+		}
 		if (client != null) {
 			client.destroy();
 			client = null;
@@ -353,7 +358,7 @@ private void connect(String host, int port, String database, String user, String
 		 *     maxRouteConnections);
 		 */
 		// start 4.1
-		ThreadSafeClientConnManager connMgr = new ThreadSafeClientConnManager(
+		connMgr = new ThreadSafeClientConnManager(
 				schemeRegistry);
 		connMgr.setMaxTotal(maxTotalConnections);
 		connMgr.setDefaultMaxPerRoute(maxRouteConnections);
@@ -470,6 +475,8 @@ public void release() {
 			logger.debug("Releasing connection");
 
 		connection = null;
+		connMgr.shutdown();
+		connMgr = null;
 		client.destroy();
 		client = null;
 	}