-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
10.0.0.Final
-
None
Missing info which services failed to start on server startup
E.g. when I change in mod_cluster subsystem connector reference to invalid one (/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=connector, value=invalid), the server fails to start several services without explaining which ones. This is user unfriendly as it creates hard effort to find out what is actually wrong. There should be at least pointed out which services failed to start.
- duplicates
-
WFLY-5688 mod_cluster subsystem remains silent if connector set to undefined connector
- Closed
- is cloned by
-
JBEAP-5312 (7.1.0) Missing explanation which services failed to start
- Closed