tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Commented: (TAPESTRY-223) Offer cleanup method to JanitorThread
Date Wed, 10 Nov 2004 14:21:24 GMT
     [ http://nagoya.apache.org/jira/browse/TAPESTRY-223?page=comments#action_55300 ]
Howard M. Lewis Ship commented on TAPESTRY-223:

Thanks for the patch; Tapestry 3.1 removes the Janitor concept (at least for the meantime).
 It will probably come back in some form, but we'll be sure to get the thread to shut down
when the HiveMind Registry is shutdown (i.e., during undeployment).

> Offer cleanup method to JanitorThread
> -------------------------------------
>          Key: TAPESTRY-223
>          URL: http://nagoya.apache.org/jira/browse/TAPESTRY-223
>      Project: Tapestry
>         Type: Improvement
>   Components: Framework
>     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.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

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

View raw message