Github user merlimat commented on the issue:
https://github.com/apache/bookkeeper/pull/116
I have been testing quite a while with the leak detector and across all the
leaked files I haven't seen any since netty 4 created socket.
What I mostly saw with the file leak detector has been a whole bunch of
file leaks in different tests. Eg:
* Tests that instantiate bookies and call `shutdown()` without calling
`start()` before are creating and initializing the ledger storage but not
closing it, leaking threads and several fds
* ZooKeeperClient sometimes doesn't shutdown the zk handle if the test
completes too quickly, leaking sockets.
* Several tests are passing bad config, so the bookie/client start gets
exception (on purpose) and then doesn't clean up some partial objects.
* ...
I don't think there is an easy fix for the issue. A bigger refactor would
be needed to address them.
Also, I've noticed that in `pom.xml` there was already:
```xml
<forkMode>always</forkMode>
```
This directive was intended to use a fresh JVM fork for each test, but it's
deprecated in maven and it doesn't seem to be working.
I'd propose to fix that and to use in the surefire configuration:
```xml
<reuseForks>true</reuseForks>
```
I'll create a separate Jira for this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
