<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">On Tue, Jan 14, 2020 at 1:16 PM Crawford, Jeffrey <<a href="mailto:jcrawford@it.ucla.edu">jcrawford@it.ucla.edu</a>> wrote:</span><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang="EN-US">
<div class="gmail-m_-4554995066037369791WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Hi All,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="gmail-m_-4554995066037369791p1"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">We have a misbehaving load balancer in front of our LDAP server that seems to drop connections that are open for too long, despite being configured to allow connections
 up to one hour. Until we can figure out why that is happening, we want to disable pooling on the attribute resolver. We tried commenting out the section:</span><span style="font-size:11pt;font-family:Calibri,sans-serif"><br>
</span><span class="gmail-m_-4554995066037369791apple-converted-space">        </span><span class="gmail-m_-4554995066037369791s1"><ConnectionPool minPoolSize="3"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">maxPoolSize="10"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">blockWhenEmpty="true"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">blockWaitTime="PT5S"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">validatePeriodically="true"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">validateTimerPeriod="PT30M"</span><u></u><u></u></p>
<p class="gmail-m_-4554995066037369791p1"><span class="gmail-m_-4554995066037369791apple-converted-space">                    </span><span class="gmail-m_-4554995066037369791s1">expirationTime="PT10M"/></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">But that seems to revert pooling to default values, is there a flag of some sort that disables pooling altogether?<br></span></p></div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Commenting out the pool config should do the trick. Can you share your configuration and some DEBUG logs for the org.ldaptive package at startup?</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">--Daniel Fisher</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></div></div>