springboot1.3升1.4启动报错

bing546874133 2017-07-12 05:52:41
2017-07-12 17:45:29.897 WARN 8140 --- [ restartedMain] o.m.s.mapper.ClassPathMapperScanner : No MyBatis mapper was found in '[com.bonc.micro.mapper]' package. Please check your configuration.
2017-07-12 17:45:29.902 INFO 8140 --- [ restartedMain] c.b.c.d.DynamicDataSourceRegister : Dynamic DataSource Registry
2017-07-12 17:45:30.082 ERROR 8140 --- [ restartedMain] o.s.boot.SpringApplication : Application startup failed

java.lang.NoClassDefFoundError: org/apache/ibatis/annotations/Mapper
at org.mybatis.spring.boot.autoconfigure.MybatisAutoConfiguration$AutoConfiguredMapperScannerRegistrar.registerBeanDefinitions(MybatisAutoConfiguration.java:175)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromRegistrars(ConfigurationClassBeanDefinitionReader.java:352)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:143)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:333)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:243)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273)
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:98)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:681)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:523)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:369)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:313)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1185)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1174)
at com.bonc.micro.MicroApplication.main(MicroApplication.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49)
Caused by: java.lang.ClassNotFoundException: org.apache.ibatis.annotations.Mapper
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 22 common frames omitted

2017-07-12 17:45:30.085 INFO 8140 --- [ restartedMain] ationConfigEmbeddedWebApplicationContext : Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@486739ab: startup date [Wed Jul 12 17:45:26 CST 2017]; root of context hierarchy
2017-07-12 17:45:30.087 WARN 8140 --- [ restartedMain] ationConfigEmbeddedWebApplicationContext : Exception thrown from LifecycleProcessor on context close

java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@486739ab: startup date [Wed Jul 12 17:45:26 CST 2017]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:416)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:997)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:956)
at org.springframework.boot.SpringApplication.handleRunFailure(SpringApplication.java:815)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:324)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1185)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1174)
at com.bonc.micro.MicroApplication.main(MicroApplication.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49)
...全文
240 3 打赏 收藏 转发到动态 举报
写回复
用AI写文章
3 条回复
切换为时间正序
请发表友善的回复…
发表回复
bing546874133 2017-07-12
  • 打赏
  • 举报
回复
2017-07-12 18:03:56.657 DEBUG 9708 --- [kground-preinit] o.h.v.i.e.r.DefaultTraversableResolver : Found javax.persistence.Persistence on classpath containing 'getPersistenceUtil'. Assuming JPA 2 environment. Trying to instantiate JPA aware TraversableResolver 2017-07-12 18:03:56.663 DEBUG 9708 --- [kground-preinit] o.h.v.i.e.r.DefaultTraversableResolver : Instantiated JPA aware TraversableResolver of type org.hibernate.validator.internal.engine.resolver.JPATraversableResolver. 2017-07-12 18:03:56.664 INFO 9708 --- [ restartedMain] ationConfigEmbeddedWebApplicationContext : Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@15a05afb: startup date [Wed Jul 12 18:03:56 CST 2017]; root of context hierarchy 2017-07-12 18:03:59.632 WARN 9708 --- [ restartedMain] o.m.s.mapper.ClassPathMapperScanner : No MyBatis mapper was found in '[com.bonc.micro.mapper.framework]' package. Please check your configuration. 2017-07-12 18:03:59.638 INFO 9708 --- [ restartedMain] c.b.c.d.DynamicDataSourceRegister : Dynamic DataSource Registry 2017-07-12 18:03:59.838 ERROR 9708 --- [ restartedMain] o.s.boot.SpringApplication : Application startup failed
bing546874133 2017-07-12
  • 打赏
  • 举报
回复
<?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE configuration PUBLIC "-//mybatis.org//DTD Config 3.0//EN" "http://mybatis.org/dtd/mybatis-3-config.dtd"> <configuration> <!--配置数据库用户 --> <properties resource="db.properties" /> <settings> <!-- mybatis map空处理为null --> <setting value="true" name="callSettersOnNulls"/> <!--日志 --> <setting name="logPrefix" value="mapper." /> </settings> <!--mapper映射 --> <mappers> <mapper resource="mybatisMapper/example/KpiCodeExtendTableMapper.xml"/> </mappers> </configuration>
bing546874133 2017-07-12
  • 打赏
  • 举报
回复
spring-boot-starter-parent 1.3.3升到1.4.7 mybatis-spring-boot-starter 1.0.0升级到1.1.1就报错了
代码下载链接: https://pan.quark.cn/s/a4b39357ea24 QNAP 301w 免拆刷机方法 特别感谢 @coolsnowwolf @asushugo 等一众牛B的开发者适配301w路由器! QNAP QHora-301W 产品介绍 当前促销:https://www.materiel.net/produit/202011090007.html?offerId=AR202011090007 一. 开启SSH服务 在开启路由器可以正常进系统的状态下,长按路由器后的 WPS 键,直到听到第二声“嘟”松开(大约 12 秒)就 OK。 -- 二. SSH连接路由器后台 这里需要注意一点 路由器默认开启的SSH的端口号是 22200 用户名是,密码是路由器网页登录密码 ssh命令就是 ( 如果端口没开重复步骤1 ) 或者使用putty连接 putty -- 三. 将启动分区切换到第二分区 提示要输入的密码就是刚刚你登录 ssh 的密码,以下不再赘述 重启 -- 四. 检查路由器当前启动分区 查看分区,确保这里会输出 1,如果不是,重复步骤 三。 -- 五. 使用 Winscp 上传QSDK的 kernel.bin 和 rootfs.bin 到 /tmp (! 别问我固件从哪儿拿) -- 六. 将QSDK到dd刷入第一分区 注意:强烈建议使用dd命令(方法自行搜索引擎)备份一些重要的分区例如mtd闪存分区以及mmc闪存分区,以便以后可以恢复官方固件 截图参考: putty 执行完上述命令之后即可刷入QSDK并从第一分区启动QSDK,注意由于目前还没有刷10G PHY的firmware,需刷入firmware。 -- 七. 刷入 10G PHY 的 fi...
内容概要:本文提出了一种基于WMSST(加权多尺度奇异值变换)结合MCNN-GRU的深度学习模型,用于网络故障诊断。该方法首先利用WMSST对原始信号进行多尺度特征提取与去噪处理,增强故障特征的可辨识性;随后构建多尺度卷积神经网络(MCNN)以捕获局部时域特征,并通过门控循环单元(GRU)捕捉时间序列中的长期依赖关系,从而实现对复杂网络故障的高效、准确识别。整个模型充分发挥了卷积网络在特征提取和循环网络在时序建模方面的优势,结合信号预处理技术提了诊断精度与鲁棒性,适用于非平稳、强噪声环境下的故障检测场景。; 适合人群:具备一定信号处理、机器学习或深度学习基础,从事电气工程、自动化、通信网络或故障诊断相关研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①解决传统故障诊断方法在复杂噪声环境下特征提取困难的问题;②提网络系统(如电力通信网、工业控制网等)中故障识别的准确性与时效性;③为智能运维与预测性维护提供技术支持。; 阅读建议:建议读者结合Matlab代码实现部分,深入理解WMSST的信号处理流程与MCNN-GRU网络架构的设计细节,重点关注数据预处理、模型训练及分类结果可视化等环节,以便在实际项目中进行迁移与优化应用。

87,993

社区成员

发帖
与我相关
我的任务
社区描述
Web 开发 JavaScript
社区管理员
  • JavaScript
  • 无·法
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

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