[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919293#action_12919293
]
Thomas Koch commented on ZOOKEEPER-823:
---------------------------------------
How to continue with this?
I know have a couple of Heisenbugs that do not appear with every test run. Most
often
* org.apache.zookeeper.test.ACLTest.testAcls
* org.apache.zookeeper.test.AsyncHammerTest.testObserversHammer
* org.apache.zookeeper.test.AsyncHammerTest.testHammer
I have the following believing:
- there are some issues with missing / misplaced synchronization blocks in the
Netty java client code
- there may also be some bugs in the server netty code. Sometimes I get bugs
like this, which could also be caused on the server side, but I have not yet
learned the ZK server code:
Exception caught [id: 0x19509443, /127.0.0.1:53300 =>
localhost/127.0.0.1:11270] EXCEPTION: java.io.IOException: Xid out of order.
Got Xid 32 with err 0 expected Xid 33 for a packet with details:
I'd rather like to commit the current state to trunk and to continue the bug
hunting in trunk. This would allow me to do some cleanups that could help to
understand the correct synchronizations. This cleanups should be ZOOKEEPER-878
and ZOOKEEPER-879
This Exception by example could be better understood by solving the above
mentioned issues:
java.lang.NullPointerException
at org.apache.zookeeper.ClientCnxn.conLossPacket(ClientCnxn.java:574)
at org.apache.zookeeper.ClientCnxn.access$2300(ClientCnxn.java:76)
at
org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:869)
at
org.apache.zookeeper.ClientCnxnSocketNetty.cleanup(ClientCnxnSocketNetty.java:147)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:741)
> 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, 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.
