Hm, this is getting weird. After deploying the new war file into tomcat and working with the application I get a "service not available" message, and catalina.out says that the context has been undeployed (see below).
-- Note that I deployed a second test application parallel to the productive application (deployed a symbolic link "bcst.war" pointing to the "bcs.war") so that the same application is running in different contexts ("bcs" and "bcst"). But I am doing so since 2011 to test my app...
(Is there some tomcat specific group? I did not find one on Usenet...)
Magnus
-----
Nov 22, 2013 6:09:07 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive bcst.war
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: A web application registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
SEVERE: A web application appears to have started a TimerThread named [Timer-21657] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-21976] but has failed to stop it. This is very likely to create a memory leak.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
SEVERE: A web application appears to have started a TimerThread named [Timer-21665] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.
Nov 22, 2013 6:09:15 AM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/bcst]
INFO: Deploying web application archive bcst.war
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: A web application registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
SEVERE: A web application appears to have started a TimerThread named [Timer-21657] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-21976] but has failed to stop it. This is very likely to create a memory leak.
Nov 22, 2013 6:09:14 AM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThread
SEVERE: A web application appears to have started a TimerThread named [Timer-21665] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.
Nov 22, 2013 6:09:15 AM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/bcst]
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment