Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1329

'whoami' operation unexpectedly requires the domain wide configuration lock

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Alpha2
    • None
    • Management
    • None
    • Hide

      1. Start EAP 6 in domain mode. The out-of-the-box domain.xml is sufficient.
      2. Deploy attached 'slowdeployweb.war'.
      3. Undeploy it from CLI. It will take about 1 hour.
      4. In another terminal, execute several 'whoami' HTTP management requests like this:
      –
      curl --digest -L -D - http://admin:password@localhost:9990/management --header "Content-Type: application/json" -d '

      {"operation":"whoami","address":[],"json.pretty":1}

      ' &
      –
      5. Take a thread dump of the host controller. You can see all 'HttpManagementService-threads' are stuck.

      Show
      1. Start EAP 6 in domain mode. The out-of-the-box domain.xml is sufficient. 2. Deploy attached 'slowdeployweb.war'. 3. Undeploy it from CLI. It will take about 1 hour. 4. In another terminal, execute several 'whoami' HTTP management requests like this: – curl --digest -L -D - http://admin:password@localhost:9990/management --header "Content-Type: application/json" -d ' {"operation":"whoami","address":[],"json.pretty":1} ' & – 5. Take a thread dump of the host controller. You can see all 'HttpManagementService-threads' are stuck.

    Description

      'whoami' operation in domain mode seems to require the domain wide configuration lock. This is problematic when there is an editing operation of domain.xml like a long running undeployment because all 'whoami' requests are blocked by the existing task. The number of blocked thread increases indefinitely and it will cause an OutOfMemoryError.
      It doesn't happen in standalone mode.

      Attachments

        Activity

          People

            emuckenhuber_jira Emanuel Muckenhuber (Inactive)
            rhn-support-onagano Osamu Nagano
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: