Hi We are running several clusters with resin-pro and have problems with the sessions.
We have tried several versions of Resin / Java but the current setup is: Win Server 2008 R2 SP1 Java 1.7.0_55 from Oracle Resin-Pro 4.0.39 Current session config: <session-config> <use-persistent-store/> <enable-url-rewriting>false</enable-url-rewriting> <reuse-session-id>false</reuse-session-id> <save-mode>on-shutdown</save-mode> <serialization-type>hessian</serialization-type> <session-timeout>120</session-timeout> </session-config> The sites works fine for a couple of days after restart and deletion of resin-data/. Then all of a sudden the following messages start to flood the log (several each second): [2014/05/17 09:33:56.298] {resin-30} Watchdog received warning from Resin[fi_b,pid=0]: java.lang.IllegalStateException: block at 0xb1bc0000 is invalid for file /D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db (length 0x80000000) JniRandomAccessFile[/D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile [2014/05/17 09:33:56.311] {resin-30} Watchdog received warning from Resin[fi_b,pid=0]: java.lang.IllegalStateException: block at 0xb1bd8000 is invalid for file /D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db (length 0x80000000) JniRandomAccessFile[/D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile [2014/05/17 09:33:56.342] {resin-30} Watchdog received warning from Resin[fi_b,pid=0]: java.lang.IllegalStateException: block at 0xb1be6000 is invalid for file /D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db (length 0x80000000) JniRandomAccessFile[/D:/resin-pro-4.0.39/resin-data/fi_b/distcache/data.db]:class com.caucho.vfs.JniRandomAccessFile ..... The log can become many GB during a day of operation. The sites are quite busy and a lot of sessions are created. Ferg indicated to me in an earlier conversation that the "length 0x80000000" looked strange. Does this mean that the session storage is too big? Are we somehow running 32-bit things when we shouldn't? I have tried to recreate the problem locally on my Linux machine but I am not able to trigger the error. I am not sure if this has to do with me running Linux or that my simulated load isn't triggering the error. What can I do to the track this down? Best regards Mathias Lagerwall _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest