Issue #360 has been updated by Clément OUDOT. Status changed from Closed to Assigned % Done changed from 100 to 90
In fact, seems still be problems when connection is closed and we get : <pre> Nov 15 15:11:27 - ERROR - Error while looking for (&(objectClass=xxx)(employeeNumber=1115)) in ou=people,ou=xxx: javax.naming.ServiceUnavailableException: ldap-xxx:636; socket closed; remaining name 'ou=people' Nov 15 15:11:27 - ERROR - Error while synchronizing ID uid=jean.grey,ou=people,ou=xxx: org.lsc.exception.LscServiceException: javax.naming.ServiceUnavailableException: ldap-xxx:636; socket closed; remaining name 'ou=people' </pre> ---------------------------------------- Bug #360: Connection reset not handled by JndiServices http://tools.lsc-project.org/issues/360 Author: Stéphane Bond Status: Assigned 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
