From owner-freebsd-java@FreeBSD.ORG Wed Jun 26 08:20:01 2013 Return-Path: Delivered-To: freebsd-java@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D30CB45 for ; Wed, 26 Jun 2013 08:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6601316EE for ; Wed, 26 Jun 2013 08:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5Q8K01W063096 for ; Wed, 26 Jun 2013 08:20:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5Q8K0Nh063095; Wed, 26 Jun 2013 08:20:00 GMT (envelope-from gnats) Date: Wed, 26 Jun 2013 08:20:00 GMT Message-Id: <201306260820.r5Q8K0Nh063095@freefall.freebsd.org> To: freebsd-java@FreeBSD.org Cc: From: Mark Linimon Subject: Re: java/179927: JBoss 7.2 Can't start with rc script X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Linimon List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 08:20:01 -0000 The following reply was made to PR ports/179927; it has been noted by GNATS. From: Mark Linimon To: bug-followup@FreeBSD.org Cc: Subject: Re: java/179927: JBoss 7.2 Can't start with rc script Date: Wed, 26 Jun 2013 03:17:45 -0500 ----- Forwarded message from horst leitenmueller ----- Date: Wed, 26 Jun 2013 09:46:55 +0200 From: horst leitenmueller To: Alexander Yerenkow Cc: hasanalpinan@gmail.com, "freebsd-java@freebsd.org" Subject: Re: java/179927: JBoss 7.2 Can't start with rc script X-Mailer: Apple Mail (2.1503) hi Alexander, this is not enough the script has more problems: 1) if i call the generate startup code i get the error message /usr/local/etc/rc.d/jboss72 start calls daemon -u www /usr/local/jboss-as-7.2.0.Final/bin/standalone.sh >> /var/log/jboss72/stdout.log 2>> /var/log/jboss72/stderr.log >> /var/log/jboss72/boot.log 2>> /var/log/jboss72/boot.log Ambiguous output redirect. if i remove the >> /var/log/jboss72/boot.log 2>> /var/log/jboss72/boot.log its working... 2) the jboss startup attributes are also missing jboss_args they are declared but not sent to standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -c standalone-full.xml as example daemon -u ${jboss72_user} ${JBOSS_HOME}/bin/standalone.sh ${jboss72_args} >> ${jboss72_logdir}/stdout.log 2>> ${jboss72_logdir}/stderr.log results in daemon -u www /usr/local/jboss-as-7.2.0.Final/bin/standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -c standalone-full.xml >> /var/log/jboss72/stdout.log 2>> /var/log/jboss72/stderr.log is same like direct call from terminal /usr/local/jboss-as-7.2.0.Final/bin/standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -c standalone.xml and it will start; jboss72_enable="YES" jboss72_jvm_opts=" -server -Xms128m -Xmx512m -XX:MaxPermSize=256m" >>> not working !! jboss72_args=" -b 0.0.0.0 -bmanagement 0.0.0.0 -c standalone-full.xml " # standalone.xml standalone-full.xml it will not work, because params are not given to standalone.sh 3) please add at the end & from the script not to block the terminal ; also for stopping 4) cool would be to be definable which i want to start standalone.sh / domain.sh 5) cool would be also to get info after installation that its needed to execute /usr/local/jboss-as-7.2.0.Final/bin/add-user.sh for administration access br horst ----- End forwarded message -----