This content has been marked as final. Show 8 replies
Since the sessions are created and managed by JBoss, SessionManager.sessionInvalidationTime will not be used, application servers session timeout value will be used. After 30 mins (that you have configured in JBoss) also session is still active?
I gave one minute,as the by-default is 30 mins,but,my problem is , session is not expired after 1 minute.I've enabled the debug also,but nothing is shown on the console.
The session would be managed by JBoss and since you are on ATG 10 so you would be using JBoss 5.1 which allows to define a common session-timeout for all applications and is defined at:
Looks like timeout there could be overriding your application's web.xml. Try updating the value in web.xml of jbossweb.deployer under your server directory and see if it helps.
Even,this is not working.
Session timeout for HttpSessions is handle by the hosting app server. If you are referring to timeout of Nucleus session scope (and session NameContexts), Nucleus session scope timeout only happens only when all the app-server HttpSessions that are part of the name Nucleus session have expired (multiple web-apps can can participate in the same Nucleus session, even though they have separate app-server HttpSessions).
For non-dyn/admin sessions, the GenericSessionManager component handles Nucleus session management. You can go to GenericSessionManager in the component browser in /dyn/admin, go up a level (to /atg/dynamo/servlet/sessiontracking/), and see some of the child sessions. If you click on one of those (at least in newer versions of ATG), you can see the (perhaps multiple) HttpSessions that are associated with a given Nucleus session.
Depending on version, it's possible the a web-app (like the "/dyn" web-app) is holding a Nucleus session open... so be sure to make sure that all the web-apps involved have the session-timeout you want.
Try creating SessionManager Component directly under the server layer. For eg.:
and put just one line:
I guess then it'll pick it up.
Few things to look at:
1. Make sure you do not have keep alive setting on or any client side based pooling implemented with your application. There are browser plugin to keep sessions alive too, make sure you don't have one installed.
2. If answer to 1 is NO then check for any exception or warning in logs related to HTTP Session. I remember I had faced issue where one of the OOTB ATG Session Listeners was throwing Exception stopping sessions from dying.
Also setting session timeout in SessionManager won't work, also Jboss gives precedence to session timeout in your web-app web.xml so setting session timeout in web.xml.
Rahul,I tried this also,even,this is also, not picking.