[
https://issues.apache.org/jira/browse/GERONIMO-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153129#comment-13153129
]
David Frahm commented on GERONIMO-5800:
---------------------------------------
Any ideas on if/when this might be fixed? This seems like something that would
be a very big deal, but maybe its just me?
My linux/geronimo servers run for about a week and then need to be restarted.
I've got a cron job that does it, but that is way more downtime than we're used
to requiring. Plus, it just seems so wrong ;-)
I understand and respect the fact that this is open source and free software,
so this is NOT a complaint. I'm just trying to figure what our strategy moving
forward.
On another note, we are working on some official IBM WASCE support. Would that
help to get this resolved or are they just going to diagnose and tell me what I
already know?
> logged-in Subjects are cleaned up after web requests complete
> -------------------------------------------------------------
>
> Key: GERONIMO-5800
> URL: https://issues.apache.org/jira/browse/GERONIMO-5800
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Jetty, Tomcat
> Affects Versions: 2.2.1, 3.0
> Reporter: David Jencks
> Assignee: David Jencks
>
> We generally don't clean up the logged in Subject when a web request returns.
> This results in a memory leak in ContextManager.subjectContexts. As well as
> geronimo changes I think this will need changes in the Jetty Authenticators
> we use. I think we control all the affected tomcat code. Ejb requests
> appear to already clean this up on exit.
> As an application-level workaround your app can call:
> Subject subject = ContextManager.getCurrentCaller();
> ContextManager.unregisterSubject(subject);
> immediately before control returns to the client. (I haven't tested this to
> make sure it doesn't break something else)
> Thanks to Morten Svanaes and David Frahm for reporting this problem on the
> user list. There may be a similar problem in 2.1.x but the code and solution
> will be somewhat different.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
