Bug 1083474

Summary:	JBOSS_HOME is not available in domain.conf
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Josef Cacek <jcacek>
Component:	Scripts and Commands	Assignee:	Chao Wang <chaowan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kremensky <pkremens>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	chaowan, fnasser, kkhan, pgier
Target Milestone:	DR1
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Josef Cacek 2014-04-02 10:18:41 UTC

Move the domain.conf call in domain.sh (and also domain.conf.bat in domain.bat) so it's called after the JBOSS_HOME is set. Then it's possible to use it in the configuration file.

E.g. we use following line to enable security manager:
JAVA_OPTS="$JAVA_OPTS -Djava.security.manager -Djava.security.policy==/tmp/security.policy -Djboss.home.dir=$JBOSS_HOME -Djboss.modules.policy-permissions=true"

The order is correct in the scripts for standalone (so the JBOSS_HOME is available in its conf file).

Comment 1 Chao Wang 2014-06-16 02:21:39 UTC

6.x PR: https://github.com/jbossas/jboss-eap/pull/1458

Comment 2 Petr Kremensky 2014-09-19 07:44:57 UTC

Verified on EAP 6.4.0.DR1.1. JBOSS_HOME is now available in domain.conf(.bat) file.