[SPR-10492] Async does not work anymore when switching from 3.2 to 3.2.2 Created: 25/Apr/13  Updated: 15/Jan/19  Resolved: 24/Jul/13

Status: Closed
Project: Spring Framework
Component/s: Core
Affects Version/s: 3.2.2
Fix Version/s: 3.2.4, 4.0 M2

Type: Bug Priority: Minor
Reporter: Janning Vygen Assignee: Juergen Hoeller
Resolution: Complete Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
is related to SPR-10715 method demarcated with @Async isn't e... Closed
Days since last comment: 1 year, 18 weeks, 6 days ago
Last commented by a User: true
Last updater: Spring Issuemaster

 Description   
java.lang.IllegalStateException: No executor qualifier specified and no default executor set on AnnotationAsyncExecutionAspect either
	at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.determineAsyncExecutor(AsyncExecutionAspectSupport.java:104)
	at org.springframework.scheduling.aspectj.AbstractAsyncExecutionAspect.ajc$around$org_springframework_scheduling_aspectj_AbstractAsyncExecutionAspect$1$6c004c3e(AbstractAsyncExecutionAspect.aj:60)
...


 Comments   
Comment by Stefan Haberl [ 24/May/13 ]

Still unresolved in release 3.2.3 ...

Comment by Arjan van B. [ 10/Jul/13 ]

In case it helps: this still worked in 3.2.1 (for me; using compile time weaving and including spring-aspects for that), but indeed not in 3.2.3.

Comment by Juergen Hoeller [ 24/Jul/13 ]

I've moved that executor null check to our proxy-based AsyncExecutionInterceptor now where we do want a strict check, allowing the AspectJ AbstractAsyncExecutionAspect to fall back to sync execution (as in 3.2.1).

Juergen

Comment by Spring Issuemaster [ 14/Jan/19 ]

The Spring Framework has migrated to GitHub Issues. This issue corresponds to spring-projects/spring-framework#15125.

Generated at Mon May 25 02:21:10 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.