Hi All, I my case, I removed the below dependency from pom.xml files and it solved the issue.<dependency>
<groupId>biz.aQute</groupId>
<artifactId>bndlib</artifactId>
</dependency>
Hi All, I my case, I removed the below dependency from pom.xml files and it solved the issue.<dependency>
<groupId>biz.aQute</groupId>
<artifactId>bndlib</artifactId>
</dependency>
Hi @sush6 - 1. Do request log analysis to know which request is taking huge time around the package installation.2. Check for errors in error.log to see if this issue is happening at the time of bundle installation. Business logic in OSGi services' activate and deactivate methods could cause the is...
Hi @Lalitha_j There are many ways of doing this, if acs-tools package is installed in your AEM instance then this can be achieved through AEM Fiddle console. And adding a new component to the page can be achieved through ResourceResolver API. Write the business logic in Fiddle console and run your c...
The Property Index is useful whenever there is a query with a property constraint that is not full-text, i.e exact match. So if you want to index properties whose values are numbers, timestamp or any other specific data then go with Property Index. On the other hand, Lucene Index is for full text co...
Hi @GPhillips58 - Can we write a URL rewrite rule such that request to ^/etc.clientlibs(.*) would redirect to AEM server? (Consider this as a workaround)
@vijaymanoharan - OK!!URL rewrite happens on the request before it get passed to dispatcher module. And this redirection will not carry the payload data. Please check, in browser console or using redirect trace(Chrome plugin) or in Apache redirect.log, whether the /bin/notification underwent any red...
Hi @vijaymanoharan - The dispatcher log shows 500 as the response code, are you sure that you see 404(not found) as response code? In case of 500, you need to look into error.log of your publish instance.