zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2751) Investigate why existing unit tests does not leak connection bean for NIO code path
Date Mon, 10 Apr 2017 17:13:41 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963205#comment-15963205
] 

Michael Han commented on ZOOKEEPER-2751:
----------------------------------------

If anyone is interested in server side code and concurrency, this is a good one to work on.

> Investigate why existing unit tests does not leak connection bean for NIO code path
> -----------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2751
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2751
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: server
>            Reporter: Michael Han
>            Priority: Minor
>
> In ZOOKEEPER-2743 we observed a race condition in Netty code path that could lead to
connection bean leaking; similar code pattern exists in NIO code path as well, however existing
unit tests never fail when NIO code path is activated. This is a follow up of ZOOKEEPER-2743
to ensure we don't have connection bean leak when NIO code path is used. 
> Deliverable:
> * Unit tests that fail with connection bean when NIO code path is enabled.
> Or
> * Proof / analysis that NIO code path does not leak cnx bean and why.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message