Application slowed in JackRabbit CachingEntryCollector

Solution Verified - Updated -

Issue

  • JBoss becomes unresponsive and our thread pools are exhausted in calls like the following:
   java.lang.Thread.State: BLOCKED (on object monitor)
    at org.apache.jackrabbit.core.security.authorization.acl.CachingEntryCollector.getEntries(CachingEntryCollector.java:95)
    - waiting to lock <0x000000058c050be8> (a java.lang.Object)
    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:264)
    - locked <0x00000005b7b77f30> (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:843)
    at org.apache.jackrabbit.core.ItemManager.getItemData(ItemManager.java:391)
    at org.apache.jackrabbit.core.ItemManager.itemExists(ItemManager.java:304)
    at org.apache.jackrabbit.core.ItemManager.itemExists(ItemManager.java:523)
    at org.apache.jackrabbit.core.NodeImpl.hasProperty(NodeImpl.java:2403)

Environment

  • JBoss Enterprise Application Platform (EAP)
  • Apache JackRabbit

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content