You have configuration policy require and there is no component configuration shown, so the configuration is missing.
If at least one matching configuration were available to DS you’d see one component configuration for each configuration, and then you could tell if the references were satisfied or not from the references section of the component configuration. thanks david jencks > On Jul 6, 2016, at 8:52 AM, Benson Margulies <ben...@basistech.com> wrote: > > Folks, I have a service that isn't starting, and I cannot see why. Any clues? > > > karaf@root>scr:details com.basistech.ws.worker.service.WorkerService > Component Details > Name : com.basistech.ws.worker.service.WorkerService > State : UNSATISFIED > Properties : > service=worker > References > > ----- > > karaf@root>scr:info com.basistech.ws.worker.service.WorkerService > *** Bundle: com.basistech.ws.rosapi-worker-service (144) > Component Description: > Name: com.basistech.ws.worker.service.WorkerService > Default State: enabled > Activation: immediate > Configuration Policy: require > Activate Method: activate > Deactivate Method: deactivate > Modified Method: - > Configuration Pid: [com.basistech.worker.service] > Services: > com.basistech.ws.common.WebServiceAvailable > Service Scope: singleton > Reference: CxfTransport > Interface Name: org.apache.cxf.transport.http.DestinationRegistry > Cardinality: 1..1 > Policy: static > Policy option: reluctant > Reference Scope: bundle > Reference: Metrics > Interface Name: com.basistech.ws.common.metrics.MetricsRegistryService > Cardinality: 1..1 > Policy: static > Policy option: reluctant > Reference Scope: bundle > Reference: Worker > Interface Name: com.basistech.ws.worker.api.WorkerInterface > Cardinality: 1..1 > Policy: static > Policy option: reluctant > Reference Scope: bundle > Properties: > service = worker
