Skip to content

Upgrading from 2.0.5 to anything higher results in application never finishing startup #16479

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
dillius opened this issue Apr 6, 2019 · 3 comments
Labels
status: invalid An issue that we don't feel is valid

Comments

@dillius
Copy link

dillius commented Apr 6, 2019

Attempting to start back on an older project I haven't worked on in a while, and attempting to upgrade to a newer spring boot release results in a non-start. No errors are logged, and trying to debug has led me nowhere.

It appears that for some reason my routing configuration is completely ignored, and the application never starts to listen on 8080.

I have tried going from 2.0.5 to 2.0.6, 2.0.9, and to 2.1.4. All have the same result on startup, which I have attached logs for.

I could not find anything in the 2.0.6 release notes that seemed to relate. If I try to go as far as 2.1.4 I do have very obvious issues with bean overriding no longer being enabled by default and my application conflicting, so possibly even the 2.0.X problems are related to this symptom?

successful_2_0_5_startup.log
failed_2_0_9_startup.log

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 6, 2019
@snicoll
Copy link
Member

snicoll commented Apr 6, 2019

Sharing the logs is nowhere near enough to be able to help you. Can you share a sample that reproduces the problem you're experiencing (a zip file or a link to a github repo we can run ourselves would be ideal).

@snicoll snicoll added the status: waiting-for-feedback We need additional information before we can continue label Apr 6, 2019
@dillius
Copy link
Author

dillius commented Apr 6, 2019

I believe I have determined the cause, and it relates to another issue:

spring-projects/spring-framework#20904

My security setup involved blocking a publisher to pull information from a reactive repository for user information, then manipulate it, during the creation of a Bean. Starting in 2.0.6 this apparently is no longer valid, and the thread will simply block waiting forever for that repository.

I am going to have to redo my security setup such that no blocking is required.

Can just leave this issue here in case another user comes across it.

@dillius dillius closed this as completed Apr 6, 2019
@snicoll
Copy link
Member

snicoll commented Apr 6, 2019

I was actually suspecting something like that. Glad you figured it out.

The issue isn't going anywhere.

@snicoll snicoll added status: invalid An issue that we don't feel is valid and removed status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Apr 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants