Highlighted

CQ 5.6 , Thread Blocked/CPU Utilization issue

Avatar

Avatar

vivekk75439140

Avatar

vivekk75439140

vivekk75439140

05-03-2018

Hi,

I am facing thread block issue on CQ 5.6, where 100 threads are blocked all waiting for the follwing thread to finish. This is happening after every dispatcher cleanup.

Could you please help me to identify the root cause of this and how to resolve this issue.

10.236.16.8 [1519387176366] GET <path omitted >writing-instruments.filter.html HTTP/1.1

Stack Trace is:

java.lang.Thread.State: BLOCKED (on object monitor)

at org.apache.jackrabbit.spi.commons.conversion.GenerationalCache.put(GenerationalCache.java:137)

- locked <0x000000067de65c00> (a org.apache.jackrabbit.spi.commons.conversion.GenerationalCache)

at org.apache.jackrabbit.spi.commons.conversion.CachingPathResolver.getJCRPath(CachingPathResolver.java:121)

at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getJCRPath(DefaultNamePathResolver.java:90)

at org.apache.jackrabbit.core.SessionImpl.getJCRPath(SessionImpl.java:644)

at org.apache.jackrabbit.core.security.authorization.acl.EntryFilterImpl$1.getPath(EntryFilterImpl.java:50)

at org.apache.jackrabbit.core.security.authorization.acl.EntryFilterImpl.getPath(EntryFilterImpl.java:124)

at org.apache.jackrabbit.core.security.authorization.acl.EntryFilterImpl.matches(EntryFilterImpl.java:111)

at org.apache.jackrabbit.core.security.authorization.acl.EntryFilterImpl.filterEntries(EntryFilterImpl.java:83)

at org.apache.jackrabbit.core.security.authorization.acl.EntryCollector.filterEntries(EntryCollector.java:173)

at org.apache.jackrabbit.core.security.authorization.acl.EntryCollector.collectEntries(EntryCollector.java:148)

at org.apache.jackrabbit.core.security.authorization.acl.CompiledPermissionsImpl.canRead(CompiledPermissionsImpl.java:263)

- locked <0x00000006ce795a58> (a java.lang.Object)

at org.apache.jackrabbit.core.security.DefaultAccessManager.canRead(DefaultAccessManager.java:265)

at org.apache.jackrabbit.core.ItemManager.canRead(ItemManager.java:438)

at org.apache.jackrabbit.core.ItemManager.createItemData(ItemManager.java:848)

at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:391)

at org.apache.jackrabbit.core.ItemManager.getNode(ItemManager.java:669)

- eliminated <0x00000006ce78b580> (a org.apache.jackrabbit.core.ItemManager)

Thanks,

Vivek Kumar

Replies

Highlighted

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

05-03-2018

AEM 5.6 is very old and there has been many improvements to Dispatcher since them. I assume many community member are past 5.6 as well as 5.6 is no longer supported according to the docs. Let see if other community members on 5.6 address this thread.

Highlighted

Avatar

Avatar

MC_Stuff

Avatar

MC_Stuff

MC_Stuff

05-03-2018

Hi Vivek,

  The problem description & stack trace does not match. Sounds you are snipping the actual piece of it.   Because AFAIK there is no out of the box selecter filter.   In any case you can try following

CacheEntryCollector cache size is too small

Thanks,