[
https://issues.apache.org/jira/browse/ZOOKEEPER-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416190#comment-15416190
]
Ted Dunning commented on ZOOKEEPER-2509:
----------------------------------------
[~rgs] It is possible that would work. I have a working test now that exhibits
the problem and the fix, but I don't yet like how I had to get the test system
to instantiate a Netty connection factory. What I did was to change the system
property controlling this. That is, of course, a recipe for non-deterministic
disaster if multiple tests run at the same time.
Once I got the test to run at all, I ran into a
java.nio.channels.ClosedChannelException as the server shuts down. That
probably indicates something is wrong with the test framework or the netty code
itself, but it is very hard to see what.
> Secure mode leaks memory
> ------------------------
>
> Key: ZOOKEEPER-2509
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2509
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.1
> Reporter: Ted Dunning
>
> The Netty connection handling logic fails to clean up watches on connection
> close. This causes memory to leak.
> I will have a repro script available soon and a fix. I am not sure how to
> build a unit test since we would need to build an entire server and generate
> keys and such. Advice on that appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
