Podczas prezentacji pojawiły się jakieś wyjątki w konsoli i to pomogło mi wykryć wycieki :)
- SEVERE: A web application registered the JBDC driver [org.hsqldb.jdbcDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
- SEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
- SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.codehaus.groovy.grails.commons.spring.ReloadAwareAutowireCapableBeanFactory$2@55dd7f]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
- SEVERE: A web application created a ThreadLocal with key of type [org.codehaus.groovy.reflection.ClassInfo.ThreadLocalMapHandler] (value [org.codehaus.groovy.reflection.ClassInfo$ThreadLocalMapHandler@3127f6]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@d5d9cc]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
- 2010-05-20 16:06:28 org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap
- SEVERE: A web application created a ThreadLocal with key of type [org.codehaus.groovy.runtime.GroovyCategorySupport.MyThreadLocal] (value [org.codehaus.groovy.runtime.GroovyCategorySupport$MyThreadLocal@6e98d7]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@f46e5a]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed.
- log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.
I co się okazało, że po przejśćiu na nowszą wersję grailsów jedna z wtyczek a dokładnie quartz nie była odpowiednia do wersji grailsów. No więc spędziłem trochę czasu z profilerem, a rozwiązanie polegało na zmianie numeru wersji wtyczki, ale bez tych logów było by cieżko, a co dziwne sam tomcat w normalnym trybie tego nie logował:/