Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8275A200C7D for ; Tue, 2 May 2017 01:49:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 81164160BC3; Mon, 1 May 2017 23:49:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C8051160BC1 for ; Tue, 2 May 2017 01:49:07 +0200 (CEST) Received: (qmail 24640 invoked by uid 500); 1 May 2017 23:49:07 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 24628 invoked by uid 99); 1 May 2017 23:49:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 May 2017 23:49:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 92DF41B14CA for ; Mon, 1 May 2017 23:49:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 0Z-b0fY3cIDi for ; Mon, 1 May 2017 23:49:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 49B7C5FB29 for ; Mon, 1 May 2017 23:49:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 86BE6E0234 for ; Mon, 1 May 2017 23:49:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 46E6021DE2 for ; Mon, 1 May 2017 23:49:04 +0000 (UTC) Date: Mon, 1 May 2017 23:49:04 +0000 (UTC) From: "Anthony RAYMOND (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IO-535) FileAlterationMonitor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 01 May 2017 23:49:08 -0000 Anthony RAYMOND created IO-535: ---------------------------------- Summary: FileAlterationMonitor Key: IO-535 URL: https://issues.apache.org/jira/browse/IO-535 Project: Commons IO Issue Type: Bug Affects Versions: 2.5 Environment: Components managed by a DI Framework Reporter: Anthony RAYMOND Priority: Critical The thread if FileAlterationMonitor wasn't stopped by the `stop(int)` method, which forbid application to shutdown unless all `Thread` are exited (if FileAlterationMonitor is part of a DI managed component). This behavior conflict with the method javadoc `@param stopInterval the amount of time in milliseconds to wait for the thread to finish.` ### Simple exemple to understand ```java Thread t = new Thread(() -> { try { Thread.sleep(500000); } catch (final InterruptedException e) { } }); t.start(); t.join(50); // Ok, we reach this point until 500000ms are elapsed, but the thread is still alive. // because Thread#join(int) does not kill the thread. And the thread remains alive. ``` ```java Thread t = new Thread(() -> { try { Thread.sleep(500000); } catch (final InterruptedException e) { } }); t.start(); t.join(50); t.interupt(); // Thread is exited ``` In this case, we waited the given time BEFORE exiting the `Thread`, as described in the javadoc, and the `Thread` is now finished and killed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)