Re: Service Factory returned null

DS will explain in great detail what happened in circumstances like this, so look in the log. You might need to increase the amount logged by setting the ds.loglevel property to debug, as a framework property or in the DS configuration. What exactly are you setting and where with the "keep

Re: Service Factory returned null

I cant tell atm what is going on, but I suggest you to use the latest Apache Felix SCR Release (org.apache.felix.scr) just to rule out already known and solved problems. The same is true for the DS web console plugin Regards Carsten Martin12 wrote > Update: > Activating the keep component switch

Service Factory returned null

Hi there, we are facing the following issue: We've updated our application: from Java 7 to Java 8 org.apache.felix.metatype from 1.0.4 to 1.0.8 org.apache.felix.webconsole from 3.1.8 to 4.2.0. We've also added the org.apache.felix.webconsole.plugins.ds (1.0.0) bundle since we were experiencing

Re: Service Factory returned null

Oh, and the maven-scr-plugin has been updated as well: maven-scr-plugin 1.9.0 -> 1.20.0 -- View this message in context: http://apache-felix.18485.x6.nabble.com/Service-Factory-returned-null-tp5021777p5021778.html Sent from the Apache Felix - Users mailing list archive at Nabble.com.

Re: Service Factory returned null

Update: Activating the keep component switch of org.apache.felix.scr.ScrService seems to solve the problem. Any ideas why? This seems to suggest that delayed components are cleaned up (for good) even if they are still needed. -- View this message in context: