You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Fred Moore (JIRA)" <ji...@apache.org> on 2010/01/14 16:36:43 UTC
[jira] Created: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
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
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.
[jira] Resolved: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-2568.
-----------------------------
Fix Version/s: 5.4.0
(was: 6.0.0)
Resolution: Fixed
Fixed by SVN revision 946600
> 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.
[jira] Assigned: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
Posted by "Candy Chiu (JIRA)" <ji...@apache.org>.
[ 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/%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.
[jira] Updated: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2568:
----------------------------
Fix Version/s: 5.4.0
> 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.
[jira] Updated: (AMQ-2568) Embedded broker not shutting down
cleanly because of lingering threads
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies updated AMQ-2568:
----------------------------
Fix Version/s: (was: 5.4.0)
6.0.0
There are a lot of references to the Scheuler - safer to defer this to 6.0
> 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: 6.0.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.