Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B15217553 for ; Sat, 11 Apr 2015 18:11:13 +0000 (UTC) Received: (qmail 99393 invoked by uid 500); 11 Apr 2015 18:11:13 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 99348 invoked by uid 500); 11 Apr 2015 18:11:13 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 99337 invoked by uid 99); 11 Apr 2015 18:11:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Apr 2015 18:11:12 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FORGED_YAHOO_RCVD,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of mister_nat@yahoo.com) Received: from [162.253.133.43] (HELO mwork.nabble.com) (162.253.133.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Apr 2015 18:11:08 +0000 Received: from mtom.nabble.com (unknown [162.253.133.81]) by mwork.nabble.com (Postfix) with ESMTP id D5C0C1A8E308 for ; Sat, 11 Apr 2015 11:10:57 -0700 (PDT) Date: Sat, 11 Apr 2015 10:56:34 -0700 (MST) From: natl To: httpclient-users@hc.apache.org Message-ID: <1428774994354-26020.post@n7.nabble.com> In-Reply-To: <1428775321.13321.1.camel@apache.org> References: <1428731923651-26011.post@n7.nabble.com> <1428771156.7896.14.camel@apache.org> <1428773271275-26018.post@n7.nabble.com> <1428775321.13321.1.camel@apache.org> Subject: Re: HttpClient write timeout MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org SocketChannel is interruptible so any pending read()/write() operation can be interrupted by Thread.interrupt()[1] unlike SocketInputStream.read/SocketOutputStream.write[2][3] [1]http://www.java2s.com/Code/Java/Network-Protocol/Thisprogramshowshowtointerruptasocketchannel.htm [2]http://bugs.java.com/view_bug.do?bug_id=4905626 [3]http://bugs.java.com/view_bug.do?bug_id=4514257 -- View this message in context: http://httpcomponents.10934.n7.nabble.com/HttpClient-write-timeout-tp26011p26020.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org