Could be the possibility, many times your package manager show a message "Different version seems to be installed" as shown below. Uninstalling the package from CRX manager and redeploy your code fix this problem.

Thanks @Jörg_Hoh for the response.For the visitors (having same problem), My code is calling tagManager.findTagsByTitle() and tagManager.findTagsByTitle() which triggers a query and I was having this issue. Solution which fixed the issue is adding below indexes/oak:index/cqTagLucene/indexRules/cq:Ta...

Hello Community, We are seeing lot of warning in our publish instance (only) because of which CPU usage is going high.30.07.2021 12:07:12.078 *WARN* org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated: /oak:index/lucene; it is used for query Filter(query=selec...

Hello,Give a read to this https://adobe-consulting-services.github.io/acs-aem-commons/features/sling-model-injectors/hierarchical-page-property/index.html if this helps

I have seen one more problem with the version in the package manager where it says "A different version seems to be installed". Uninstalling the package and then deploy the code bring my latest changes to AEM.

Two ways I can think of (Not sure but changing pwd from command line is since 6.3, not sure if that will work for 6.1, again something to check)Java -jar aem-publish-p4502.jar and then in console it will ask for password.Or java -Dadmin.password.file =/path/to/passwordfile.properties -jar aem6.3.jar...

If you don't see login screen, alternative is to login from http://localhost:4502/crx/de/index.jsp. Login through crx and then hit login screen, it should work.

Jörg_Hoh What I understood from your security concern, we should not edit these configuration with custom values and think of other way to do it ? Please correct me if I get this wrong. Also, if you could educate more on this topic it will be helpful

@Vijayalakshmi_S Initially haven't added -domain but when it didn't worked added -domain for testing purpose. And I tried adding directly to Felix, that broke the instance too. Wondering if it's a good idea to edit these configs as mentioned by Jörg_Hoh

@Vijayalakshmi_S OOTB properties were not touched and I added my own custom property as shown below. When I tried putting these new values in code base under /config, I encountered the error. I tried putting just the new values adding -domain to the config's PID & using OOTB PID as is mentioning exi...