Bug 1083474 - JBOSS_HOME is not available in domain.conf
Summary: JBOSS_HOME is not available in domain.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Scripts and Commands
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR1
: EAP 6.4.0
Assignee: Chao Wang
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-02 10:18 UTC by Josef Cacek
Modified: 2019-08-19 12:41 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3472 0 Minor Resolved JBOSS_HOME is not available in domain.conf 2014-08-29 14:39:09 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.