title: Long lasting Declarative Service activate method
body: <p>I tried to understand <a href="https://osgi.org/specification/osgi.cmpn/7.0.0/service.component.html" rel="nofollow noreferrer">from the OSGi specs</a> what it should happen in case an activate method blocks indefinitely but I did not find an answer. On the other hand, it seams that that Felix SCR has  <code>ds.lock.timeout.milliseconds</code> and <code>ds.stop.timeout.milliseconds</code> properties to manage activate/deactivate timeouts, right?</p>
  
  <p>Questions:</p>
  
  <ul>
  <li>Why OSGi specs do not mention activate/deactivate deadlock management?</li>
  <li>In case a DS needs more time to run its activate method, is it wise to increase the default SCR <code>ds.lock.timeout.milliseconds</code> value? Or is it better to avoid the activate method altogether and register the service "by hand" using <code>context.registerService</code> in a dedicated thread?</li>
  </ul>