Any race condition in Felix 1.8 service lookup you are aware of?

[Filippo Diotalevi]

Hi,
  I'm experiencing a weird (and not easily reproducible) behavior with
my Spring DM + Felix application, that counts quite a lot (>50) of
Spring DM bundles.

What's happening is that an instance of the wrong type gets injected
in a Spring managed bean. In particular, a service retrieved with a
simple

<osgi:reference id="xmlproxy" interface="com.acme.api.XmlProxy"
filter="(&amp;(APPLICATION=SL)(COUNTRY=UK))" />

and injected in a Spring bean turns out to be a totally different
service, with the same filter (&amp;(APPLICATION=SL)(COUNTRY=UK)), but
obviously with a different interface (service name).

I'm using Felix 1.8.0... are you aware of any race condition in that
version with service lookup?

Unfortunately is quite difficult to reproduce the error, so I don't
have a simple test case.

-- 
Filippo Diotalevi