Tomcat 7.0.42错误listenerStart

Question

我在tomcat(jdk 7)上部署我的war文件,并且看到了以下错误.我不确定导致这个问题的原因.

INFO: OpenSSL successfully initialized (OpenSSL 1.0.1d 5 Feb 2013)
Feb 27, 2014 11:02:50 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-8081"]
Feb 27, 2014 11:02:50 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-apr-8009"]
Feb 27, 2014 11:02:50 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1588 ms
Feb 27, 2014 11:02:50 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Feb 27, 2014 11:02:50 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.42
Feb 27, 2014 11:02:50 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive D:\Dev\tools\apache-tomcat-7.0.42\webapp
s\CollaborationPortal.war
Feb 27, 2014 11:03:09 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/core is already defined
Feb 27, 2014 11:03:09 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/fmt is already defined
Feb 27, 2014 11:03:09 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Feb 27, 2014 11:03:09 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/CollaborationPortal] startup failed due to previous errors
Feb 27, 2014 11:03:09 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8081"]
Feb 27, 2014 11:03:09 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
Feb 27, 2014 11:03:09 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 18890 ms

Answer 1

您可以通过添加到war存档来重新配置java.utils.logging/WEB-INF/classes/logging.properties:

org.apache.catalina.core.ContainerBase.[Catalina].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers = java.util.logging.ConsoleHandler

然后应该可以看到实际的错误消息.此外,如果已配置其他日志记录框架(例如,log4j),请检查应用程序日志.