there is one web.xml in your webapp /WEB-INF/
ander there is one web.xml in tomcat /conf/
I had problems in earlier tomcat versions, that the tomcat conf was the ruling setting
greets
chris
| "Hendrik Neumann" <[EMAIL PROTECTED]>
18.05.2005 14:30
|
An: [email protected] Kopie: Thema: Tomcat totally ignores my timeout-settings |
Hi everybody,
I'm sorry for posting this tomcat-question on the myfaces-list, but maybe some of you guys can give me a hint!
I have following problem (see "What is happening to the session if a user closes his browser?" for more informations): I have created and registered an HttpSessionListener which sets the MaxInactiveInterval to 120 seconds in the sessionCreated-method, whenever a new session is created. Then I have System.out.println("session is killed") in the sessionDestroyed-method of this listener. But the sessionDestroyed-method is never called and the session is NEVER killed. I have also a
<session-config>
<session-timeout>2</session-timeout>
</session-config>
in my web.xml but this doesn't help ether.
What am I doing wrong? Why doesn't tomcat kill my session why does it ignore my settings?
Greetings,
Hendrik
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
