Hey Yuanjia Chi,
Sorry its taken so long to get back to you - the problem you are seeing is because the war that you are deploying contains ALL the jars needed to build and run the platform. All of these jars are not necessary in JBoss, because JBoss has its own version of some of them that it prefers to use. Unfortunately, some of them actually cause JBoss to not deploy your war, but because the war is packaged as generically as possible we don't just exclude these jars.
So the solution is for you to open up the war, delete the necessary jars, repackage the war file and redeploy it. The list of jars that COULD cause trouble are:
The jars that are most likely the root of your problem are servlet-api.jar and jsp-api.jar. I would recommend removing atleast those two, redeploying and seeing if you experience any other troubles. Let me know how it goes for you!
Hope you wont mind
Thank you for your suggestion,I have cracked it already.
The reason could be like that: my war include a servlet,many threads will start when servlet init,and the servlet init as the jboss start.
the most important point is that : as threads(many threads will start when servlet init) start,they blocking many jboss inner threads。
It leads jboss http service can't be accessed normally。
So I change the servlet init configuration,many threads won't start when servlet init,It work,jboss http service can be accessed normally。
In a word,threads blocking the jboss inner threads,we must ensure jboss start completly.