Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-1184

PageSavingThread keeps running after undeploy

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.3.0-rc1
    • Fix Version/s: None
    • Component/s: wicket
    • Labels:
      None
    • Environment:
      Glassfish v2

      Description

      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)

        Activity

        Hide
        knopp Matej Knopp added a comment -

        Unless I get more information on this I will have to close this as can't reproduce.

        Show
        knopp Matej Knopp added a comment - Unless I get more information on this I will have to close this as can't reproduce.
        Hide
        francisdb Francis De Brabandere added a comment -

        I won't be able to get more info on this bug as I'm working for a different company now... Since nobody else is watching this bug I suggest you close it.

        Show
        francisdb Francis De Brabandere added a comment - I won't be able to get more info on this bug as I'm working for a different company now... Since nobody else is watching this bug I suggest you close it.
        Hide
        arisuu Ari Suutari added a comment -

        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.

        Show
        arisuu Ari Suutari added a comment - 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.
        Hide
        frankbille Frank Bille Jensen added a comment -

        I think it's because the pagesaving thread has been marked for stopping but has not yes stopped before the main threads ends.

        Show
        frankbille Frank Bille Jensen added a comment - I think it's because the pagesaving thread has been marked for stopping but has not yes stopped before the main threads ends.
        Hide
        frankbille Frank Bille Jensen added a comment -

        Fixed this in current trunk. Can you please check if it fixes your problem?

        Show
        frankbille Frank Bille Jensen added a comment - Fixed this in current trunk. Can you please check if it fixes your problem?
        Hide
        arisuu Ari Suutari added a comment -

        I took a look at the change at DiskPageStore.java you made and it looks about just the same I was going to suggest.
        I'm currently using wicket 1.3 release so I didn't really test this - is there going to be a maintenance release
        for 1.3 ?

        Show
        arisuu Ari Suutari added a comment - I took a look at the change at DiskPageStore.java you made and it looks about just the same I was going to suggest. I'm currently using wicket 1.3 release so I didn't really test this - is there going to be a maintenance release for 1.3 ?
        Hide
        akhlystov Khlystov Alexandr added a comment -

        problem is still not fixed, I use wicket 1.3.5, and Tomcat 6.0 as application server.

        Show
        akhlystov Khlystov Alexandr added a comment - problem is still not fixed, I use wicket 1.3.5, and Tomcat 6.0 as application server.
        Hide
        ivaynberg Igor Vaynberg added a comment -

        tried to repro with latest 1.4.x and everything worked just fine

        Show
        ivaynberg Igor Vaynberg added a comment - tried to repro with latest 1.4.x and everything worked just fine

          People

          • Assignee:
            ivaynberg Igor Vaynberg
            Reporter:
            francisdb Francis De Brabandere
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development