I am using Adobe 6.5 JDK Version 1.8 and oak version 1.10.2 whenever I build maven project or close down the system this error pops up I tried 1. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/503-error-authenticationsu...
3.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-2-starting-with-503-...
4.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-2-starting-with-503-...
Nothing actually worked I tried stopping AEM instance delete the folder logs and repository/index , downloaded the OAK-Run-Jar restarted the instances several times restarted the PC chrome everything but when I build the project I am getting this same error.
Please Help
I found the solution one of my bundle was Active but still giving an error kindly delete the index file from crx-quickstart and run again the instance will work fine.
For reference use this- https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-devel...
Solved! Go to Solution.
Hi @shuter009
Do you see anything in the error.log?
Was this working earlier and now after deploying any specific code this issue started popping up?
You are running AEM 6.5 with what service pack? What is the JDK version?
Thanks!
Hi @shuter009
Do you see anything in the error.log?
Was this working earlier and now after deploying any specific code this issue started popping up?
You are running AEM 6.5 with what service pack? What is the JDK version?
Thanks!
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
@shuter009 Package share is no more accessible and the binary can be downloaded from here; https://downloads.experiencecloud.adobe.com/
Also I have the package available here in my drive which you can download and install:
https://drive.google.com/file/d/1jVXyE3OZoCFQMPWJffLH67WYj8w0_a7F/view?usp=sharing
Thanks!
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @shuter009,
Check if you have enough memory required for an AEM instance.
If it was working before and the issue is observed recently, try to dig down the old error.log files (error.log files that are rotated as old files with dates) and check if you have any error related to memory like the below
java.lang.OutOfMemoryError: Java heap space
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @shuter009,
No worries. Can you update the value of -Xmx alone as -Xmx2048m
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies