Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1050033 - [GSS] (6.2.x) WAIT_FOR_BEFORE_START does not work for / context applications
[GSS] (6.2.x) WAIT_FOR_BEFORE_START does not work for / context applications
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity unspecified
: CR1
: EAP 6.2.1
Assigned To: Aaron Ogburn
Radim Hatlapatka
Russell Dickenson
:
Depends On: 1050204
Blocks: eap62-cp01-blockers
  Show dependency treegraph
 
Reported: 2014-01-08 11:19 EST by Aaron Ogburn
Modified: 2014-08-13 22:35 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A bug in the web connector service resulted in `WAIT_FOR_BEFORE_START` not working when deploying `/` context applications. If `WAIT_FOR_BEFORE_START` was to `/` and a `/` application is deployed, the connectors would never start. This issue has been fixed in this release of JBoss EAP 6. When setting `WAIT_FOR_BEFORE_START` to `/` and deploying a `/` context application, the connectors now start successfully.
Story Points: ---
Clone Of:
: 1050204 (view as bug list)
Environment:
Last Closed: 2014-02-24 15:14:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aaron Ogburn 2014-01-08 11:19:57 EST
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):

EAP 6.2.0


How reproducible:

Always


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

Actual results:

Connectors never start with WAIT_FOR_BEFORE_START=/

Expected results:

Connectors start with WAIT_FOR_BEFORE_START=/ when / context app is deployed

Additional info:

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.
Comment 1 Aaron Ogburn 2014-01-08 15:18:45 EST
PR:

https://github.com/jbossas/jboss-eap/pull/762
Comment 3 Aaron Ogburn 2014-01-08 17:41:29 EST
Correct 6.x PR:

https://github.com/jbossas/jboss-eap/pull/768
Comment 4 Scott Mumford 2014-01-20 00:45:09 EST
Marking for inclusion in 6.2.1 release notes documentation.
Comment 6 Radim Hatlapatka 2014-01-27 10:25:22 EST
Verified in 6.2.1.CP.CR1-patch

Note You need to log in before you can comment on or make changes to this bug.