-
Bug
-
Resolution: Outdated
-
Neutral
-
4.4.8, 4.5.3
When shutting down Jackrabbit repositories, at least in the 1.6 version of Jackrabbit, Magnolia leaves the Transient File Reaper thread active without apparent reason.
Restarting the app a few times without restarting the application server will leave a bunch of these threads open, thus wasting the thread pool.
The attached patch simply shuts down the TransientFileFactory after the repositories shutdown.
There is a note on the shutdown method that left me a little doubt: obviously repositories are started by the webapp itself and the method is called just after the repo shutdown, but I have no idea on how to check that the TransientFileFactory was loaded within the webapp classloader... Are there Magnolia configuration in which this is not true? Is it really possible to add a check?
- is related to
-
MGNLOBS-14 Leftover threads when unregistering listeners.
- Closed
- relates to
-
MAGNOLIA-6353 (Database) sessions are kept alive after stopping the application using the console
- Closed