Amend the messages displayed by Find Leaks diagnostics in the Manager application.
authorkkolinko <kkolinko@13f79535-47bb-0310-9956-ffa450edef68>
Mon, 1 Mar 2010 18:25:39 +0000 (18:25 +0000)
committerkkolinko <kkolinko@13f79535-47bb-0310-9956-ffa450edef68>
Mon, 1 Mar 2010 18:25:39 +0000 (18:25 +0000)
git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@917633 13f79535-47bb-0310-9956-ffa450edef68

java/org/apache/catalina/manager/LocalStrings.properties

index 4032f22..711797c 100644 (file)
@@ -43,12 +43,15 @@ htmlManagerServlet.deployUploadNotWar=FAIL - File uploaded \"{0}\" must be a .wa
 htmlManagerServlet.deployUploadNoFile=FAIL - File upload failed, no file
 htmlManagerServlet.deployUploadWarExists=FAIL - War file \"{0}\" already exists on server
 htmlManagerServlet.deployWar=WAR or Directory URL:
-htmlManagerServlet.diagnosticsLeak=Check to see if a web application has caused a memory leak on reload
+htmlManagerServlet.diagnosticsLeak=Check to see if a web application has caused a memory leak on stop, reload or undeploy
 htmlManagerServlet.diagnosticsLeakButton=Find leaks
 htmlManagerServlet.diagnosticsLeakWarning=This diagnostic check will trigger a full garbage collection. Use it with extreme caution on production systems.
 htmlManagerServlet.diagnosticsTitle=Diagnostics
-htmlManagerServlet.findleaksList=The following web applications appear to have triggered a memory leak on reload (use a profiler to confirm):\n
-htmlManagerServlet.findleaksNone=No web applications appear to have triggered a memory leak on reload.
+htmlManagerServlet.findleaksList=\
+  The following web applications were stopped (reloaded, undeployed), but their\n\
+  classes from previous runs are still loaded in memory, thus causing a memory\n\
+  leak (use a profiler to confirm):\n
+htmlManagerServlet.findleaksNone=No web applications appear to have triggered a memory leak on stop, reload or undeploy.
 htmlManagerServlet.list=List Applications
 htmlManagerServlet.manager=Manager
 htmlManagerServlet.messageLabel=Message: