Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1050204 - WAIT_FOR_BEFORE_START does not work for / context applications
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
: DR0
: EAP 6.3.0
Assigned To: Aaron Ogburn
Radim Hatlapatka
Russell Dickenson
:
Depends On:
Blocks: 1050033 1115117
  Show dependency tree / graph
 
Reported: 2014-01-08 15:38 EST by Aaron Ogburn
Modified: 2014-07-14 22:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: 1050033
Environment:
Last Closed: 2014-06-28 11:24:56 EDT
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)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Aaron Ogburn 2014-01-08 15:38:35 EST 
+++ 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):

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.

--- Additional comment from Aaron Ogburn on 2014-01-08 15:18:45 EST ---

PR:

https://github.com/jbossas/jboss-eap/pull/762
Comment 1 Aaron Ogburn 2014-01-08 15:48:17 EST 
6.0.x PR:

https://github.com/jbossas/jboss-eap/pull/763
Comment 2 Aaron Ogburn 2014-01-08 17:40:50 EST 
Correct 6.x PR:

https://github.com/jbossas/jboss-eap/pull/768
Comment 3 Radim Hatlapatka 2014-02-17 06:14:27 EST 
Verified in EAP 6.3.0.DR0
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.