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 GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/14 12:19:00 UTC
[jira] [Commented] (JENA-1651) Improve the TDB internal consistency
checking for safe replay.
[ https://issues.apache.org/jira/browse/JENA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721339#comment-16721339 ]
ASF GitHub Bot commented on JENA-1651:
--------------------------------------
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/509
JENA-1651: Specific counter for tracking active transactions.
This only happens occasionally even under high update load and is harmless, only leading to a spurious log message.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena tdb1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/509.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #509
----
commit 124c7c631dd6b668b79d8628269aae8a56122b4b
Author: Andy Seaborne <an...@...>
Date: 2018-12-14T12:16:13Z
JENA-1651: Specific counter for tracking active transactions.
----
> Improve the TDB internal consistency checking for safe replay.
> --------------------------------------------------------------
>
> Key: JENA-1651
> URL: https://issues.apache.org/jira/browse/JENA-1651
> Project: Apache Jena
> Issue Type: Task
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> {{TransactionManager.checkReplaySafe}} reads two AtomicLongs but updated to these aren't coordinated so for a short time, they can be out of step. Updates happen just outside the true transaction start-finish in {{TSM_Counters}}.
> There should be one atomic operation to note whether there are active transaction or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)