Updated the AEM 6.5 instance from SP5 to SP9, we are facing rollout issue. | Community
Skip to main content
K
kbitra1998
Level 4
August 27, 2021
Question

Updated the AEM 6.5 instance from SP5 to SP9, we are facing rollout issue.

  • August 27, 2021
  • 1 reply
  • 3977 views

We have upgraded the AEM 6.5 instance from SP5 to SP9, We are facing the rollout issue, I have observed the network tab in which we are getting /bin/asynccommand has 500 error. we have observed the logs and found the this error "com.adobe.ams.environment.indicator.wcm.impl.AemEnvironmentIndicatorFilter not accepted for uri /bin/asynccommand".

Just an observation, Previously we had AEM 6.5 SP5 when we click the rollout button the request went to /bin/wcmcommand but in SP9 the request went to /bin/asynccommand. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community Advisor
Community Advisor
August 27, 2021

Hi @kbitra1998 

 

This is an ongoing issue with AEM 6.5 with ACS Commons Environment Indicator.

https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1848

 

What version of ACS Commons are you using? Try to upgrade to latest version and see if it's resolving the issue else for now disable the Environement Indicator to resolve the issue.

 

I just tried to rollout the pages with AEM 6.5.9.0 without ACS Commons on my system and it works perfectly fine.

 

Thanks!

    K
    kbitra1998Author
    Level 4
    August 27, 2021

    Thanks @asutosh_jena_ , currently we are using ACS Commons version 4.2.2 and I have updated the ACS Commons to latest version(5.0.8) in my local still facing the rollout issue. Could you please tell how to disable the ACS Commons. When I tried to stop the ACS Common bundle from system/console/bundles, the page content is not loading showing blank page.

      Asutosh_Jena_
      Community Advisor
      Asutosh_Jena_Community Advisor
      Community Advisor
      August 27, 2021

      Hi @kbitra1998 

       

      You should not disable the ACS Commons bundle as it might impact your existing application. Instead of that I will suggest you to find all the OSGi configuration with name com.adobe.acs.commons.wcm.impl.AemEnvironmentIndicatorFilter.xml and remove it and try to see if it resolves the issue.

       

      Thanks!

        Terms & ConditionsAccessibility statement

        Loading footer...