老哥们,萌新启动项目时,出现这个错误,求大佬们支援

qq_38025086 2017-12-09 09:21:35
09-Dec-2017 09:13:17.956 INFO [RMI TCP Connection(5)-127.0.0.1] org.apache.jasper.servlet.TldScanner.scanJars 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.
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:18.159,listener.PluginContextListener.parsePluginFolder:79 - Plugins: looking in: C:\legendshop\legendshop_sources\app\legendshop_app\target\legendshop_app-0.0.2-SNAPSHOT\WEB-INF\plugins
Sat Dec 09 09:13:19 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:19 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:22 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:22 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:22 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:22 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
Sat Dec 09 09:13:22 CST 2017 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.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.
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:22.363,pool.DruidDataSource.init:715 - {dataSource-1} inited
2017-12-09 09:13:23.113 INFO net.spy.memcached.MemcachedConnection: Added {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0} to connect queue
2017-12-09 09:13:24.129 INFO net.spy.memcached.MemcachedConnection: Reconnecting due to failure to connect to {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:677)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:436)
at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:1446)
2017-12-09 09:13:24.129 WARN net.spy.memcached.MemcachedConnection: Closing, and reopening {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}, attempt 1.
09-Dec-2017 09:13:26.311 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\tomcat\apache-tomcat-8.0.37\webapps\manager
09-Dec-2017 09:13:26.373 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\tomcat\apache-tomcat-8.0.37\webapps\manager has finished in 62 ms
WARN,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:26.645,dao.EntityFactoryImpl.registerEntityOperation:87 - className com.legendshop.model.entity.integral.IntegralProd has exists in entityMap
WARN,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:26.676,dao.EntityFactoryImpl.registerEntityOperation:87 - className com.legendshop.model.entity.integral.IntegralOrder has exists in entityMap
WARN,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:26.692,dao.EntityFactoryImpl.registerEntityOperation:87 - className com.legendshop.model.entity.integral.IntegralOrderItem has exists in entityMap
2017-12-09 09:13:28.145 INFO net.spy.memcached.MemcachedConnection: Reconnecting {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
2017-12-09 09:13:29.160 INFO net.spy.memcached.MemcachedConnection: Reconnecting due to failure to connect to {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:677)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:436)
at net.spy.memcached.MemcachedConnection.run(MemcachedConnection.java:1446)
2017-12-09 09:13:29.160 WARN net.spy.memcached.MemcachedConnection: Closing, and reopening {QA sa=/127.0.0.1:11211, #Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}, attempt 2.
WARN,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:29.707,dao.EntityFactoryImpl.registerEntityOperation:87 - className com.legendshop.model.entity.Headline has exists in entityMap
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:30.714,listener.InitSysListener.contextInitialized:72 - ********* Initializing LegendShop System now *************
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:30.730,sql.ConfigCode._$1:? - The current version of DAL is : 2012-04-26.
2017-12-09 09:13:31.152 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for SystemConfigcom.legendshop.business.dao.impl.SystemConfigDaoImplgetSystemConfig.
09-Dec-2017 09:13:32.161 SEVERE [RMI TCP Connection(5)-127.0.0.1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
09-Dec-2017 09:13:32.161 SEVERE [RMI TCP Connection(5)-127.0.0.1] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:32.176,impl.SysDestoryProcessor.process:38 - ********* system destory *************
2017-12-09 09:13:32.192 INFO net.spy.memcached.MemcachedConnection: Shut down memcached client
INFO,RMI TCP Connection(5)-127.0.0.1,12-09 09:13:32.207,pool.DruidDataSource.close:1444 - {dataSource-1} closed
09-Dec-2017 09:13:32.223 WARNING [RMI TCP Connection(5)-127.0.0.1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] 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.
09-Dec-2017 09:13:32.223 WARNING [RMI TCP Connection(5)-127.0.0.1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] 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.
[2017-12-09 09:13:32,239] Artifact legendshop_app:war exploded: Error during artifact deployment. See server log for details.
...全文
732 3 打赏 收藏 转发到动态 举报
AI 作业
写回复
用AI写文章
3 条回复
切换为时间正序
请发表友善的回复…
发表回复
YuanTous 2017-12-28
  • 打赏
  • 举报
回复
大喊一句,握草
wuzhou2222 2017-12-25
  • 打赏
  • 举报
回复
复制感觉还不如截一下图,复制的感觉好乱不知道从哪里看起
qq_38025086 2017-12-09
  • 打赏
  • 举报
回复
我把项目连接到服务器上的memcached也不行,不知这是什么原因?求大神解答啊
内容概要:本文详细介绍了一个基于C++语言开发的疫苗接种和儿童体检系统的设计与实现全过程,涵盖项目背景、目标意义、架构设计、核心功能模块、数据库实现、API接口规范、前后端代码实现及部署应用等多个方面。系统采用分层架构与模块化设计,实现了儿童信息管理、疫苗接种记录、体检数据录入、多用户权限控制、数据统计分析、异常预警、安全加密与日志审计等核心功能,并通过MySQL数据库进行数据持久化,结合Qt实现图形化界面,支持高并发、数据脱敏、多平台对接与自动化部署。项目强调数据安全、隐私保护与系统可扩展性,适用于社区医疗、疾控中心、学校及医院等场景。; 适合人群:具备C++编程基础,熟悉数据库操作和基本软件工程流程的开发人员、计算机及相关专业学生、医疗信息化项目开发者,以及希望了解完整医疗管理系统开发流程的技术人员。; 使用场景及目标:①学习如何使用C++构建完整的医疗信息管理系统;②掌握数据库设计、前后端交互、权限控制、多线程处理和GUI开发等关键技术;③应用于社区卫生服务、学校健康管理、疾控数据统计等实际业务场景,提升儿童健康管理水平;④作为课程设计、毕业设计或实际项目的参考模板。; 阅读建议:建议读者结合文档中的代码示例与数据库脚本,搭建本地开发环境进行实践操作,重点关注系统架构设计、模块解耦、安全机制与前后端交互逻辑,深入理解各功能模块的实现原理,并尝试在此基础上进行功能扩展,如接入移动端或增加AI分析模块。

25,980

社区成员

发帖
与我相关
我的任务
社区描述
高性能WEB开发
社区管理员
  • 高性能WEB开发社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧