[
https://issues.apache.org/activemq/browse/AMQ-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59480#action_59480
]
Candy Chiu commented on AMQ-2568:
---------------------------------
Is this related to the "ActiveMQ Data File Writer" thread not being cleaned up?
This thread is keeping the Java VM from exiting even after I called
Scheduler.getInstance().shutdown().
> 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/%[email protected]%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.
