It's solved. It caused by a timing bug of VMWare... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233275#4233275 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4233275