| 主题 : 阿里云ECS Ubuntu 16.04 安装jeecms 显示安装成功但是运行页面不展示 |
级别: 举人
 |
42# 发表于:2018-09-11 15:27:56 IP:115.56.*.*
|
||
|---|---|---|---|
级别: 举人
|
44# 发表于:2018-09-11 15:54:48 IP:115.56.*.*
5.7 的 下面是 所有的日志
Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Server version: Apache Tomcat/7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Server built: Jul 2 2018 17:05:37 UTC Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Server number: 7.0.90.0 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: OS Name: Linux Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: OS Version: 4.4.0-117-generic Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Architecture: amd64 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Java Home: /web/bin/jdk1.8.0/jre Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: JVM Version: 1.8.0_77-b03 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: JVM Vendor: Oracle Corporation Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: CATALINA_BASE: /usr/local/tomcat/apache-tomcat-7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: CATALINA_HOME: /usr/local/tomcat/apache-tomcat-7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Djava.util.logging.config.file=/usr/local/tomcat/apache-tomcat-7.0.90/conf/logging.properties Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Djdk.tls.ephemeralDHKeySize=2048 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Dignore.endorsed.dirs= Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Dcatalina.base=/usr/local/tomcat/apache-tomcat-7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Dcatalina.home=/usr/local/tomcat/apache-tomcat-7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.VersionLoggerListener log INFO: Command line argument: -Djava.io.tmpdir=/usr/local/tomcat/apache-tomcat-7.0.90/temp Sep 11, 2018 3:52:07 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 Sep 11, 2018 3:52:07 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler ["http-bio-8080"] Sep 11, 2018 3:52:07 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler ["ajp-bio-8009"] Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 804 ms Sep 11, 2018 3:52:07 PM org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina Sep 11, 2018 3:52:07 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.90 Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/host-manager Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/host-manager has finished in 497 ms Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/ROOTBAK Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/ROOTBAK has finished in 57 ms Sep 11, 2018 3:52:07 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/manager Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/manager has finished in 90 ms Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/docs Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/docs has finished in 75 ms Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/examples Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/examples has finished in 217 ms Sep 11, 2018 3:52:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/ROOT Sep 11, 2018 3:52:13 PM org.apache.catalina.startup.TaglibUriRule body INFO: TLD skipped. URI: http://www.springframework.org/tags is already defined Sep 11, 2018 3:52:13 PM org.apache.catalina.startup.TaglibUriRule body INFO: TLD skipped. URI: http://www.springframework.org/tags/form is already defined Sep 11, 2018 3:52:13 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. log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Tue Sep 11 15:52:18 CST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL *.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Sep 11, 2018 3:52:23 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 Sep 11, 2018 3:52:23 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [] startup failed due to previous errors Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc SEVERE: The web application [] 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. Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->1brb1ai9x1jdwy4k6bl2yf|1678904f]-AdminTaskTimer] but has failed to stop it. This is very likely to create a memory leak. Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->1brb1ai9x1jdwy4k6bl2yf|1678904f]-HelperThread-#0] but has failed to stop it. This is very likely to create a memory leak. Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->1brb1ai9x1jdwy4k6bl2yf|1678904f]-HelperThread-#1] but has failed to stop it. This is very likely to create a memory leak. Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->1brb1ai9x1jdwy4k6bl2yf|1678904f]-HelperThread-#2] but has failed to stop it. This is very likely to create a memory leak. Sep 11, 2018 3:52:23 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads SEVERE: The web application [] 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. Sep 11, 2018 3:52:23 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deployment of web application directory /usr/local/tomcat/apache-tomcat-7.0.90/webapps/ROOT has finished in 14,904 ms Sep 11, 2018 3:52:23 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-bio-8080"] Sep 11, 2018 3:52:23 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["ajp-bio-8009"] Sep 11, 2018 3:52:23 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 15917 ms Sep 11, 2018 3:52:28 PM org.apache.catalina.loader.WebappClassLoaderBase findResourceInternal INFO: Illegal access: this web application instance has been stopped already. Could not load . The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. |
||
|---|---|---|---|
级别: 总版主
 |
45# 发表于:2018-09-11 16:12:30 IP:117.140.*.*
服务器的jdk版本和和Tomcat版本用和你本地一样的版本号 |
||
|---|---|---|---|
回复第46楼
级别: 举人
|
48# 发表于:2018-09-13 18:33:12 IP:115.61.*.*
是我配置错了 以为直接把 上传的目录必须得配置到 远程目录， 但是根目录权限不够，
现在又出了另外一个问题，上传的文件都是0kb |
||
|---|---|---|---|