Could I assume then that your context source for the ldao authN handler is of type LdapContextSource? If so, is that set to pool?
-Misagh From: Richard Versace [mailto:[email protected]] Sent: Tuesday, March 12, 2013 8:32 AM To: [email protected] Subject: Re: [cas-user] Intermittent login problem I'm guessing no connection pooling since it is commented out in the deployer.xml file. Now that I'm thinking about it I believe it was causing problem when we first installed cas. Any other ideas? </bean> <!-- <bean id="pooledContextSource" class="org.springframework.ldap.pool.factory.PoolingContextSource" p:minIdle="${ldap.pool.minIdle}" p:maxIdle="${ldap.pool.maxIdle}" p:maxActive="${ldap.pool.maxSize}" p:maxWait="${ldap.pool.maxWait}" p:timeBetweenEvictionRunsMillis="${ldap.pool.evictionPeriod}" p:minEvictableIdleTimeMillis="${ldap.pool.idleTime}" p:testOnBorrow="${ldap.pool.testOnBorrow}" p:testWhileIdle="${ldap.pool.testWhileIdle}" p:dirContextValidator-ref="dirContextValidator" p:contextSource-ref="contextSource"/> <bean id="dirContextValidator" class="org.springframework.ldap.pool.validation.DefaultDirContextValidator " p:base="" p:filter="objectclass=*"> <property name="searchControls"> <bean class="javax.naming.directory.SearchControls" p:timeLimit="1000" p:countLimit="1" p:searchScope="0" p:returningAttributes=""/> </property> </bean> --> <!-- On Mon, Mar 11, 2013 at 3:25 PM, Richard Versace <[email protected]> wrote: Yes, not sure and not sure. I'll be back. Thanks for the hints. On Mon, Mar 11, 2013 at 2:55 PM, Misagh Moayyed <[email protected]> wrote: Guessing you're authenticating against an LDAP repository of some sort? and you're pooling your ldap connections? and the failure occurs when there's been some idle time between the first successful login and the second (the failure)? -Misagh From: Richard Versace [mailto:[email protected]] Sent: Monday, March 11, 2013 11:36 AM To: [email protected] Subject: [cas-user] Intermittent login problem Occasionally but regularly we have an interesting login problem. The first authentication attempt will "fail" and the second will succeed. There is nothing in the catalina log about the "failed" attempt, only the second. We have 2 recently updated, ehcached nodes behind a Barracuda Load Balancer 340 Firmware v4.2.1.007 (2013-02-22 06:57:27), which I know nothing about. We shouldn't go live with this little annoyance. Any troubleshooting hints would be appreciated. Thanks, Rick Versace. Vassar College -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
