Community
Participate
Working Groups
The DefaultServlet does not release locks on files that it serves. This prevents the file that has been served (at least once) from being replaced / deleted / renamed / or moved. Speculation: the DefaultServlet isn't releasing the streams or closing the file handles. The unit test org.eclipse.jetty.servlet.DefaultServletTest.testWelcomeServlet can be used as the test case for this under Windows.
I've been able to reproduced this issue. In one of the applications that I've tried to edit a file with it complains about user-mapped area being open when I try to save the edited file. I will look into this some more tomorrow.
Is this something more than http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows can you also check if that doco has been updated for jetty-7 on the eclipse wiki.
I've confirmed that setting the following parameter for DefaultServlet corrects the issue, as Greg had suggested above. <init-param> <param-name>useFileMappedBuffer</param-name> <param-value>false</param-value> </init-param> The documentation page above need to be ported to Eclipse WIKI. -Michael
http://wiki.eclipse.org/Jetty/Howto/Deal_with_Locked_Windows_Files