No Session timeout occurs even if the timeout was specified

any help?

http://www.theserverside.com/discussions/thread.tss?thread_id=21643
http://72.14.203.104/search?q=cache:NXmN12ubI2EJ:www.javapassion.com/j2ee/StrutsBestPractices.pdf+session+timeout+struts&hl=en&ct=clnk&cd=12

https://www.experts-exchange.com/questions/21757435/Maintaining-Session-Problem-Struts-and-Tomcat.html
https://www.experts-exchange.com/questions/21703432/JSP-Session-Timeout-Want-to-Redirect-to-Sign-in-Page.html

have a look at these links....
this may help you

you can make you of HttpSession.getMaxInactiveInterval() and decide on session should expire or no.

https://www.experts-exchange.com/questions/10351616/session-timeout.html

Hi avinthm,
thank you for the links. My question is still open,
-how the session invalidate process works (exactly), what does websphere after an session should timeout.
-and what type of java code (or Websphere settings) can avoid websphere to remove a session?

thanks
gabriel

When you make a call to invalidate() all objects bound to the session are unbound. The HttpSession object and the data values it contains are removed from the memory. Hence you can tell that Session has expired.

Timeout can be overridden for a specific session by calling HttpSession.setMaxInactiveInterval(int secs) - negative value indicates session should never time out.

WebSphere Application Server destroys the allocated HttpSession when it expires (default = 1800 seconds or 30 minutes). The WebSphere Application Server maintains a certain number of HTTP sessions in memory based on Session Management settings. When maximum cache limit is reached in memory, the Session Management facility removes the least recently used (LRU) one from cache to make room for a session.

Hi avinthm,
Well thats the default behaviour what we can expect from any Webserver, isn't it?
When the maximum cache limit is reached in memory, does it make some session persisten on the disk (if timeout was not reached), and where?
I need mooooore information to find our bug/solve our problem.
thanks
gabriel

Another thing about how websphere makes a session timeout....
when does it call the garbagecollector and what strategy does it have (webspher on solaris)
thanks

Hi,

you need to cofigure at web.xml, for WAS will be at the admin console.

Example (add after servlet-mapping tag):
web.xml
----------------------------------------
    ...
    </servlet-mapping>

    <session-config>
      <session-timeout>30</session-timeout>
    </session-config>

</web-app>

The default timeout for WebSphere Application Server (WAS) is 30 minutes, meaning that if your user doesn't make a request within that length of time, the session closes.

Session Timeout:

As its name implies, the Session Timeout parameter specifies how long an unused session exists before it times out and is removed from the memory table for local sessions or the cache for distributed sessions. This setting is an important one from a performance perspective because of the memory impact that unused sessions can have on the application server JVM until they are removed. In the same vein, specifying "No Timeout" can result in a memory leak since the session objects are never eligible for garbage collection by the JVM, unless the application explicitly calls        "session.invalidate()" .        As a result, No Timeout is generally not recommended, though it might be appropriate for a small percentage of applications where the user population is very small and stable. In order to minimize the memory impact of session objects, this setting should be set as low as practical in order to satisfy application requirements and use patterns. For applications with a large number of short-lived visits of perhaps a few minutes, a timeout of 5–10 minutes would likely be appropriate. Some web sites even provide a timer to show when the current session will expire and a logout function that invalidates the session.

i hope it may help you

R.K

Hi avinthm,
thank you for helping....
I had also following information from IBM (support call).
-Our session times out after 30min. It will not be removed if the flag in the console is set (Sorry, german console so I don't know the excact naming...) 'access after timeout'. This flag allows websphere to remove a collection of old session, because removing uses lot of cpu power.
If the flag is not set, it will remove it after the timeout. There is another flag, which will allow users that returns after a timeout (but not removed session) to work further on within the same session.
Well this solves my problem and lack of knowledge...
thank you.
gabriel jufer

wel come :)