#97 IndexOutOfBoundsException

[Serg]

Hello,

The latest version 1.2.14.1 throws
java.lang.IndexOutOfBoundsException
at java.nio.Buffer.checkIndex(Buffer.java:438)
at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:121)
at com.healthmarketscience.jackcess.UsageMap.read(UsageMap.java:146)
at com.healthmarketscience.jackcess.UsageMap.read(UsageMap.java:125)
at com.healthmarketscience.jackcess.Table.readTableDefinition(Table.java:1407)
at com.healthmarketscience.jackcess.Table.<init>(Table.java:226)
at com.healthmarketscience.jackcess.Database.readTable(Database.java:2008)
at com.healthmarketscience.jackcess.Database.getTable(Database.java:1442)
at com.healthmarketscience.jackcess.Database.getTable(Database.java:1374)
at com.healthmarketscience.jackcess.Database.getTable(Database.java:1362)</init>

in the code:

Database db = Database.open(new File("bug.mdb"));
Table t = db.getTable("test");

But Jackcess 1.2.13 doesn’t throw that exception… A test MDB file is attached.

[James Ahlborn]

how did you create this database? it's actually invalid. if you open it up in ms access and try to type a large amount of data into the memo field, you'll get a "system resource exceeded" error.

[James Ahlborn]

any more feedback on this?

[Serg]

The file was created formerly by an earlier version of Jackcess, so I can't reproduce it now. Anyway Jackcess 1.2.13 read that file without exceptions, at the same time version 1.2.14 throw IndexOutOfBoundsException. Maybe you missed something...

[James Ahlborn]

do you know what version of jackcess it was created with? it may indicate an issue with table creation. but the table as it currently stands has invalid configuration. the reason it worked on older versions of jackcess is because those versions didn't understand all of the table info. this info is now understood, and the new info is invalid in that file. if that new info was created by jackcess, then that bug should be fixed. but in order to fix that, i need to know how the file was created and the appropriate version of jackcess.

[James Ahlborn]

This will be fixed in 1.2.14.3 and 2.0.1.