Patrick Hunt commented on ZOOKEEPER-823:

I was also seeing some intermittent nettynetty failures previously. However now 
I'm seeing this each time (3 out of 3) I run on one of my beefier server boxes 

junit.framework.AssertionFailedError: thread HammerThread-0 still alive after 

this only showed up after merging in ZOOKEEPER-846, so I suspect that something 
has changed in this patch such that more than just applying 846 is necessary.

I'm pretty swamped, Thomas can you look at these issues? (incl the ones 
I/flavio cited earlier?)

> 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, 
> 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.

Reply via email to