The point of the test was to illustrate the current usage that causes locking problems.
How one thread can reliably delete a file when there are scanner threads that may have
recently been active is what needs to be handled. It does not matter if the deployDir(in
general there can be multiple dirs) should be cached from the initial point where the
deploy dir uris are setup.
There should be a better api than having to set a system property to clear all unused
locks. Can't this be incorporated into the VirtualFileHandler delete implementation?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160576#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...