Closed aditya1990mandrekar closed 2 months ago
@chemicL Have you seen issue like this?
Hey. I looked into a similar case on the Micrometer Slack. I don't feel there was a conclusive outcome unfortunately, so let me just gather the resources mentioned in that thread for more transparency, but I recommend following the discussion while it's still available. The gist of it is: same type of class loading problem, Kubernetes, random occurences.
The reporter created this SO question: https://stackoverflow.com/questions/78013321/how-to-handle-the-spring-boot-classloader-problem
I managed to find a few related reports in other repositories:
To summarize, I'd look for class loaders being used and check specifically for the use of ForkJoinPool
and CompletableFuture
and eager use of the reactor-core APIs by some libraries, as they can run into these issues if the ordering is in conflict.
At the same time it doesn't feel this is a Spring/Reactor issue unless evidence points to us doing something fishy.
One update that i missed. The issue happened again today. The common pattern between the two is, The issue occurs on the newly created pod as part of autoscaling. So looks like sporadically on the new pods, the issue occurs.
Note: we are using OpenJdk17
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open.
We have a weird issue that we saw in production couple of days back. So i have this springboot webflux application which is running in prod on Google Kubernetes engine for more than 3 months now. We faced this out of the blue bug where we got an issue connecting to one of our subsystem. To call the subsystem over http we are using WebClient. More strange thing was out of the 4 pods in prod, it appeared on only one of them.
To resolve the issue we redeployed the app and the issue seem to vanish.
Error trace:
Dependencies:
Actual Behaviour: The http call is failing Expected behaviour: http call via webclient should not fail