[ 
https://issues.apache.org/jira/browse/JENA-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874726#comment-15874726
 ] 

Alexis Armin Huf commented on JENA-1290:
----------------------------------------

Thanks for the assistance with the build.

I had the same problem with the full -Pbootstrap at the jena root project and 
building just jena-arq.  Tried the full build on the oficial sources for 3.2.0 
and the module build on a git clone (the mvn-clean-install-arq.log.gz 
attachment). I also downgraded mave to 3.3.3 (the oldest version I had on my 
system's cache). The boot classpath on the logs seems right and the jena-core 
jar has the not found classes. Also changed the MWE project to depend directly 
on jena-core-3.0.0-SNAPSHOT and it worked.

Setting {{JenaSystem.DEBUG_INIT = true}}  
(mvn-clean-install-arq-JenaSystem.log.gz) got me the following:
{noformat}
Running org.apache.jena.query.TS_ParamString
JenaSystem.init - start
Found:
  InitRIOT             [20]
  InitARQ              [30]
  InitJenaCore         [10]
Initialization sequence:
  JenaInitLevel0       [0]
  InitJenaCore         [10]
  InitRIOT             [20]
  InitARQ              [30]
Init: JenaInitLevel0
Init: InitJenaCore
JenaCore.init - start
JenaCore.init - finish
Init: InitRIOT
RIOT.init - start
RIOT.init - finish
Init: InitARQ
ARQ.init - start
Tests run: 140, Failures: 0, Errors: 140, Skipped: 0, Time elapsed: 0.409 sec 
<<< FAILURE! - in org.apache.jena.query.TS_ParamString
test_param_string_injection_01(org.apache.jena.query.TestParameterizedSparqlString)
  Time elapsed: 0.338 sec  <<< ERROR!
java.lang.Exception: Unexpected exception, 
expected<org.apache.jena.sparql.ARQException> but 
was<java.lang.ExceptionInInitializerError>
        at 
org.apache.jena.query.TestParameterizedSparqlString.test_param_string_injection_01(TestParameterizedSparqlString.java:1382)
Caused by: java.lang.NullPointerException
        at 
org.apache.jena.query.TestParameterizedSparqlString.test_param_string_injection_01(TestParameterizedSparqlString.java:1382)

test_param_string_injection_02(org.apache.jena.query.TestParameterizedSparqlString)
  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: Unexpected exception, 
expected<org.apache.jena.sparql.ARQException> but 
was<java.lang.NoClassDefFoundError>
        at 
org.apache.jena.query.TestParameterizedSparqlString.test_param_string_injection_02(TestParameterizedSparqlString.java:1393)
{noformat}

Later tonight I will try get closer to the cause, any hints are welcome.

> Slow Model.createList()
> -----------------------
>
>                 Key: JENA-1290
>                 URL: https://issues.apache.org/jira/browse/JENA-1290
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: Jena 3.0.1, Jena 3.2.0
>         Environment: OpenJDK 1.8.0.121-b13
>            Reporter: Alexis Armin Huf
>            Priority: Minor
>         Attachments: JENA-1290.patch, jena-slow-rdflist.tar.gz, 
> mvn-clean-install-arq-JenaSystem.log.gz, mvn-clean-install-arq.log.gz, 
> mvn-clean-install.log.gz
>
>
> Model.createList(Iterator) is slow for large list sizes. Starting at 128 
> nodes, creating a list from an ArrayList iterator takes ~3.6ms and the time 
> goes up to 182ms for 1024 nodes. Creating the RDF list by hand and then doing 
> .as(RDFList.class) for the 1024-nodes tests takes only 1.2ms. I will attach a 
> MWE.
> Going through the code, the cause seems to be that RDFListImpl.with() , which 
> is called for every member added, will always walk the entire list to get the 
> last node. It mentions a possible cache for that, but it is not implemented. 
> I wrote a patch for this issue replacing ModelCom.createList() 
> implementation. I could not find tests for createList, so I added three 
> simple ones to TestModel.
> PS: I'm having a classpath issue with jena-arq tests on mvn clean install, so 
> I could only run tests for jena-core. Are there more specific instructions 
> somewhere for building and testing jena?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to