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. > > Kevin Wirth > Sr. Systems Engineer > Information Services > Astoria Bank > * (516) 327-7762 | * kwi...@astoriabank.com<mailto: > kwi...@astoriabank.com> > > Astoria Federal Savings is now Astoria Bank. We can now be contacted at > our new email addresses @astoriabank.com. > > > This e-mail and any attachments that accompany it are confidential and may > be legally privileged. It is intended solely for the use of the > individual(s) to whom it was intended to be addressed. Access to this > e-mail by anyone else is unauthorized. If you are not the intended > recipient, please immediately return the e-mail to the sender and delete > the original and any copy from your computer. If the reader of this message > is not the intended recipient, or an employee or agent responsible for > delivering this message to its intended recipient, you are herewith > notified that any dissemination, distribution, copying or retention of this > communication or the information contained herein is strictly prohibited. >
