Today we have just updated the Java version 1.8.0_202 after upgrading I am tried to log in to AEM Felix UI but its given error: A custom errorhandler for 404 responses. And also i tried to check the logs in server i found 404 error : GET /aem/start.html HTTP/1.1" 404 134 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36"
Please let me know how to resolve this issue.
Could you please check error.logs, can you see any error?
Did you try to restart instances after upgrade?
Below are the errors and after upgrade we restarted the instances we are able to access crx/de, system/bundles etc not the AEM welcome/login screen :
==> stderr.log <==
Opening browser using cmd=x-www-browser "http://localhost:4502/" || gnome-open "http://localhost:4502/" || firefox "http://localhost:4502/" || mozilla "http://localhost:4502/" || konqueror "http://localhost:4502/" || netscape "http://localhost:4502/" || chromium-browser "http://localhost:4502/" || opera "http://localhost:4502/" || links "http://localhost:4502/" || lynx "http://localhost:4502/"
Installation time:173 seconds
MAIN process: shutdown hook
MAIN process: exiting
GET /aem/start.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /libs/granite/ui/content/shell/start.html not found
==> stdout.log <==
Attempting to load validation.properties via file I/O.
Attempting to load validation.properties as resource file via file I/O.
Not found in 'org.owasp.esapi.resources' directory or file not readable: /opt/aem/author/validation.properties
Not found in SystemResource Directory/resourceDirectory: .esapi/validation.properties
Not found in 'user.home' (/root) directory: /root/esapi/validation.properties
Loading validation.properties via file I/O failed.
Attempting to load validation.properties via the classpath.
SUCCESSFULLY LOADED validation.properties via the CLASSPATH from '/ (root)' using class loader for DefaultSecurityConfiguration class!
RAWProcessor succesfully installed
19.03.2019 07:45:29.218 *INFO * [main] Startup completed
Also i found something in upgrade.log :
19.03.2019 07:45:29.109 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.VersionRangeTaskIgnorelist Bundlelist for upgrade version comparison could not be read from /opt/aem/author/crx-quickstart/conf/sourceInstanceBundles.json
What is the AEM version?
Check if all bundles are in active state?
What is the error observed in the error.log when you try to access login page ?
AEM Version is 6.4 and Error Log :GET /aem/start.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /libs/granite/ui/content/shell/start.html not found
check if the login page configurations are fine. You could even compare/package the default ACLs and move it to this instance to rule out permission issues while upgrading.
All the messages you posted have nothing to do with the non-loading of a page in AEM. I am also not sure if you mean the webconsole ("/system/console/bundle") or the regular AEM UI ("/aem/start.html").
The "404" indicates a permission problem, most likely the login failed. But this can have a lot of reasons. And I doubt that it has something to do with the changed Java version in the first place.
I was wondering if there were any update on that? We have these issues very often and only way we can fix that it's sometimes by re-indexing, but if not working it needs a full rebuild of our environment, which is really annoying.
Anyone knows how to salvage the env to get back the ui to a working state ? Without using backups, offline maintenance... which is a no go with our kube setup and pods restarting straight away as soon as we kill the entry point process.
like the others, we have access to crx/de and system/console.
Thanks in advance for your help :-).
could you please check if you are starting your jar with updated java version.
sometimes it can be basic miss.
also try giving this command on your start.bat, not inside the bin folder. but where your jar file is located. create new one.
java -debug -Xverify:none -XX:MaxPermSize=1024M -Xnoagent -Xmx4096M -Dsling.run.modes=author,nosamplecontent,dev -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=30303 -verbose:g -jar AEM_6.3_Quickstart.jar -nofork -gui
-XX:MaxPermSize=1024M is important thing which you should check.