Issue #360 has been updated by Raphaël Ouazana.

Status changed from Assigned to Feedback
Assigned to changed from Raphaël Ouazana to Clément OUDOT


----------------------------------------
Bug #360: Connection reset not handled by JndiServices 
http://tools.lsc-project.org/issues/360

Author: Stéphane Bond
Status: Feedback
Priority: High
Assigned to: Clément OUDOT
Category: Core
Target version: 2.0.2
Problem in version: 


JndiServices.getInstance maintains a cache of connections but doesn't check if 
the cached connection is alive before returning it.

This causes problems when LSC is embedded in a web server: the cache could be 
used over a very long period of time. If the connection is broken, all LDAP 
operations will cause a "javax.naming.CommunicationException: Connection reset" 
error.

The provided patch fixes the problem by testing the old connection before 
returning it.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev

Reply via email to