-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
7.0.3.GA
-
None
Customer set 'JBOSS_OPTS="-Djboss.server.base.dir=/abc/def/standalone"' in "/etc/default/jboss-eap.conf" to separate application home from EAP_HOME and start EAP 7.0.3 as Linux service successfully.
A file "startup-marker"(success:xxxxxxx) will be created on "/abc/def/standalone/tmp" as expected.
And we can also see below from "/etc/init.d/"jboss-eap-rhel.sh":
# Startup mode script if [ "$JBOSS_MODE" = "standalone" ]; then JBOSS_SCRIPT=$JBOSS_HOME/bin/standalone.sh if [ -z "$JBOSS_CONFIG" ]; then JBOSS_CONFIG=standalone.xml fi JBOSS_MARKERFILE=$JBOSS_HOME/standalone/tmp/startup-marker
The path above is still pointing to $JBOSS_HOME/standalone, however it will be created at "jboss.server.base.dir/tmp" in practice, we try to change the path and file name to find the reason, but got the same result.
And after start EAP service the terminal shows:
[/opt/jboss-eap7/bin/init.d]@abc (jboss)$ sudo service jboss-eap restart
Stopping jboss-eap: [ OK ]
Starting jboss-eap: /
jboss-eap started with errors, please see server log for details
However, "server.log" has no errors at all.
- is duplicated by
-
JBEAP-7045 [GSS](7.2.0) Startup error when started as system service
- Closed
-
JBEAP-13983 [GSS](7.1.z) Startup error when started as system service
- Closed
-
JBEAP-13984 [GSS](7.0.z) Startup error when started as system service
- Closed