尽管有超时,但CloseableHttpClient.execute每隔几周会冻结一次

Question

我们有一个groovy单例,它使用池大小为200的PoolingHttpClientConnectionManager(httpclient:4.3.6)来处理与搜索服务的非常高的并发连接并处理xml响应.

尽管已经指定了超时,但它每月冻结一次,但在其余时间运行完全正常.

下面的常规单身人士.方法retrieveInputFromURL似乎在client.execute(get)上阻塞;

@Singleton(strict=false)
class StreamManagerUtil {
   // Instantiate once and cache for lifetime of Signleton class

   private static PoolingHttpClientConnectionManager connManager = new PoolingHttpClientConnectionManager();

   private static CloseableHttpClient client;

   private static final IdleConnectionMonitorThread staleMonitor = new IdleConnectionMonitorThread(connManager);

   private int warningLimit;
   private int readTimeout;
   private int connectionTimeout;
   private int connectionFetchTimeout;

   private int poolSize;
   private int routeSize;

   PropertyManager propertyManager  = PropertyManagerFactory.getInstance().getPropertyManager("sebe.properties")

   StreamManagerUtil() {
      // Initialize all instance variables in singleton from properties file

      readTimeout = 6
      connectionTimeout = 6
      connectionFetchTimeout =6

      // Pooling
      poolSize = 200
      routeSize = 50

      // Connection pool size and number of routes to cache
      connManager.setMaxTotal(poolSize);
      connManager.setDefaultMaxPerRoute(routeSize);

      // ConnectTimeout : time to establish connection with GSA
      // ConnectionRequestTimeout : time to get connection from pool
      // SocketTimeout : waiting for packets form GSA

      RequestConfig config = RequestConfig.custom()
      .setConnectTimeout(connectionTimeout * 1000)
      .setConnectionRequestTimeout(connectionFetchTimeout * 1000)
      .setSocketTimeout(readTimeout * 1000).build();

      // Keep alive for 5 seconds if server does not have keep alive header
      ConnectionKeepAliveStrategy myStrategy = new ConnectionKeepAliveStrategy() {
         @Override
         public long getKeepAliveDuration(HttpResponse response, HttpContext context) {
            HeaderElementIterator it = new BasicHeaderElementIterator
               (response.headerIterator(HTTP.CONN_KEEP_ALIVE));
            while (it.hasNext()) {
               HeaderElement he = it.nextElement();
               String param = he.getName();
               String value = he.getValue();
               if (value != null && param.equalsIgnoreCase
                  ("timeout")) {
                  return Long.parseLong(value) * 1000;
               }
            }
            return 5 * 1000;
         }
      };

      // Close all connection older than 5 seconds. Run as separate thread.
      staleMonitor.start();
      staleMonitor.join(1000);

      client = HttpClients.custom().setDefaultRequestConfig(config).setKeepAliveStrategy(myStrategy).setConnectionManager(connManager).build();
   }     

   private retrieveInputFromURL (String categoryUrl, String xForwFor, boolean isXml) throws Exception {

      URL url = new URL( categoryUrl );

      GPathResult searchResponse = null
      InputStream inputStream = null
      HttpResponse response;
      HttpGet get;
      try {
         long startTime = System.nanoTime();

         get = new HttpGet(categoryUrl);
         response =  client.execute(get);

         int resCode = response.getStatusLine().getStatusCode();

         if (xForwFor != null) {
            get.setHeader("X-Forwarded-For", xForwFor)
         }

         if (resCode == HttpStatus.SC_OK) {
            if (isXml) {
               extractXmlString(response)
            } else {
               StringBuffer buffer = buildStringFromResponse(response)
               return buffer.toString();
            }
         }

      }
      catch (Exception e)
      {
         throw e;
      }
      finally {
         // Release connection back to pool
         if (response != null) {
            EntityUtils.consume(response.getEntity());
         }
      }

   }

   private extractXmlString(HttpResponse response) {
      InputStream inputStream = response.getEntity().getContent()

      XmlSlurper slurper = new XmlSlurper()
      slurper.setFeature("http://xml.org/sax/features/validation", false)
      slurper.setFeature("http://apache.org/xml/features/disallow-doctype-decl", false)
      slurper.setFeature("http://apache.org/xml/features/nonvalidating/load-dtd-grammar", false)
      slurper.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false)

      return slurper.parse(inputStream)
   }

   private StringBuffer buildStringFromResponse(HttpResponse response) {
      StringBuffer buffer= new StringBuffer();
      BufferedReader rd = new BufferedReader(new InputStreamReader(response.getEntity().getContent()));
      String line = "";
      while ((line = rd.readLine()) != null) {
         buffer.append(line);
         System.out.println(line);
      }
      return buffer
   }

public class IdleConnectionMonitorThread extends Thread {

    private final HttpClientConnectionManager connMgr;
    private volatile boolean shutdown;

    public IdleConnectionMonitorThread
      (PoolingHttpClientConnectionManager connMgr) {
        super();
        this.connMgr = connMgr;
    }

    @Override
    public void run() {
        try {
            while (!shutdown) {
                synchronized (this) {
                    wait(5000);
                    connMgr.closeExpiredConnections();
                    connMgr.closeIdleConnections(10, TimeUnit.SECONDS);
                }
            }
        } catch (InterruptedException ex) {
            // Ignore
        }
    }
    public void shutdown() {
        shutdown = true;
        synchronized (this) {
            notifyAll();
        }
    }
}

我还发现在日志中发现这一点让我相信它发生在等待响应数据上

java.net.SocketTimeoutException:在java.net.SocketInputStream.read(SocketInputStream.java:150)java.net.SocketInputStream.read(SocketInputStream.java:150)的java.net.SocketInputStream.socketRead0(Native Method)中读取超时时间(SocketInputStream.java:121 )at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)

到目前为止的调查结果:

• 我们使用的是java 1.8u25.在类似的情况下有一个未解决的问题 https://bugs.openjdk.java.net/browse/JDK-8075484
• HttpClient有一个类似的报告https://issues.apache.org/jira/browse/HTTPCLIENT-1589但这已在我们使用的4.3.6版本中修复

问题

• 这可能是同步问题吗？根据我的理解,即使单线程由多个线程访问,唯一的共享数据是缓存的CloseableHttpClient
• 这段代码还有什么根本原因导致这种行为吗？

Answer 1

我没有看到你的代码有任何明显的错误。不过，我强烈建议在连接管理器上设置 SO_TIMEOUT 参数，以确保它在创建时（而不是在请求执行时）应用于所有新套接字。

我还想帮助您了解“冻结”的确切含义。工作线程是否被阻止等待从池中获取连接或等待响应数据？

另请注意，如果服务器继续发送块编码数据位，则工作线程可能会显示为“冻结”。像往常一样，客户端会话的线路/上下文日志会有很大帮助 http://hc.apache.org/httpcomponents-client-4.3.x/logging.html