On May 5, 2014 3:54:59 PM CEST, "Boxer, Aaron" <aaron.bo...@uhn.ca> wrote: > >> >> On Fri, 2014-05-02 at 16:23 +0000, Boxer, Aaron wrote: >> > Hello List, >> > >> > What is the best way of cancelling an httpclient-asynch put ? >> > >> > Currently, I am issuing a cancel(true) on the Future I receive back >from the put call. >> > >> > But, if I am sending large files, then requests that are in the >middle of sending are not cancelled. >> > I would like to stop all network activity as soon as possible. >> > >> > Is there a way of forcing the client to abort these connections ? >> > >> >> Simply throw an exception either from request producer or response >> consumer. That will immediately terminate the ongoing HTTP message >> exchange and shut down the underlying connection. >> >> Oleg >> >> >> >> Thanks so much, Oleg. Is it odd that calling shutdown on the >connection manager does not >> shut down the underlying connection? As I mentioned in previous >email, connection continues >> even if I exit my program. >> > >This makes no sense. > >Oleg > > >Thanks, Oleg. From what I have read about TCP, closing a socket puts >the socket in a TIME WAIT state for up to 4 minutes; during this time, >send buffers that have data can continue to send. > >Now, in my case, these buffers would have to be MBs in size, so it >still seems strange. But not impossible. > >Aaron
TIME_WAIT is perfectly legal for closed connections. I would not consider it as evidence of connection manager shutdown not working. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
