[FELIX-5270] [DS] Config race between update and delete

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-2.0.2
• Fix Version/s: scr-2.0.4
• Component/s: Declarative Services (SCR)
• Assignee: David Jencks
• Reporter: David Jencks
• Created: 01/Jun/16 00:12
• Updated: 30/Nov/16 22:47
• Resolved: 11/Jun/16 01:15

Description

Thanks to Fabian Lange for reporting this problem and providing logging that shows what is going on.

The first getConfiguration when the location is not set generates a LocationChanged event. When we get such an event, we get the configuration to see what happened.

DS: (either from query or initial CM_UPDATED event) calls getConfiguration, setting the bundle location and generating a CM_LOCATION_CHANGED event.
User: delete configuration, setting the properties to null
DS: receive CM_LOCATION_CHANGED, call getConfiguration (incidentally recreating the configuration) and get configuration with null properties and a location. We then throw:

if (configInfo.getProps() == null)

{ throw new IllegalStateException("Existing Configuration with pid " + pid + " has had its properties set to null and location changed. We expected a delete event first."); }

Issue Links

• breaks: FELIX-5435 Service does not get loaded with updated properties that have been modified on file system after felix framework restart