posted 9 years ago
You might try deleting everything under TOMCAT_HOME/work, /logs, and /temp before starting Tomcat. Leftover lint can cause problems.
Also, check to see if you are tight for disk space. It's possible that the serialized session cannot be saved. Another thing that can cause the session not to be saved, of course, is if Tomcat doesn't have access rights to create or update that file. In addition to the obvious problem (improper access rights), I occasionally zap myself by accidentally launching Tomcat under a superuser context, then re-launching it later under its proper user context - which won't have rights to update files created by the root user.
And finally, check your TOMCAT_HOME/conf/server.xml for any mods (or damage) to the configured session manager.
That should address the problem with SESSIONS.ser. However, it looks like your root cause may be an application bug. Possibly not properly managing connections in com.qad.xmlengine.telnet or failing to properly handle errors coming from that resource. Also, it looks like that's a spawned thread. What spawns it?
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.