Hi Jon, Yes I confirm that the underlying class into DateUtils which is SimpleDateFormat is not thread safe. We should replace it with org.apache.commons.lang3.time.FastDateFormat or any other thread safe implementation.
Regards, Sebastien BAHLOUL 2016-02-25 15:35 GMT+01:00 Jon C Kidder <[email protected]>: > Hey gang. I’ve recently started working on an initiative to sync login > times between AD and OpenLDAP using 2.1.3. I’ve encountered some unusual > behavior. When using AD.aDTimeToUnixTimestamp combined with > DateUtils.simpleFormat I occasionally get incorrect, sometimes future, > values for logon time. It seems completely random. For example out of > 18,000 records on 3 different runs I found 88, 130, and 57 records with > future dated logon times. Each run corrects the timestamps from the > previous run but creates an entirely new batch of corrupt timestamps. I > also discovered that this works perfectly when I run LSC single threaded > using –t 1. If I can get some spare time at the office I may look in to > the source and try to explain this myself. In the interim, I was wondering > if you guys might have some thoughts on this before I throw it out there as > a bug. > > -Jon C. Kidder > > American Electric Power > > Middleware Services > > Email: [email protected] > > Phone: 614-716-4970 > > > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-dev mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-dev >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
