+++ This bug was initially created as a clone of Bug #960741 +++ Description of problem: Users will experience a timeout bug when starting their server in standalone-full-ha profile. jboss-as-standalone.sh snippet ... 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 ... Version-Release number of selected component (if applicable): EAP 6.4.0.ER1 How reproducible: Always Steps to Reproduce: 1. Add the following line into $JBOSS_HOME/bin/init.d/jboss-as.conf file JBOSS_CONFIG=standalone-full-ha.xml 2. follow the documentation to start standalone server as a service http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Installation_Guide/Install_JBoss_Enterprise_Application_Platform_6_Red_Hat_Enterprise_Linux_Service.html Actual results: Starting jboss-as: jboss-as failed to startup in the time allotted [FAILED] Expected results: Starting jboss-as: [ OK ]
Agreed with Tomaž to assign to jboss-set
I am not able to reproduce it with 6.4.10 version. This issue has been fixed with other issues (see 960741).