OK, convinced. I'll change that tomorrow and add a respective note to the docs fpr ajp retries in relation to lb.
Mladen Turk schrieb: > 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. > > Regards, > Mladen. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]