Bug 1125826

Summary:	The page can't be access after restart if it was deployed using jboss management console
Product:	OpenShift Online	Reporter:	Anping Li <anli>
Component:	Image	Assignee:	Ben Parees <bparees>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.x	CC:	jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1125827 (view as bug list)		Environment:
Last Closed:	2014-08-01 16:26:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1125827

Description Anping Li 2014-08-01 07:38:27 UTC

Description of problem:
The page can be access after deployed package and enable it, However the page became inaccessible once the app was restart.
I found there only one blank directory under jbosseap/standalone/tmp/work/jboss.web/default-host. It seems jboss management deployed the package to memory, the package disappear after restart. 

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


How reproducible:
Always

Steps to Reproduce:
1.create one Jboss application.
2.port forward to your desktop and the go to http://127.0.0.1:9990/, deploy/enable one war package. for example: sample.war
3.access the http://url/sample
4. restart the application and access http://url/sample again
5. check the deployment directory
find . -name sample* 

Actual results:
For step 3: the page can be access.
For step 4: the page can't be access.
For step 5: there is only one empty directory jbosseap/standalone/tmp/work/jboss.web/default-host/sample

Expected results:
The war package should be kept in application, the page can be access after app restart.

Additional info:

Comment 1 Ben Parees 2014-08-01 16:26:52 UTC

Since you are using the jboss console directly to configure this application, you need to prevent openshift from rewriting the standalone.xml on restart.

To do so, set the following environment variable:
DISABLE_OPENSHIFT_MANAGED_SERVER_CONFIG=true

with that value set, you can manipulate the jboss configuration directly (including doing direct deployments like this) without losing the changes on restart.