Server is not responding after attempt to set parent of profile to non-existent profile --------------------------------------------------------------------------------------- Key: WFLY-5225 URL: https://issues.jboss.org/browse/WFLY-5225 Project: WildFly Issue Type: Bug Components: CLI Affects Versions: 10.0.0.Beta2 Reporter: Marek Kopecký Assignee: Kabir Khan *Description of problem:* Server is not responding after attempt to set parent of profile to non-existent profile. Server is not responding also after attempt to set parent of socket-binding-group to non-existent socket-binding-group. This works correctly on wildfly-core (2.0.0.Beta4). But this occurs on wildfly (master branch) and on EAP 7.0.0.DR9. It may be some integration issue. Priority of this jira tends to be critical. *How reproducible:* Always *Steps to Reproduce (profile):* # Get fresh EAP # ./domain.sh # ./jboss-cli.sh ## /profile=new:add() ## /profile=new:write-attribute(name=includes,value=\[nonsence\]) ## /profile=new:remove *Actual results:* {noformat} [domain@localhost:9990 /] /profile=new:write-attribute(name=includes,value=[nonsence]) { "outcome" => "failed", "failure-description" => "java.lang.NullPointerException:null" } [domain@localhost:9990 /] /profile=new:remove {noformat} * server needs to be restarted *Expected results:* {noformat} [domain@localhost:9990 /] /profile=new:write-attribute(name=includes,value=[nonsence]) { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available: org.wildfly.domain.profile.nonsence in context 'profiles'"}, "rolled-back" => true } [domain@localhost:9990 /] /profile=new:remove { "outcome" => "success", "result" => undefined, "server-groups" => undefined } {noformat} *Steps to reproduce (socket-binding-group):* # Get fresh EAP # ./domain.sh # ./jboss-cli.sh ## /profile=new:add() ## /socket-binding-group=testt:add(default-interface=public,includes=\[nonsence\]) ## /profile=new:remove