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

remoting cannot start without default worker and does not work with non-default worker for http-upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 9.0.1.Final
    • 8.0.0.Final, 9.0.0.Final
    • Remoting
    • None
    • Hide

      The example standalone-full demonstrates remoting failing to start without the default worker defined but the broader issue is that http-upgrade does not work when the http-listener is using a different worker because remoting appears to keep using the default worker
      ./bin/standalone.sh -c standalone-full.noDefault.xml

      Show
      The example standalone-full demonstrates remoting failing to start without the default worker defined but the broader issue is that http-upgrade does not work when the http-listener is using a different worker because remoting appears to keep using the default worker ./bin/standalone.sh -c standalone-full.noDefault.xml

      Originally we could not get remote+http to work with a non-default worker after following all the changes we found in the schema. It looks like remoting uses the default worker even when the endpoint is configured to use a different worker.

        1. standalone-full.noDefault.xml
          32 kB

              bstansbe@redhat.com Brian Stansberry
              wreicher1@redhat.com Will Reichert
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: