[FELIX-6317] dynamic greedy optional/mandatory references can get wrong service ranking

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: scr-2.1.22
• Component/s: Declarative Services (SCR)
• Assignee: Unassigned
• Reporter: Tom Watson
• Created: 06/Aug/20 18:37
• Updated: 12/Aug/20 15:53
• Resolved: 12/Aug/20 15:53

Description

@Reference(service = Service.class, cardinality = ReferenceCardinality.OPTIONAL, policy = ReferencePolicy.DYNAMIC, policyOption = ReferencePolicyOption.GREEDY)

OR

@Reference(service = Service.class, cardinality = ReferenceCardinality.MANDATORY, policy = ReferencePolicy.DYNAMIC, policyOption = ReferencePolicyOption.GREEDY)

The above references may get injected with a service that is not the highest ranked service in scenarios that involve multiple threads registering the referenced service with different service rankings at the same time.

If more than one thread is registering the service type with different rankings it is random which will be the final reference bound to the component. The expected result is that the highest ranked service is the final service bound to the component.

Issue Links

• links to: GitHub Pull Request #39