Description of problem: When using the standalone-full-ha.xml profile or removes the console logger from their profile they will experience a timeout bug when starting their server. #from /etc/init.d/jbossas until [ $count -gt $JBOSS_STARTUP_WAIT ] do grep -q 'JBoss EAP 6.*started in' $JBOSS_CONSOLE_LOG > /dev/null 2>&1 if [ $? -eq 0 ] ; then launched=true success "${NAME} startup" echo break fi sleep 10 let count=$count+10; done How reproducible: Set or alter the JBoss init script to use 'standalone-full-ha.xml' JBOSS_SERVER_CONFIG=${JBOSS_SERVER_CONFIG:-""} ^ Add it here. or export JBOSS_SERVER_CONFIG='standalone-full-ha.xml' in your /etc/jbossas/jbossas.conf file Actual results: Start up times out, because its looking for 'JBoss EAP 6.*started in' in the console log. Solution: Ensure that the following in in your configuration: <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <!--FIXME: This Line--> <handler name="FILE"/> </handlers> </root-logger> This may be a clone of https://bugzilla.redhat.com/show_bug.cgi?id=900663
Changed the component to Server. This is a problem in the provided sample configuration file (or it is a plain duplicate of 900663). You just happened to be using a RPM installation.
The issue seems to be with the provided configuration file. However I feel that this issue may be a duplicate of 900663 but would like for engineering to confirm. The BZ's are technically different however they may be two solutions to the same problem.
I tried using the current init script (from EAP 6.3.2) with JBOSS_SERVER_CONFIG set to "standalone-full-ha.xml", it starts and stops without any issue, marking this as MODIFIED. Please reopen if there are further issue.
I cannot speak for RPM distribution, but this is still an issue for jboss-as-standalone.sh inside zip distribution. Scripts is still searching the console log which is not available (comment 7). ... until [ $count -gt $STARTUP_WAIT ] do grep 'JBAS015874:' $JBOSS_CONSOLE_LOG > /dev/null if [ $? -eq 0 ] ; then launched=true break fi sleep 1 let count=$count+1; done ... Just add the following line into jboss-as.conf file to reproduce. JBOSS_CONFIG=standalone-full-ha.xml
This BZ was reported specifically against the init scripts in the RPM, for the issue you find with jboss-as-standalone.sh, please file a separate BZ against the scripts that are part of the zip and are maintained upstream so that we can keep this one for the init script. Thanks.
No RPMs delivered with EAP 6.4.0.ER1 build. Postponing verification to ER2.
Verified in RPM installation of EAP 6.4.0.ER2.
(In reply to Petr Kremensky from comment #9) > I cannot speak for RPM distribution, but this is still an issue for > jboss-as-standalone.sh inside zip distribution. > > Scripts is still searching the console log which is not available (comment > 7). > ... > until [ $count -gt $STARTUP_WAIT ] > do > grep 'JBAS015874:' $JBOSS_CONSOLE_LOG > /dev/null > if [ $? -eq 0 ] ; then > launched=true > break > fi > sleep 1 > let count=$count+1; > done > ... > > Just add the following line into jboss-as.conf file to reproduce. > JBOSS_CONFIG=standalone-full-ha.xml Hi, hope this could help: I had to modify standalone-full-ha.xml adding these lines: 1) ADD console-handler CONSOLE ... <profile> <subsystem xmlns="urn:jboss:domain:logging:1.4"> <console-handler name="CONSOLE"> <level name="INFO"/> <formatter> <named-formatter name="COLOR-PATTERN"/> </formatter> </console-handler> ... 2) ADD the handler CONSOLE and the FORMATTER COLOR-NAME ... <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> <formatter name="PATTERN"> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <formatter name="COLOR-PATTERN"> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> ... Regards