[ http://issues.apache.org/jira/browse/TAPESTRY-223?page=all ]
Jesse Kuhnert updated TAPESTRY-223:
-----------------------------------
Fix Version/s: 3.0.5
> Offer cleanup method to JanitorThread
> -------------------------------------
>
> Key: TAPESTRY-223
> URL: http://issues.apache.org/jira/browse/TAPESTRY-223
> Project: Tapestry
> Issue Type: Improvement
> Components: Framework
> Affects Versions: 3.0.1
> Reporter: Cherry Development
> Priority: Minor
> Fix For: 3.0.5
>
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
