Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-954

Server is not responding after attempt to set parent of profile to non-existent profile

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Duplicate Issue
    • 2.0.0.Beta5
    • 2.0.0.Beta6
    • Management
    • None

    Description

      This is a clone of WFLY-5225 to make sure that if the fix is in core, that we track it with this one.

      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):

      1. Get fresh EAP
      2. ./domain.sh
      3. ./jboss-cli.sh
        1. /profile=new:add()
        2. /profile=new:write-attribute(name=includes,value=[nonsence])
        3. /profile=new:remove

      Actual results:

      [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
      
      
      • server needs to be restarted

      Expected results:

      [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
      }
      

      Steps to reproduce (socket-binding-group):

      1. Get fresh EAP
      2. ./domain.sh
      3. ./jboss-cli.sh
        1. /profile=new:add()
        2. /socket-binding-group=testt:add(default-interface=public,includes=[nonsence])
        3. /profile=new:remove

      Attachments

        Issue Links

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: