Abhik Setia opened SPR-15671 and commented
ava.lang.NoSuchMethodError: org.springframework.scheduling.aspectj.AbstractAsyncExecutionAspect.ajc$around$org_springframework_scheduling_aspectj_AbstractAsyncExecutionAspect$1$6c004c3e(Lorg/aspectj/runtime/internal/AroundClosure;Lorg/aspectj/lang/JoinPoint$StaticPart;Lorg/aspectj/lang/JoinPoint;)Ljava/lang/Object;
I was running version 4.0.x and it was running fine ,after updating it to 4.3.x it caused this error.
Affects: 4.3.9
Comment From: spring-projects-issues
Juergen Hoeller commented
Is this happening on invocation of your @Async-annotated methods? Have you recompiled your classes accordingly, picking up spring-aspects-4.3.x against AspectJ 1.8.x? This looks like old pre-compiled code running against a new version of the aspect, so recompilation should fix it.
Comment From: spring-projects-issues
Abhik Setia commented
AspectJTrails=1.8; AspectJTools=1.8; SpringAspects=4.3.x;
These are the dependencies which are in my versionSet. Code was re-compiled and is compatible with latest version. But yes, this is happening at the invocation of Async annotation and it was running without any problem with SpringAspects=4.0.x,
Comment From: spring-projects-issues
Juergen Hoeller commented
Such a NoSuchMethodError indicates a mismatch between the aspect version used at compilation and the one used at runtime, since it does work for us in our integration tests where the versions are strictly the same. Are there possibly some old Spring jars on either your compilation or your runtime classpath, maybe brought in transitively by some other Maven dependencies?
Comment From: spring-projects-issues
Abhik Setia commented
Yes , you are right. The main problem is because of mismatch between the aspect versions but all latest versions are being used at build,compile and run time. Only these dependencies which i sent to you are there in my versionset . No other old spring jars are present.
But how is that possible that 4.0.x is still working fine.
Comment From: snicoll
I think this issue has run its course now. I hope you found out what the problem.