Expand my Community achievements bar.

SOLVED

Assets.html not showing folders and assets.

Avatar

Level 1

Assets.html not showing folders and assets inside after build. We need to restart the querybuilder configuration to getting it working. In the logs we are getting this.

 

29.10.2020 19:50:47.861 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=com.day.cq.search.impl.builder.QueryBuilderImpl)] com.day.cq.cq-search bundle com.day.cq.cq-search:5.12.14 (390)[com.day.cq.search.impl.builder.QueryBuilderImpl(2112)] : Timeout waiting for reg change to complete unregistered
29.10.2020 19:50:50.780 *INFO* [oak-repository-executor-1] com.adobe.granite.repository Service [133111, [org.apache.jackrabbit.oak.api.jmx.SessionMBean]] ServiceEvent REGISTERED
29.10.2020 19:50:51.612 *INFO* [sling-default-4-health-org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck] org.apache.sling.discovery.oak.SynchronizedClocksHealthCheck execute: no topology connectors connected to local instance.
29.10.2020 19:50:54.000 *ERROR* [CM Event Dispatcher (Fire ConfigurationEvent: pid=com.day.cq.search.impl.builder.QueryBuilderImpl)] com.day.cq.cq-search bundle com.day.cq.cq-search:5.12.14 (390)[com.day.cq.search.impl.builder.QueryBuilderImpl(2112)] : Timeout waiting for reg change to complete registered

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi Rahul,

Welcome to Adobe AEM Community.

What is the exact version of AEM Author?

Are you seeing this issue after a recent installation or change on AEM Author?

Is this happening with all the folders or with a specific folder?

Thanks,

Vikram Gaur

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hi Rahul,

Welcome to Adobe AEM Community.

What is the exact version of AEM Author?

Are you seeing this issue after a recent installation or change on AEM Author?

Is this happening with all the folders or with a specific folder?

Thanks,

Vikram Gaur

Avatar

Level 1
Hi Vikram, The issue was because of an old code, Once we removed that this was resolved.