You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/03/19 09:37:00 UTC
[jira] [Commented] (JENA-1866) SPARQLQueryProcessor: Need volatile
to make method thread-safe
[ https://issues.apache.org/jira/browse/JENA-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062400#comment-17062400 ]
ASF subversion and git services commented on JENA-1866:
-------------------------------------------------------
Commit 89edba32859c3653a75f5ae580e3a5563c14d82c in jena's branch refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=89edba3 ]
Merge pull request #709 from intrigus-lgtm/patch-1
JENA-1866: Add volatile to make method thread-safe
> SPARQLQueryProcessor: Need volatile to make method thread-safe
> --------------------------------------------------------------
>
> Key: JENA-1866
> URL: https://issues.apache.org/jira/browse/JENA-1866
> Project: Apache Jena
> Issue Type: Task
> Components: Fuseki
> Affects Versions: Jena 3.14.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.15.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This ticket tracks https://github.com/apache/jena/pull/709 ("intrigus-lgtm" on GitHub).
> There needs to be a "happens before" barrier so that any Set and the objects it contains created by {{generateAcceptedParams()}} is completed and available to other threads.
> Making {{acceptedParams_}} volatile achieves this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)