Menu ▾ ▴

#13 Extra steps in automatic plugin updates

Core_subsystem
closed-fixed
Stephen H. Edwards
Internals (17)
5
2006-11-10
2006-09-15
Todd Whittaker
No

The auto-update mechanism seems to lag by one server
restart. For example, here's the sequence I followed:

1. Updates are available from VT
2. I go to the "Subsystems" screen under "Administer"
3. Nothing is shown as "out of date" even though it
really is.
4. I restart Tomcat.
5. The updates are downloaded on Web-CAT startup.
6. I log in and go the "Subsystems" screen again.
7. Now the subsystems are shown as out of date (even
though they've just been updated).
8. I restart Tomcat again.
9. The "Subsystems" screen shows everything as being
updated.

Step 3 is an issue as updates are available.
Steps 7-8 is an issue as the updates have already been
installed.

Discussion

  • Stephen H. Edwards

    Stephen H. Edwards - 2006-11-10
    • status: open --> closed-fixed
     

  • Stephen H. Edwards

    Stephen H. Edwards - 2006-11-10

    Logged In: YES
    user_id=1296748

    Fixed in v 1.3.5 of the Core subsystem and v.1.1.4 of the
    Admin subsystem.
    This fix does require new bootstrap code as well. Any
    Web-CAT admins who are
    affected should download the latest bootstrap jar from
    http://web-cat.cs.vt.edu/updates/Bootstrap.jar and place it
    in their web
    app's Web-CAT/WEB-INF/lib directory, overwriting the older
    version that is
    already there.