[seam-issues] [JBoss JIRA] Updated: (JBSEAM-3070) Tomcat not cleaning up HttpSessions after a single FeedServlet request

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-3070:
------------------------------

    Assignee:     (was: Christian Bauer)


> Tomcat not cleaning up HttpSessions after a single FeedServlet request
> ----------------------------------------------------------------------
>
>                 Key: JBSEAM-3070
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3070
>             Project: Seam
>          Issue Type: Bug
>          Components: Wiki
>            Reporter: Christian Bauer
>            Priority: Critical
>
> Only reproducible in production: The number of HttpSessions is growing over several days. I wrote a listener and it shows the following pattern:
> <User> <Action> <Creation timestamp> <Last access timestamp> <Idle> <Expired since>
> Guest	Feed: 1 04. Jun 2008, 16:01:46	04. Jun 2008, 16:01:46	00:13:49	00:03:49 (EXPIRED!) 	5 KiB
> Guest	Feed: 1 04. Jun 2008, 15:59:56	04. Jun 2008, 15:59:56	00:15:39	00:05:39 (EXPIRED!) 	5 KiB
> Guest	Feed: 1450 04. Jun 2008, 16:03:31	04. Jun 2008, 16:03:31	00:12:04	00:02:04 (EXPIRED!) 	5 KiB
> The EXPIRED! sessions are alive past their maxInactiveInterval (see the time next to it). Tomcat does not clean them up and I don't know why. The only recognizable pattern is that they are all from the FeedServlet, and a single request to that servlet. At this point I suspect that something in Seams ContextualRequest filter is wrong and influencing Tomcat negatively. Will keep this assigned to the wiki until the cause is clearer.

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