Hi Hez,
As Tony said, setting the session time out in the server would be the better
way.
I guess that you are trying to set this timeout in client side because you
let individual users configure their session time out period. If that is the
case, then you will have to follow the way that have
Hi
Yes, it is working by setting the timeout in the server.
To summarize, the following are what I did:
1) Configured the session timeout in web.xml (say for 1 minute):
session-config
session-timeout1/session-timeout
/session-config
2) Then create a session in the login RemoteServiceServlet:
Seems you have set the session time out in server side. So what is the use
of Cookies here?
---
Kamal Mettananda
http://lkamal.blogspot.com
On Wed, Jun 3, 2009 at 10:00 PM, hezjing hezj...@gmail.com wrote:
Hi
Yes, it is working by setting the timeout in
Hi Kamal
I removed the cookies too.
BTW, I saw some example that set the timeout like the following:
HttpSession session = getThreadLocalRequest().getSession();
session.setMaxInactiveInterval(1000 * 60);
I tried the above code before adding session-timeout in web.xml.
That doesn't work in my
I can remember that I used this method for setting the time out through the
code; however not quite sure why that method is not working for you.
---
Kamal Mettananda
http://lkamal.blogspot.com
On Wed, Jun 3, 2009 at 10:44 PM, hezjing hezj...@gmail.com wrote:
What about timing out the session on the server?
Assuming that you're using a Java application container on the server,
you can add the following to web.xml:
session-config
session-timeout5/session-timeout
/session-config
This will cause the server to time out connections after
