Consistent volatile access to running flag in Lifecycle implementations [SPR-16596] #21137
Labels
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
Juergen Hoeller opened SPR-16596 and commented
As #21031 revealed, several of our
Lifecycle
implementations enforce overly strong locks, in particular in theirisRunning()
implementations. As we do in a many places already,running
should be avolatile
flag that can be checked outside of any lifecycle monitor.Affects: 4.3.14, 5.0.4
Issue Links:
Referenced from: commits b8c92ce
Backported to: 4.3.15
The text was updated successfully, but these errors were encountered: