Yep, that gets past FileCleaner's reaper thread not being shut down. Should
I create a JIRA entry for this? I only see the destroy() method called in
the WebApplication.internalDestroy() method so it is probably safe to do.
I'm on to another problem with Tomcat (5.5.23 on Windows) still hanging
after that change. I don't see a wicket or my own class mentioned in the
thread dump so it is something with tomcat.
Chris
igor.vaynberg wrote:
>
> try
> {
> // Wait for a tracker to remove.
> tracker = (Tracker)q.remove();
> }
> catch (InterruptedException e) <=== added lines
> { <=== added
> lines
> break; <=== added lines
> } <=== added
> lines
> catch (Exception e)
> {
> continue;
> }
>
>
> let me know if that helps
>
> -igor
>
> On 8/28/07, cwilkes <[EMAIL PROTECTED]> wrote:
>>
>>
>> I'm having a problem reloading my wicket application only when running on
>> Windows (this doesn't happen on my Mac). From what I can tell it looks
>> like
>> the problem lies in FileCleaner. When hot deploying (that is, copying a
>> new
>> war file over the existing war file) Tomcat's output hangs with
>> "Deploying
>> web application archive yourapp.war"
>>
>
--
View this message in context:
http://www.nabble.com/Does-FileCleaner.destroy-stop-the-reaper-thread--tf4342035.html#a12372337
Sent from the Wicket - Dev mailing list archive at Nabble.com.
