[jboss-jira] [JBoss JIRA] (DROOLS-473) Drools spawning a lot of JIT threads

[Mario Fusco (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Fusco reassigned DROOLS-473:
----------------------------------

    Assignee: Mario Fusco  (was: Mark Proctor)


> 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: Mario Fusco
>
> {{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 was sent by Atlassian JIRA
(v6.2.3#6260)