ScheduledAnnotationBeanPostProcessor should unregister tasks on destruction of individual beans [SPR-12216]

[spring-projects-issues]

Juergen Hoeller opened SPR-12216 and commented

At this point, ScheduledAnnotationBeanPostProcessor cancels all tasks on shutdown of the entire application context. While this is generally fine for the typical singleton bean case, @Scheduled may also be placed on non-singleton beans which we should track for individual unregistration on destruction of each such individual bean.

This is a follow-up to #16803.

---

Issue Links:

• Scheduled/JmsListenerAnnotationBeanPostProcessor needlessly scans every scoped instance [SPR-12189] #16803 Scheduled/JmsListenerAnnotationBeanPostProcessor needlessly scans every scoped instance
• Scheduled tasks aren't cancelled on ScheduledTaskRegistrar destruction anymore [SPR-14286] #18858 Scheduled tasks aren't cancelled on ScheduledTaskRegistrar destruction anymore
• Performance regression when scheduling is enabled and context contains URL beans [SPR-14666] #19230 Performance regression when scheduling is enabled and context contains URL beans
• Improve reference documentation for Task Execution and Scheduling about bean scopes [SPR-14167] #18739 Improve reference documentation for Task Execution and Scheduling about bean scopes
• @Scheduled methods in @Lazy beans are not scheduled [SPR-12872] #17470 @Scheduled methods in @Lazy beans are not scheduled

Referenced from: commits ab478d1

[spring-projects-issues]

Juergen Hoeller commented

As of 4.3 RC2, ScheduledAnnotationBeanPostProcessor features a revised registration mechanism capable of tracking individual bean instances, both on creation for beans of any scope and on destruction of each individual bean. In other words, @Scheduled works on any Spring-managed bean now, not just on non-lazy singleton beans anymore.