Yes, It will be really best if you can please share the information which Tomaz Cerar is requested that will help us in understanding what is the actual issue here.
You said "I am just blindly sharing some of my experiences here. Sometime we need to restart the JBOSS, due to unplanned activities. but we are unable to start the JBOSS."
>>> Looks like in your case when you are trying to restart the JBoss the Users are not aware of the restart and they are keep sending the requests to the application which are deployed on the JBoss. In such scenarios may you can configure a front end webserver where you can show the static page saying that the JBossAS7 is under maintenance. (OR set the firewall rule to not accept any request during the JBoss restart ...)
Something like described in the following article (statis maintenance pages):
JBossAS7 is too old you can try using WildFly. If not then the JBoss EAP6.4 as i see some of the feature in JBoss EAP 6 like "org.apache.catalina.connector.WAIT_FOR_BEFORE_START" See 
So ideally JBoss will wait for the applications to be deployed first and then it will open the connector ports.