Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 10407 invoked from network); 14 Aug 2009 11:12:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Aug 2009 11:12:23 -0000 Received: (qmail 86363 invoked by uid 500); 14 Aug 2009 11:12:29 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 86259 invoked by uid 500); 14 Aug 2009 11:12:28 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 86250 invoked by uid 99); 14 Aug 2009 11:12:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 11:12:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kdobrik.axis2@googlemail.com designates 209.85.210.179 as permitted sender) Received: from [209.85.210.179] (HELO mail-yx0-f179.google.com) (209.85.210.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Aug 2009 11:12:17 +0000 Received: by yxe9 with SMTP id 9so1720424yxe.30 for ; Fri, 14 Aug 2009 04:11:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=TGn62Ypva0+GRBckcUsZU5C4qUUPD4I0y9y/fnw4kvI=; b=FgCBfn85SDY11Gw7R9bY2zXnN/hIqUqZgcmmk81CkNcW67V4KirCWEIPq3ya+4lVUn FdRnyhd9tt18alZSFyrivnO0R2Be0hZg5PlZGEmiJFBc4kkVYTQypWF3tJrDBvuQaWUP LrEBf+9N1NDhZhHgXbdihl+ub81SQMSO88/N8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=NUnA/IXGBWV9mWaD+68CkKbunvdChRuu2eQ+gTVjUfdzI9zkqTtzRWE0rjVxqJDlST FiEbm0dA9dUgiMQ/e71ItCbeKZam2lufJrrKKtbG7Ijg4SA1v763W7wb4ILfkirPBgie Q71WiDuW0HeqKkK1fJEQEMzViRUNtcEvKgFgY= MIME-Version: 1.0 Received: by 10.231.16.136 with SMTP id o8mr1436400iba.24.1250248314985; Fri, 14 Aug 2009 04:11:54 -0700 (PDT) Date: Fri, 14 Aug 2009 14:11:54 +0300 Message-ID: <3b3bfaf80908140411x59b55385s75bbb44e52378f1f@mail.gmail.com> Subject: Axis2 1.5.1 and the default HttpClient reuse From: Dobri Kitipov To: axis-dev@ws.apache.org Content-Type: multipart/alternative; boundary=000325575b22b21e060471181ea2 X-Virus-Checked: Checked by ClamAV on apache.org --000325575b22b21e060471181ea2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi guys, I read in Axis2 1.5.1 RC anounce that: "We now share an instance of HTTPClient across each ConfigurationContext (i.e. each Axis2 server or ServiceClient) - connection reuse is now automatic. This means the REUSE_HTTP_CLIENT flag is no longer necessary or useful, nor is creating your own MultithreadedHttpConnectionManager." Since I have done some research and patches in HttpClient reuse area (ref. https://issues.apache.org/jira/browse/AXIS2-4288) I want to ask for some more information - like JIRAs involved or mail threads explaining this change. I glimpsed at part of the changes in the code related to this and some questions popped up in my mind: 1) Did we test this for the asynchronous invocation use case? IMHO it is not that easy to reuse one HttpClient instance in this case. I am pretty sure there are some JIRAs that discuss this topic. 2) As explained in https://issues.apache.org/jira/browse/AXIS2-4288 we can have some unwanted behaviour if we cannot associate an explicite HttpState when we invoke: httpClient.executeMethod(config, method); Since this commit is not part of the RC we need to document this. 3) Anyway, depending on 1) we may need to have a property that could be configured so a separate HttpClient instance is created and used per call - if needed? What do you think? I will appreciate any comments and guide lines. Thank you, Dobri --000325575b22b21e060471181ea2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

I read in Axis2 1.5.1 RC anounce that:

"We = now share an instance of HTTPClient across each ConfigurationContext (i.e.<= br>each Axis2 server or ServiceClient) - connection reuse is now automatic.= This
means the REUSE_HTTP_CLIENT flag is no longer necessary or useful, nor iscreating your own MultithreadedHttpConnectionManager."

Since = I have done some research and patches in HttpClient reuse area (ref. https://issues.apach= e.org/jira/browse/AXIS2-4288) I want to ask for some more information -= like JIRAs involved or mail threads explaining this change.

I glimpsed at part of the changes in the code related to this and some = questions popped up in my mind:

1) Did we test this for the asynchro= nous invocation use case? IMHO it is not that easy to reuse one HttpClient = instance in this case. I am pretty sure there are some JIRAs that discuss t= his topic.

2) As explained in https://issues.apache.org/jira/browse/AXIS2-4288 we can have s= ome unwanted behaviour if we cannot associate an explicite HttpState when w= e invoke:

httpClient.executeMethod(config, method);

Since this commit is = not part of the RC we need to document this.

3) Anyway, depending on= 1) we may need to have a property that could be configured so a separate H= ttpClient instance is created and used per call - if needed?

What do you think?
I will appreciate any comments and guide lines.
Thank you,
Dobri

--000325575b22b21e060471181ea2--