You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Kenneth W. Meehan" <me...@progress.com> on 2004/02/16 23:01:17 UTC

Axis web services - multi-threaded ??

 


Hi,

I have been running many of the Axis 1.1 sample web services with
several different web services clients.

In one of my web services client packages I have turned on HTTP
pipelining, and I can now write a client that immediately sends numerous
SOAP requests out to an Axis web service.

If I monitor the Axis web service I can see that it processes each
request sequentially.  Is there any way to configure an Axis web service
to run multi-threaded??

I have been using the supplied samples from Axis like HelloWorld and the
Interop Echo service.  Plus a simple one of my own to sleep a specified
number of seconds so that I can time operations.

I am using Tomcat 4.1.27, and optionally Apache 2 in front of this Axis
implementation.


I also get consistent results if I use a .NET web service (with IIS in
front).  When I enable HTTP pipelining, and run my WS client, I see all
my SOAP requests go right out, but monitoring the web service indicates
everything running sequentially.

Any pointers are greatly appreciated.
Thanks,
Ken M.


Re: Axis web services - multi-threaded ??

Posted by Tony Blair <hr...@yahoo.com>.
Hamid,
 
That's true. "Request" will cause a new object to be created per request. This would be an ideal choice only if the service object contains state. Otherwise "Application" or "Session" would be preferable.
Tony.

Aaron Hamid <ar...@cornell.edu> wrote:
Doesn't that create a new object per request? I thought "Application" 
scope allows the service to persist accross many requests.

Anyway, regardless, if you are using HTTP pipelining, then there is a 
good chance whatever calls are queued on your pipeline will be issued 
sequentially (that is the whole point of a pipeline - to avoid the 
overhead of another connection). If you don't want this behavior, 
disable pipelining, or open a new pipelined connection.

Aaron


Tony Blair wrote:
> Hi there,
> 
> You need to set the scope to "Request".
> 
> Tony.
> 
> */"Kenneth W. Meehan" /* wrote:
> 
> 
> 
> 
> Hi,
> 
> I have been running many of the Axis 1.1 sample web services with
> several different web services clients.
> 
> In one of my web services client packages I have turned on HTTP
> pipelining, and I can now write a client that immediately sends numerous
> SOAP requests out to an Axis web service.
> 
> If I monitor the Axis web service I can see that it processes each
> request sequentially. Is there any way to configure an Axis web service
> to run multi-threaded??
> 
> I have been using the supplied samples from Axis like HelloWorld and the
> Interop Echo service. Plus a simple one of my own to sleep a specified
> number of seconds so that I can time operations.
> 
> I am using Tomcat 4.1.27, and optionally Apache 2 in front of this Axis
> implementation.
> 
> 
> I also get consistent results if I use a .NET web service (with IIS in
> front). When I enable HTTP pipelining, and run my WS client, I see all
> my SOAP requests go right out, but monitoring the web service indicates
> everything running sequentially.
> 
> Any pointers are greatly appreciated.
> Thanks,
> Ken M.
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online 
> 



---------------------------------
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online

Re: Axis web services - multi-threaded ??

Posted by Aaron Hamid <ar...@cornell.edu>.
Doesn't that create a new object per request?  I thought "Application" 
scope allows the service to persist accross many requests.

Anyway, regardless, if you are using HTTP pipelining, then there is a 
good chance whatever calls are queued on your pipeline will be issued 
sequentially (that is the whole point of a pipeline - to avoid the 
overhead of another connection).  If you don't want this behavior, 
disable pipelining, or open a new pipelined connection.

Aaron


Tony Blair wrote:
> Hi there,
>  
> You need to set the scope to "Request".
>  
> Tony.
> 
> */"Kenneth W. Meehan" <me...@progress.com>/* wrote:
> 
> 
> 
> 
>     Hi,
> 
>     I have been running many of the Axis 1.1 sample web services with
>     several different web services clients.
> 
>     In one of my web services client packages I have turned on HTTP
>     pipelining, and I can now write a client that immediately sends numerous
>     SOAP requests out to an Axis web service.
> 
>     If I monitor the Axis web service I can see that it processes each
>     request sequentially. Is there any way to configure an Axis web service
>     to run multi-threaded??
> 
>     I have been using the supplied samples from Axis like HelloWorld and the
>     Interop Echo service. Plus a simple one of my own to sleep a specified
>     number of seconds so that I can time operations.
> 
>     I am using Tomcat 4.1.27, and optionally Apache 2 in front of this Axis
>     implementation.
> 
> 
>     I also get consistent results if I use a .NET web service (with IIS in
>     front). When I enable HTTP pipelining, and run my WS client, I see all
>     my SOAP requests go right out, but monitoring the web service indicates
>     everything running sequentially.
> 
>     Any pointers are greatly appreciated.
>     Thanks,
>     Ken M.
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online 
> <http://us.rd.yahoo.com/evt=22055/*http://taxes.yahoo.com/filing.html>


Re: Axis web services - multi-threaded ??

Posted by Tony Blair <hr...@yahoo.com>.
Hi there,
 
You need to set the scope to "Request".
 
Tony.

"Kenneth W. Meehan" <me...@progress.com> wrote:



Hi,

I have been running many of the Axis 1.1 sample web services with
several different web services clients.

In one of my web services client packages I have turned on HTTP
pipelining, and I can now write a client that immediately sends numerous
SOAP requests out to an Axis web service.

If I monitor the Axis web service I can see that it processes each
request sequentially. Is there any way to configure an Axis web service
to run multi-threaded??

I have been using the supplied samples from Axis like HelloWorld and the
Interop Echo service. Plus a simple one of my own to sleep a specified
number of seconds so that I can time operations.

I am using Tomcat 4.1.27, and optionally Apache 2 in front of this Axis
implementation.


I also get consistent results if I use a .NET web service (with IIS in
front). When I enable HTTP pipelining, and run my WS client, I see all
my SOAP requests go right out, but monitoring the web service indicates
everything running sequentially.

Any pointers are greatly appreciated.
Thanks,
Ken M.


---------------------------------
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online