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

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.