activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes (Updated) (JIRA)" <>
Subject [jira] [Updated] (AMQ-3514) MessageListenerServlet does not clear the timer on destroy
Date Wed, 28 Sep 2011 16:10:47 GMT


Johannes updated AMQ-3514:

    Attachment: AMQ-3514_destroy_timer_on_shutdown.patch

Patch which clears the timer on destroy
> MessageListenerServlet does not clear the timer on destroy
> ----------------------------------------------------------
>                 Key: AMQ-3514
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.0
>            Reporter: Johannes
>            Priority: Trivial
>         Attachments: AMQ-3514_destroy_timer_on_shutdown.patch
> Hi, 
> we are debugging a shutdown problem using the activemq-web-console deployed into jetty.

> It seems as if everything is terminated as expected, apart from a TimerThread which logs
to the console about every minute. 
> 05 Jul 2011 09:03:19,246 DEBUG [Timer-1] org.apache.activemq.web.MessageListenerServlet.debug()
-- Cleaning up expired web clients. 
> Tracing down the problem indicated one possible cause. 
> The web-console package declares the AjaxServlet to send messages via the web to the
broker, it extends MessageListenerServlet. 
> The init() mehtod of the MessageListenerServlet schedules task 
>         clientCleanupTimer.schedule( new ClientCleaner(), 5000, 60000 ); 
> but the timer (clientCleanupTimer) is never canceled and according to the javadoc of
Timer this can prevent the JVM from shutting down cleanly. 
> Patch attached

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message