ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

JCS Connector Status is not 'Active'


Article ID: 14876


Updated On:


CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On


The OSGI bundles have the following life cycle states: 

1. Installed 

2. Resolved 

     a. Starting 

     b. Active 

     c. Stopping 

3. Uninstalled 


After a JCS restart, the specified bundles should be in an 'active' state instead of 'resolved'. 


After restarting the Java Connector Server (JCS) some servers show a status of 'Resolved' rather than 'Active' in the JCS connector web interface.

For example, connectors with Resolved Status after JCS restart: 

1)  JCS :: Connector :: Common ( conectors.common) 

2)  JCS :: Connector :: CsvEmailSender ( 

3)  JCS :: Connector :: JNDI ( 




Release: CAPUEL99000-12.5-Identity Manager-Blended upgrade to Identity &-Access Mgmt Ente


Change the order of the featuresBoot options in the file org.apache.karaf.features.cfg  (located by default in the connector server home, ..\CA\Identity Manager\Connector Server\etc).

Move these two options: jcs-connector-jdbc, jcs-connector-jndi  before  jcs-connector-gab.

The featuresBoot section should look like this:


# servicemix-smpp,servicemix-snmp,servicemix-vfs



Restart JCS. Changes take effect after restarting the JCS services.