[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920715#action_12920715
]
Thomas Koch commented on ZOOKEEPER-823:
---------------------------------------
Hi Patrick,
I saw the same exceptions as you saw. They are not _thrown_ inside the netty
code, but they occurred in my cases every time during the NettyNettySuiteTest.
It isn't very obvious from the junit log, whether a test was run as part of the
NettyNettySuiteTest or not. I do a forward search for "FAILED" and from this
position a backwards search for "running" to find the name of the actual test
suite.
Are you perfecty sure, the failed tests were not run as part of the
NettyNettySuiteTest?
> 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.
