我想知道关于tomcat服务器消息[重复]

Question

我想详细了解启动我的tomcat时出现的这些消息。 我在我的项目中使用显示标签。服务器是apache tomcat 7.0。

当我将它托管在服务器上时，这会产生问题吗？

> May 30, 2014 10:56:13 AM org.apache.catalina.core.StandardContext
> reload
>     INFO: Reloading Context with name [/ZestYouth] has started
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
>     SEVERE: The web application [/ZestYouth] registered the JDBC 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.
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
>     SEVERE: The web application [/ZestYouth] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely
> to create a memory leak.
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
>     SEVERE: The web application [/ZestYouth] appears to have started a thread named
> [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but
> has failed to stop it. This is very likely to create a memory leak.
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
>     SEVERE: The web application [/ZestYouth] appears to have started a thread named
> [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but
> has failed to stop it. This is very likely to create a memory leak.
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
>     SEVERE: The web application [/ZestYouth] appears to have started a thread named
> [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but
> has failed to stop it. This is very likely to create a memory leak.
>     May 30, 2014 10:56:13 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
>     SEVERE: The web application [/ZestYouth] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to
> stop it. This is very likely to create a memory leak.
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/core_rt is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/core is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt_rt is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/permittedTaglibs is already
> defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/scriptfree is already
> defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/sql_rt is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/sql is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/xml_rt is already defined
>     May 30, 2014 10:56:15 AM org.apache.catalina.startup.TaglibUriRule body
>     INFO: TLD skipped. URI: http://java.sun.com/jstl/xml is already defined
>     May 30, 2014 10:56:16 AM org.apache.catalina.core.StandardContext reload
>     INFO: Reloading Context with name [/ZestYouth] is completed

Answer 1

就他们自己而言，不，没关系。 Tomcat 只是告诉您 URI 已经在 Tomcat 实例中加载和定义。

但是，可能的内存泄漏可能会引起关注，因为它们告诉您线程已由您的程序启动，但在程序退出时并未停止。在将其投入生产之前，我会执行一些核心内存分析，以确保线程不会泄漏内存。

为了测试您的系统没有泄漏内存，请将您的 Tomcat 实例挂接到 VisualVM 并在启动时检查内存配置文件，然后用 1000 个用户、10000 个用户、100000 个用户敲击您的系统，直到它崩溃。然后启动它，运行一段时间，然后关闭它。使用 VisualVM 检查保持活动状态的线程。