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

Write lock is acquired reading patching resource using include-runtime

    Details

      Description

      This is initially created as a bug but it needs first some investigation to discover if it is really necessary to acquire the write lock when the patching resource is read. If it is unnecessary, we should remove this need.

      The following operation is acquiring the write lock:

      /host=slave/core-service=patching:read-resource(include-runtime=true) 
      

      It potentially will block if there is any other operation that has already acquired the lock. One consequence found due to this issue was HAL could block and hang if an HC is starting and the user clicks on 'Patching' menu entry. It was fixed in HAL, where an HC being restarted is no longer shown in the Patching menu.

      The main problem seems to be in PatchStreamResourceOperationStepHandler, which is the parent handler used for the handlers that manage patching operations. This parent handler is always acquiring the write lock.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  yersan Yeray Borges Santana
                  Reporter:
                  yersan Yeray Borges Santana
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: