[
https://issues.apache.org/jira/browse/ZOOKEEPER-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-597:
-----------------------------------
Status: Open (was: Patch Available)
this is still happening, but in another area:
http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/577/testReport/org.apache.zookeeper.test/AsyncHammerTest/testObserversHammer/
It is good to have the handler here!
2009-12-04 13:46:13,493 - ERROR [CommitProcessor:0:commitproces...@146] -
Unexpected exception causing CommitProcessor to exit
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:64)
at
org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:378)
at
org.apache.zookeeper.server.NIOServerCnxn.sendCloseSession(NIOServerCnxn.java:349)
at
org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:356)
at
org.apache.zookeeper.server.quorum.Leader$ToBeAppliedRequestProcessor.processRequest(Leader.java:532)
at
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:73)
> ASyncHammerTest is failing intermittently on hudson trunk
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-597
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-597
> Project: Zookeeper
> Issue Type: Bug
> Components: tests
> Reporter: Patrick Hunt
> Assignee: Benjamin Reed
> Priority: Critical
> Fix For: 3.3.0
>
> Attachments: ZOOKEEPER-597.patch, ZOOKEEPER-597.patch,
> ZOOKEEPER-597.patch, ZOOKEEPER-597_2.patch, ZOOKEEPER-597_3.patch,
> ZOOKEEPER-597_3.patch
>
>
> ASyncHammerTest is failing intermittently on hudson trunk. There is no clear
> reason why this is happening, but
> it seems from the logs that a session connection to a follower is failing
> during session establishment - the
> failure seems to be a problem either on the follower or leader. The server
> gets the session create request, but
> it stalls in the request processor pipeline. (we see it go in, but we do not
> see it com eout)
> unfortunately all efforts to reproduce this on non-hudson trunk have failed.
> Even trying to reproduce by
> running on hudson host itself (manually) has failed.
> We need to instrument the client session creation code in the test to dump
> the thread stack if the
> session creation fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
