Skip to content

Consistent volatile access to running flag in Lifecycle implementations [SPR-16596] #21137

@spring-projects-issues

Description

@spring-projects-issues

Juergen Hoeller opened SPR-16596 and commented

As #21031 revealed, several of our Lifecycle implementations enforce overly strong locks, in particular in their isRunning() implementations. As we do in a many places already, running should be a volatile 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

Metadata

Metadata

Assignees

Labels

status: backportedAn issue that has been backported to maintenance branchestype: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions