Le 11/08/2016 à 02:55, [email protected] a écrit :
Hi all,
I’m experimenting with setting up asynch mode for a small tutorial
test between a postgresql and active directory lightweight directory
service (AD LDS) but cannot get a previously working synch config to
work in asynch mode. There is quite a lack of docs/examples in setting
up asynch compared to normal mode, I did find and attempt to follow
the postgresql2opendj sample listed from this link
http://lists.lsc-project.org/pipermail/lsc-users/2014-April/001865.html but
am getting not what I expected as output and am unsure if the setup I
am using is correct. Is the below config supposed to be like this for
asynch mode?
If launched with no changes to synch it will sit on the below output
for about a minute before writing thread exceptions continuously until
a java.lang.OutOfMemoryError occurs. If launched with a difference
between the database and directory it will sync the change multiple
times which error out after the first one as the first entry has
already been added, then it will wait until the thread exceptions
occur. Any change to the database after it has been launched is not
detected and does not show in the directory. Below is the pasted
console output in respective order as well as the sql and lsc
configurations with the database table.
Hi,
first, I think there is no wide usage of async with source database. If
someone on this mailing list has already set it, please share your feedback.
Concerning the "already exists" errors, I suggest you force a single
thread (-t 1) as the modification seems to have been pushed in every
threads.
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
87, rue de Turbigo - 75003 PARIS
Blog: http://sflx.ca/coudot
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
