Description astefan 2010-05-10 04:59:51 EDT

Build Identifier: 2.0.0.RELEASE

If I deploy a bundle to dm Server (using /pickup folder or STS) and this bundle keeps waiting for a service reference to be available (service which, intentionally, is not available) and if I undeploy it, the "Reference ... is waiting for service with filter ..." message keeps being printed out.

Deploying other bundles in the meantime is possible.

Reproducible: Always

Steps to Reproduce:
1. Create a simple "test" bundle importing a package com.foo and having under /META-INF/spring/osgi-context.xml a reference to an OSGi service:
<reference interface="com.foo.Interface" id="myService" />
2. Create a simple "test_intf" bundle exporting com.foo package. In this bundle create under com.foo package a simple interface: com.foo.Interface
3. Start a clean instance of dm Server 2.0.0.RELEASE
4. Copy to pickup folder the "test_intf" bundle
5. Copy to pickup folder the "test" bundle
6. An output similar to the following will be printed out:
 <HD0001I> Hot deployer processing 'CREATED' event for file 'test-1.0.0.jar'.
 <DE0000I> Installing bundle 'test' version '1.0.0'.
 <DE0001I> Installed bundle 'test' version '1.0.0'.
 <DE0004I> Starting bundle 'test' version '1.0.0'.
 <KE0100W> Reference '&myService' in bundle 'test' version '1.0.0' is waiting for service with filter '(objectClass=com.foo.Interface)'.
 <KE0100W> Reference '&myService' in bundle 'test' version '1.0.0' is waiting for service with filter '(objectClass=com.foo.Interface)'.
 <KE0100W> Reference '&myService' in bundle 'test' version '1.0.0' is waiting for service with filter '(objectClass=com.foo.Interface)'.
7. Remove the "test" bundle from the pickup folder
8. The "<KE0100W> Reference '&myService' in bundle 'test' version '1.0.0' is waiting for service with filter '(objectClass=com.foo.Interface)'." message will keep being printed out