[org.springframework.web.context.support.XmlWebApplicationContext] Exception thr
2018-03-02 12:20:24 [WARN]-[org.springframework.web.context.support.XmlWebApplicationContext] Exception thrown from ApplicationListener handling ContextClosedEvent
java.lang.IllegalStateException: ApplicationEventMulticaster not initialized - call 'refresh' before multicasting events via the context: Root WebApplicationContext: startup date [Fri Mar 02 12:20:23 CST 2018]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:347)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1049)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:1010)
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:549)
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:143)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5157)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5830)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1694)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1684)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2018-03-02 12:20:24 [WARN]-[org.springframework.web.context.support.XmlWebApplicationContext] Exception thrown from LifecycleProcessor on context close
java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: Root WebApplicationContext: startup date [Fri Mar 02 12:20:23 CST 2018]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:360)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1057)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:1010)
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:549)
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:143)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5157)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5830)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1694)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1684)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2018-03-02 12:20:24 [INFO]-[org.springframework.beans.factory.support.DefaultListableBeanFactory] Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@4ce27a4d: defining beans [activityController,dangfeiController,partyBranchActivityController,publicController,td_newsTypeControll,td_tbexamlistController,td_tblPartyOrgBranchControll,TD_tblPartyOrgMembersController,td_tbquestionbankController,td_teamControll,WXController,dangfeiDAOImpl,partyBranchActivityAttendDaoImpl,partyBranchActivityDaoImpl,partyMemberCostlogDaoImpl,partyMemberCostSetDaoImpl,partyOrgMembersDaoImpl,webchatMenuDaoImpl,webchatRoleDaoImpl,webchatRolePrivilageDaoImpl,webchatUserRoleDaoImpl,dangfeiJob,activityService,dangfeiServiceImpl,dangyuanServiceImpl,td_newsTypeServiceImple,td_tblPartyOrgBranchServiceImple,TD_tblPartyOrgMembersServiceImple,td_teamServiceImple,customCredentialsMatcher,myAuthorizingRealm,weiXinService,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,org.springframework.context.annotation.internalAsyncAnnotationProcessor,org.springframework.context.annotation.internalScheduledAnnotationProcessor,org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,dataSource,sessionFactory,transactionManager,txAdvice,org.springframework.aop.config.internalAutoProxyCreator,mypointcut,org.springframework.aop.support.DefaultBeanFactoryPointcutAdvisor#0,td_teamDaoInter,td_newsTypeDaoInter,td_tblPartyOrgBranchDaoInter,tD_tblPartyOrgMembersDaoInter,tD_tblPartyOrgMembersServiceInter,formAuthenticationFilter,shiroFilterChainDefinitions,shiroFilter,securityManager,lifecycleBeanPostProcessor,serviceAuthorizationAttributeSourceAdvisor,weiXinTool,td_tbexamlistDaoInter,td_tbexamlistServiceInter,td_tbexamscoreDaoInter,td_tbexamscoreServiceInter,td_tbquestionbankDaoInter,td_tbquestionbankServiceInter,org.springframework.context.annotation.ConfigurationClassPostProcessor.importAwareProcessor]; root of factory hierarchy
怎么看哪个文件配错了?难道只能一个一个文件找?
相关推荐
化工行业可信数据空间应用规划方案(生态合作版).pptx
化工行业可信数据空间应用规划方案(生态合作版).pptx
强度和硬度对照表金属强度和硬度对照表
强度和硬度对照表金属强度和硬度对照表
汽车制造行业可信数据空间应用规划方案(决策评审版).pptx
汽车制造行业可信数据空间应用规划方案(决策评审版).pptx
Java编程hash算法性能优化示例3
内容概要:本文介绍了Java中hash算法性能优化的关键方法,重点在于优化hashCode()的实现与调用路径,而非修改HashMap本身。主要包括两个方面的优化策略:一是通过预设HashMap初始容量来减少扩容导致的rehash开销,二是针对长字符串或大文本作为Key时,避免重复拼接和重复哈希计算带来的性能损耗。文中提供了具体的代码示例,如根据预期元素数量计算初始容量、使用自定义Key类缓存哈希值以及提前构造并复用组合字符串等实用技巧。; 适合人群:具备一定Java编程基础,对集合类性能优化感兴趣的研发人员,尤其是工作1-3年希望提升代码效率的开发者。; 使用场景及目标:①在高频操作中减少HashMap扩容带来的性能抖动;②优化复杂Key的生成与哈希计算过程,提升查找效率;③应用于大数据量下的缓存、索引、去重等场景,提高系统响应速度。; 阅读建议:此资源侧重于实际编码层面的性能调优,建议结合JVM内存模型和HashMap底层机制一起理解,并在实际项目中针对热点代码进行类似优化时参考应用。
含分布式电源的配电网可靠性评估研究(Matlab代码实现)
内容概要:本文围绕含分布式电源的配电网可靠性评估展开研究,利用Matlab代码实现相应的评估模型与算法。通过序贯蒙特卡洛模拟法等先进仿真技术,对分布式电源接入后配电网的运行可靠性进行系统性量化分析,重点涵盖系统故障概率、负荷点停电频率、停电持续时间、供电可用率等关键可靠性指标的计算与评估。研究深入探讨了不同类型、容量和接入位置的分布式电源对配电网可靠性的影响机制,旨在科学评估其在提升供电连续性和系统韧性方面的积极作用,为现代智能配电网的规划、运行优化及可靠性提升提供坚实的理论依据和技术支撑。; 适合人群:具备电力系统分析、概率统计及可靠性工程等基础知识,熟练掌握Matlab编程语言,从事电力系统规划、运行维护、可靠性研究或相关领域的研究生、科研人员及工程技术人员。; 使用场景及目标:①作为高校和科研院所开展智能配电网、分布式能源并网影响等课题研究的核心参考资料;②应用于电网公司对现有配电网进行可靠性评估、薄弱环节诊断及升级改造方案的制定;③作为电力系统专业高年级本科生或研究生的教学案例,帮助学生深入理解配电网可靠性评估的理论体系、建模方法与仿真技术。; 阅读建议:建议读者结合Matlab代码与文中详尽的理论分析进行同步学习,亲自动手调试和运行代码以深刻理解序贯蒙特卡洛模拟的算法流程和实现细节,同时鼓励在不同拓扑结构的标准测试系统(如IEEE RBTS Bus6)或自定义网络中进行仿真实验,通过对比分析探究影响可靠性的关键因素,从而达到融会贯通的学习效果。


