On Thu, Feb 12, 2015 at 11:20 AM, Wirth, Kevin <kwi...@astoriabank.com> wrote:
> > > -----Original Message----- > From: Daniel Mikusa [mailto:dmik...@pivotal.io] > Sent: Thursday, February 12, 2015 9:52 AM > To: Tomcat Users List > Subject: Re: tomcat severe error when shutting down service but startup is > clean > > On Thu, Feb 12, 2015 at 9:43 AM, Wirth, Kevin <kwi...@astoriabank.com> > wrote: > > > If I move it won't the app break because it will look for the driver > > in the folder and not find it? > > > > 1.) Please don't top post. Reply inline like this or at the bottom. > > 2.) No. The app doesn't look for the driver in that specific location. > It looks on the classpath. Since the lib directory is also on the > classpath, it will still be available. > > Dan > Update: I added this to the java tab > -Dsun.lang.ClassLoader.allowArraySyntax=true and all of the severe errors > are gone except one: > Feb 12, 2015 11:14:17 AM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/identityiq] appears to have started a thread > named [Thread-3] but has failed to stop it. This is very likely to create a > memory leak. > > Any ideas? > Something in your app is starting a thread. Because the app starts the thread, it's responsible to cleaning it up. This message is telling you that the thread is not being cleaned up. If you take a thread dump when your app is running and then stop the app, you should be able to get an idea as to what created this thread. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F Dan > > > > > -----Original Message----- > > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > > Sent: Thursday, February 12, 2015 9:37 AM > > To: Tomcat Users List > > Subject: Re: tomcat severe error when shutting down service but > > startup is clean > > > > You need to move, not copy. > > > > Copying is not enough, as webapp jars are preferred over Tomcat ones. > > Also having the same class in two places may result in a behaviour > > that you do not expect. > > http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html > > > > > > 2015-02-12 17:33 GMT+03:00 Wirth, Kevin <kwi...@astoriabank.com>: > > > Ok, I will copy the driver into tomcat\lib and see what happens. > > > Thank > > you. > > > > > > -----Original Message----- > > > From: Daniel Mikusa [mailto:dmik...@pivotal.io] > > > Sent: Thursday, February 12, 2015 9:31 AM > > > To: Tomcat Users List > > > Subject: Re: tomcat severe error when shutting down service but > > > startup is clean > > > > > > On Thu, Feb 12, 2015 at 9:06 AM, Wirth, Kevin > > > <kwi...@astoriabank.com> > > > wrote: > > > > > >> I keep getting these weird tomcat errors on shutdown on a newly > > >> built system using tomcat 7.0.57 on a windows 2012 server with jdk > > >> 1.7 that I can't figure out. This is the catalina log: > > >> Feb 12, 2015 8:54:31 AM > > >> org.apache.catalina.loader.WebappClassLoader > > >> clearReferencesJdbc > > >> SEVERE: The web application [/identityiq] registered the JDBC > > >> driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to > > >> unregister it when the web application was stopped. To prevent a > > >> memory leak, the JDBC Driver has been forcibly unregistered. > > >> > > > > > > This is saying that there was a problem unregistering this JDBC driver. > > > It's my understanding that this is common for JDBC drivers and why > > > it's > > generally recommended that you put them in either $CATALINA_HOME/lib > > or $CATALINA_BASE/lib instead of bundled with the web app. Can you > > give that a try and see if this message goes away? > > > > > > > > >> Feb 12, 2015 8:54:31 AM > > >> org.apache.catalina.loader.WebappClassLoader > > >> clearReferencesThreads > > >> SEVERE: The web application [/identityiq] appears to have started a > > >> thread named [Thread-3] but has failed to stop it. This is very > > >> likely to create a memory leak. > > >> > > > > > > Something (possibly your JDBC driver) in your app is starting a thread. > > > Because the app starts the thread, it's responsible to cleaning it up. > > > This message is telling you that the thread is not being cleaned up. > > > If > > you take a thread dump when your app is running and then stop the app, > > you should be able to get an idea as to what created this thread. > > > > > > > > >> > > >> The jdbc driver I am using is in the folder identityiq under the > > >> webapps directory in tomcat. It is the sqljdbc4.jar driver. This > > >> driver is not in the tomcat\lib directory. Please help because I > > >> am getting no help from the vender. Thank you. > > >> > > > > > > Is there any reason it's bundled with the app and not in the lib > > directory? Usually you'd put JDBC drivers in the lib directory. > > > > > > Dan > > > > > > On Thu, Feb 12, 2015 at 9:06 AM, Wirth, Kevin > > > <kwi...@astoriabank.com> > > > wrote: > > > > > >> I keep getting these weird tomcat errors on shutdown on a newly > > >> built system using tomcat 7.0.57 on a windows 2012 server with jdk > > >> 1.7 that I can't figure out. This is the catalina log: > > >> Feb 12, 2015 8:54:31 AM > > >> org.apache.catalina.loader.WebappClassLoader > > >> clearReferencesJdbc > > >> SEVERE: The web application [/identityiq] registered the JDBC > > >> driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to > > >> unregister it when the web application was stopped. To prevent a > > >> memory leak, the JDBC Driver has been forcibly unregistered. > > >> Feb 12, 2015 8:54:31 AM > > >> org.apache.catalina.loader.WebappClassLoader > > >> clearReferencesThreads > > >> SEVERE: The web application [/identityiq] appears to have started a > > >> thread named [Thread-3] but has failed to stop it. This is very > > >> likely to create a memory leak. > > >> > > >> The jdbc driver I am using is in the folder identityiq under the > > >> webapps directory in tomcat. It is the sqljdbc4.jar driver. This > > >> driver is not in the tomcat\lib directory. Please help because I > > >> am getting no help from the vender. Thank you. > > >> > >
