I've made a quick test, as described on JBAS-4545, creating a dummy jmx-console.war/tst.jsp, and jmx-console is re-deployed, so the problem is still there. I understand that we monitor the top level deployment for changes (in this case the jmx-console.war directory) so any changes in the directory content (addtions/removals/updates) causes it's date to be modified, which in turn triggers the re-deployment. For unpacked deployments shouldn't we monitor some inner META-INF/web.xml descriptor, like in 4.x ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156953#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...