Closed KrishnaST closed 4 years ago
Hello and thanks for your report.
We've found out that the issue is caused by both JmxModule
module registering jmx-compatible components (the launcher itself and a server are both such compontents) to the global jmx registry while never unregistering them later and by the .awaitShutdown()
and .shutdown()
methods not being implemented appropriately for such use case.
While the latter one I've already fixed in b4c16180, the JmxModule
is a bit harder to fix, so until it is fixed you can just remove it altogether - and also use the DataKernel branch that contains the fix I've mentioned.
@necauqua Can the fix be expected in next release?
Hello, @KrishnaST
We have fixed JmxModule
related problem in 7905b1ca . Now all registered MBeans are unregistered upon launcher shutdown. This fix has not been yet released to maven central repository, but you can install a local version of datakernel
to be used in your project.
For example, to install version 3.1 just run:
git clone --branch v3.1 https://github.com/softindex/datakernel
cd datakernel
./install.sh
datakernel server and its referenced objects not garbage collected after server shutdown and while not having any strong reference.
Sample Output :