Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 31442 invoked from network); 29 Sep 2008 17:21:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Sep 2008 17:21:03 -0000 Received: (qmail 52434 invoked by uid 500); 29 Sep 2008 17:20:54 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 52401 invoked by uid 500); 29 Sep 2008 17:20:53 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 52390 invoked by uid 99); 29 Sep 2008 17:20:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2008 10:20:53 -0700 X-ASF-Spam-Status: No, hits=-2.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [64.18.2.167] (HELO exprod7og107.obsmtp.com) (64.18.2.167) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 29 Sep 2008 17:19:51 +0000 Received: from source ([198.177.232.249]) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP; Mon, 29 Sep 2008 10:20:24 PDT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C92257.A8E90700" Subject: RE: What is the advantage of using async clients if Axis creates a wait thread for every request? Date: Mon, 29 Sep 2008 12:21:46 -0500 Message-ID: <363B4FD4987A3345BBDAFCFB83019EC7F720E9@hsv-email2.corp.avocent.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What is the advantage of using async clients if Axis creates a wait thread for every request? Thread-Index: AckiVx+gC6BCYV4LT5K63CzIb/uOmwAAJSzQ References: <363B4FD4987A3345BBDAFCFB83019EC7F720C9@hsv-email2.corp.avocent.com> From: "Franklin, Allen" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C92257.A8E90700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Can you recommend any sample code for me to look at? I have been using 'wsdl2java -a' to generate client stubs. What you are recommending sounds a bit more complex. =20 From: keith chapman [mailto:keithgchapman@gmail.com]=20 Sent: Monday, September 29, 2008 1:15 PM To: axis-user@ws.apache.org Subject: Re: What is the advantage of using async clients if Axis creates a wait thread for every request? =20 Axis2 client support two levels of async behavior. One of them is the one you've explained. This is something like pseudo async. The other is where you send a request and then listen on a separate port (by spinning up a simple http server on the client) for the response (It is compulsory that you use WS-Addressing for this to work). This does not block a thread. Thanks, Keith. On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen wrote: It is my understanding that Axis2 v1.4 creates a thread to wait for the reply for every async client request. What is the advantage (on the client side) of using Axis2 async/non-blocking clients if Axis creates a wait thread for every request? In fact the blocking call seems more efficient because it saves Axis the trouble of having to create another thread. There appears to be a cost of one thread per outstanding for the duration of the call with either way, blocking or non-blocking. --=20 Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org ------_=_NextPart_001_01C92257.A8E90700 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Can you recommend any sample code for me to look = at?

I have been using ‘wsdl2java –a’ to = generate client stubs.

What you are recommending sounds a bit more = complex.

 

From:= keith = chapman [mailto:keithgchapman@gmail.com]
Sent: Monday, September 29, 2008 1:15 PM
To: axis-user@ws.apache.org
Subject: Re: What is the advantage of using async clients if Axis creates a wait thread for every request?

 

Axis2 client support = two levels of async behavior. One of them is the one you've explained. This is = something like pseudo async. The other is where you send a request and then listen = on a separate port (by spinning up a simple http server on the client) for = the response (It is compulsory that you use WS-Addressing for this to work). = This does not block a thread.

Thanks,
Keith.

On Mon, Sep 29, 2008 at 10:38 PM, Franklin, Allen = <Allen.Franklin@avocent.com= > wrote:

It is my understanding that Axis2 v1.4 creates a thread to wait for = the reply for every async client request.

What is the advantage (on the client side) of using Axis2 = async/non-blocking clients if Axis creates a wait thread for every request?

In fact the blocking call seems more efficient because it saves Axis = the trouble of having to create another thread.

There appears to be a cost of one thread per outstanding for the = duration of the call with either way, blocking or non-blocking.




--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

------_=_NextPart_001_01C92257.A8E90700--