tomcat项目部署在linux下404

家超 发布于 2016/02/18 16:22
阅读 4K+
收藏 0

项目打成war包在windows下的tomcat运行正常,在linux下的tomcat就运行失败,tomcat主页显示正常但是自己部署的项目没有启动:如图

tomcat日志:

Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version:        Apache Tomcat/7.0.68
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built:          Feb 8 2016 20:25:54 UTC
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number:         7.0.68.0
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name:               Linux
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version:            2.6.18-274.el5
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture:          amd64
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home:             /usr/java/jdk7/jre
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version:           1.7.0_71-b14
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor:            Oracle Corporation
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE:         /usr/java/tomcat7
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME:         /usr/java/tomcat7
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.config.file=/usr/java/tomcat7/conf/logging.properties
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=/usr/java/tomcat7/endorsed
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=/usr/java/tomcat7
Feb 18, 2016 3:58:39 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=/usr/java/tomcat7
Feb 18, 2016 3:58:40 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.io.tmpdir=/usr/java/tomcat7/temp
Feb 18, 2016 3:58:40 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Feb 18, 2016 3:58:40 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-80"]
Feb 18, 2016 3:58:40 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Feb 18, 2016 3:58:40 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 651 ms
Feb 18, 2016 3:58:40 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Feb 18, 2016 3:58:40 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.68
Feb 18, 2016 3:58:40 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /usr/java/tomcat7/webapps/duoya.war
Feb 18, 2016 3:58:40 PM org.apache.catalina.deploy.WebXml setVersion
WARNING: Unknown version string [3.1]. Default version will be used.
Feb 18, 2016 3:58:42 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Feb 18, 2016 3:58:48 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file
Feb 18, 2016 3:58:48 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/duoya] startup failed due to previous errors
Feb 18, 2016 3:58:48 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc
SEVERE: The web application [/duoya] registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Feb 18, 2016 3:58:48 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc
SEVERE: The web application [/duoya] 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.
Feb 18, 2016 3:58:48 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/duoya] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.


加载中
0
lovecws
lovecws
SEVERE: The web application [/duoya] registered the JDBC driver [com.alibaba.druid.proxy.DruidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
家超
家超
?
0
KylinSun
KylinSun
http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-jdbc-driver-has-been-forcibly-unregistered
0
lovecws
lovecws
这里报错啦 说是jdbc建立太多链接
0
家超
家超
解决了的,是阿里云服务器项目要授权777权限,修改了就好了
返回顶部
顶部