|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There will always be people who are ahead of the curve, and people who are behind the curve. But knowledge moves the curve. --Bill James
Justin Rundle wrote:This solution does work but for a better understanding for myself why does this fix the issue and what causes this issue?
Experience keeps a dear School, but Fools will learn in no other.
---
Benjamin Franklin - Postal official and Weather observer
Tim Holloway wrote:
Justin Rundle wrote:This solution does work but for a better understanding for myself why does this fix the issue and what causes this issue?
Apparently some of the saved session files were damaged somehow, possibly tomcat crached while writing them, possibly hardware problems. Since session files are not critical resources, the best solution was just to get rid of them.
Note that when I say "not critical resources", I mean that if you delete them while Tomcat isn't running, the user session will have been terminated when Tomcat restarts, so the user will effectively have been logged off and lost work in progress. They're DEFINITELY critical while Tomcat is running!
|
