[jira] [Commented] (ZOOKEEPER-1806) testCurrentServersAreObserversInNextConfig failing frequently on trunk with non-jdk6

["Alexander Shraer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815539#comment-13815539 ] 

Alexander Shraer commented on ZOOKEEPER-1806:
---------------------------------------------

Seems like this is whats killing it. Have you seen this before ?

    [junit] 2013-10-29 10:51:35,944 [myid:0] - ERROR [SyncThread:0:SyncRequestProcessor@164] - Severe unrecoverable error, exiting
    [junit] java.nio.channels.ClosedChannelException
    [junit]     at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:94)
    [junit]     at sun.nio.ch.FileChannelImpl.position(FileChannelImpl.java:237)
    [junit]     at org.apache.zookeeper.server.persistence.Util.padLogFile(Util.java:215)
    [junit]     at org.apache.zookeeper.server.persistence.FileTxnLog.padFile(FileTxnLog.java:238)
    [junit]     at org.apache.zookeeper.server.persistence.FileTxnLog.append(FileTxnLog.java:216)
    [junit]     at org.apache.zookeeper.server.persistence.FileTxnSnapLog.append(FileTxnSnapLog.java:371)
    [junit]     at org.apache.zookeeper.server.ZKDatabase.append(ZKDatabase.java:532)
    [junit]     at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:121)


> testCurrentServersAreObserversInNextConfig failing frequently on trunk with non-jdk6
> ------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1806
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1806
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.0
>            Reporter: Patrick Hunt
>            Assignee: Alexander Shraer
>             Fix For: 3.5.0
>
>
> testCurrentServersAreObserversInNextConfig failing frequently on trunk with jdk7
> I see a number of failures recently on this test. Is it a real issue or flakey? Perhaps due to re-ordering/cleanup with jdk7 as we've seen with some other tests? (I don't see this test failing with jdk6)



--
This message was sent by Atlassian JIRA
(v6.1#6144)