Return-Path: Delivered-To: apmail-jakarta-httpclient-dev-archive@www.apache.org Received: (qmail 11040 invoked from network); 17 Oct 2005 11:25:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Oct 2005 11:25:50 -0000 Received: (qmail 4011 invoked by uid 500); 17 Oct 2005 11:25:50 -0000 Delivered-To: apmail-jakarta-httpclient-dev-archive@jakarta.apache.org Received: (qmail 3977 invoked by uid 500); 17 Oct 2005 11:25:49 -0000 Mailing-List: contact httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "HttpClient Project" Reply-To: "HttpClient Project" Delivered-To: mailing list httpclient-dev@jakarta.apache.org Received: (qmail 77932 invoked by uid 99); 17 Oct 2005 10:57:39 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rJqxHGFvNuwBJxz7wWCwZyuVSmOY7yYbKjfJ6FGHDVvCjGfNXSnlmEzC0uIlIsRqi3w+fbUGcTS3jimDUKyDwdnJUuJfXMjD31TozVGKcfWccZEKwOrLobukxmok4bSoccaJS0y57VHt8ATqaM6MrhAJcz8zx0yb9ePejO5fEJw= ; Message-ID: <20051017105717.33754.qmail@web35114.mail.mud.yahoo.com> Date: Mon, 17 Oct 2005 11:57:17 +0100 (BST) From: Teja Sai Krishna Subject: CLOSE_WAIT state at the HTTP Client side To: httpclient-dev@jakarta.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1393660732-1129546637=:32404" Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --0-1393660732-1129546637=:32404 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, We have HTTP Client application that connects to the HttpListening Connector , which runs on weblogic 8.1. We are using apache's HTTPClient API to connect to the server. Once the communication is over, some client side connections are in CLOSE_WAIT state. Some times i have seen these CLOSE_WAIT connections will disappear after one day. But most of the times it will not disappear even after one day. I have to kill my application. Is CLOSE_WAIT at the client side means, my client is waiting for final ack from the server? Could you please suggest , how to resolve this issue? My client code looks like this . I am releasing the connection after the communication happens. -------------- HttpClient client = new HttpClient(); // Create a method instance. GetMethod method = new GetMethod(url); // Provide custom retry handler is necessary method.getParams().setParameter(HttpMethodParams.RETRY_HANDLER, new DefaultHttpMethodRetryHandler(3, false)); method.setRetryCount(0); try { // Execute the method. int statusCode = client.executeMethod(method); // Read the response body. byte[] responseBody = method.getResponseBody(); System.out.println(new String(responseBody)); } catch (HttpException e) { e.printStackTrace(); } catch (IOException e) { e.printStackTrace(); } finally { // Release the connection. method.releaseConnection(); } } }------------- Thanks Regards Teja Send instant messages to your online friends http://uk.messenger.yahoo.com --0-1393660732-1129546637=:32404--