Description of problem:
During jboss startup, a @Singleton bean fails to initialize and throws a RuntimeException in the @PostConstruct method in order to stop initialization.
using older jboss (tested on 7.1.1) throwing the exception at this point would stop initialization, and it was visible to the users something is wrong (service was not available)
on newer (tested EAP 6.3.0), this exception would not stop initialization, and jboss would start, appearing as service is available, but it would not function correctly.
i was able to test that this was resolved by
https://issues.jboss.org/browse/WFLY-2281
Version-Release number of selected component (if applicable):
EAP 6.3.0
How reproducible:
always
Steps to Reproduce:
1. throw a RuntimeException during @PostConstruct of @Singleton bean
Actual results:
server continue to load
Expected results:
server fail to load