[ https://issues.apache.org/jira/browse/ZOOKEEPER-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-121: ----------------------------------- Status: Open (was: Patch Available) Failed in my testing, this time in org.apache.zookeeper.test.ZooKeeperQuotaTest.testCorruption [junit] 2010-03-16 21:33:52,868 - FATAL [SyncThread:1:syncrequestproces...@148] - Severe unrecoverable error, exiting [junit] java.nio.channels.ClosedChannelException [junit] at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:91) [junit] at sun.nio.ch.FileChannelImpl.position(FileChannelImpl.java:256) [junit] at org.apache.zookeeper.server.persistence.Util.padLogFile(Util.java:214) [junit] at org.apache.zookeeper.server.persistence.FileTxnLog.padFile(FileTxnLog.java:228) [junit] at org.apache.zookeeper.server.persistence.FileTxnLog.append(FileTxnLog.java:206) [junit] at org.apache.zookeeper.server.persistence.FileTxnSnapLog.append(FileTxnSnapLog.java:269) [junit] at org.apache.zookeeper.server.ZKDatabase.append(ZKDatabase.java:435) [junit] at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:107) > SyncRequestProcessor is not closing log stream during shutdown > -------------------------------------------------------------- > > Key: ZOOKEEPER-121 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-121 > Project: Zookeeper > Issue Type: Bug > Components: server > Reporter: Patrick Hunt > Assignee: Mahadev konar > Priority: Blocker > Fix For: 3.3.0 > > Attachments: ZOOKEEPER-121.patch, ZOOKEEPER-121.patch, > ZOOKEEPER-121.patch, ZOOKEEPER-121.patch, ZOOKEEPER-121_3.patch, > ZOOKEEPER-121_3.patch, ZOOKEEPER-121_3.patch > > > The SyncRequestProcessor is not closing log stream during shutdown. > See FIXMEs with this ID in ClientBase.java -- I've commented out the > assertion for the time being (checking for logs being deleted), as part of > this fix re-enable these asserts and also verify tests on a Windows system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.