You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/07/07 21:34:00 UTC

[jira] Assigned: (AMQ-1839) There's no way to stop thread spawned by org.apache.activemq.thread.Scheduler

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

Rob Davies reassigned AMQ-1839:
-------------------------------

    Assignee: Rob Davies

> There's no way to stop thread spawned by org.apache.activemq.thread.Scheduler
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-1839
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1839
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Roman Puchkovskiy
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>         Attachments: AMQ-shutting-scheduler-down.patch
>
>
> When ActiveMQ is unloaded (for instance, if it was loaded by a web-application from its WEB-INF/lib), a timer thread spawned by Scheduler still remains in memory, which prevents a classloader to be unloaded. There's no any way to stop the timer explicitly.
> Attaching a patch which adds a shutdown method which may be called when ActiveMQ is unloaded.

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