You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2020/11/15 18:36:00 UTC

[jira] [Closed] (JENA-824) Concurrent usage of query causes NPE

     [ https://issues.apache.org/jira/browse/JENA-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne closed JENA-824.
------------------------------

> 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
>            Assignee: Andy Seaborne
>            Priority: Major
>             Fix For: Jena 3.15.0
>
>
> 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
(v8.3.4#803005)