On 6/27/2018 3:29 PM, Ghiurea, Isabella wrote:
David to answer your Q ,
the idea is to have the www existing idle connections being
reused, so I think the access analyzer(logconv) advice to increase
the idle timeout ldap may be misleading in this case and we are
debating if we should
David to answer your Q ,
the idea is to have the www existing idle connections being reused, so I
think the access analyzer(logconv) advice to increase the idle timeout ldap
may be misleading in this case and we are debating if we should turn off in
and only cfg idle timeout on www poo
Can I ask why is the timeout a problem? Wouldn't the pool manager just
open a new connection when required?
Put another way : is a pool connection that has been idle for 120
seconds actually useful?
On 6/27/2018 1:50 PM, Ghiurea, Isabella wrote:
Hi List
we are running 389-ds-base-1.3.5.
Hi List
we are running 389-ds-base-1.3.5.15-1.fc24.x86_64 ( OS -FC24)
analyzing access log file today , I am seeing for each of the client T1 msg,
our applications are using www pools connection to ldap we have a large number
of hosts cfg for min and max pools size , most of connections are
