[
https://issues.apache.org/jira/browse/ZOOKEEPER-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913095#action_12913095
]
Patrick Hunt commented on ZOOKEEPER-823:
----------------------------------------
Saw an additional test failure on another machine, it failed with:
[junit] Running org.apache.zookeeper.test.NettyNettySuiteTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.apache.zookeeper.test.NettyNettySuiteTest FAILED (timeout)
That was the entire content of the log output for the test
However the prior test failed with a ton of warnings, including this which
seems suspicious, it needs to be tracked down why this could happen:
[junit] 2010-09-21 09:42:25,890 [myid:] - INFO [New I/O server worker
#32-3:zookeeperser...@801] - Client attempting to establish new session at
/127.0.0.1:48780
[junit] 2010-09-21 09:42:25,891 [myid:] - INFO
[SyncThread:0:zookeeperser...@577] - Established session 0x12b352cbcb80001 with
negotiated timeout 30000 for client /127.0.0.1:48780
[junit] 2010-09-21 09:42:25,900 [myid:] - INFO [New I/O client worker
#41-1:clientcnxn$sendthr...@904] - Session establishment complete on server
localhost/127.0.0.1:11250, sessionid = 0x12b352cbcb80001, negotiated timeout =
30000
[junit] 2010-09-21 09:42:26,205 [myid:] - WARN [New I/O client worker
#41-1:clientcnxnsocketnetty$zkclienthand...@289] - Exception caught [id:
0x66bb1ead, /127.0.0.1:48780 => localhost/127.0.0.1:11250] EXCEPTION:
java.io.IOException: Nothing in the queue, but got 294
[junit] java.io.IOException: Nothing in the queue, but got 294
[junit] at
org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:968)
[junit] at
org.apache.zookeeper.ClientCnxnSocketNetty$ZKClientHandler.messageReceived(ClientCnxnSocketNetty.java:270)
[junit] at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
[junit] at
org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
[junit] at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
[junit] at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
[junit] at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
[junit] at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[junit] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[junit] at java.lang.Thread.run(Thread.java:619)
> 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:
> 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
>
>
> 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.
