JBossWeb connectors start before application deployments and start up is complete on EAP 6

Issue

• JBossWeb connectors fully start and accept requests long before the server starts and applications fully deploy. This leads to unneeded 404s as JBoss starts accepting the incoming traffic before completing deployments.
• With very heavy load starting to those early started connectors, the resulting activity in web request threads for these 404s can even impact performance of MSC threads at start up to delay a full start by several minutes.
• When the jboss starts with errors in a node we do not want mod_cluster to send requests to that node. Is that possible? How can we do it?