[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920750#action_12920750
]
Thomas Koch commented on ZOOKEEPER-823:
---------------------------------------
The problem with the failing testWatchAutoResetWithPending might be the
following. The test uses testableZooKeeper.pauseCnxn($milliSeconds)
PauseCnxn tries to block the ClientCnxn by holding a lock on the ClientCnxn
instance, interrupting the connection and not releasing the lock for
$milliSeconds.
Actually I wonder how this could have ever worked reliable in the first place.
The only thing I see that also synchronizes on ClientCnxn is the getXid()
method.
The solution might be to find a better implementation for
testableZooKeeper.pauseCnxn
> update ZooKeeper java client to optionally use Netty for connections
> --------------------------------------------------------------------
>
> Key: ZOOKEEPER-823
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-823
> Project: Zookeeper
> Issue Type: New Feature
> Components: java client
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Fix For: 3.4.0
>
> Attachments: NettyNettySuiteTest.rtf,
> TEST-org.apache.zookeeper.test.NettyNettySuiteTest.txt.gz,
> testDisconnectedAddAuth_FAILURE, testWatchAutoResetWithPending_FAILURE,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch, ZOOKEEPER-823.patch, ZOOKEEPER-823.patch,
> ZOOKEEPER-823.patch
>
>
> This jira will port the client side connection code to use netty rather than
> direct nio.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
