Hi,
>
> If connections to LDAP timeout, is there any way to detect it? Or the
> only way is caching an exception when trying to make an operation on
> that connection? (I'm just guessing here, I don't know deeply JNDI and
> the LDAP provider) If we have the later, that makes difficult to have a
> connection pool, as we could serve connections that have timed out,
> unless you have some tricky mechanism to refresh older connections in
> your pool, as you suggest in your mail. D
You could take a similar approach to WebLogic JDBC connection pools - they
have the options to test connections on reserve or release, by doing some
operations on a scratch/temp table.
Possibly you could create a temp context and run a short lookup on it before
returning to the client - this is *WAY* quicker than re-establishing the
connection each time, and ensures that the client has a good connection.
regards,
-Rob
----------
Robert Castaneda [EMAIL PROTECTED]
CustomWare http://www.customware.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
