Bug 1093497

Description of problem:
When using the provided jboss-as-domain.sh script on RHEL 6, it reports that it started OK even though it doesn't. The same script works correctly on both Fedora 17 and 20.

Version-Release number of selected component (if applicable):
Any. I've tested with EAP 6.2.0, 6.2.1, and 6.2.2.

How reproducible:
Put a typo in the domain.xml so that it cannot be parsed/started correctly and use the script to start it.

Steps to Reproduce:
1. Add a typo to the domain.xml. I added <auth/> to line 213 in domain.xml to break it.
2. Start the service with `service jboss-as-domain start`
3.

Actual results:
[root@localhost bin]# service jboss-as-domain start
Starting jboss-as:                                         [  OK  ]

Expected results:
[root@localhost bin]# service jboss-as-domain start
Starting jboss-as:                                         [  FAILED  ]


Additional info:
This seems to be a problem with the RHEL init.d/functions to me as it works on Fedora, but not RHEL. As a note, the only other related BZ I found was BZ1015237. It doesn't seem related to the issue, but I tried changing the start line it was looking for just in case; still gives a false success message.