We started to use AEM 6.2 in our recent projects. Generally, Early adopters face bit more problems. Same applies here too. Resolving each issue has been a challenge for us and a learning too. I’d like to share few of them, So it could be helpful for those who try later.
This link from Adobe explains the steps for upgrade to AEM 6.2. Here, I have listed the issues and it’s solution by the order I faced:
1. WCM Mode does not work or Side rail does not show up in pages:
This is an interesting issue. Once we install our project to AEM, the wcmmode does not work or Side rail will not show the components as shown in below snapshots.
Components are not showing up in the side rail:
WCM Mode does not work:
The problem in this issue is below stack trace:
GET /libs/wcm/core/content/components.1466401259424.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException org.apache.sling.api.request.TooManyCallsException: /libs/cq/gui/components/authoring/componentbrowser/component/component.jsp at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:530) at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44) at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:77) at com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:96) at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68) at com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:151) at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
TooManyCallsException is causing it. There is a configuration called “Apache Sling Main Servlet“, we need to increase the “Number of calls per request“.
This exception happens when the project is huge and making so many calls to your instance.
Below is the screenshot of the configuration:
The default value for Number of calls per request is 1000. I increased to 2500
2. Social Login – Authoring:
Social login was throwing exception in AEM Author, Later on we identified the Social login does not work in AEM author from 6.2 onwards (bug or feature?). It was working till AEM 6.1
Versioning related issues:
With AEM 6.2, there is a major clean up interms of API and classes. This link explains it
These issues are expected. But with few tricks we had to manage these
3. ACS commons versioning:
ACS commons that supports for AEM 6.2 is ACS 3+. With 6.1 it was 2.7. The reason for this is so many API and Classes are deprecated and removed in AEM 6.2. The list is in this.
4. UberJar versioning:
UberJar is provided by Adobe which contains all public jar files. DOCS is here.
Note: The dependency need to be added to parent POM first then if required it needs to be added to bundle’s POM.
I’ll keep updating this post, if I face any other issues (hopefully, I won’t :)). If you face any more issue, please comment here. Let us discuss. Keep learning.