[
https://issues.apache.org/jira/browse/MARMOTTA-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625929#comment-13625929
]
Peter Ansell commented on MARMOTTA-191:
---------------------------------------
It isn't the cause, it is just the reason for it happening on maven but not in
other systems. The reasoning is that java.lang.AssertionError should not occur
at runtime if you haven't enabled it with "-ea".
I am not familiar with the internals of MemoryStore so you would need to bring
the issue up on the sesame mailing list or Jira tracker to get a description of
why the assertion is there, and what could be the cause. I have never seen that
assertion triggered in my 6 or so years of using of MemoryStore with Sesame2,
but I typically do everything inside of a transaction, so that may be a factor
here.
> SPARQL graph results fails under some circunstances
> ---------------------------------------------------
>
> Key: MARMOTTA-191
> URL: https://issues.apache.org/jira/browse/MARMOTTA-191
> Project: Marmotta
> Issue Type: Bug
> Components: Platform
> Affects Versions: 2.6, 3.0-incubating
> Reporter: Sergio Fernández
> Assignee: Sergio Fernández
> Priority: Minor
> Fix For: 3.1-incubating
>
>
> Write some unit tests:
> https://git-wip-us.apache.org/repos/asf?p=incubator-marmotta.git;a=blob;f=platform/marmotta-sparql/src/test/java/org/apache/marmotta/platform/sparql/webservices/SparqlWebServiceTest.java;h=06d03ebdcbcdec8cdf33e4ae975383ee6c2332bf;hb=HEAD#l91
> I realized the SPARQL Graph results fails:
> java.lang.AssertionError: Created a duplicate MemURI for URI
> http://www.wikier.org/foaf#wikier
> at
> org.openrdf.sail.memory.model.MemValueFactory.getOrCreateMemURI(MemValueFactory.java:281)
> at
> org.openrdf.sail.memory.model.MemValueFactory.getOrCreateMemResource(MemValueFactory.java:247)
> at
> org.openrdf.sail.memory.MemoryStore.addStatement(MemoryStore.java:538)
> at
> org.openrdf.sail.memory.MemoryStoreConnection.addStatementInternal(MemoryStoreConnection.java:441)
> at
> org.openrdf.sail.memory.MemoryStoreConnection.addStatementInternal(MemoryStoreConnection.java:395)
> at
> org.openrdf.sail.helpers.SailConnectionBase.addStatement(SailConnectionBase.java:441)
> at
> org.openrdf.repository.sail.SailRepositoryConnection.addWithoutCommit(SailRepositoryConnection.java:281)
> at
> org.openrdf.repository.base.RepositoryConnectionBase.addWithoutCommit(RepositoryConnectionBase.java:561)
> at
> org.openrdf.repository.base.RepositoryConnectionBase.add(RepositoryConnectionBase.java:433)
> at
> org.apache.marmotta.platform.sparql.services.sparqlio.rdf.SPARQLGraphResultWriter.write(SPARQLGraphResultWriter.java:68)
> at
> org.apache.marmotta.platform.sparql.services.sparql.SparqlServiceImpl.query(SparqlServiceImpl.java:195)
> at
> org.apache.marmotta.platform.sparql.services.sparql.SparqlServiceImpl.query(SparqlServiceImpl.java:108)
> at
> org.apache.marmotta.platform.sparql.services.sparql.SparqlServiceImpl$Proxy$_$$_WeldClientProxy.query(SparqlServiceImpl$Proxy$_$$_WeldClientProxy.java)
> at
> org.apache.marmotta.platform.sparql.webservices.SparqlWebService$1.write(SparqlWebService.java:485)
> But I'm not totally sure it's actually a bug, either on our side or in
> Sesame, because I cannot easily reproduce it on all environments: it works
> fine at runtime and from junit at eclipse, but it fails from maven.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
