Issue #742 has been updated by Raphaël Ouazana.
Related commits: r2020 & r2023 Some points I would like to enhance: - 10000 is hardcoded, is it a good idea? - once 10000 threads are created, LSC will wait for all of them to stop. If 1 thread is stuck, it will cause a bottleneck, isn't it? - isn't ThreadPoolExecutor meant to handle all of this? Else it could be time to use an other pool, see ThreadPoolExecutor documentation: "To be useful across a wide range of contexts, this class provides many adjustable parameters and extensibility hooks. However, programmers are urged to use the more convenient Executors factory methods Executors.newCachedThreadPool() (unbounded thread pool, with automatic thread reclamation), Executors.newFixedThreadPool(int) (fixed size thread pool) and Executors.newSingleThreadExecutor() (single background thread), that preconfigure settings for the most common usage scenarios." ---------------------------------------- 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
