"This is happen due to sticky connection enabled on dispatcher?" I don't think so, unless you are generating content from publishers (storing it on publisher).Can you check folders(like datastore, index etc.) sizes under crx-quickstart/repository? 

@bhagchandWhat do you mean by repository size?If you are referring to the content repository, please check the package manager, there might packages manually build in one publisher which are not available on the other one.See if this make sense, you can share more detail for better help..   

Hello @Anilkumar9  The error you mentioned, "npm run prod failed," typically occurs when the npm command fails during the execution of the frontend-maven-plugin. This can happen for various reasons, such as missing dependencies, issues in your project's configuration, or problems with the npm enviro...

@Uppari_Ramesh I am a bit confused about the path (/content/test) that you want to put assets under. However, there are multiple ways to share/expose assets with the end user- for any user -> the asset path under /dam needs accessible by the anonymous user group (Read Permission)- for selected users...

Hello @Anilkumar9, The reason of this error possibly is the following structure of your codebase+-- root-project-A `-- pom.xml +-- module-A | `-- pom.xml +-- module-B | `-- pom.xml +-- root-project-B `-- pom.xml +-- module-C `-- pom.xml It shou...

Hello @UdayashriGo, Are you using the AEM Core WCM search component? In such case you can overlay the component and write your own search.html.https://github.com/adobe/aem-core-wcm-components/blob/main/content/src/content/jcr_root/apps/core/wcm/components/search/v1/search/search.htmlThere you can wr...

Hello @MisbaBijapuri See if this one make sense: import org.apache.sling.api.SlingHttpServletRequest; import org.apache.sling.api.SlingHttpServletResponse; import org.junit.Before; import org.junit.Test; import org.mockito.InjectMocks; import org.mockito.Mock; import org.mockito.MockitoAnnotations; ...

@Nikhil98 I would suggest to review your code and resources for any inefficiencies that might be causing a high number of concurrent requests. Look for any infinite loops, resource-intensive operations, or excessive usage of system resources. Optimize your code to reduce the overall load.Thanks 

@MisbaBijapuri can you please provide some more detail about the problem you are facing and what is your expectation?Thanks

@SDusane 1. An AEM website is a completely dependent entity (outcome) of the AEM ecosystem. To make it work it needs to be connected with the AEM setup (for authoring, content delivery etc). However, if you want to migrate the whole setup on Azure servers its surely doable2. Like other AEM features,...