directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kiran Ayyagari <kayyag...@apache.org>
Subject Re: JNID vs. Apache DS API - Reconnect to LDAP
Date Tue, 29 Jan 2013 14:24:03 GMT
except in situations like, the network cable is unplugged or the server
crashes
 isConnected() gives the accurate status (even if server terminates the
client connection client is notified through a callback)

On Tue, Jan 29, 2013 at 7:47 PM, Jim Willeke <jim@willeke.com> wrote:

> Within JNDI, you can search for some know entry and determine if it returns
> a value (or if an exception is thrown).
> If you get the "correct" response, you know you are good.
>
> I did not check, but undoubtedly, the isConnected() call is doing something
> similar as the LDAP protocol has no method to determine "isConnected".
>
> --
> -jim
> Jim Willeke
>
>
> On Tue, Jan 29, 2013 at 9:06 AM, Nick Duan <nduan@dtechspace.com> wrote:
>
> > One of the problem when using the JNDI API is that it's hard to manage
> LDAP
> > connections.   It is common that LDAP servers close connections that have
> > been idle for a while automatically.   When that happens, you will have
> to
> > restart your app server to be able to re-establish the LDAP connection.
> > There is no straightforward way in JNDI to automatically detect the
> > connection lost and reestablish the connection automatically, since the
> > LDAP
> > connection is completely hidden inside the directory context in JDNI.
> >
> >
> >
> > Is there any simple way to perform status checking on LDAP connections
> and
> > reconnect automatically to LDAP using Apache DS API?   Any
> > suggestions/hints
> > are highly appreciated.
> >
> >
> >
> > ND
> >
> >
>



-- 
Kiran Ayyagari
http://keydap.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message