[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Micah Whitacre updated JCR-1440:
--------------------------------

    Attachment: jackrabbit-1.5-JCR-1440.tar.gz

While coding against the 1.5-SNAPSHOT I started seeing a different exception 
being logged[1].  The attachment includes the same test that was previously 
attached (but modified to run on linux) and it will reliably produce the stack 
trace.  The two repository.xml files were updated to support the newer security 
configuration needed as well.  I have not tried applying Ryan's patch yet to 
see if it fixes this issue.

Could someone look at/comment on the patch?  It would be nice if this fix could 
make it into an upcoming release like 1.4.6 but if not maybe the 1.5.  Thanks.

[1]
java.lang.NullPointerException
        at 
org.apache.jackrabbit.core.version.AbstractVersionManager.calculateCheckinVersionName(AbstractVersionManager.java:458)
        at 
org.apache.jackrabbit.core.version.AbstractVersionManager.checkin(AbstractVersionManager.java:392)
        at 
org.apache.jackrabbit.core.version.VersionManagerImpl$2.run(VersionManagerImpl.java:280)
        at 
org.apache.jackrabbit.core.version.VersionManagerImpl$DynamicESCFactory.doSourced(VersionManagerImpl.java:563)
        at 
org.apache.jackrabbit.core.version.VersionManagerImpl.checkin(VersionManagerImpl.java:276)
        at 
org.apache.jackrabbit.core.version.XAVersionManager.checkin(XAVersionManager.java:155)
        at org.apache.jackrabbit.core.NodeImpl.checkin(NodeImpl.java:3309)
        at 
com.cerner.system.configuration.repository.jcr.SimpleJackrabbitConflictTest.testNullPointerExceptionThrown(SimpleJackrabbitConflictTest.java:105)

> NPE Thrown when two Cluster Nodes are hitting the same underlying database.
> ---------------------------------------------------------------------------
>
>                 Key: JCR-1440
>                 URL: https://issues.apache.org/jira/browse/JCR-1440
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: clustering, jackrabbit-core
>    Affects Versions: 1.4, core 1.4.1
>         Environment: Vista JDK 1.5.0_12.  Using Derby and Derby Client 
> 10.1.2.1
>            Reporter: Micah Whitacre
>            Priority: Critical
>         Attachments: jackrabbit-1.5-JCR-1440.tar.gz, 
> jcr-1440-workaround.patch, repository1.xml, 
> SimpleJackrabbitConflictTest.java, SimpleJackRabbitTest.zip
>
>
> I've created a test that creates two repositories with clustering enabled 
> that are backed by the same database.  Using the following workflow causes a 
> NullPointerException to be thrown.
> The workflow I'm using is:
> The root node is versioned.
> ClusterNode1 creates a versioned child node named "foo".
> The test waits to make sure the syncDelay has passed so ClusterNode2 will 
> notice the newly created node.
> ClusterNode2 retrieves the "foo" child node and removes it.
> The test waits for the change ClusterNode1 to sync with that change.
> ClusterNode1 tries to create another new node however a NullPointerException 
> is thrown when the it tries to checkout the rootNode.
> java.lang.NullPointerException: null values not allowed
>       at 
> org.apache.commons.collections.map.AbstractReferenceMap.put(AbstractReferenceMap.java:251)
>       at 
> org.apache.jackrabbit.core.version.VersionManagerImpl.getItem(VersionManagerImpl.java:280)
>       at 
> org.apache.jackrabbit.core.version.XAVersionManager.getItem(XAVersionManager.java:334)
>       at 
> org.apache.jackrabbit.core.version.AbstractVersionManager.getVersion(AbstractVersionManager.java:87)
>       at 
> org.apache.jackrabbit.core.NodeImpl.getBaseVersion(NodeImpl.java:3198)
>       at org.apache.jackrabbit.core.NodeImpl.checkout(NodeImpl.java:2991)
>       at 
> com.cerner.system.configuration.repository.jcr.SimpleJackrabbitConflictTest.testNullPointerExceptionThrown(SimpleJackrabbitConflictTest.java:96)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to