Configuration problem: Only one AsyncAnnotationBeanPostProcessor may exist within the context.

去配置文件中找 , 某个配置文件被引用了两次以上.移除后保留一个即可.如下即可产生上述问题

     <import resource="classpath:testContext-currentproduct.xml" />
     <import resource="classpath:testContext-currentproduct.xml" />
     <import resource="classpath:testContext-elitecurrentproduct.xml" />
时间： 2024-10-06 11:29:09

Configuration problem: Only one AsyncAnnotationBeanPostProcessor may exist within the context.的相关文章

Only one AsyncAnnotationBeanPostProcessor may exist within the context.

4down vote I had this problem when I copied applicationContext.xml and created new one called applicationContextAdditional.xml. I didn't try to find the reason, but both contained namespace <bean ... xmlns:task="http://www.springframework.org/sche

springsecurity启动出现org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: You must use a 3.0 schema with Spring Security 3.0.

在换了spring-security的jar包以后启动出现org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: You must use a 3.0 schema with Spring Security 3.0.Please update your schema declarations to the 3.0.3 schema (spring-securi

开机报错 windows could not start because of a computer disk hardware configuration problem

近日,遇到一台hp商务机在更换硬盘之后,出现开机时不能正常进入系统和安装操作系统,并在自检过后提示: windows could not start because of a computer disk hardware configuration problem. could not read from the selected boot disk. check boot path and disk hardware. olease check the windows documentatio

Configuration problem: Failed to import bean definitions from relative location

问题现象: 最近开始做新需求,然后在Tomcat上部署项目时,出现了如下报错: [12-05 09:54:27,161 ERROR] ContextLoader.java:351 - Context initialization failedorg.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definition

org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unexpected failure during bean definition parsing Offending resource: class path resource [applicationC

这个错误是 org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unexpected failure during bean definition parsing Offending resource: class path resource [applicationContext.xml] Bean 'stu'; nested exception is

Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace 解决方法

这个问题是在用到spring时,本地IDE里面跑的很正常,但是打包后在集群上运行时报错. 多方查找资料后确定了问题的根源,由于在依赖中调用了spring的许多包,会存在文件覆盖的情况. 具体是 这三个文件.查看后,只剩下tx的配置了. 解决方法 第一种方法是使用maven的打包插件,在里面保留各个spring包的配置信息: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>mav

Description Resource Path Location Type Dynamic Web Module 3.1 requires Java 1.7 or newer. Ascend line 1 Maven Java EE Configuration Problem

pom.xml build中加入 <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.7</source> <target>1.7&

Description Resource Path Location Type web.xml is missing and &lt;failOnMissingWebXml&gt; is set to true pom.xml /Ascend line 7 Maven Java EE Configuration Problem

pom.xml build 中加入 <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.6</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXm

Maven Java EE Configuration Problem问题

问题:Cannot change version of project facet Dynamic Web Module to 2.4. 解决方案: 找到该项目目录.settings下的文件org.eclipse.wst.common.project.facet.core.xml进行修改! 例:E:\workerspace\main\lics\.settings\org.eclipse.wst.common.project.facet.core.xml 把 <installed facet=&quo