当我尝试重新部署我的项目时，有时它会耗尽内存并抛出 perGemSpace 错误（只需重新部署 2-3 次）我知道我的项目有一些内存泄漏问题但无法弄清楚，有人可以解释我请。:-?
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/qlbc-portlet] registered the JDBC driver [net.sf.log4jdbc.DriverSpy] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/qlbc-portlet] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/qlbc-portlet] appears to have started a thread named [Thread-43] but has failed to stop it. This is very likely to create a memory leak.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/qlbc-portlet] appears to have started a thread named [Timer-4] but has failed to stop it. This is very likely to create a memory leak.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/qlbc-portlet] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/qlbc-portlet] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Jan 14, 2013 1:12:21 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/qlbc-portlet] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.