[CAMEL-12987] camel-core-osgi: OsgiServiceRegistry.onContextStop never gets called.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.18.0, 2.19.0, 2.20.0, 2.21.0, 2.22.0, 2.23.0, 2.24.0
• Fix Version/s: 2.22.3, 2.23.1, 2.24.0
• Component/s: camel-osgi

Environment

Java 10

Karaf 4.2.1

Camel 2.22.0

• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Flags: Patch
• Assignee: Claus Ibsen
• Reporter: Bob Paulin
• Created: 09/Dec/18 02:58
• Updated: 11/Dec/18 13:22
• Resolved: 11/Dec/18 13:22

Description

There is also a second problem with how the registry is being managed within the OsgiDefaultCamelContext.  OsgiServiceRegistry is currently extends LifecycleStrategySupport which is suppose to unload the serviceReferenceQueue onContextStop.  However the registry is never getting added to the CamelContext to manage the Lifecycle because the overridden createRegistry method in OsgiDefaultCamelContext is not being called.  This is because the registry is being set in the constructor of OsgiDefaultCamelContext with

super(registry);

this calls the DefaultCamelContext implementation of createRegistry which does not add the registry to lifecyclemanagement since

OsgiCamelContextHelper.wrapRegistry(this, registry, bundleContext);

is never called. 

See CAMEL-12969 for screen captures.

 

Issue Links

• links to: GitHub Pull Request #2660