Hi @rgravisankar  Can you try below code snippet:String processArgs = processArguments.get("PROCESS_ARGS", "string").toString(); Regards,Arpit Varshney

Hi @anupam_miglani This might be an issue with an index or some packages installed on the prod environment. Could you please try and check if some additional package/index has been installed on prod which is causing this issue. Note: try to figure out the packages which are installed around the time...

Hi @rahulb31017943  I have just noticed that you want to read a property located at /etc/abx/xyz/* and the corresponding dispatcher rule is /0151 { /type "allow" /url "/etc/xyz/*" } which doesn't seem to be right to allow /etc/abx/xyz/*. Could you please try updating your rule like below:/0151 { /ty...

Hi @Kam-nyc  Please download it from here https://github.com/adobe/aem-core-wcm-components/releases/tag/core.wcm.components.reactor-2.5.0 and install it in your AEM instance. Regards,Arpit varshney

Hi @saurabh_intel Why don't you create a common client-lib which include common files and create two clientlibs embedding the common clientlibs? Regards,Arpit Varshney

Hi @Kam-nyc  The link you are referring is using core component release 2.5.0 as a reference. Could you please verify if it is the same version in your instance as well? Regards,Arpit Varshney

Hi @danilo-delfio There might be many reasons for this behavior. Some of them might be:AEM instance is not up and running.AEM instance might be running on different port than the one configured in your pom.xml file. In that case, you can change your pom port parameter or run aem on the same port men...

Hi @ajin0093  This is an upgrade project which needs proper planning and approach to make a decision. It is not recommended to replicate content from a lower AEM version to a higher AEM version. Start from here to get an understanding of the AEM upgrade. You will understand the few additional steps ...

Hi @v1101 It seems you are mixing JSP and HTL syntaxes. If your script file contains extension as .html then follow HTL documentation else follow JSP. It looks like your script file is JSP as most of your shared code follows JSP syntaxes and JSP doesn't support sly and data-sly-test. It is HTL synta...

I will still recommend you to wait for next time and see the CPU usage. Apart from that try checking if you can find any error in browser console when you click upload button. Also try to test this functionality on different browsers during that time.