Author: markt
Date: Mon May 16 15:01:26 2016
New Revision: 1744068
URL: http://svn.apache.org/viewvc?rev=1744068&view=rev
Log:
Fix typo
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java?rev=1744068&r1=1744067&r2=1744068&view=diff
==============================================================================
---
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
(original)
+++
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/JreMemoryLeakPreventionListener.java
Mon May 16 15:01:26 2016
@@ -191,7 +191,7 @@ public class JreMemoryLeakPreventionList
* multiple root causes for this. Some of these are particularly nasty as
* profilers may not identify any GC roots related to the leak. For
example,
* with YourKit you need to ensure that HPROF format memory snapshots are
- * used to be abel to trace some of the leaks.
+ * used to be able to trace some of the leaks.
*/
private boolean xmlParsingProtection = true;
public boolean isXmlParsingProtection() { return xmlParsingProtection; }
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
