Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Performance issues with CugSupportImpl

Alex_Popov1
Level 4
Level 4

Hi all,

We are using AEM6.2SP1 and during tree activation we see a significant drawdowns of performance.

During thread dump analyzing we see a lot of:

java.lang.Thread.State: BLOCKED at com.day.cq.auth.impl.cug.CugSupportImpl.updateRegistration(CugSupportImpl.java:478) ...

We have found that CugSupportImpl#updateRegistation method (Please note that this method contains synchronized block) is invoked by org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event.

It seems that this event is triggered by MapEntries. This event handler is trigger org/apache/sling/api/resource/ResourceResolverMapping/CHANGED on each node creation under /var/eventing/jobs/assigned/...

Please see events log:

- Dispatcher Flush Agent enabled on publish instance.

- Dispatcher Flush Agent disabled on publish instance.

This events are appeared after activation of "/etc/tags/workflow/system" node.

 

It seems that org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event should NOT be triggered during activation.

We performed performance test with disabled CugSupportImpl component and see much better results.

Could someone comment such behavior?

Is it make sense to trigger each time org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event?

How can we avoid calls to CugSupportImpl#updateRegistration during dispatcher flush event?

Thanks,
Alex

1 Accepted Solution
MC_Stuff
Correct answer by
Level 9
Level 9

Hi Alex,

Make sure resource resolver bundle is greater than 1.5.14 will fix the issue. 

Thanks,

View solution in original post

1 Reply
MC_Stuff
Correct answer by
Level 9
Level 9

Hi Alex,

Make sure resource resolver bundle is greater than 1.5.14 will fix the issue. 

Thanks,