Corruption of index files (double get and IndexOutOfBounds errors) #101
Comments
|
JDBM3 is no longer supported. Please migrate to MapDB (aka JDBM4) On Wednesday 30 January 2013 16:45:37 Derek Chen-Becker wrote: We're using JDBM with a large number (15k+) of distinct DBs (each with a |
|
Hi Jan, Does the API have known issues like getting runtime ArrayIndexOutOfBounds Exception while doing an insert. How do you resolve these. Is the only solution migrating to JDBM4 and how will this mitigate the issue. It will be helpful in knowing how JDBM4 fixes these issues. Thanks, |
|
MapDB is complete rewrite. So it does not The difference is that it had much more testing |
|
Hi Jan, Thanks for the reply . I like the API and am still discovering the features. Could you let me know why I could be getting this when I do an insert java.lang.ArrayIndexOutOfBoundsException: 32 Thanks, |
|
Honestly no idea. It is almost |
|
It looks like a bug and I am getting it often. Would you be able to suggest what I need to do . Should I continue with this API or something else. The documentation is sketchy. Could you direct me to any documentation on the API or some known issues etc... Whatever help will be really useful... |
|
My suggestion is to move to |
|
I am using JDBM3 . The issue is with JDBM3. |
We're using JDBM with a large number (15k+) of distinct DBs (each with a single TreeMap instance) and while overall they're working well, we're getting what appears to be intermittent corruption of the files. When they corrupt, we can open and read values from the files just fine, but if we attempt to add values to the map and then commit, we get one of a number of errors:
java.lang.Error: double get for page 101
at org.apache.jdbm.PageFile.get(PageFile.java:141) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.allocNew(PhysicalRowIdManager.java:163) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.alloc(PhysicalRowIdManager.java:138) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.insert(PhysicalRowIdManager.java:57) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.insert2(DBStore.java:255) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.insert(DBStore.java:219) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.insert(DBCache.java:75) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.writeValues(BTreeNode.java:1040) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.serialize(BTreeNode.java:990) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.serialize(BTreeNode.java:43) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.update2(DBStore.java:333) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.update(DBStore.java:317) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.updateCacheEntries(DBCache.java:146) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.commit(DBCache.java:100) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
java.lang.IndexOutOfBoundsException: null
at java.nio.Buffer.checkIndex(Buffer.java:538) ~[na:1.7.0_09]
at java.nio.DirectByteBuffer.getShort(DirectByteBuffer.java:584) ~[na:1.7.0_09]
at org.apache.jdbm.PageIo.readShort(PageIo.java:172) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.RecordHeader.getAvailableSize(RecordHeader.java:72) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.allocNew(PhysicalRowIdManager.java:179) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.alloc(PhysicalRowIdManager.java:138) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.PhysicalRowIdManager.insert(PhysicalRowIdManager.java:57) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.insert2(DBStore.java:255) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.insert(DBStore.java:219) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.insert(DBCache.java:75) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.writeValues(BTreeNode.java:1040) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.serialize(BTreeNode.java:990) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.BTreeNode.serialize(BTreeNode.java:43) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.update2(DBStore.java:333) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBStore.update(DBStore.java:317) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.updateCacheEntries(DBCache.java:146) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
at org.apache.jdbm.DBCache.commit(DBCache.java:100) ~[shard-assembly-2.3.0-1-g9ca4462.jar:na]
I can provide copies of the corrupted files if that helps.
The text was updated successfully, but these errors were encountered: