Bundle deployed via JCR does not show up in OSGI Bundle list

[Former Community Member]

Hi everyone,

AEM 6.1.

I deploy a bundle via the "maven-sling-plugin" into /apps/<name>/install/<bundle-nam>-1.0.0.jar .

On my local machine, the bundle gets deployed into the JCR and shows up in the AEM Console Bundle list as installed and started.

On the remote server, it only gets deployed in the JCR but it does not get started nor installed.

I can install and start the bundle, if I download the file which is saved in the JCR and installed via the Install Button in the OSGI Interface. 

Runmode locally :

CQ_RUNMODE='author'

Runmode remote Server:

 CQ_RUNMODE='author,build,nosamplecontent'

Why doesn't it get installed automatically on the remote server?

No errors in log regarding that bundle.

Kind regards,

Jerry

[edubey]

which aem version you are using ?

[smacdonald2008]

I have seen this before. Check you logs. I personally prefer installing manually via the Felix console. I have never had issues doing so. 

[Former Community Member]

@edubey: as said AEM 6.1.

@smacdonald2008: Nothing in the normal logs. Activated Debug Log and found sth

@kautuksahni: Manual Installation is just simply not possible for a Build Server.

If it is not possible to automate the deployment of code to a shared development environment, then the product is not worth it. It won't scale..

Found the solution in the debug logs:

"01.12.2015 10:46:41.664 *DEBUG* [JcrInstaller.1] org.apache.sling.installer.provider.jcr.impl.JcrInstaller Found child nodes [c4a63b27-4255-4506-9d2c-a051914b5a5a, 545ef56d-d3c7-4459-9504-f879dec46023, 34d281dc-c060-49b9-8c86-0301486ce28b, dc873775-7a37-4b9b-ba87-bdd15a2ef679, 9e90f2ac-472a-4ea6-9b66-f515e3c78f78, 1fe81d40-ad0f-4ae2-ad58-79a109a86b79, cd2d9ab0-f598-4fef-b406-161170a74f48, 6e379520-517c-45d6-af6a-05af3dfdaddc, 7b866caf-a05f-4bf2-9875-30c8cc0d2e32, 80f16a6f-2002-4b3b-90ac-0ee6bd915305, 98a56205-402b-4770-acac-66f59b56403f, 19e55281-8b15-47c0-b4b3-98fe5036fe7a] at path /system/sling/installer/jcr/pauseInstallation. Scanning would be paused"

Deleted all the nodes beneath "/system/sling/installer/jcr/pauseInstallation". 

Pushed again the jar -> gets deployed and installed.

[kautuk_sahni]

Hi 

Agreeing with Scott, i also personally prefer installing them manually. 

~kautuk