Components are in satisfied state

[pallavis8124480]

Hi ,

My servlets are giving 404 not found error as the component is in satisfied state.

If I see the component ,the references are in satisfied state.It uses the following reference :
ResourceResolverFactory.

Steps I did  :

1) Added @activate to activate method
2) Made the component immediate =true
3)Added the dependencies of sling api etc

4)Restarted the instance.

But I wasn't able to make it to Active.It is still in satisfied state.
Note : All my bundles are active .

Please help me to resolve the issue.

Thanks,

Pallavi

[Hemant_arora]

There is problem with the code. Can you share it? Also let us know the version of AEM

[pallavis8124480]

Hi ,

I am using 6.2 version .

Please find 1 snippet of code

import org.apache.felix.scr.annotations.Activate;

import org.apache.felix.scr.annotations.Component;

import org.apache.felix.scr.annotations.Deactivate;

import org.apache.felix.scr.annotations.Service;

@component(immediate = true, metatype = true, label = "sample", description = "Service that exposes configured environment info. " )

@service(value = SampleInfo.class)

public class SampleInfoImpl implements SampleInfo{

private static final Logger log = LoggerFactory.getLogger(SampleInfoImpl.class);

@activate

protected final void activate(ComponentContext ctx) {

Dictionary<?, ?> props = ctx.getProperties();

this.environmentName = PropertiesUtil.toString(props.get(OSGI_ENV_NAME), DEFAULT_ENV_NAME);

this.taskURL= PropertiesUtil.toString(props.get(TASK_SSO_URL), "");

}

@deactivate

protected final void deactivate(final ComponentContext context) {

log.debug("deactivating service");

}

//some more logic

}

Thanks,

Pallavi

[smacdonald2008]

Did you build your project using Maven Archetype 10?

[pallavis8124480]

Hi ,

Yes we are using archetype 10.

Thanks,
Pallavi

[srssrinu]

Hi,

Is this issue resolved? We are also facing similar issue in our project.

Thanks,

Srini

[Jörg_Hoh]

Hi,

If a component is in satisfied state although all dependencies are available, it's often caused by an exception in the activate method.

Jörg

[Hemant_arora]

I agree with Jorg. It can also be caused if you are using deprecated methods or the attribute value in one of the annotations that you are using is incorrect. Can you share the code here ?

[gspatil11]

Hi All,

We are also facing same issue as below mentioned components are in satisfied state and we are in AEM 6.5.5.

org.apache.sling.jcr.webdav.impl.handler.DefaultHandlerService com.adobe.cq.dam.webdav.impl.io.AssetIOHandler com.adobe.cq.dam.webdav.impl.io.SpecialFilesHandler com.adobe.granite.workflow.core.offloading.WorkflowOffloadingJobConsumer

Any help would be appreciated.

Regards,

G Patil