Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 31514 invoked from network); 11 Mar 2008 12:32:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Mar 2008 12:32:17 -0000 Received: (qmail 45659 invoked by uid 500); 11 Mar 2008 12:32:14 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 45630 invoked by uid 500); 11 Mar 2008 12:32:14 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 45621 invoked by uid 99); 11 Mar 2008 12:32:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 05:32:14 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2008 12:31:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2EFE1234C090 for ; Tue, 11 Mar 2008 05:30:47 -0700 (PDT) Message-ID: <1186516707.1205238647191.JavaMail.jira@brutus> Date: Tue, 11 Mar 2008 05:30:47 -0700 (PDT) From: "Asankha C. Perera (JIRA)" To: dev@synapse.apache.org Subject: [jira] Resolved: (SYNAPSE-244) some IO-Exception immediatly detected, but cannot be processed immediatly In-Reply-To: <819930636.1204169451924.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/SYNAPSE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved SYNAPSE-244. --------------------------------------- Resolution: Fixed Fix Version/s: NIGHTLY Assignee: Asankha C. Perera Applied patch from https://issues.apache.org/jira/browse/SYNAPSE-248 with some minor changes Thanks xuhongbo, can you please verify that everything works as expected now? > some IO-Exception immediatly detected, but cannot be processed immediatly > ------------------------------------------------------------------------- > > Key: SYNAPSE-244 > URL: https://issues.apache.org/jira/browse/SYNAPSE-244 > Project: Synapse > Issue Type: Improvement > Components: Transports > Affects Versions: 1.1 > Environment: windows, axisClient <--->synapse<-->axisServer > Reporter: xuhongbo > Assignee: Asankha C. Perera > Fix For: NIGHTLY > > > scenarios: > axisClient<-->synapse <--> axisServer > 1) axisClient send request to synapse > 2) syanpse relay request to axisServer > 3) after axisServer received the request, break down the network between synapse and axisServer (etc: shutdown axisServer) > 4) axisClient doens't failure immediatly, It's alway's failure when it's timeout exceed or synapse TimeOut handler checked time-out > =============================================================================================== > The more details reson I have find out is: > When network breakdown(etc axisServer shutdown), org.apache.synapse.transport.nhttp.ClientHandler's corresponding callback handler is invoked (closed(), or exception(),...) . and the callback only just shutdown the connection. > But the sessionRequestCallback(HttpCoreNIOSender.sessionRequestCallback) registed when establish http connection(ioreactor.connect(...)) will never be called. > so the failure response will not be generated and send back to axisClient. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org For additional commands, e-mail: dev-help@synapse.apache.org