I see. Definitely put the log analyzer recommendations through a sanity filter : if connections are timing out , that doesn't necessarily mean you should increase the timeout until they don't! It may mean (as it does in this case) that they should be timed out because they're not being used and probably won't be used in the near future.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 pool side .