CAS 6.1.6 and taskExecutor not found

20 views
Skip to first unread message

Matthieu Marc

unread,
May 5, 2020, 2:19:57 AM5/5/20
to CAS Community
Hello,

I am running CAS 6.1.6 (https://gitlab.ensam.eu/auth/cas-server.git branch 6.1) from gradle overlays with those dependencies :

dependencies {
    compile "org.apereo.cas:cas-server-webapp-tomcat:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-ldap:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-json-service-registry:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-memcached-ticket-registry:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-memcached-spy:${project.'cas.version'}"
    compile "org.apereo.cas:cas-server-support-audit-jdbc:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-jdbc-drivers:${casServerVersion}"
    compile "org.apereo.cas:cas-server-support-person-directory:${casServerVersion}"
    compile "org.apereo.cas:cas-server-core-events-configuration:${casServerVersion}"
}

I put my configuration in /etc/cas/config as expected, with all log4j level to debug.

I build the archive and run it : java -jar build/libs/cas.war

Just after the "READY" message, I got this error :

2020-05-04 16:10:44,499 INFO [org.apereo.cas.web.CasWebApplication] - <Ready to process requests @ [2020-05-04T16:10:44.498Z]>
2020-05-04 16:10:44,502 DEBUG [org.springframework.scheduling.annotation.AnnotationAsyncExecutionInterceptor] - <Could not find unique TaskExecutor bean>
org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type 'org.springframework.core.task.TaskExecutor' available: expected single matching bean but found 2: applicationTaskExecutor,taskScheduler
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveNamedBean(DefaultListableBeanFactory.java:1180) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveBean(DefaultListableBeanFactory.java:416) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:349) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBean(DefaultListableBeanFactory.java:342) ~[spring-beans-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.getDefaultExecutor(AsyncExecutionAspectSupport.java:233) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.interceptor.AsyncExecutionInterceptor.getDefaultExecutor(AsyncExecutionInterceptor.java:157) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.lambda$configure$2(AsyncExecutionAspectSupport.java:119) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.util.function.SingletonSupplier.get(SingletonSupplier.java:100) ~[spring-core-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.determineAsyncExecutor(AsyncExecutionAspectSupport.java:172) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.interceptor.AsyncExecutionInterceptor.invoke(AsyncExecutionInterceptor.java:107) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:747) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:689) ~[spring-aop-5.2.0.RELEASE.jar!/:5.2.0.RELEASE]
    at org.apereo.cas.config.CasCoreServicesConfiguration$$EnhancerBySpringCGLIB$$e6407d0b.refreshServicesManagerWhenReady(<generated>) ~[cas-server-core-services-6.1.6.jar!/:6.1.6]

I don't know what to do to resolve this problem. I don't know if it is really a problem, but since I ran 6.1 version, when modifying configuration in applications.properties, the configuration is not reloaded automaticaly (it does so on my 5.2.9 version).
Reply all
Reply to author
Forward
0 new messages