You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/06/20 17:58:26 UTC

[jira] Closed: (TAPESTRY-223) Offer cleanup method to JanitorThread

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

Jesse Kuhnert closed TAPESTRY-223.
----------------------------------

    Resolution: Won't Fix

> Offer cleanup method to JanitorThread
> -------------------------------------
>
>                 Key: TAPESTRY-223
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-223
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 3.0.1
>            Reporter: Cherry Development
>            Priority: Minor
>
> There is no way to stop the JanitorThread from running.  When a web application using one gets stopped and re-started, it leaks a thread.  I believe, ideally, the TapestryServlet's destroy() method should stop the shared JanitorThread.  At the very least, the JanitorThread class should have some sort of method on it to request it to stop.  This enhancement should require a dozen lines of code at the very most to implement.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org