https://bz.apache.org/bugzilla/show_bug.cgi?id=58900
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Memory leak due to infinite |Infinite redeploy loop with
|redeploy loop |undeployOldVersions="true"
--- Comment #4 from Mark Thomas <ma...@apache.org> ---
+1 to Chris's comment regarding the memory leak. 99% of those turn out to be
bugs in applications or 3rd party libraries. The redeploy loop is definitely a
Tomcat bug.
getCanonicalPath() is used handle docBases such as "../../someapp.war" which
will be resolved relative to the appBase but should not be deleted because they
are outside the appBase. In this case the context would probably have been
configured via a someapp.xml file (which does need to be removed).
There are likely to be similar issues with any code that triggers an undeploy
if the WAR, DIR or XML files are symlinked into the appBase or configBase. The
fix will be to remove those symlinks. The checks are going to have to be more
sophisticated than the current getCanonicalPath().
I plan to look at this today.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
