[
https://issues.jboss.org/browse/WFCORE-4510?page=com.atlassian.jira.plugi...
]
Brian Stansberry moved JBEAP-17029 to WFCORE-4510:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-4510 (was: JBEAP-17029)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Remoting
(was: Remoting)
Affects Version/s: 9.0.0.Final
(was: 7.3.0.CD16)
remoting cannot start without default worker and does not work with
non-default worker for http-upgrade
-------------------------------------------------------------------------------------------------------
Key: WFCORE-4510
URL:
https://issues.jboss.org/browse/WFCORE-4510
Project: WildFly Core
Issue Type: Bug
Components: Remoting
Affects Versions: 9.0.0.Final
Environment: jboss-eap-7.3.0.CD16-CR1
Reporter: Will Reichert
Assignee: Flavia Rainone
Priority: Critical
Attachments: 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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)