Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: "Nick Duan" <nduan@dtechspace.com>
To: <users@directory.apache.org>
Subject: JNID vs. Apache DS API - Reconnect to LDAP
Date: Tue, 29 Jan 2013 09:06:58 -0500
Message-ID: <001901cdfe29$e75a6e30$b60f4a90$@dtechspace.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001A_01CDFDFF.FE846630"
Thread-Index: Ac3+KJaOWq3GEgtmTr6pTnYWv2OFww==
Content-Language: en-us

------=_NextPart_000_001A_01CDFDFF.FE846630
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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


------=_NextPart_000_001A_01CDFDFF.FE846630--