2012/7/26 Stan Yates <[email protected]>: > I recently downloaded and installed lsc-2.0, and am syncing an AD directory > with ~200K users to an UnboundID directory on my Linux box. After several > added entries I get add failures and lots of console messages like: > > Exception in thread "cisco-users-sync-task-122599" > java.lang.OutOfMemoryError: GC overhead limit exceeded > > (These aren't captured in the logfile, a stack trace isn't available...am > guessing that the code should catch Throwable instead of Exception to > capture errors like this.) > > I see where bug "[LDAP Synchronization Connector - Bug #337] Memory leak in > ScriptingEvaluator" was resolved a few months ago in 2.0rc2 - I'm not sure > if this fix is included in the current 2.0 release. If not, I wanted to > find out if memory tuning needs to be done in general, and if so what the > guidelines for that are; or whether there are other bugs open related to > memory leaks. > > (Sorry if this is a duplicate post - I sent yesterday before registering > with the mailer and didn't see this show up in the archive today, so > resending.)
Hi, thanks for this message. You are right, the patch was applied to trunk but not 2.0 branch. So I opened a new issue: http://tools.lsc-project.org/issues/513 Clément; _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
