Andrey,
I grabbed the 1.7.5-SNAPSHOT (20140627.095914-6-distribution) late last
week something similar occurred again today. The good news is that it did
not seem to corrupt the database this time, as when I restarted the
database and my processes, it completed the second time without generating
the decompression error. I'm guessing whatever fix you made needs to
happen somewhere else as well? Details below:
Exception from loading application --
Exception in thread "main"
com.orientechnologies.orient.core.exception.ODatabaseException: Error on
saving record #19:-1
at
com.orientechnologies.orient.core.db.raw.ODatabaseRaw.save(ODatabaseRaw.java:279)
at
com.orientechnologies.orient.core.db.record.ODatabaseRecordAbstract.executeSaveRecord(ODatabaseRecordAbstract.java:1133)
at
com.orientechnologies.orient.core.tx.OTransactionNoTx.saveRecord(OTransactionNoTx.java:79)
at
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:322)
at
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:297)
at
com.orientechnologies.orient.core.db.record.ODatabaseRecordTx.save(ODatabaseRecordTx.java:40)
at
com.orientechnologies.orient.core.db.ODatabaseRecordWrapperAbstract.save(ODatabaseRecordWrapperAbstract.java:292)
at
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:320)
at
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:257)
at
com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:56)
at
com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.createRecord(OBinaryNetworkProtocolAbstract.java:287)
at
com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.createRecord(ONetworkProtocolBinary.java:1371)
at
com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.executeRequest(ONetworkProtocolBinary.java:305)
at
com.orientechnologies.orient.server.network.protocol.binary.OBinaryNetworkProtocolAbstract.execute(OBinaryNetworkProtocolAbstract.java:169)
at
com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:45)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:635)
at java.util.ArrayList.get(ArrayList.java:411)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.wal.OWriteAheadLog.fixMasterRecords(OWriteAheadLog.java:983)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.wal.OWriteAheadLog.log(OWriteAheadLog.java:795)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.logPageChanges(ODurableComponent.java:114)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.logPageChanges(OPaginatedCluster.java:1545)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.addEntry(OPaginatedCluster.java:1026)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.OPaginatedCluster.createRecord(OPaginatedCluster.java:438)
at
com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.createRecord(OLocalPaginatedStorage.java:673)
at
com.orientechnologies.orient.core.db.raw.ODatabaseRaw.save(ODatabaseRaw.java:267)
... 14 more
Exception in server logs:
-1
-> java.util.ArrayList.elementData(ArrayList.java:400)
-> java.util.ArrayList.get(ArrayList.java:413)
->
com.orientechnologies.orient.core.storage.impl.local.paginated.wal.OWriteAheadLog.flush(OWriteAheadLog.java:733)
->
com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache.flushPage(OWOWCache.java:1082)
->
com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache.access$1000(OWOWCache.java:67)
->
com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache$PeriodicFlushTask.iterateBySubRing(OWOWCache.
java:291)
->
com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache$PeriodicFlushTask.flushRing(OWOWCache.java:24
6)
->
com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache$PeriodicFlushTask.run(OWOWCache.java:222)
-> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
-> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
->
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
->
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
->
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
->
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
When I restarted by server:
2014-06-30 15:27:32:254 INFO OrientDB Server v1.7.5-SNAPSHOT is active.
[OServer]
2014-06-30 15:27:40:204 WARN segment file 'database.ocf' was not closed
correctly last time [OSingleFileSegment]
2014-06-30 15:27:42:022 WARN Storage linked was not closed properly. Will
try to restore from write ahead log. [OLocalPa
ginatedStorage]
2014-06-30 15:27:42:023 SEVE Restore is not possible because write ahead
log is empty. [OLocalPaginatedStorage]
2014-06-30 15:27:42:109 INFO Storage data restore was completed
[OLocalPaginatedStorage]
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.