I've seen something like this once before involving an app designed for a small number of large sessions. My problem was that I was persisting my sessions in-memory. When there was no more memory available, my app server (weblogic 8.1) conveniently started discarding sessions. Turning on JDBC session persistence and making a bunch of classes implement Serializable fixed the problem. I expect disk-based persistence would also have worked fine. I'm not sure if this problem is specific to weblogic or applies to other app servers, though.
-Steve -----Original Message----- From: John Menke [mailto:[EMAIL PROTECTED] Sent: Monday, June 05, 2006 10:04 AM To: Tapestry User Subject: strange problem losing session variables Is anyone experiencing any problems with "lost" session variables? We have an application that stores some state in the session and we are getting strange errors caused by objects that were previously being in the session being "lost". When our code tries to access these variables it gives nullpointer errors. What is strange is that the session is not being lost itself - if this was the case the StaleSession page would appear via tapestry... -jm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
