[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Philipp Bracher (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841907#action_12841907
 ] 

Philipp Bracher commented on JCR-1440:
--

Dear sender,

Due to marriage I have taken a new surname. Please use in future my new email 
address which is philipp.baerf...@gmx.ch.

A copy of this mail has already been sent to the new account.

Have a nice day!

Philipp Bärfuss


-- 
Diese E-Mail wurde automatisch als Antwort auf Ihre Nachricht verschickt, da 
der Empfänger Ihrer E-Mail seine GMX Abwesenheitsschaltung aktiviert hat. Sie 
erhalten diese Benachrichtigung auch bei mehreren E-Mails nur ein Mal pro 
Woche. 

GMX ist eine eingetragene Marke der GMX GmbH. 


> 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 Content Repository
>  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
>Assignee: Jukka Zitting
>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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Jukka Zitting (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841903#action_12841903
 ] 

Jukka Zitting commented on JCR-1440:


In revision 919461 I added automatic invalidation of the internal version 
history caches based on related update events from other cluster nodes. This 
still needs some testing, but ideally I'd like to get rid of the previous 
double-load solution.

> 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 Content Repository
>  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
>Assignee: Jukka Zitting
>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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Jukka Zitting (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835807#action_12835807
 ] 

Jukka Zitting commented on JCR-1440:


I'm sorry about the long inaction on this issue.

I've now committed Ryan's patch, as it seems to solve the immediate issue. The 
solution however seems a bit hacky and reminds me of the double-checked locking 
antipattern. It would be better if the caches were loaded only on-demand and 
correctly invalidated on cluster changes. Or perhaps we could drop the version 
history caches entirely, as the underlying item state managers should already 
take care of the performance impact.

> 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 Content Repository
>  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
>Assignee: Jukka Zitting
>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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Philipp Bracher (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835761#action_12835761
 ] 

Philipp Bracher commented on JCR-1440:
--

Dear sender,

Due to marriage I have taken a new surname. Please use in future my new email 
address which is philipp.baerf...@gmx.ch.

A copy of this mail has already been sent to the new account.

Have a nice day!

Philipp Bärfuss


-- 
Diese E-Mail wurde automatisch als Antwort auf Ihre Nachricht verschickt, da 
der Empfänger Ihrer E-Mail seine GMX Abwesenheitsschaltung aktiviert hat. Sie 
erhalten diese Benachrichtigung auch bei mehreren E-Mails nur ein Mal pro 
Woche. 

GMX ist eine eingetragene Marke der GMX GmbH. 


> 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 Content Repository
>  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
>Assignee: Jukka Zitting
>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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Philipp Bracher (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727569#action_12727569
 ] 

Philipp Bracher commented on JCR-1440:
--

Dear sender,

Due to marriage I have taken a new surname. Please use in future my new email 
address which is philipp.baerf...@gmx.ch.

A copy of this mail has already been sent to the new account.

Have a nice day!

Philipp Bärfuss


-- 
Diese E-Mail wurde automatisch als Antwort auf Ihre Nachricht verschickt, da 
der Empfänger Ihrer E-Mail seine GMX Abwesenheitsschaltung aktiviert hat. Sie 
erhalten diese Benachrichtigung auch bei mehreren E-Mails nur ein Mal pro 
Woche. 

GMX ist eine eingetragene Marke der GMX GmbH. 


> 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 Content Repository
>  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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727557#action_12727557
 ] 

Micah Whitacre commented on JCR-1440:
-

What can someone do to help this issue be resolved?  A patch and junit have 
been supplied a long time ago.  What else is needed for this to be resolved for 
one of the official releases?

> 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 Content Repository
>  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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632294#action_12632294
 ] 

Micah Whitacre commented on JCR-1440:
-

I applied Ryan's patch to trunk and it fixed the NPE being thrown.

> 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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598468#action_12598468
 ] 

Micah Whitacre commented on JCR-1440:
-

Ryan's patch fixes the issue I was seeing.  I agree it isn't necessarily the 
most elegant solution.  Can someone review his patch and commit it to trunk or 
perhaps propose a better solution?  Thanks.

> 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: 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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582058#action_12582058
 ] 

Micah Whitacre commented on JCR-1440:
-

It should also be noted that this is not purely related to removing nodes.  
I've changed the test around so the two nodes are adding independent child 
nodes to the root and it causes the same NPE exception to be thrown when trying 
to find the item at the item for the given id.

> 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: 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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582054#action_12582054
 ] 

Micah Whitacre commented on JCR-1440:
-

I'm still trying to find a workaround or solution to this issue.  Looking at 
the code the issues comes from the fact that the map, versionItems, of 
VersionManagerImpl class is never updated/syncrhonized between the two cluster 
nodes.  The only time this method is changed is on calls to 
itemsUpdated(Collection) which is never called during the synchronization 
process.  So that map becomes stale pretty quickly when multiple nodes are 
interacting with it.

> 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: 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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Micah Whitacre (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575431#action_12575431
 ] 

Micah Whitacre commented on JCR-1440:
-

I changed PMs and the Clustering to use the org.apache.derby.jdbc.Driver30 and 
I still get the same exception.

You mentioned that the PMs needed to use a shared datasource.  What additional 
configuration is needed for me to be able to do that?  Do I need to configure a 
DataSource[1] at the top of the  configuration?  I've been using 
the Clustering[2] wiki page as my guide and it doesn't show any special 
configuration for using the OraclePersistenceManager.  I'm actually seeing this 
issue when hitting an Oracle database.  I just used an embedded derby database 
for this example/tests.  

[1] - http://wiki.apache.org/jackrabbit/DataStore
[2] - http://wiki.apache.org/jackrabbit/Clustering

> 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
>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: 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.

[jira] Commented: (JCR-1440) NPE Thrown when two Cluster Nodes are hitting the same underlying database.

[Dominique Pfister (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575280#action_12575280
 ] 

Dominique Pfister commented on JCR-1440:


Clustering in jackrabbit requires persistence managers that connect to a shared 
datasource. I noticed that the persistence managers in your repository.xml use 
the embedded Derby JDBC driver, which will not work in a clustered setup. Did 
you try switching to Derby in standalone mode?

> 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
>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: 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.