Yes that condition will mask maxconn ever getting set, fixed.

On 25/09/13 7:26 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote:

>H,
>
>I am trying to hack at the haproxy.cfg and encountered the following
>obstacle:
>
>        if (!serviceProviderMap.containsKey(Service.Lb) &&
>lbServiceCapabilityMap != null && !lbServiceCapabilityMap.isEmpty()) {
>            maxconn = cmd.getMaxconnections();
>            if (maxconn == null) {
>
>maxconn=Integer.parseInt(_configDao.getValue(Config.NetworkLBHaproxyMaxCon
>n.key()));
>            }
>        }
>
>this means that max-concurrent-connections can only be set if no load
>balancer functionality is used. this makes no sense to me as the value
>is used in haproxy.cfg
>
>Anyone has some background on this for me?
>
>thanks,

Reply via email to