-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Spring Boot v3.4.x consistently fails to respond on GCP Cloud Run [after some event occurs] #44288
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
Comments
#43332 ? |
Hi @bclozel Indeed - We have been holding off for months trying upgrade to 3.4.x. Every time we try to, this mysterious case of the hanging Cloud Run instance occurs.
The last time we checked we could get it to hang on the first secured endpoint we call after log-in. There are some unconfirmed reports that our secured API endpoints also worked fine until someone would log in and have have our SPA call our endpoints. I want to confirm that this way of duplicating an endpoint is not an issue: We expose endpoints through our API docs that then call undocumented Swagger endpoints that our SPAs use internally.
|
Let’s keep everything in one place please. |
Hi Team Spring Boot 🫡
We are successfully running Spring Boot 3.3.x on GCP Cloud Run with Java 23 and have been running successfully with all previous Spring Boot versions for years.
When we upgrade to Spring Boot 3.4.x, an unknown hang occurs that makes the instance completely unresponsive until it's restarted.
It's a simple MongoDb query returning a Page.
We have spent days on this and because we cannot retrieve a thread dump from GCP Cloud Run, we are all sitting here scratching our heads 🫤 over here. I had another developer from another team reach out to me, who have the same issue as us, ask us if we have been able to figure it out. For a brief period, we thought it was the new Sentry 8.x, but after completely removing Sentry and still seeing the hang in staging, we are unsure where to look next.
Here's our 3rd party dependencies that might help you:
Our SAS instance dependencies look like this:
The text was updated successfully, but these errors were encountered: