In previous versions of JBoss EAP the `WAIT_FOR_BEFORE_START` property did not work for root context applications. If a user set `WAIT_FOR_BEFORE_START` to / and deployed a root application, the connectors did not start as expected.
This has been corrected in this release and now when setting WAIT_FOR_BEFORE_START to / and deploying a root application, the connectors will start as expected.
+++ This bug was initially created as a clone of Bug #1050033 +++
Description of problem:
WAIT_FOR_BEFORE_START does not work for / context applications. If you set WAIT_FOR_BEFORE_START to / and deploy a / application, the connectors never start.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ./standalone.sh -Dorg.apache.catalina.connector.WAIT_FOR_BEFORE_START=/
2. Deploy a / context
3. Check and see that the connectors never started as expected after / was deployed
Connectors never start with WAIT_FOR_BEFORE_START=/
Connectors start with WAIT_FOR_BEFORE_START=/ when / context app is deployed
It gets the newly started context through context.getPath(). When deployed to /, context.getPath() is returning "" so that doesn't match the "/" value specified on WAIT_BEFORE_START and so the condition is never satisfied. WAIT_BEFORE_START can't be set to "" to get a matching value there since only values containing "/" are effectively used.
--- Additional comment from Aaron Ogburn on 2014-01-08 15:18:45 EST ---
Correct 6.x PR:
Verified in EAP 6.3.0.DR0