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

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 8.0.0.Final, 9.0.0.Final
    • Fix Version/s: 9.0.1.Final
    • Component/s: Remoting
    • Labels:
      None
    • Environment:

      jboss-eap-7.3.0.CD16-CR1

    • Steps to Reproduce:
      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

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  willreichert Will Reichert
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: