Hi Spring community,
And before saying anything, thank you so much for that wonderful adventure! I'm spring afficionado since 2008 and will never be able to bring you back enough value than the one you bring to the community.
Spring boot version: 3.5.5 with (for frontend facing libraries) - spring actuator - spring-data-jpa
Context: I'm working on a good old 'fat batch' app which transfers data from a database (with a transformation in between source code Sometimes, database migration can take more than 30 minutes.
When using bare spring configuration a an @Order(1) bean, starter becomes stuck after 3 minutes or so without giving any information to the user (neither telling something is stuck), without any notification (I guess it expects an endpoint to be exposed) unless spring.main.web-application-type: none is defined.
Took me approximately 9 month spare time to discover the fix, thus I'm just asking something for the next comers: may you please add a log message to tell someone in the same situation?
- 'thread will starve because no healthiness probe responding (pring.main.web-application-type: none may be set)'
- Not blocking the thread?
Thank you for your understanding and to take this feedback into account. Best regards, and never hesitate to reach me if I can help somehow
Comment From: snicoll
I don't understand neither the title nor the description. What fix is that? What's the @Order got to do with it?
If you can build a small sample that reproduces the problem, that would be ideal to make sure we're on the same page.
Comment From: Tcharl
Sorry.
To make it simple.
A simple spring boot app, exposing no controller (not a web one, a good old fat jar executed with java -jar) freezes after 3 minutes or so with spring by default.
No logs, no information or anything if thrown to the user to tell that there's an issue.
A spring boot option exists to circumvent that issue: spring: web-application-type: none should be set.
Discovering that magic trick is hard: why would a java execution would stop abruptly?
One of the reproducer would be to use https://github.com/OsgiliathEnterprise/data-migrator/releases/tag/1.114, with a large enough input db dump.
Comment From: wilkinsona
Unfortunately, we don't have an input DB dump and we can't easily create one as we don't know how big "large enough" is. If you want us to spend time investigating the problem, you're going to have to spend some time providing us with a reproducer.
Comment From: snicoll
To make it simple.
Unfortunately, it isn't simple at all. What does "freeze" mean? If It isn't a web application, then spring.main.web-application-type=none should have no effect.
why would a java execution would stop abruptly?
It would be interesting to see if you can reproduce outside of your app. You sound like this behavior is accounted to Spring Boot and the property is one way out but we've never heard of this problem before.
One of the reproducer would be to use https://github.com/OsgiliathEnterprise/data-migrator/releases/tag/1.114,
As Andy said, that isn't a reproducer but a complete app. We can't justify spending time to debug your app.
Comment From: Tcharl
Thank you for your time answering. I'll try to create a simple reproducer with the spring libraries I use in that app. Coming soon!
Charlie Mordant
Le lun. 24 nov. 2025, 08:37, Stéphane Nicoll @.***> a écrit :
snicoll left a comment (spring-projects/spring-boot#48231) https://github.com/spring-projects/spring-boot/issues/48231#issuecomment-3569315057
To make it simple.
Unfortunately, it isn't simple at all. What does "freeze" means? If It isn't a web application, then spring.main.web-application-type=none should have no effect.
why would a java execution would stop abruptly?
It would be interesting to see if you can reproduce outside of your app. You sound like this behavior is accounted to Spring Boot and the property is one way out but we've never heard of this problem before.
One of the reproducer would be to use https://github.com/OsgiliathEnterprise/data-migrator/releases/tag/1.114,
As Andy said, that isn't a reproducer but a complete app. We can't justify spending time to debug your app.
— Reply to this email directly, view it on GitHub https://github.com/spring-projects/spring-boot/issues/48231#issuecomment-3569315057, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGBSXP4WVJO7QPKTOOAZ7T36KYTNAVCNFSM6AAAAACM22NO7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRZGMYTKMBVG4 . You are receiving this because you authored the thread.Message ID: @.***>
Comment From: Tcharl
Tried to reproduce on a smaller sample (only one db, just spring components). Could not reproduce.
Seems to be between the chair and the keyboard. Definitely sorry for the inconvenience, I'm closing this issue since I'll find the right reproduction