Hello Clément, Before testing with Eclipse i try with a single thread (option -t 1) as you propose, and i have no error. So it could be a concurrency problem ? Do i have to test it with Eclipse to give you identify more clearly the problem ?
Other questions/suggestions, i have a task where there is no entries inside source nor or destination. And LSC send a ERROR log message for both sync and clean phase. It is normal for me that LSC detect it but it could be more correct for me to log a WARNING instead as LSC runs correctly ? Here are the messages : Oct 16 11:09:28 - ERROR - Empty or non existant source (no IDs found) Oct 16 11:09:28 - ERROR - Empty or non existant destination (no IDs found) Also is it possible to have new a feature with LSC (if not already requested), here is my idea ? When you configure LSC you can test the configuration (option -v) to validate XML file, you can check with no update. But if source made many changes not really wanted you can't stop LSC synchronization to reflect these changes. So is it possible to set a maximum number of creation/deletion/modification per task. And if LSC encounter this limit during a run it could enter in an "interactive mode" to show/apply or not the future LDIF creation/deletion/modification. In my idea i suppose it could be only available in a synchronous mode. And if run is done by cron, it could log ERRORS. Is it possible or does it make sense with LSC principles ? Regards, Le 16/10/12, Clément OUDOT <[email protected]> a écrit : > 2012/10/15 "POISSON Frédéric" <[email protected]>: > > Hello, > > > > i'm testing an LSC configuration with a AD source to a Oracle DSEE server. > > And inside my configuration i have 15 tasks with quite same attribute > > mapping but on different ldap base (some are for groups other for users). I > > synchronize around 16 000 entries and when i launch LSC with all task i have > > randomly some error messages like this : > > Oct 15 17:32:13 - ERROR - Error while synchronizing ID {usncreated=602408}: > > java.lang.NullPointerException > > > > I have tested separately all task and i never seen this error. > > > > Could you give me advice to find where is my mistake, or help on more debug > > on these errors ? > > > > Regards, > > PS: I have tested on both lsc 2.0 and 2.0.1 > > You can try to run LSC into Eclipse and use breakpoints to identify > the problem : > http://lsc-project.org/wiki/documentation/2.0/development/ideintegration > > You can also try to set threads to 1 (-t 1) to see if this is not a > concurrency problem. > > Clément. > > -- Frederic Poisson
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
