Legacy encrypt protocol support is missing a requirement on elytron subsystem ----------------------------------------------------------------------------- Key: WFLY-8582 URL: https://issues.jboss.org/browse/WFLY-8582 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1 Environment: All Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Can the error message be improved to recognise that not only is there no operation registered at the address, but there is no subsystem registered with that name. Example: If ASYM_ENCRYPT is configured, without the elytron subsystem being present, there is a runtime error which doesn't make it obvious how to address the problem. Customers porting EAP 7.0.x domain config to EAP 7.1.0 with fix for CVE-2016-2141 will see this Runtime Error: [Host Controller] 16:21:35,148 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ [Host Controller] ("profile" => "full-ha"), [Host Controller] ("subsystem" => "jgroups"), [Host Controller] ("stack" => "tcpping"), [Host Controller] ("protocol" => "ASYM_ENCRYPT") [Host Controller] ]) - failure description: "WFLYCLJG0026: No add operation registered at /profile=full-ha/subsystem=elytron/key-store=jgroups-tcpping" [Host Controller] 16:21:35,164 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. [Host Controller] 16:21:35,170 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99