[
https://issues.apache.org/jira/browse/JENA-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235388#comment-14235388
]
Kristian Rosenvold commented on JENA-824:
-----------------------------------------
But "seal" is supposed to come "after" create, I assume - to allow the user to
/do/ things with the object before sealing it ?
We'd be looking at something like this, I assume:
Query q1 = QueryFactory.parse(...)
q1.setStuff();
q1.seal();
Send q1 off to execution
Alternately the object could come readily "sealed" out of the QueryFactory ?
> Concurrent usage of query causes NPE
> ------------------------------------
>
> Key: JENA-824
> URL: https://issues.apache.org/jira/browse/JENA-824
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Kristian Rosenvold
>
> Callin gQueryFactory.parse and then handling the Query off to multiple
> threads can/will cause the error show in the stacktrace.
> As long as setResultVars is called on the Query before handing off to
> threads, it seems to be safe.
> Pull request is coming on this.
> java.lang.NullPointerException
> at com.hp.hpl.jena.sparql.core.Var.varNames(Var.java:193)
> at com.hp.hpl.jena.query.Query.getResultVars(Query.java:369)
> at
> com.hp.hpl.jena.sparql.engine.QueryExecutionBase.asResultSet(QueryExecutionBase.java:470)
> at
> com.hp.hpl.jena.sparql.engine.QueryExecutionBase.execResultSet(QueryExecutionBase.java:533)
> at com.hp.hpl.jena.sparql.engine.QueryExecutionBase.execSelect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
