Skip to content

WebServers are not destroyed on application failure in ReactiveWebServerApplicationContext #44101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
boolivar opened this issue Feb 4, 2025 · 1 comment
Labels
status: superseded An issue that has been superseded by another type: bug A general bug

Comments

@boolivar
Copy link

boolivar commented Feb 4, 2025

With #34955 feature (spring-boot >=3.2.0) tomcat is not destroyed on reactive webserver application failure.
Application reports an error on startup but process is not terminated.

Minimal application to reproduce: https://github.com/boolivar/spring-webserver-test (3 dependencies and trivial TestApplication class).
Issue is not reproduced on spring-boot v3.1.12 or if servlet web application is configured.

Here is the differences in context behaviors:
ReactiveWebServerApplicationContext - webserver stopped
ServletWebServerApplicationContext - webserver stopped and destroyed

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 4, 2025
@philwebb philwebb changed the title Tomcat reactive is not destroyed on application failure WebServers are not destroyed on application failure in ReactiveWebServerApplicationContext Feb 5, 2025
@philwebb philwebb added this to the 3.3.x milestone Feb 5, 2025
@philwebb philwebb added type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 5, 2025
@wilkinsona
Copy link
Member

Closing in favour of #44134.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2025
@wilkinsona wilkinsona added the status: superseded An issue that has been superseded by another label Feb 13, 2025
@wilkinsona wilkinsona removed this from the 3.3.x milestone Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: superseded An issue that has been superseded by another type: bug A general bug
Projects
None yet
Development

No branches or pull requests

4 participants