Mantis - Resin
Viewing Issue Advanced Details
5441 major random 05-14-13 09:47 05-20-13 11:28
Mathias Lagerwall  
ferg  
normal  
closed 4.0.33  
fixed  
none    
none 4.0.36  
0005441: Resin session db corruption
After upgrade to 4.0.33-Pro we have started to see things like this in the console. Once it occurs it will not go away. It seems to be some sort of corruption in the internal session database.

EXN: java.lang.IllegalStateException: block at 0x895be000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)
  JniRandomAccessFile[/D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile
EXN: java.lang.IllegalStateException: block at 0x89626000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)
  JniRandomAccessFile[/D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile
EXN: java.lang.IllegalStateException: block at 0x8962a000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)
  JniRandomAccessFile[/D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile
EXN: java.lang.IllegalStateException: block at 0x89640000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)
  JniRandomAccessFile[/D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile
EXN: java.lang.IllegalStateException: block at 0x896b2000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)
  JniRandomAccessFile[/D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile
EXN: java.lang.IllegalStateException: block at 0x896b4000 is invalid for file /D:/resin-pro-4.0.33/resin-data/dk_c/distcache/data.db (length 0xffffffff80000000)

Notes
(0006254)
ferg   
05-20-13 11:28   
This should be fixed in 4.0.36.

If you see a similar issue with 4.0.36, please file it as a new bug. (Because the issue is timing related, a different, future bug might have similar symptoms.)

You can work around the problem by deleting resin-data.