+++ This bug was initially created as a clone of Bug #1020677 +++

Description of problem:
JBoss EAP 6.2.0 script uses "JBoss AS.*started in" string to verify if the JBoss started. It should be JBAS015874. Thus, it will work for different languages (and with EAP). 
Currently the service start() will success even if no "started in" message is found.
from JBoss EAP 6.2.0 jboss-as-domain.sh script:
start() {
...
  count=0
  launched=false

  until [ $count -gt $STARTUP_WAIT ]
  do
    grep 'JBoss AS.*started in' $JBOSS_CONSOLE_LOG > /dev/null
    if [ $? -eq 0 ] ; then
      launched=true
      break
    fi
    sleep 1
    let count=$count+1;
  done

  success
  echo
  return 0
}

Version-Release number of selected component (if applicable):
EAP 6.2.0.ER6

started log:
[Host Controller] 08:13:44,258 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-9) (Host Controller) started in 8766ms - Started 12 of 12 services (0 services are passive or on-demand)

Additional info:
Keep in mind that greping just JBAS015874 will return success once domain-controller is up, this doesn't mean that whole domain is up.
Original issue BZ1015237

--- Additional comment from Permaine Cheung on 2013-10-18 08:48:32 EDT ---

Jason, please reassign accordingly.

When this is fixed in Wildfly, we'll need to merge the fix into the EAP branch.

--- Additional comment from Petr Kremensky on 2014-02-17 08:11:25 EST ---

This is same with jboss-as-standalone.sh script. Launched variable is ignored and script return success even if server failed to start once the timeout expires.

{ ...
  count=0
  launched=false

  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

  success
  echo
  return 0
}