[
https://issues.apache.org/jira/browse/WICKET-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561296#action_12561296
]
Ari Suutari commented on WICKET-1184:
-------------------------------------
This bites us too. It is easy to reproduce. Just install tomcat 5.5 or 6.0 and
have your wicket-based application .war ready. Open browser and go to
http://localhost:8080/manager/html. Find "war file to deploy", enter war path
there and click deploy.
After application has been deployed, check that it works.
After that, find application from manager list and click "undeploy". It seems
to go ok, but if you now take a look at webapps directory, you'll notice that
it hasn't been removed. Check whats left: there is at least wicket.jar, for us
also wicket-extensions.jar.
If you take a thread dump from tomcat now, you'll see that there is this thread:
[2008-01-22 12:36:15] [info] "PageSavingThread-Wicket"
[2008-01-22 12:36:15] [info] daemon
[2008-01-22 12:36:15] [info] prio=10 tid=0x0ae79c00
[2008-01-22 12:36:15] [info] nid=0x1764
[2008-01-22 12:36:15] [info] waiting on condition
[2008-01-22 12:36:15] [info] [0x0b50f000..0x0b50fc14]
[2008-01-22 12:36:15] [info] java.lang.Thread.State: TIMED_WAITING (sleeping)
[2008-01-22 12:36:15] [info] at java.lang.Thread.sleep(Native Method)
[2008-01-22 12:36:15] [info] at
org.apache.wicket.protocol.http.pagestore.DiskPageStore$PageSavingThread.run(DiskPageStore.java:832)
[2008-01-22 12:36:15] [info] at java.lang.Thread.run(Unknown Source)
Obviously when WicketFilter is stopped, it should also take care that also this
thread is stopped.
> PageSavingThread keeps running after undeploy
> ---------------------------------------------
>
> Key: WICKET-1184
> URL: https://issues.apache.org/jira/browse/WICKET-1184
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-rc1
> Environment: Glassfish v2
> Reporter: francisdb
> Assignee: Matej Knopp
>
> We are deploying our wicket application to Glassfish (v2). After undeploying
> and deploying a few times the PageSavingThread's of each deploy keeps
> running.
> I'm not having this problem when deploying the phonebook example (it does not
> seem tot be triggering that thread)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
