[jboss-jira] [JBoss JIRA] (WFLY-2836) http-listener requires 'https' socket-binding
[
https://issues.jboss.org/browse/WFLY-2836?page=com.atlassian.jira.plugin....
]
dfisher commented on WFLY-2836:
-------------------------------
I need multiple http-listeners, so I renamed the listeners and the socket-bindings in the
default config to be representative of their purpose in our environment.
That's how I discovered this dependency on a socket-binding named 'https'.
http-listener requires 'https' socket-binding
---------------------------------------------
Key: WFLY-2836
URL: https://issues.jboss.org/browse/WFLY-2836
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Affects Versions: 8.0.0.CR1
Reporter: dfisher
Assignee: Tomaz Cerar
Priority: Minor
Fix For: 8.0.0.Final
Using a http-listener without the redirect-socket attribute requires the configuration to
define a socket-binding with name "https".
The following error is produced attempting to configure wildfly without https:
{code}
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613:
Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("http-listener" => "default")
]) - failure description: {"JBAS014771: Services with missing/unavailable
dependencies" => ["jboss.undertow.listener.default is missing
[jboss.binding.https]"]}
{code}
I believe this constant is defined in ListenerResourceDefinition on line 80.
If this is the desired behavior, the undertow schema should probably be updated to make
redirect-socket required or at least document the dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira