[
https://issues.apache.org/jira/browse/JCR-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Hendriks updated JCR-1148:
----------------------------------
Component/s: jackrabbit-core
Description:
The following happens quite regularly when multiple threads are adding,
retrieving and removing nodes simultaneously. Looking at the code of the pull
method, this seems due to under-synchronization somewhere as overlayedState was
tested at line 153 for null.
java.lang.NullPointerException
at org.apache.jackrabbit.core.state.ItemState.pull(ItemState.java:156)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.stateModified(LocalItemStateManager.java:421)
at
org.apache.jackrabbit.core.state.StateChangeDispatcher.notifyStateModified(StateChangeDispatcher.java:85)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.stateModified(SharedItemStateManager.java:434)
at
org.apache.jackrabbit.core.state.ItemState.notifyStateUpdated(ItemState.java:241)
at
org.apache.jackrabbit.core.state.ChangeLog.persisted(ChangeLog.java:271)
at
org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:741)
at
org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:937)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:327)
at
org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:313)
at
org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:303)
at
org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemStateManager.java:307)
at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1374)
Affects Version/s: 1.3
Summary: NullPointerException in ItemState (was: NullPoi)
> NullPointerException in ItemState
> ---------------------------------
>
> Key: JCR-1148
> URL: https://issues.apache.org/jira/browse/JCR-1148
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.3
> Reporter: Martijn Hendriks
>
> The following happens quite regularly when multiple threads are adding,
> retrieving and removing nodes simultaneously. Looking at the code of the pull
> method, this seems due to under-synchronization somewhere as overlayedState
> was tested at line 153 for null.
> java.lang.NullPointerException
> at org.apache.jackrabbit.core.state.ItemState.pull(ItemState.java:156)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.stateModified(LocalItemStateManager.java:421)
> at
> org.apache.jackrabbit.core.state.StateChangeDispatcher.notifyStateModified(StateChangeDispatcher.java:85)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager.stateModified(SharedItemStateManager.java:434)
> at
> org.apache.jackrabbit.core.state.ItemState.notifyStateUpdated(ItemState.java:241)
> at
> org.apache.jackrabbit.core.state.ChangeLog.persisted(ChangeLog.java:271)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:741)
> at
> org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:937)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:327)
> at
> org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:313)
> at
> org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:303)
> at
> org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemStateManager.java:307)
> at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1374)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.