HttpUrlConnection leaves connections in CLOSED_WAIT state

Our java application fetches pages from various websites. One of our customers is finding that their machines have a very large number of TCP/IP connections in CLOSED_WAIT states that are remaining for long periods of time. We have not been able to reproduce this -- any thoughts?

I have attached our basic processing code (with non-relevant code removed). We are running on Microsoft Windows Server 2003 and using Java 6 and the java.net.HttpURLConnection class. For each connection, we close the input stream after reading it, but do not disconnect, so that Java can re-use the connection. This normally produces many connections with TIMED_WAIT states, but only an occasional short-lived CLOSED_WAIT state.

URLConnection urlConnection = url.openConnection();
    urlConnection.setConnectTimeout(timeout);
    urlConnection.setReadTimeout(timeout);

if (isPost()){
      ((HttpURLConnection)urlConnection).setDoOutput(true);
    }
    urlConnection.connect();   
    urlConnection.getResponseCode();
    
    try{
      try{
        contentsStream = urlConnection.getInputStream();
      }
      catch(IOException e){
        if (urlConnection instanceof HttpURLConnection){
          contentsStream = ((HttpURLConnection)urlConnection).getErrorStream();
        }
        if (contentsStream == null){
          throw e;
        }
      }
  
      String contentEncodingHeader = getResponseHeader().getOne("Content-Encoding");
      if (contentEncodingHeader != null){
        if (contentEncodingHeader.equalsIgnoreCase("gzip")){
          contentsStream = new GZIPInputStream(contentsStream);
        }
        else if (contentEncodingHeader.equalsIgnoreCase("deflate")){
          contentsStream = new InflaterInputStream(contentsStream, new Inflater(true));
        }
        else{
          throw new UnsupportedContentEncodingException(getRequest(), contentEncodingHeader);
        }
      }
      
      while (bytesRead = contentsStream.read(current)) >= 0) {
      }
    }
    finally{
        if (contentsStream != null){
          contentsStream.close();
        }
        //Don't disconnect, as we want to let Java re-use the connection if possible.
        //disconnect(urlConnection);
    }

There is a bug report
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6215050

related to this. It seems to exactly match what you describe.

can you find out what version of java that particular customer is using?

Thanks for the reply. I saw that bug report, but we are using Windows, Java 6 update 3. It seems the bug only applies to Linux and there are only complaints for Java 5 and earlier.