Description of problem: After updating JBoss EAP 6.4.13,we tried to configure JBoss as service in domain mode using init scripts. For this we copy the new jboss-as-domain.sh file to /etc/init.d, and start the daemon with service jboss-as-domain.sh start,it throw below error: ~~~ Starting jboss-as: /usr/bin/dirname: extra operand `--domain-config=domain.xml' Try `/usr/bin/dirname --help' for more information. / [ OK ] ~~~ Version-Release number of selected component (if applicable): 6.4.13 RHEL 6.8 How reproducible: configure JBoss as service in domain mode. Steps to Reproduce: 0. update JBOSS_HOME and jboss-as.conf file location in jboss-as-domain.sh script 1. copy init script jboss-as-domain.sh from $JBOSS_HOME/bin/init.d to /etc/init.d 2. Try to start JBoss service using below command: ~~ service jboss-as-domain.sh start ~~ 3. Actual results: Expected results: Additional info:
The jboss-as-domain.sh script from EAP 6.4.7 patch works without throws the error. The difference between both scripts is: EAP 6.4.7: daemon --user $JBOSS_USER LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT --domain-config=$JBOSS_DOMAIN_CONFIG --host-config=$JBOSS_HOST_CONFIG 2>&1 > $JBOSS_CONSOLE_LOG & EAP 6.4.13: daemon --user $JBOSS_USER "LAUNCH_JBOSS_IN_BACKGROUND=1 JBOSS_PIDFILE=$JBOSS_PIDFILE $JBOSS_SCRIPT --domain-config=$JBOSS_DOMAIN_CONFIG --host-config=$JBOSS_HOST_CONFIG &" 2>&1 > $JBOSS_CONSOLE_LOG
Verified with EAP 6.4.15.CP.CR3
Released on May 18 as part of EAP 6.4.15.