Moving this discussion here: - https://jira.jboss.org/jira/browse/JBAS-5953 I guess this is similar to what we've already seen in some VFS failures: - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134177 - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137839 - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=138343 Taken from one of these threads: "adrian(a)jboss.org" wrote : | Also you need to be careful with JAR files and their URL connections. | | The JDK caches them internally and can even mmap them on some operating systems. | So testing a jar entry has changed isn't the same thing as checking the top level file | changed. | Additionally, closing the top jar connection will close the cached version | which can lead to strange errors. | | The internal caching is the source of the problems (e.g. locking on windows) | and something Sun have consistently refused to fix. :-( | Shelly, what exactly do you mean here: "but wanted to check if you have concerns on org.jboss.vfs logic (refer to attached stack trace)"? Since jar handling is quite broken in JDK, we definitely have some ideas of doing this on our own: - https://jira.jboss.org/jira/browse/JBVFS-53 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179535#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...