sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothee Maret (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-9340) Don’t use Thread.interrupt()
Date Tue, 07 Apr 2020 21:40:00 GMT

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

Timothee Maret resolved SLING-9340.
-----------------------------------
    Resolution: Fixed

Done in [fe471d6d2158d70b74197499cf6a66132f3ab5e7|https://github.com/apache/sling-org-apache-sling-distribution-journal/commit/fe471d6d2158d70b74197499cf6a66132f3ab5e7].

> Don’t use Thread.interrupt()
> ----------------------------
>
>                 Key: SLING-9340
>                 URL: https://issues.apache.org/jira/browse/SLING-9340
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>    Affects Versions: Content Distribution Journal Core 0.1.0
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.12
>
>
> Interrupt don't play well with Oak and can trigger stopping the repository, see OAK-2609.
The Oak team documents to not use interrupt in 
>     https://jackrabbit.apache.org/oak/docs/dos_and_donts.html
> Distribution journal code leverages interrupt at multiple places. This issue is about
avoiding interruption in favour of running flags.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message