No, They didn't open any new web page. They submitted request last opened page which is idle for a long time.
--- On Fri, 4/27/12, Chris Pratt <thechrispr...@gmail.com> wrote: From: Chris Pratt <thechrispr...@gmail.com> Subject: Re: Parameter value set to null when page submitted after 30 minutes. To: "Struts Users Mailing List" <user@struts.apache.org> Cc: karna...@yahoo.com Date: Friday, April 27, 2012, 12:15 PM When you say "User opened web page", do you mean they started a new web browser after 30min and tried to join an existing session? If so, that won't work with typical cookie based sessions, since the cookies are discarded when the browser is exited. If that's the behavior you are looking for, you should look into a persistent session scheme, or an auto-relogin capability. (*Chris*) On Fri, Apr 27, 2012 at 9:11 AM, sharath karnati <karna...@yahoo.com> wrote: Hi All, We are having session-timeout set to 8 hours. User opened web page and submitted page after 30 minutes. We are validating user session value in 'LoginInterceptor' and it is having value and it is calling next action. <session-config> <session-timeout>480</session-timeout> </session-config> In Action when we are printing parameter value it is showing null. I never heard is there any parameter timeout?? why we are getting value null for these parameters?? As far as this page concern there is NO problems, without any idle time it is working perfectly. Thanks in advance. Regards, Sharath Karnati.
