[
https://issues.apache.org/jira/browse/TIKA-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346384#comment-17346384
]
Hudson commented on TIKA-3399:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk8 #234 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/234/])
fix for TIKA-3399 contributed by kamaci (#440) (github:
[https://github.com/apache/tika/commit/03a02b760e614c2fd6f5f004dd1b2db99d4024c9])
* (edit)
tika-batch/src/main/java/org/apache/tika/batch/fs/strawman/StrawManTikaAppDriver.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/TikaServerWatchDog.java
* (edit)
tika-batch/src/main/java/org/apache/tika/batch/FileResourceConsumer.java
* (edit) tika-xmp/src/main/java/org/apache/tika/xmp/convert/RTFConverter.java
* (edit)
tika-parsers/tika-parsers-ml/tika-parser-nlp-module/src/main/java/org/apache/tika/parser/journal/TEIDOMParser.java
> Fix Non-Atomic Operations on Volatile Fields
> --------------------------------------------
>
> Key: TIKA-3399
> URL: https://issues.apache.org/jira/browse/TIKA-3399
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.26
> Reporter: Furkan Kamaci
> Priority: Major
> Fix For: 2.0.0
>
>
> It is possible for the value of the volatile field at non-atomic operations
> to change between the read and the write, possibly invalidating the operation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
