|
|
[
http://issues.apache.org/jira/browse/TAPESTRY-230?page=comments#action_59271 ]
Nicholas Stuart commented on TAPESTRY-230:
------------------------------------------
I've just tried version 3.0.2 on Windows Server 2003 and Tomcat 5.5.4 and the
issue is still there. I am unable to reload the context because the Tapestry
and Tapestry-Contrib jars are still locked, and can not be deleted until I
manually stop tomcat and delete the files by hand.
> Ignored interruptedException prevents Janitorthread termination
> ---------------------------------------------------------------
>
> Key: TAPESTRY-230
> URL: http://issues.apache.org/jira/browse/TAPESTRY-230
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 3.0, 3.0.1
> Environment: Tomcat 4 & 5 (on Windows platform)
> Reporter: Martijn Stellinga
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 3.0.2
>
> The org.apache.tapestry.util.JanitorThread uses a waitForNextPass() function
> that makes it sleep for 30 seconds and then do another pass.
> In this method an InterruptedException is caught and ignored. This prevents
> the thread from terminating normally when, for instance, a context is
> reloaded. See also
> http://java.sun.com/j2se/1.5.0/docs/guide/misc/threadPrimitiveDeprecation.html.
> I think it would be better if the while-loop in the run() method exited when
> the wait() in waitfornextpass() method was interrupted.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: tapestry-dev-help@xxxxxxxxxxxxxxxxxx
|
|