[jboss-jira] [JBoss JIRA] Commented: (JBAS-3007) session timeout not implimented properly

[vikas mishra (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3007?page=comments#action_12399190 ] 
            
vikas mishra commented on JBAS-3007:
------------------------------------

I had same problem with jboss-4.0.4.CR2.
It never invalidate the session even after days.but same aplication working fine with tomcat 5.5.X.
if i user a sample war with only use of session.setMaxInactiveInterval() for timeout then it work properly.
but the case like us where complexity is more(bcoz we uses own Httpsession[child class of HttpSession] class) then it never invalidate session.

so I replaced the catalina.jar of jboss_home\server\default\deploy\jbossweb-tomcat55.sar  with tomcat's and my problem is gone away.




> session timeout not implimented properly
> ----------------------------------------
>
>                 Key: JBAS-3007
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3007
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.3 SP1
>         Environment: Windows XP Professional Service Pack 2
>            Reporter: Prashant Tejura
>         Assigned To: Remy Maucherat
>             Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4.GA
>
>
> HttpSession lives well beyond the specified time in {myWebApp}WEB/web.xml   <session-timeout>1</session-timeout> . I also tried to programatically override it using session.setMaxInactiveInterval(60); but it is still alive for more than 60 secs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira