struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sharath karnati <karna...@yahoo.com>
Subject RE: Parameter value set to null when page submitted after 30 minutes.
Date Fri, 27 Apr 2012 19:36:36 GMT
Hi Edward,

   We are checking Session with below line in 'LoginInterceptor', if LoginBean is null then
we are taking request to Login page.

LoginBean loginBean = (LoginBean)ActionContext.getContext().getSession().get(Constants.SESSION_LOGIN);

   In our current problem, the LoginBean is NOT null and it is having value.

   The page submission done with doPost method so it is not passing any parameters in URL
but when we are printing parameter value in logger it is showing null. Without any idle time
it is working correctly so I'm really skeptical what do now?? 

Thanks,
Sharath.

--- On Fri, 4/27/12, Edward W. Rouse <erouse@comsquared.com> wrote:

From: Edward W. Rouse <erouse@comsquared.com>
Subject: RE: Parameter value set to null when page submitted after 30 minutes.
To: "'Struts Users Mailing List'" <user@struts.apache.org>
Date: Friday, April 27, 2012, 2:01 PM

Since you can print the parameters from the request, does that mean you have
also checked the session to see if it is the same session as the one they
had before the long idle period (verified that the session id didn't
change)? Are there other session variables (param or attrib) that you can
check to see if those are null as well?

Since these are params, I assume a doGet vice a doPost, so when to look at
the request query are the params there with null values or do the params not
exist in the param list? It may be an issue on the browser side.

Not knowing what you have looked at and eliminated so far makes it difficult
to pinpoint the issue.

> -----Original Message-----
> From: sharath karnati [mailto:karnatis@yahoo.com]
> Sent: Friday, April 27, 2012 1:34 PM
> To: Struts Users Mailing List; Chris Pratt
> Subject: Re: Parameter value set to null when page submitted after 30
> minutes.
> 
> 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 <thechrispratt@gmail.com> wrote:
> 
> From: Chris Pratt <thechrispratt@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: karnatis@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 <karnatis@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.
> 
> 
> 
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message