You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent case in Spring Integration and scenarios as shown in #32109 suggest that we should revisit our default lifecycle phases: currently Integer.MAX_VALUE for ThreadPoolTaskScheduler which leads to it being in the first round of stopping, not giving other tasks room for a custom phase earlier than that without tweaking the scheduler's own phase definition. Also, the default timeout for a lifecycle phase is 30 seconds which seems long (in particular in common cloud deployment arrangements) if you may actually plan to run into this in certain scenarios.