Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <10377886.post@talk.nabble.com>
Date: Tue, 8 May 2007 08:21:30 -0700 (PDT)
From: david2 <David.Bueche@l-3comcept.com>
To: commons-user@jakarta.apache.org
Subject: HttpMethodBase.setConnectionCloseForced(boolean)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


We have an application that creates MANY short-term (< 1 second) client
connections, but they are not be closed immediately and stay in a TIME_WAIT
state for the full TcpTimedWaitDelay (30 seconds on Windows XP).  We would
like them to be closed immediately (during cleanup).

I would like to modify (hack) the
HttpMethodBase.setConnectionCloseForced(boolean) method to make it public. 
On the other hand, if this pursuit is going to be disasterous, I don't even
want to go down that road.

Does anyone know the reason why this method was made protected and not
public, as well as whether or not making it public will create great and
grave problems elsewhere?  Or (preferably), what is the correct means of
always forcing a shared HttpClient, ConnectionManager, etc. to always close
its connections during cleanup?
Thanks,
-David
-- 
View this message in context: http://www.nabble.com/HttpMethodBase.setConnectionCloseForced%28boolean%29-tf3710282.html#a10377886
Sent from the Commons - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org