Fixes #19229: Deadlock at start when loading new licence #380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.rudder.io/issues/19229
So, I wasn't able to reproduce the problem, and that PR is a bit of testing from what I know can lead to that given the thread dump @ncharles got.
My best guess is that the
lazy val
in the object +runNow
is the root of the problem. We had that problem (hard to debug) in other tickets (https://issues.rudder.io/issues/17228).So: change the
lazy val
forcache
.There was other problems in the services init that are unlikely to be linked to the deadlock, but who knows?
toserve/branding
andbranding/toserve
),