Java tends to handle that so I don't think its an issue with CAS. There's a thread on this list about Java's timeouts with regards to LDAP and sockets, check that out.
You're way behind on your CAS versions though ;-) -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Wed, Jul 2, 2008 at 9:57 PM, Unai Rodriguez <[EMAIL PROTECTED]> wrote: > > That's strange that it checks all of them though. Generally client side > > failover it only in the case where it can't contact the server, not when > > the > > binding fails. > > > > -Scott > > Where can I start looking at to get the issue completely fixed? Is this a > known issue of older versions of CAS? I am using 3.0.5. Should a CAS > upgrade do, or it is more on the LDAP side? What sort of responses trigger > the failover? > > thanks, > unai > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
