Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1128227730.2881263565363559.JavaMail.jira@brutus.apache.org>
Date: Fri, 15 Jan 2010 14:22:43 +0000 (UTC)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Assigned: (AMQ-2568) Embedded broker not shutting down
 cleanly because of lingering threads
In-Reply-To: <1416057131.1721263483403778.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Rob Davies reassigned AMQ-2568:
-------------------------------

    Assignee: Rob Davies

> Embedded broker not shutting down cleanly because of lingering threads
> ----------------------------------------------------------------------
>
>                 Key: AMQ-2568
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2568
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMX
>    Affects Versions: 5.3.0
>         Environment: Windows
>            Reporter: Fred Moore
>            Assignee: Rob Davies
>             Fix For: 5.4.0
>
>
> See also this thread: http://mail-archives.apache.org/mod_mbox/activemq-users/201001.mbox/%3C4E50CAAD-0600-46FB-B5D0-B623C21A362D@gmail.com%3E
> See also this bug: http://issues.apache.org/activemq/browse/AMQ-1214
> ========================
> we have a 5.3.0 embedded broker that refuses to shutdown cleanly because of lingering threads. A long time (dozens of seconds) after broker stop() is called,  these threads are still active:
> * [ActiveMQ Scheduler] (Daemon) Group: main
> * [Timer-0] (Daemon) Group: main
> We discovered that [ActiveMQ Scheduler] can be closed adding this snippet to our code:
> Scheduler scheduler = Scheduler.getInstance();
> scheduler.shutdown();
> After doing this the other lingering thread -- "[Timer-0]" -- did not go away, but at least we discovered that this timer is JMX related: if we disable JMX connector the timer disappear.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.