[
http://opencast.jira.com/browse/MH-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28157#comment-28157
]
Josh Holtzman commented on MH-8205:
-----------------------------------
> Either a filter or an exhaustive search of HttpServletRequest is not enough
A filter is definitely the way to go here. I'd be interested to see what you
tried to determine that it is not sufficient.
The key is to a) ensure the filter is enabled for every request, and b) is the
very last thing to run during a request/response cycle, so you can be sure your
settings aren't being overridden by any other code.
If the session is first in the chain, simply delegate to the next filter, then
do your session cleanup (set the timeout, or invalidate the session if it's
digest auth).
> Jetty Sessions lead to memory leak
> ----------------------------------
>
> Key: MH-8205
> URL: http://opencast.jira.com/browse/MH-8205
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Administrative Tools, Engage Tools
> Affects Versions: 1.2, 1.3
> Reporter: David Horwitz
> Assignee: Adam McKenzie
> Priority: Release Blocker
> Fix For: 1.2.1, 1.3
>
> Attachments: 1.2.x-HttpServletRequest.list,
> MH-8205-Memory-Leak-Trunk.patch, trunk-HttpServletRequest.list
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
