Issue #742 has been updated by Sébastien Bahloul.
Hi Raphaël, You are completely right: the issue is encountered when a great number of modifications are scheduled and fullfil the memory. Blocking the addition of new objects to synchronize is the only method to avoid the full JVM memory consumption. I agree that the current implementation is probably not the best so if you have an idea to fix it (specific threadpool implementation, you are welcome :)) Kind regards, ---------------------------------------- Bug #742: OutOfMemory unable to create new native thread http://tools.lsc-project.org/issues/742 Author: Sébastien Bahloul Status: New Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 2.1.2 Problem in version: 2.1.1 Bug and fix proposed in the following thread http://lists.lsc-project.org/pipermail/lsc-users/2013-August/001588.html -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
