When Eclipse starts Tomcat in debug mode, a memory overflow exception occurs when you modify a Java class or paging file, and you must restart Tomcat after each modification to be normal and to affect development efficiency. Later, the check was found under servers/tomcatv5.5 server at Localhost-config/server.xml in Eclipse.
Reloadable= "true" in the Context tab, it is normal to change it to false.
Find solutions on the Internet to put the server.xml of Tomcat
<listener classname= "Org.apache.catalina.core.JreMemoryLeakPreventionListener"/>
Comment out also does not work ...
the exception that occurs when you modify a Java file after you start using Tomcat5.5:
Log4j:error logmananger.repositoryselector is null likely due to ERROR in class reloading, using noploggerrepository.< br> 2015-6-24 14:51:24 org.apache.tomcat.util.threads.threadpool$controlrunnable run
Serious: Caught exception ( Java.lang.OutOfMemoryError:PermGen space) Executing org.apache.tomcat.util.net.leaderfollowerworkerthread@ 4df09169, terminating thread
2015-6-24 14:51:26 org.apache.catalina.core.containerbase$ Containerbackgroundprocessor Processchildren
Critical: Exception invoking periodic operation:
Java.lang.OutOfMemoryError:PermGen space
2015-6-24 14:51:56 org.apache.catalina.core.containerbase$ Containerbackgroundprocessor Processchildren
Critical: Exception invoking periodic operation:
Java.lang.OutOfMemoryError:PermGen space
2015-6-24 14:52:07 org.apache.catalina.core.containerbase$ Containerbackgroundprocessor Processchildren
Critical: Exception invoking periodic operation:
Java.lang.OutOfMemoryError:PermGen Space
Use the exception that occurs when the Java file is modified when Tomcat6.0 is started:
2015-6-24 14:54:12 Org.apache.catalina.loader.WebappClassLoader Clearreferencesjdbc
Serious: A Web application registered the JBDC driver [Oracle.jdbc.driver.OracleDriver] but failed to unregister it when the We b application was stopped. To prevent a memory leak, the JDBC Driver has been, forcibly.
2015-6-24 14:54:12 Org.apache.catalina.loader.WebappClassLoader clearreferencesthreads
Serious: A Web application appears to have started a thread named [Resource Destroyer in Basicresourcepool.close ()] but has FAI led to stop it. This is very likely to create a memory leak.