Jeroen van Erp created JCR-3468:
-----------------------------------
Summary: ConcurrentModificationException in BitSetENTCacheImpl
Key: JCR-3468
URL: https://issues.apache.org/jira/browse/JCR-3468
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 2.2.10
Reporter: Jeroen van Erp
Priority: Critical
Irregularly the following ConcurrentModificationException occurs in the logs of
our application, seems like there is either a sync missing, or a copy to a new
collection before iterating.
{noformat}
java.util.ConcurrentModificationException: null
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1100)
~[na:1.6.0_32]
at java.util.TreeMap$KeyIterator.next(TreeMap.java:1154) ~[na:1.6.0_32]
at
org.apache.jackrabbit.core.nodetype.BitSetENTCacheImpl.findBest(BitSetENTCacheImpl.java:114)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getEffectiveNodeType(NodeTypeRegistry.java:1082)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.getEffectiveNodeType(NodeTypeRegistry.java:508)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at org.apache.jackrabbit.core.NodeImpl.getEffectiveNodeType(NodeImpl.java:776)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at
org.apache.jackrabbit.core.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:826)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at org.apache.jackrabbit.core.ItemManager.getDefinition(ItemManager.java:255)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at org.apache.jackrabbit.core.ItemData.getDefinition(ItemData.java:101)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at
org.apache.jackrabbit.core.PropertyData.getPropertyDefinition(PropertyData.java:55)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at
org.apache.jackrabbit.core.PropertyImpl.internalGetValues(PropertyImpl.java:461)
~[jackrabbit-core-2.2.10.jar:2.2.10]
at org.apache.jackrabbit.core.PropertyImpl.getValues(PropertyImpl.java:498)
~[jackrabbit-core-2.2.10.jar:2.2.10]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
