Rudder

Our usage of threadpool grew a little organically, and we don't really now what kind of thread pools are used by what.
This leads to unefficiency, in both the type of thread pool given their usage, and the sharing of threads by usage type.

We need to list all threadpools and there usage. There is a least for rudder:

- LDAP connection pool,
- PostgreSQL connection pool,
- Lift requests
- Lift backend processing
- Lift scheduler
- scala Future / scala global execution context (hooks, compliance, changes by rule, file migration...)
- JS engine
- generation parallism

And for inventories:
- inventory watcher,
- LDAP connection,
- web requests

This is a template, please edit and remove what is not relevant.

I found this bug in Rudder version [Your Version here], on [Distribution here]

This bug happens:

• During installation of Rudder agent / Rudder server
• While running rudder agent on a Node
• When using Rudder web interface
• When looking at compliance of a Node
• When configurations are generated on Rudder Server
• When a Nodes applies a configuration

Description:

You can reproduce it with the following steps:

• ...
• ...

You can workaround this issue by doing likewise: