[
https://issues.apache.org/jira/browse/OAK-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363343#comment-14363343
]
Carsten Ziegeler commented on OAK-2609:
---------------------------------------
Just to be clear: I'm not encouraging the use of Thread.interrupt - in many
cases it can be replaced by a better way. However, as noted, I've seen a
Thread.interrupt call bringing down Oak and while I agree that replacing this
with something else is a better solution, I'm not sure about how practible this
is. If you own all the code in the world, you can do this.
Can this at least be catched somehow with a big log message?
> Thread.interrupt seems to stop repository
> -----------------------------------------
>
> Key: OAK-2609
> URL: https://issues.apache.org/jira/browse/OAK-2609
> Project: Jackrabbit Oak
> Issue Type: Bug
> Affects Versions: 1.1.7
> Environment: Java 7
> Reporter: Carsten Ziegeler
> Priority: Critical
> Fix For: 1.1.8, 1.0.13
>
>
> We have a sporadic problem with Sling's JCR installer 3.3.8 and Oak (tar mk).
> It seems to timing related: the JCR installer does a Thread#interrupt at one
> point and sometimes this brings the hole instance to stop. Nothing else is
> going on any more.
> While of course, a workaround is to remove the Thread.interrupt call in the
> JCR installer (which we did, see SLING-4477), I have the fear that this can
> happen with any code that is using the repository and gets interrupted.
> This error is hard to reproduce, however with three people testing we could
> see this several times happening
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
