tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: State of affairs for mod_jk 1.2.20
Date Mon, 27 Nov 2006 13:05:53 GMT

On Nov 24, 2006, at 3:06 PM, Mladen Turk wrote:

> Rainer Jung wrote:
>> In my opinion the only change is:
>> - old code: retries=2 means first try to close all conns and  
>> second try
>> with new connection
>> - new code: retries=2 means first try to close all conns and  
>> immediate
>> new conn, second try a "real" retry.
>>
>
> Right, and that is the problem.
> With retries=1 the old code would in case of connect failure
> go to the next worker in the lb, while in the new code it
> would first try to reconnect.
> Now, this is OK for sticky session, but if you have session
> replication there is simply no need to try to reconnect,
> because it will connect on the next election.
>
> What I'm saying is that right now we would always reconnect,
> and the user has no influence in that, while with default
> retries=2 he can set retries=1 and have that option.
> Of course there will be extra [info] lines in the log in that
> case.
>

+1


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message