Dialog taking long time to open | Community
Skip to main content
Level 4
July 22, 2018
Solved

Dialog taking long time to open

  • July 22, 2018
  • 13 replies
  • 5972 views

Hello All,

             We are migrating from  AEM 6.0 to AEM 6.3.2.2(SP2 + CFPS 1 and 2).  All our application related tags are  present under /etc/tags/xyzApp

After migration, when we open any of our components dialog, they are taking long time (around 10~15 seconds) to open.

When we tail error.log, while opening dialog,  we are seeing below warnings in error.log

07.2018 06:28:25.803 *WARN* [10.246.75.239 [1532082503111] GET /mnt/override/apps/xyzApp/components/content/site/abc-pqr/_cq_dialog.html/content/xyz/dfh/jcr:content/rhs/abc-pqr HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 14000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [cq:Tag] as a where isdescendantnode(a, '/etc/tags/xyzApp') /* xpath: /jcr:root/etc/tags/xyzApp//element(*, cq:Tag) */, path=/etc/tags/xyzApp//*); consider creating an index or changing the query

20.07.2018 06:28:25.962 *WARN* [10.246.75.239 [1532082503111] GET /mnt/override/apps/xyzApp/components/content/site/abc-pqr/_cq_dialog.html/content/xyz/dfh/jcr:content/rhs/abc-pqr HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 15000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [cq:Tag] as a where isdescendantnode(a, '/etc/tags/xyzApp') /* xpath: /jcr:root/etc/tags/xyzApp//element(*, cq:Tag) */, path=/etc/tags/xyzApp//*); consider creating an index or changing the query

Please let us know how to solve this problem. We have not seen this issue in AEM 6.0

Regards

Sreeni

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vish.dhaliwal

These warnings may be stemming from bad index definition, where the "propertyNames" property has type String but the expected type is Name[] and that index is used to index "lastUnpacked" property.

13 replies

smacdonald2008
Level 10
August 3, 2018

Support said:

They need to use chrome dev tool to capture the slowest request....

If he open a support case we would ask for HAR file and if he was able to duplicate the same on an another server

user00725Author
Level 4
August 5, 2018

Thank you Scott for your reply!

I followed leo advice exactly, but no luck.

1. The issue is on upgraded instance from 6.0 to 6.3.

2. When we verify the slowest call from chrome developer tools( network tab), it's the call to open dialogue which is taking long time.

Regards

Sreeni

user00725Author
Level 4
August 6, 2018