Thanks, I tried to check this for wicket examples and it works with default server configuration. This means that there are some error in my application... but I haven't any error messages... ok, I'll continue experiments. Does that message "page expired" mean that the session is gone? So I have next question: default session timeout for Tomcat is 30 minutes but "page expired" appears much earlier - even for wicket examples. Why?
Johan Compagner wrote: > > the default config of tomcat already restarts the wicket example sessions > just fine for me > I havent changed 1 thing about that > > > On Tue, May 13, 2008 at 11:59 AM, ElSe <[EMAIL PROTECTED]> wrote: > >> >> Do you mean tomcat logs? No I don't. Some *.ser files appear in the >> work\Catalina\localhost\<application> directory so session is serialized >> but >> isn't restored. >> >> Do I understand correctly that my assumption is correct and the wicket >> session must be restored with the tomcat persistent manager? So there >> must >> be some error in the configuration of the server or application itself? >> >> >> igor.vaynberg wrote: >> > >> > do you get any serialization errors in your logs, you might be trying >> > to store something non serializable in the wicket component. >> > >> > -igor >> > >> > >> > On Mon, May 12, 2008 at 1:09 AM, ElSe <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi, >> >> >> >> I'm just started experiments with Wicket so I suppose my question is >> >> stupid >> >> however I haven't found the answer on the forum. >> >> >> >> The point was to understand how to organize persistent sessions for >> the >> >> wicket application. It seemed to me that such application should work >> >> with >> >> the standard Tomcat mechanism transparently as any other servlet. >> >> So I have written simple wicket application - just two pages that >> show >> >> sessionid, configured Tomcat persistent manager and started session. >> >> Then I >> >> restarted the server and tried to pass from one page to another >> waiting >> >> to >> >> see the same sessionid. But I have seen "page has expired". >> >> Should I provide some serialization support in my application or >> there >> >> is >> >> some error in my logic or there aren't such possibility and I "want >> >> something strange"(c)? >> >> >> >> BR >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/persistent-sessions-in-Tomcat-tp17183181p17183181.html >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/persistent-sessions-in-Tomcat-tp17183181p17205069.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/persistent-sessions-in-Tomcat-tp17183181p17226017.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
