anes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 17:18
> To: axis-user@ws.apache.org
> Subject: Re: Too many sockets being created. Bad architecture?
>
> My question is :
> What is the standard way to architect web services which have
> a very long blocking sy
nes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 17:18
> To: axis-user@ws.apache.org
> Subject: Re: Too many sockets being created. Bad architecture?
>
> My question is :
> What is the standard way to architect web services which have
> a very long blocking synch
servers in a load-balanced cluster, you would still run out ofavailable threads after just a few seconds ...Regards,Sunil D'MonteTavant Technologieshttp://www.tavant.com > -Original Message-> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 02, 2006 17:18&
Tavant Technologies
http://www.tavant.com
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 02, 2006 17:18
> To: axis-user@ws.apache.org
> Subject: Re: Too many sockets being created. Bad architecture?
>
> My question is
My question is :
What is the standard way to architect web services
which have a very long blocking synchronous operations
?
Don't. Design an asynchronous exchange instead.
Anne
On 8/2/06, kk kk <[EMAIL PROTECTED]> wrote:
Hi,
I am developing a WS which provides an operation that
takes around
Hi,
I am developing a WS which provides an operation that
takes around 25 seconds to complete. I can not speed
this up nor I can not use a polling pattern or a
callback to inform the client of the result of the
request.
I want to make the WS server capable to handle 100 new
requests per second, s
