| Summary: | Could not delete metadata file when removing utility jar application from server | ||
|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | Steven Hung <sghung> |
| Component: | wst.server | Assignee: | Larry Isaacs <larryisaacs> |
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | Angel Vera <arvera> |
| Severity: | normal | ||
| Priority: | P3 | CC: | eyuen7 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Steven Hung
This also affects Eclipse 3.6.2 M20110210-1200 It looks like the problem may be caused by the SESSIONS.ser file gets deleted prematurely before all required operation has been completed when removing an application from the tomcat server. Sorry for not addressing this sooner. Jar locking is a feature of Windows. However, even running on Linux, adding and removing of projects from a running Tomcat is not really supported in WTP. This is addressed, in the Tomcat FAQ here: http://wiki.eclipse.org/WTP_Tomcat_FAQ#Can_I_add_or_remove_a_project_from_a_server.2C_or_publish_changes_for_a_project_already_on_a_server.2C_while_that_server_is_running.3F Due to the Windows jar locking and the fact that the "antiJarLocking" offered by Tomcat interferes with publishing, I'm marking this as NOT_ECLIPSE. There is still the issue that the Tomcat support in WTP doesn't currently have a good way request individual webapp's be started and stopped. This is the issue with the SESSIONS.ser file. JMX might be a possibility, but the number of cycles I think that would take would be impractical. This is due to the limited success possible because of the jar locking on Windows and the challenge of getting something to work across multiple versions of Tomcat. |