Hi Clément,
one little annotation concerning the displayed exception: for debugging
purposes I have added System.out.println-lines into AbstractSynchronize.java.
So the lines where the Errors appear are:
(line 825) abstractSynchronize.logActionError(lm, (id != null ? id.getValue() :
entry.getMainIdentifier()), new Exception("Technical problem while applying
modifications to the destination"));
(line 709) run((fromSource ? task.getSourceService() :
task.getDestinationService()).getBean(id.getKey(), id.getValue(), fromSource));
Sorry, I hope that didn't cause too much confusion.
Best regards,
Jutta
--------------------
Jutta Biernath
Freie Universität Berlin
Zentraleinrichtung für Datenverarbeitung (ZEDAT)
Identity & Customer Management, FUDIS
Fabeckstr. 32
14195 Berlin
Tel. +49 30 838-75090
Fax +49 30 838-475090
Von: Biernath, Jutta
Gesendet: Donnerstag, 16. Juli 2015 14:24
An: 'Clément OUDOT' <[email protected]>; 'TAMONE Francois'
<[email protected]>; [email protected]
Cc: 'FUDIS' <[email protected]>
Betreff: AW: [lsc-users] javax.naming.NamingException: LDAP response read timed
out
Hi Clément, hi François,
>>>> would advice to set threads to 1 (-t1). You indeed found the good
>>>> parameter to set the timeout value: -i. But it is not normal to have an
>>>> error, what shows the log file?
it seems that the error has something to do with the threading. Reproducing the
error on a high debug level shows:
Jul 16 13:26:15 - ERROR - Error while modifying entry XXX in directory
:javax.naming.NamingException: LDAP response read timed out, timeout
used:-1ms.; remaining name 'XXX'
Jul 16 13:26:15 - ERROR - Error while synchronizing ID XXX:
java.lang.Exception: Technical problem while applying modifications to the
destination
Jul 16 13:26:15 - DEBUG - java.lang.Exception: Technical problem while applying
modifications to the destination
java.lang.Exception: Technical problem while applying modifications to the
destination
at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:825)
[lsc-core-2.1.3.jar:na]
at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:709)
[lsc-core-2.1.3.jar:na]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_75]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_75]
Again, the group was nevertheless synchronized.
>>>>> Unfortunately not, because LSC must get the full entry to compare it to
>>>>> the destination entry and compute the differences.
I understand that you must touch the entire group to identify which differences
are to be done. But after identifiying them it would be possible to add/remove
just the (formerly) identified memberships of a group, I think.
Best regards,
Jutta
--------------------
Jutta Biernath
Freie Universität Berlin
Zentraleinrichtung für Datenverarbeitung (ZEDAT)
Identity & Customer Management, FUDIS
Fabeckstr. 32
14195 Berlin
Tel. +49 30 838-75090
Fax +49 30 838-475090
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
