Issue #261 has been reported by Jonathan Clarke. ---------------------------------------- Bug #261: [1.3] LSC tries to connect to the destination for each entry even if connection fails http://tools.lsc-project.org/issues/261
Author: Jonathan Clarke Status: New Priority: High Assigned to: Category: Core Target version: 1.3.0 Problem in version: 1.3-SNAPSHOT Running the latest 1.3-SNAPSHOT, I launched LSC with my destination directory stopped. I have 4 entries to sync from the source, and LSC tries to connect to the destination 4 times! Each time fails with an error message like this: <pre> juil. 20 14:54:55 - INFO - Starting sync for FirstTask juil. 20 14:54:55 - INFO - Connecting to LDAP server ldap://localhost:3389/dc=normation,dc=com anonymously juil. 20 14:54:56 - INFO - Connecting to LDAP server ldap://localhost:33389/dc=normation,dc=com as cn=Manager,dc=normation,dc=com juil. 20 14:54:56 - INFO - Connecting to LDAP server ldap://localhost:33389/dc=normation,dc=com as cn=Manager,dc=normation,dc=com juil. 20 14:54:56 - ERROR - Error opening the LDAP connection to the destination! juil. 20 14:54:56 - ERROR - Error opening the LDAP connection to the destination! juil. 20 14:54:56 - ERROR - Error while synchronizing ID {dn=ou=people,dc=normation,dc=com}: java.lang.RuntimeException: javax.naming.CommunicationException: localhost:33389 [Root exception is java.net.ConnectException: Connection refused] juil. 20 14:54:56 - ERROR - Connection lost! Aborting. juil. 20 14:54:56 - ERROR - Error while synchronizing ID {dn=dc=normation,dc=com}: java.lang.RuntimeException: javax.naming.CommunicationException: localhost:33389 [Root exception is java.net.ConnectException: Connection refused] juil. 20 14:54:56 - ERROR - Connection lost! Aborting. juil. 20 14:54:56 - INFO - Connecting to LDAP server ldap://localhost:33389/dc=normation,dc=com as cn=Manager,dc=normation,dc=com juil. 20 14:54:56 - ERROR - Error opening the LDAP connection to the destination! juil. 20 14:54:56 - ERROR - Error while synchronizing ID {dn=ou=Applications,dc=normation,dc=com}: java.lang.RuntimeException: javax.naming.CommunicationException: localhost:33389 [Root exception is java.net.ConnectException: Connection refused] juil. 20 14:54:56 - ERROR - Connection lost! Aborting. juil. 20 14:54:56 - INFO - Connecting to LDAP server ldap://localhost:33389/dc=normation,dc=com as cn=Manager,dc=normation,dc=com juil. 20 14:54:56 - ERROR - Error opening the LDAP connection to the destination! juil. 20 14:54:56 - ERROR - Error while synchronizing ID {dn=ou=groups,dc=normation,dc=com}: java.lang.RuntimeException: javax.naming.CommunicationException: localhost:33389 [Root exception is java.net.ConnectException: Connection refused] juil. 20 14:54:56 - ERROR - Connection lost! Aborting. juil. 20 14:54:56 - ERROR - All entries: 4, to modify entries: 0, modified entries: 0, errors: 4 </pre> If I launch LSC with "-t 1" (to have only one thread), this happens exactly the same. What should happen: # If LSC has a connection problem, it should abort *immediately*. This was the case in 1.2. # I'm not sure if there is one connection per thread, but this would make sense. In this case, why is "-t 1" not reducing this to only one error? -- 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
