[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Koch updated ZOOKEEPER-823:
----------------------------------
Attachment: ZOOKEEPER-823.patch
I may have fixed another issue:
I wrapped sendThread.readResponse(incomingBuffer) into a synchronization on the
OutgoingQueue, because it might happen otherwise, that a package is send over
netty and processed by the server, but not yet added to the pendingQueue. This
fix solved all the Heisenbugs I saw.
However there's still a bug with ASyncHammer and that the wait to join threads
times out. I added more Debugging information. The Thread that times out hangs
on ClientCnxnSocketNetty.wakeupCnxn where it waits for the
synchronized(outgoingQueue).
It seems that the outgoingQueue is already owned and blocked in the doWrites
method, hanging on write.awaitUninterruptibly(). doWrites is called by
doTransport where the synchronized(outgoingQueue) happens.
> 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
>
>
> 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.
