Hi Olaf, 1. We need to check and reopen the issue if this is confirmed. As it would be the only bug to fix on 2.0.3, we could tag and release a version quite quickly. 2. Thanks for your feedback, this has been fixed.
Best regards, Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ 2013/5/15 Olaf Pueschel <[email protected]> > Hello everyone! > > Thanks for yor fast answers from Clément and Sébastien in the first place. > > After I received the links to the sample config & they indicated that my > config is correct, I read a little source and > stumbled upon Bug #539 which seems not to be fixed in 2.0.2. So I > downloaded the current snapshot and it works! > > Since I will have trouble deploying a snapshot version into production, is > there any roadmap for something like 2.0.3? > > Additional findings: > > 1. > When making tests I learned that when the *requestNameForNextId* returns > no rows I get an Stacktrace while the documentation says: > "This request may return nothing and LSC will wait until the next > modification or its own stop ". I took nothing to mean "no rows"... but > then: > > May 15 14:44:30 - DEBUG - Asynchronous synchronize PasswordSyncTask > Exception in thread "PasswordSyncTask" java.lang.NullPointerException > at > org.lsc.service.AbstractJdbcService.getMapKey(AbstractJdbcService.java:183) > at > org.lsc.service.SimpleJdbcSrcService.getNextId(SimpleJdbcSrcService.java:174) > at org.lsc.AsynchronousRunner.run(AbstractSynchronize.java:607) > at java.lang.Thread.run(Thread.java:722) > > 2. > Also I noticed a documentaion bug. The page for database source service (* > http://lsc-project.org/wiki/documentation/2.0/configuration/service/sourcesql > *<http://lsc-project.org/wiki/documentation/2.0/configuration/service/sourcesql> > ) > lists the rerquest names in the wrong order. requestNameForNextId *must* > come before requestNameForClean (and after requestNameForObject). > > > Best regards > Olaf > > -- > *Olaf Püschel (ext.)* > Senior Consultant > IS4IT GmbH > externer Dienstleister im Auftrag der > Giesecke & Devrient GmbH, Prinzregentenstr. 159, 81677 München, > Deutschland > http://www.gi-de.com > Tel. +49 89 4119-3283, Fax +49 89 4119-1568 > mailto:[email protected] <[email protected]> > > > > > Von: Clément OUDOT <[email protected]> > An: Sébastien Bahloul <[email protected]> > Kopie: Olaf Pueschel <[email protected]>, lsc-users < > [email protected]> > Datum: 15.05.2013 10:05 > Betreff: Re: [lsc-users] Antwort: Re: Problem with running lsc in > async mode from jdbc src > ------------------------------ > > > > 2013/5/15 Sébastien Bahloul <[email protected]>: > > > > Hi Olaf, > > > > I've written a sample configuration for this use case and have tested it > > successfully : > > > > > https://lsc-project.org/svn/lsc/trunk/sample/postgresql/etc-postgresql2opendj/lsc.xml > > > > You should be able to adapt it to your need. > > > > The iBatis configuration is here: > > https://lsc-project.org/svn/lsc/trunk/sample/postgresql/etc-postgresql2opendj/sql-map-config.d/InetOrgPerson.xml > > Clément. > > > > Vorsitzender des Aufsichtsrats: Dr. Peter-Alexander Wacker > Geschäftsführer: Dr. Karsten Ottenberg (Vorsitzender, CEO), > Michael Kuemmerle, Hans Wolfgang Kunz, > Dr. Walter Schlebusch, Dr. Peter Zattler (CFO) > Gesellschaftssitz: München, Handelsregister Amtsgericht München HRB 4619. > > Bitte prüfen Sie der Umwelt zuliebe, ob der Ausdruck dieser E-Mail > erforderlich ist. >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
