[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890942#action_12890942
]
Patrick Hunt commented on ZOOKEEPER-823:
----------------------------------------
Hm... seems to be an intermittent issue with NIO now:
a test got stuck in zookeeper client waiting for close to return - which it
never did. The send thread is already gone. No logs available as junit timed
out eventually and didn't write the logs as a result.
Ben can you take a look at this?
"main" prio=10 tid=0x0000000041397800 nid=0x48c2 in Object.wait()
[0x00007f17f5afd000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00007f17d2125fd0> (a
org.apache.zookeeper.ClientCnxn$Packet)
at java.lang.Object.wait(Object.java:485)
at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1007)
- locked <0x00007f17d2125fd0> (a org.apache.zookeeper.ClientCnxn$Packet)
at org.apache.zookeeper.ClientCnxn.close(ClientCnxn.java:985)
at org.apache.zookeeper.ZooKeeper.close(ZooKeeper.java:534)
- locked <0x00007f17d1ca5858> (a
org.apache.zookeeper.test.DisconnectableZooKeeper)
at
org.apache.zookeeper.test.QuorumTest.testLeaderShutdown(QuorumTest.java:168)
> 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: 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.
