• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

difference in actual and specified timeout

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

My application requires session timeout after 20 minutes and had an entry in the web.xml.

<session-config>
<session-timeout>20</session-timeout>
</session-config>

but the session timeout happens only sometimes after 25 minutes. can anyone explain why this much delay in session timeout?

Additional info.:
IBM Websphere Application Server 5.0
Windows 2000

Thanks,
Ashok
 
Ranch Hand
Posts: 8946
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You cannot expect timeout to occur at exactly 20 minutes after the previous request because the JVM may be busy doing something else. Having said that 5 minutes delay is too much. Check whether the server is busy processing some other request which may result in the timeout thread not getting CPU cycles.
 
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We found the same thing in Websphere. The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after. This is just the way it is, unfortunately
 
Pradeep bhatt
Ranch Hand
Posts: 8946
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by David O'Meara:
We found the same thing in Websphere. The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after. This is just the way it is, unfortunately



If it prevents the user from using it after 20 minutes (and not 25 minutes)then it should be ok even if the other listener methods are invoked later.
 
ashok sashrith
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
David, There is confusion over here. Could you little more elaborate on "The timeout value prevents the user from using the session, but the actual session does not get cleared for some time after".

Thanks,
Ashok
 
a wee bit from the empire
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic