-
Notifications
You must be signed in to change notification settings - Fork 101
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
Unable to upgrade to Spring Boot 2.4.6 #810
Comments
Looks like
Stack trace doesn't really reveal why
|
Actually seems to reproduce in any of the IT modules by running |
Presumably this is caused by Jetty that keeps listening for something
I tried to downgrade Jetty to the 2.4.5 version but that didn’t seem to be the cause. Also there is a stop timeout set for Jetty in 2.4.6 but reverting that didn’t seem to help either. Maybe the 2.5.0 milestone releases could be tested to understand what change in Spring Boot causes this and what the real problem is. |
I was unable to reproduce this in a basic project from start.spring.io with springmvc It might require Vaadin in the project |
@pleku the next spring boot version (2.4.7 / 2.5.1) is released in two days which fixes over 40 issues. It's probably best to wait for it before further debugging is done. |
@knoobie not sure I follow. There is already an issue raised for this for which we were waiting for a reproducer. I am afraid 2.4.7 isn't going to fix this particular issue since we didn't manage to investigate it. |
@snicoll I had hopes that e.g. spring-projects/spring-boot#26627 is related to this, as I've seen multiple Vaadin users having problems with this after the update - could just be a coincidence tho. |
As can be seen in #809
Moving from Spring Boot 2.4.5 to 2.4.6 causes the build to fail with
Before the failure, the following modules pass
Presumably one of them leaves something running.
This can be reproduce locally also by running e.g.
in
vaadin-spring-tests
However, after Maven has terminated, nothing is left running
The text was updated successfully, but these errors were encountered: