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:
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.