[ https://issues.apache.org/jira/browse/JCR-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611170#action_12611170 ]
Micah Whitacre commented on JCR-1670: ------------------------------------- The stack trace and use case seems similar to JCR-1440. > NPE when clustered JR queries version history on a node that has just had a > version added by another JR in the same cluster > --------------------------------------------------------------------------------------------------------------------------- > > Key: JCR-1670 > URL: https://issues.apache.org/jira/browse/JCR-1670 > Project: Jackrabbit > Issue Type: Bug > Components: clustering > Affects Versions: core 1.4.3 > Environment: Windows XP servers, JDK 1.5.2.02, in process. Microsoft > SQL 2005 bundled persistence manager, datastore. > Reporter: Brett Connor > Priority: Critical > > Two computers A and B running jboss webapp, including in-process Jackrabbit > instances in a cluster. > - A checks out a versioned node, then checks it in and unlocks it > - A notifies B (through a non JR mechanism) that the node has been updated > - B finds the node (by UUID) and calls getVersionHistory().getAllVersions() > This results in java.lang.NullPointerException > at > org.apache.jackrabbit.core.version.VersionIteratorImpl.addVersion(VersionIteratorImpl.java:147) > at org.apache.jackrabbit.core.version.VersionIteratorImpl. > (VersionIteratorImpl.java:68) > at > org.apache.jackrabbit.core.version.VersionHistoryImpl.getAllVersions(VersionHistoryImpl.java:95) > The addVersion() method is synchronized, but looks like it's reading a null > from 'successors'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.