I'm currently deploying to a VPS where I'm using Tomcat 7 and I'm seeing lots of complaints deploying the most Barebones grails app, e.g.:
SEVERE: The web application [/BareBones-0.1] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Feb 8, 2012 4:32:53 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/BareBones-0.1] appears to have started a thread named [H2 Log Writer PRODDB] but has failed to stop it. This is very likely to create a memory leak.
Feb 8, 2012 4:32:53 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/BareBones-0.1] appears to have started a thread named [H2 Log Writer PRODDB] but has failed to stop it. This is very likely to create a memory leak.
Additionally, I often run out of memory just re-deploying a WAR file, even though I have 1GB dedicated and 2 GB Burst. E.g. when I run the Tomcat stop command, I get:
java.lang.OutOfMemoryError: PermGen space
on the stop.
So, I'm wondering if anyone can give me a pointer as to whether I might see less problems with Jetty in their experience. My final web app won't be a very large / heavy traffic site.