Summary: | Make 'set static fields to null' ClassLoader leak workaround behaviour configurable | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Taras Tielkes <taras.tielkes> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | P5 | ||
Version: | 5.5.13 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | Flag for toggling memory leak workaround |
Description
Taras Tielkes
2005-12-18 19:25:11 UTC
Changing to an enhancement request. Taras, if you feel like submitting a patch, that'd be great. Hi, I'd like to vote for this request. We have some problems with redeployment of a webapp that seems to result from this workaround. The webapp runs several threads (for example within JCS) that use Log4j with commons-logging. After the redeployment of the application these threads are trying to access the LogManager which results in a NPE as all the fields were set to null. So a possibility of disabling of the workaround would be really nice. I seem to have a problem accessing the anonymous cvs, so I can't offer any patches, sorry. Is your access to anonymous CVS/SVN better now? Created attachment 19291 [details]
Flag for toggling memory leak workaround
This patch for the container subproject adds a new flag to the context
configuration named "nullifyReferences" that toggles the workaround for memory
leaks on redeployment of webapplications, see changelog of the 5.5.13-beta
release. The default is true.
Hi, thanks for the help. I finally had the time to look into this. I attached a patch that adds the flag we needed in the current trunk version. Per default the workaround stays enabled. Additionally there was a minor version mismatch in the .classpath file. Re-opening since the patch has not been committed to SVN. Is there any progress here? We are facing some serious issues with this memory leak workaround (e.g. using ojb cross-context prevents redeployment) and would like to see the config option in one of the next releases. Regards, Thorsten |