Shouldn't we simply use an OS-dependent solution? i.e. depending on which OS JBoss is running on, we would use a different solution. That would mean that on some OSes, JBoss would be faster/more efficient, while on others it wouldn't. But at least, we would have a safe way of handling all situations. When I read that some solutions rely on timers, it freezes my spine. Also, given that JBoss Web will be included in JBoss 5.0 and given that we will provide by default APR libraries for most OS, couldn't we also use this as part of the OS-specific check and rely on OS-specific native calls to detect whether a file is currently being opened/locked or not? Between the presence of APR libraries and OS-specific checks we should be able to offer a performing solution on most if not all OSes, no? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160781#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...