10:56 a.m.
[
https://jira.jboss.org/jira/browse/DNA-505?page=com.atlassian.jira.plugin...
]
Luiz Fernando Teston commented on DNA-505:
------------------------------------------
Randall, I did some stress tests on Svn connector. The stress tests are pretty the same as
the commited test. The only difference i in this stress test I have a visitor to get the
file content for all valid files inside the jcr repository. I did the same test on File
system connector and it worked well.
So, during the visiting I got this NPE:
Caused by: java.lang.NullPointerException
at org.jboss.dna.jcr.SessionCache.createPropertyInfo(SessionCache.java:2058)
at org.jboss.dna.jcr.SessionCache$JcrNodeOperations.materialize(SessionCache.java:2282)
at org.jboss.dna.graph.session.GraphSession$Node.load(GraphSession.java:1418)
at org.jboss.dna.graph.session.GraphSession$Node.getPayload(GraphSession.java:2624)
at org.jboss.dna.jcr.AbstractJcrNode.getNodes(AbstractJcrNode.java:645)
at
org.openspotlight.federation.data.util.JcrNodeVisitor$VisitorSupport.fillChildren(JcrNodeVisitor.java:158)
at
org.openspotlight.federation.data.util.JcrNodeVisitor$VisitorSupport.fillQueue(JcrNodeVisitor.java:196)
at org.openspotlight.federation.data.util.JcrNodeVisitor.visit(JcrNodeVisitor.java:294)
... 28 more
The line who fires this NPE is a simple Jcr iterator like: final NodeIterator nodeIterator
= n.getNodes();
If you like I can prepare a new test to put on this issue.
Svn Repository Source with NPE and other issues while opening
connection through Jcr
------------------------------------------------------------------------------------
Key: DNA-505
URL: https://jira.jboss.org/jira/browse/DNA-505
Project: DNA
Issue Type: Bug
Components: Connectors
Affects Versions: 0.6
Environment: Mac OS X 10.5 - Jvm 1.5 - Maven 2
Reporter: Luiz Fernando Teston
Assignee: Randall Hauch
Fix For: 0.6
Attachments: 0001-fixing-a-few-null-pointer-exeptions.patch,
DnaSvnUsingJcrWithProgramaticConfigurationTest.java
Durring a test run to read data from some svn repository using Jcr api from DNA, it
throws NullPointerException when trying to read jcr:content for nodes of type folder. This
NPEs was really easy to solve. So, I created a patch for this. After this patch, when
running the same unit test, it throws a repository source exception saying
"svnRepositorySource does not allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java""
workspace".
The stack trace is here also:
org.jboss.dna.graph.connector.RepositorySourceException: svnRepositorySource does not
allow same name siblings on nodes: read children of
/{http://www.jcp.org/jcr/1.0}content[2] in the
""http://hamcrest.googlecode.com/svn/trunk/hamcrest-java"" workspace
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.checkThePath(SVNRepositoryRequestProcessor.java:1000)
at
org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:151)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:641)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:239)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
at
org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
at
org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:176)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
at
org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:314)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:613)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira