On Wed, Sep 16, 2009 at 2:53 PM, Filippo Diotalevi <[email protected]> wrote: > 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="(&(APPLICATION=SL)(COUNTRY=UK))" /> > > and injected in a Spring bean turns out to be a totally different > service, with the same filter (&(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?
We did improve our locking in 2.0.0 a lot but I can't say I remember a race condition in service handling per say (but it might be catched by the other improvements as they are in the area of classloading). regards, Karl > Unfortunately is quite difficult to reproduce the error, so I don't > have a simple test case. > > -- > Filippo Diotalevi > -- Karl Pauls [email protected]
