ACS Commons bundle is not activate in stage environment.

[rohitbck]

Required Information

ACS Commons version 5.3.0

Expected Behavior

bundle should active in all environments.

Actual Behavior

I am trying to add ACS Commons using pom.xml, the bundle and packages of ACS commons is working fine on my local but when i am trying to add same dependency using same way in stage environment the state of bundle is in install state instead of active state.

i tried to reproduce the same issue on local by changing the state of ACS commons bundle as install and hit the URL http://localhost:4502/etc/acs-commons/exporters/exporter.html

i am getting the same error as reproduced in stage we have same exported.html available on stage environment.

Steps to Reproduce

1. install ACS commons package using pom.xml
2. change the state of bundle from system/console
3. http://localhost:4502/etc/acs-commons/exporters/exporter.html hit the URL.

[davidjgonzalez]

What version of AEM are you running?

What is the status of the ACS AEM Commons bundle on in the OSGi console - the fact you have to start it manually tells me something is amiss.

Are you sure you have all the other packages installed? ui.apps, ui.content, etc?

Also, anything in the error logs? This very much sounds like an issue with your AEM rather than ACS Commons, but i could be wrong!

[gowtami-betireddy]

Hi @davidjgonzalez, kindly find my comments below as highlighted.

What version of AEM are you running? - AEM as a cloud

What is the status of the ACS AEM Commons bundle on in the OSGi console - the fact you have to start it manually tells me something is amiss. - On dev, after inspect we found that getting 400 server bad request ( Cannot serve request to /etc/acs-commons/exporters/export/_jcr_content.init.json on this server ) error. Note: We manually change the acs bundle state as installed to reproduce the issue in local environment. We got the same error in local as well after changed the state of the bundle.

Are you sure you have all the other packages installed? ui.apps, ui.content, etc? - Yes all the related acs packages are installed.

Also, anything in the error logs? This very much sounds like an issue with your AEM rather than ACS Commons, but i could be wrong! - Did not find any specific errors related to acs

The actual issue was that we could not able to access the miscadmin & create exporter pages. We are following the recommended approach in order to get the access for the same on higher environments.

below paths are not accessible on higher environments: /etc/acs-commons/exporters/users-to-csv.html /miscadmin#/etc/acs-commons/exporters

Approach that we have tried: Updated pom.xml with the acs 5.3.0 dependencies & deployed. Packages were installed & but couldn't able to find state of the bundle since we don't have access on dev & others.

Kindly let me know if anything else info is required.

Thank you

[davidjgonzalez]

Hi @gowtami-betireddy

Did you check to see if the Bundles is in-fact stopped on AEM CS Author in the Stage env using the Developer Console > Bundles? https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/debugging/debugging-aem-as-a-cloud-service/developer-console.html?lang=en#bundles

Or if you look through the Develop Console > Components .. and see if UsersInitServlet is unsatisfied, and if it is - why (it should tell you what in that is unsatisfied)

I tried 5.3.0 on latest AEM SDK and the bundle starts automatically:

So far, i cannot seem to reproduce this on my AEM CS Stage sandbox or on my AEM SDK ..