So, you still have 'connection timeout reached'?
yeah
No, you said that the <1.2.9 behaved like that as well.
So I suppose 1.2.8 and 1.2.6 do that as well?
1.2.8 and 1.2.9 in any case.
I have 1.2.6 not tested yet.
Also inside your workers.properties you have:
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
# ----> lbfactor must be > 0
# ----> Low lbfactor means less work done by the worker.
worker.mmbase02.lbfactor=0
So why did you put lbfactor=0 if it has to be > 0?
Anyhow (it will default to 1) the other worker has
lbfactor=100, meaning that he will receive 100 times
more requests then the other.
Is it intentionally?
yes, I will use the loadbalancer as fallback system. unfortunately it is not
possible to set it to 0
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
