Bill Chen opened SPR-15468 and commented

Currently, Lifecycle.stop() is documented not to be called if refresh failed. However, this makes lifecycle process really asymmetrical (especially when refresh failed due to an exception thrown from Lifecycle.start()).

Can an option be added to call Lifecycle.stop() on already started beans?


No further details from SPR-15468