You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
f17f1255a4
Previously, an AvailabilityChangeEvent was published when the servlet and reactive web server application contexts were closed, irrespective of whether or not the context was active. This caused problems when the context was not active due to a refresh failure as the event publication could then trigger bean creation and post-processing that relied upon beans that had been destroyed when cleaning up after the refresh failure. The most commonly seen symptom was a missing importRegistry bean that is required by ImportAwareBeanPostProcessor. This commit updates the two web server application contexts to only publish the availability change event if the context is active. Fixes gh-21588 |
5 years ago | |
---|---|---|
.. | ||
spring-boot | 5 years ago | |
spring-boot-actuator | 5 years ago | |
spring-boot-actuator-autoconfigure | 5 years ago | |
spring-boot-autoconfigure | 5 years ago | |
spring-boot-cli | 5 years ago | |
spring-boot-dependencies | 5 years ago | |
spring-boot-devtools | 5 years ago | |
spring-boot-docs | 5 years ago | |
spring-boot-parent | 5 years ago | |
spring-boot-properties-migrator | 5 years ago | |
spring-boot-starters | 5 years ago | |
spring-boot-test | 5 years ago | |
spring-boot-test-autoconfigure | 5 years ago | |
spring-boot-tools | 5 years ago |