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

TopologyChanged event listeners should not perform blocking operations on non-blocking thread

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 27.0.0.Final
    • 27.0.0.Beta1
    • Clustering
    • None

      Any blocking operations need to be run via the BlockingManager.  This ensures that any operations built upon the CompletionStage returned by the listener continue to run on the non-blocking thread.

      Same issue applies to passivation/activation events.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: