yes, most of time is waiting,
I use tomcat NIO connector, with async cxf webservice server (exposed as
async servlet) and async cxf client,
I use no my own threaded-queue
regards
Jakub
ps
possibly camel could do it more elegantly and with less programming effort
On Tue, Jun 18, 2013 at 5:21 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakub,
On 6/18/13 3:27 AM, Ja kub wrote:
> Ravindra,
>
> Thx for idea, I will read about it, but at first glance it looks
> like with 5000 pending servlet requests I will have 5000 threads
> awaiting response from cxf client, with async servlet and
/github.com/Netflix/Hystrix
>
> -Ravi
>
>
> From: Ja kub [jjaku...@gmail.com]
> Sent: Thursday, June 13, 2013 1:11 AM
> To: Tomcat Users List
> Subject: Re: http request (no only session) replication in cluster
>
> Christopher
&
From: Ja kub [jjaku...@gmail.com]
Sent: Thursday, June 13, 2013 1:11 AM
To: Tomcat Users List
Subject: Re: http request (no only session) replication in cluster
Christopher
Thx for response, I will inform guys from business about what You have
written, and let them consider it
Regards
Jakub
On Wed
Christopher
Thx for response, I will inform guys from business about what You have
written, and let them consider it
Regards
Jakub
On Wed, Jun 12, 2013 at 4:10 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakob,
>
> On 6/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakob,
On 6/11/13 5:04 PM, Ja kub wrote:
> requirement is system should be possible to process 160 req/sec
> (200 is better to multiply) and system is kind of failover proxy
> itself
>
> there are 2 backing webservices, each can answer max 20s, it
Andre, Christopher
thx for response,
requirement is system should be possible to process 160 req/sec (200 is
better to multiply)
and system is kind of failover proxy itself
there are 2 backing webservices, each can answer max 20s, it there is
timeout on first, I must call the second, if there is t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 6/11/13 11:32 AM, André Warnier wrote:
> Christopher Schultz wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Ja,
>>
>> On 6/11/13 9:54 AM, Ja kub wrote:
>>> What can be done to guarantee failover in below scenario:
>>>
>
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ja,
On 6/11/13 9:54 AM, Ja kub wrote:
What can be done to guarantee failover in below scenario:
2 tomcats behind cisco loadbalancer 1 http request can last very
long about 50 seconds - response from webservice can take
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ja,
On 6/11/13 9:54 AM, Ja kub wrote:
> What can be done to guarantee failover in below scenario:
>
> 2 tomcats behind cisco loadbalancer 1 http request can last very
> long about 50 seconds - response from webservice can take so long
> load is 20
What can be done to guarantee failover in below scenario:
2 tomcats behind cisco loadbalancer
1 http request can last very long about 50 seconds - response from
webservice can take so long
load is 200 requests per second
I must response in max 4 seconds more than backing webservice
is there somet
11 matches
Mail list logo
