Closed akirayamamoto closed 2 years ago
Release Note: Fixed an issue where a transient database connection issue could persist even after the transient issue has gone.
:tada: The fix for this issue has been released in:
Release stream | Release |
---|---|
2022.4 | 2022.4.5481 |
2023.1+ | all releases |
Team
Severity
a few customers were affected
Version
Present on 2021.2.3085
Latest Version
I could reproduce the problem in the latest build
What happened?
When getting the value of a Lazy object and an exception is thrown, this exception will be cached.
This happens when using the LazyThreadSafetyMode.ExecutionAndPublication (default) and the value factory constructor)).
This problem will exacerbate a transient connection to the database for example.
When this happens, the exception will continue to be thrown every time we try to access the Lazy value even if the database connection has been restored.
We observed this issue on the
SpacesCache
and theRandomConstant
classes.Reproduction
N/A
Error and Stacktrace
More Information
.NET Runtime GitHub issue.
Workaround
Restart the Octopus server.