[ https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920734#action_12920734 ]
Patrick Hunt commented on ZOOKEEPER-823: ---------------------------------------- Sorry man, but I checked that, a few things indicate that it's nio and not netty: 1) The log would have something like this in it: [junit] Running org.apache.zookeeper.test.NettyNettySuiteHammerTest which I don't see prior to this failure (running ... *Netty* 2) I can see log messages from NIO and not from netty in the log (NIO class loggers I mean) 3) I'm pretty sure (don't have one on hand) that if the *Netty*Test fails you see that in the stack trace. > 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.