RunRecoveryException due to closed log file descriptor - berkeley-db
This is a discussion on RunRecoveryException due to closed log file descriptor - berkeley-db ; I'm getting a RunRecoveryException due to a problem with the FileManager's log file. I have no idea why this might be happening, any ideas? There are a few deadlocks going on during multiple threads that properly abort() any transactions, so ...
![]() |
| | LinkBack | Thread Tools | Display Modes |
|
#1
| |||
| |||
| FileManager's log file. I have no idea why this might be happening, any ideas? There are a few deadlocks going on during multiple threads that properly abort() any transactions, so I'm at a loss. ... Adam Caused by: Environment invalid because of previous exception: com.sleepycat.je.RunRecoveryException: (JE 3.2.23) Channel closed, may be due to thread interr upt at com.sleepycat.je.log.FileManager $LogEndFileDescriptor.force(FileManager.java:1688) at com.sleepycat.je.log.FileManager.syncLogEnd(FileMa nager.java:1153) at com.sleepycat.je.log.FSyncManager.executeFSync(FSy ncManager.java:277) at com.sleepycat.je.log.FSyncManager.fsync(FSyncManag er.java: 218) at com.sleepycat.je.log.FileManager.groupSync(FileMan ager.java: 1179) at com.sleepycat.je.log.LogManager.log(LogManager.jav a:295) at com.sleepycat.je.log.LogManager.logForceFlush(LogM anager.java:129) at com.sleepycat.je.txn.Txn.commit(Txn.java:441) at com.sleepycat.je.txn.Txn.commit(Txn.java:365) at com.sleepycat.je.Transaction.commit(Transaction.ja va:80) at Caused by: java.nio.channels.ClosedChannelException at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelI mpl.java: 91) at sun.nio.ch.FileChannelImpl.force(FileChannelImpl.j ava:352) at com.sleepycat.je.log.FileManager $LogEndFileDescriptor.force(FileManager.java:1680) ... 20 more |
![]() |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
| |
All times are GMT -4. The time now is 01:33 AM.




Linear Mode