Apache Derby running within Tomcat causes shutdown issues
Posted
by
Luke
on Server Fault
See other posts from Server Fault
or by Luke
Published on 2011-01-03T23:48:46Z
Indexed on
2011/01/05
9:55 UTC
Read the original article
Hit count: 535
I have set up Derby Network Server to be hosted within a Tomcat environment. This works great. However, when I shut down Tomcat I get the following errors:
04/01/2011 10:41:41 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/derby] registered the JBDC driver [org.apache.derby.jdbc.ClientDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/derby] registered the JBDC driver [org.apache.derby.jdbc.AutoloadedDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/derby] appears to have started a thread named [derby.NetworkServerStarter] but has failed to stop it. This is very likely to create a memory leak.
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/derby] appears to have started a thread named [NetworkServerThread_4] but has failed to stop it. This is very likely to create a memory leak.
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/derby] appears to have started a thread named [DRDAConnThread_5] but has failed to stop it. This is very likely to create a memory leak.
04/01/2011 10:41:41 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/derby] appears to have started a thread named [DRDAConnThread_13] but has failed to stop it. This is very likely to create a memory leak.
04/01/2011 10:41:41 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
I'm currently starting and stopping Tomcat with the following commands:
./catalina run
./catalina stop
Is there a better way to shutdown Tomcat with Derby or can this be solved by a configuration change?
© Server Fault or respective owner