Re: [OT]Re: Session Expires too early! Help!
Hi,
what i think is, when your page refresh an action is called, in that action
you may be resetting or removeing this attribute or there must be some kind
of code that is resetting this, as of i know there is no setting in web.xml
or struts-config where you can set refresh settings.
Thanks,
Nuwan
- Original Message -
From: "vikas rao" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 17, 2007 6:05 AM
Subject: Re: [OT]Re: Session Expires too early! Help!
Yes, This is what is happening, I seperated out the condition for userType
from getSession and it turns out that it is the userType and not the
session
which is showing NULL and hence logs out.
The user type becomes null when the screen refreshes, so its a problem
with
the refresh, this is what i think.
However, i dont see any configuration to handle refresh on the web.xml or
the struts-config.xml
On 5/17/07, Nuwan Chandrasoma <[EMAIL PROTECTED]> wrote:
This is not a struts related issue, check your logic in the code, the
attribute userType may be not in the session.
Thanks,
Nuwan
- Original Message -
From: "vikas rao" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 17, 2007 5:32 AM
Subject: Re: Session Expires too early! Help!
>I did check the session time out tag, it is:
>
>3600
>
>
> But inspite of this, error comes from my logout.java:
>
>if ((request.getSession() == null) ||
>(request.getSession().getAttribute("userType") == null))
{
>System.out.print(" userType SESSION ATTRIBUTE IS
> NULL
> in
> LOGOUT Action !!!");
>
>
>
> On 5/17/07, Nuwan Chandrasoma <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> look at you web.xml, you may have specified session time out time as 2
>> mins.
>>
>>
>>
>> 30
>>
>>
>>
>> if you set this as 30, the session will time out after 30 min of idle
>> time,
>>
>>
>>
>> Thanks
>>
>> Nuwan
>>
>>
>>
>> - Original Message -
>> From: "vikas rao" <[EMAIL PROTECTED]>
>> To:
>> Sent: Thursday, May 17, 2007 4:47 AM
>> Subject: Session Expires too early! Help!
>>
>>
>> > Hi,
>> > I am working on a bug in my application, the problem is, the session
>> > expires
>> > every 2 minutes or so and I have to log back in to continue, this is
>> very
>> > frustrating. How do I go about debugging this? Which areas of the
code
>> do
>> > you guys think would be best to check for errors?
>> > Any inputs would be very appreciated.
>> > Thanks.
>> > Vikas.
>> >
>>
>>
>> -
>> 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT]Re: Session Expires too early! Help!
Yes, This is what is happening, I seperated out the condition for userType
from getSession and it turns out that it is the userType and not the session
which is showing NULL and hence logs out.
The user type becomes null when the screen refreshes, so its a problem with
the refresh, this is what i think.
However, i dont see any configuration to handle refresh on the web.xml or
the struts-config.xml
On 5/17/07, Nuwan Chandrasoma <[EMAIL PROTECTED]> wrote:
This is not a struts related issue, check your logic in the code, the
attribute userType may be not in the session.
Thanks,
Nuwan
- Original Message -
From: "vikas rao" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 17, 2007 5:32 AM
Subject: Re: Session Expires too early! Help!
>I did check the session time out tag, it is:
>
>3600
>
>
> But inspite of this, error comes from my logout.java:
>
>if ((request.getSession() == null) ||
>(request.getSession().getAttribute("userType") == null))
{
>System.out.print(" userType SESSION ATTRIBUTE IS NULL
> in
> LOGOUT Action !!!");
>
>
>
> On 5/17/07, Nuwan Chandrasoma <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> look at you web.xml, you may have specified session time out time as 2
>> mins.
>>
>>
>>
>> 30
>>
>>
>>
>> if you set this as 30, the session will time out after 30 min of idle
>> time,
>>
>>
>>
>> Thanks
>>
>> Nuwan
>>
>>
>>
>> - Original Message -
>> From: "vikas rao" <[EMAIL PROTECTED]>
>> To:
>> Sent: Thursday, May 17, 2007 4:47 AM
>> Subject: Session Expires too early! Help!
>>
>>
>> > Hi,
>> > I am working on a bug in my application, the problem is, the session
>> > expires
>> > every 2 minutes or so and I have to log back in to continue, this is
>> very
>> > frustrating. How do I go about debugging this? Which areas of the
code
>> do
>> > you guys think would be best to check for errors?
>> > Any inputs would be very appreciated.
>> > Thanks.
>> > Vikas.
>> >
>>
>>
>> -
>> 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]
[OT]Re: Session Expires too early! Help!
This is not a struts related issue, check your logic in the code, the
attribute userType may be not in the session.
Thanks,
Nuwan
- Original Message -
From: "vikas rao" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Thursday, May 17, 2007 5:32 AM
Subject: Re: Session Expires too early! Help!
I did check the session time out tag, it is:
3600
But inspite of this, error comes from my logout.java:
if ((request.getSession() == null) ||
(request.getSession().getAttribute("userType") == null)) {
System.out.print(" userType SESSION ATTRIBUTE IS NULL
in
LOGOUT Action !!!");
On 5/17/07, Nuwan Chandrasoma <[EMAIL PROTECTED]> wrote:
Hi,
look at you web.xml, you may have specified session time out time as 2
mins.
30
if you set this as 30, the session will time out after 30 min of idle
time,
Thanks
Nuwan
- Original Message -
From: "vikas rao" <[EMAIL PROTECTED]>
To:
Sent: Thursday, May 17, 2007 4:47 AM
Subject: Session Expires too early! Help!
> Hi,
> I am working on a bug in my application, the problem is, the session
> expires
> every 2 minutes or so and I have to log back in to continue, this is
very
> frustrating. How do I go about debugging this? Which areas of the code
do
> you guys think would be best to check for errors?
> Any inputs would be very appreciated.
> Thanks.
> Vikas.
>
-
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]
