Bug 810349 - create .env/OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT for non-scaled apps
Summary: create .env/OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT for non-scaled apps
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Bill DeCoste
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-05 16:49 UTC by Bill DeCoste
Modified: 2015-05-15 01:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:33:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bill DeCoste 2012-04-05 16:49:39 UTC 
Description of problem:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT doesn't exist for non-scaled apps

Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. Create non-scaled JBoss app
2.
3.
  
Actual results:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT does not exist


Expected results:
OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT should exist and use port 7600


Additional info:
Comment 1 Xiaoli Tian 2012-04-06 08:12:05 UTC 
The fix has not been included in devenv_1696, need to wait for the new build comes.
Comment 2 Xiaoli Tian 2012-04-09 03:35:41 UTC 
Verified it on devenv_1697 with cartridge-jbossas-7-0.90.2-1.git.119.b643636.el6.noarch.


[jbossapp3-domx85.dev.rhcloud.com .env]\> cat OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT 
export OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT='7600'
Comment 3 Rob Millner 2012-04-10 18:04:03 UTC 
If scaling is ever enabled on that gear, then OPENSHIFT_JBOSS_CLUSTER_PROXY_PORT will be overwritten with the proxy port (ex: 35531).  Does 7600 need to be stored in a different variable?  OPENSHIFT_JBOSS_CLUSTER_PORT?
Note You need to log in before you can comment on or make changes to this bug.