Frank Pavageau created DROOLS-473: ------------------------------------- Summary: Drools spawning a lot of JIT threads Key: DROOLS-473 URL: https://issues.jboss.org/browse/DROOLS-473 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Final Reporter: Frank Pavageau Assignee: Mark Proctor {{MvelConstraint}} submits JIT tasks to an {{Executor}} once it has been evaluated enough times, but that {{Executor}} created by {{ExecutorProviderImpl}} is a basic {{CachedThreadPool}} which can create an unbounded number of threads (though they die after idling for a minute). Firing a lot of rules quickly can create several hundreds threads. If you have several JVMs on the same machine processing the same kind of load, it can saturate the OS and result in errors as the JVMs cannot create native threads anymore. The maximum size of the thread pool should probably be limited to a more reasonable default, maybe with a configurable value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira