[jboss-jira] [JBoss JIRA] (WFLY-4245) redirect-socket="https" not explicit in default configuration

[Giuseppe Mazzotta (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032080#comment-13032080 ] 

Giuseppe Mazzotta edited comment on WFLY-4245 at 1/13/15 6:38 AM:
------------------------------------------------------------------

Ok, I've read in [documentation|https://wildscribe.github.io/Wildfly/8.1.0.Final/subsystem/undertow/server/http-listener/] that the default for redirect-socket is "https".

Would it be possible to show this attribute explicitly in the default configuration?

Specifically I would not expect anything related to "https" to be happening when I cannot string-search any "https" in the default configuration file.


was (Author: gdm85):
Ok, I've read in [documentation|https://wildscribe.github.io/Wildfly/8.1.0.Final/subsystem/undertow/server/http-listener/] that the default for redirect-socket is "https".

Would it be possible to show this attribute explicitly in the default configuration?

> redirect-socket="https" not explicit in default configuration
> -------------------------------------------------------------
>
>                 Key: WFLY-4245
>                 URL: https://issues.jboss.org/browse/WFLY-4245
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 8.2.0.Final
>         Environment: Linux 64bit
>            Reporter: Giuseppe Mazzotta
>            Assignee: Stuart Douglas
>            Priority: Minor
>
> Although this problem has been reported as fixed in WFLY-2836, I am still able to reproduce a failure by removing the https socket-binding from default standalone.xml configuration file:
> {noformat}
> --- standalone.xml.orig	2015-01-13 11:33:57.956000250 +0100
> +++ standalone.xml	2015-01-13 11:34:04.456000250 +0100
> @@ -375,11 +375,10 @@
>          <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
>          <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
>          <socket-binding name="http" port="${jboss.http.port:8080}"/>
> -        <socket-binding name="https" port="${jboss.https.port:8443}"/>
>          <socket-binding name="txn-recovery-environment" port="4712"/>
>          <socket-binding name="txn-status-manager" port="4713"/>
>          <outbound-socket-binding name="mail-smtp">
>              <remote-destination host="localhost" port="25"/>
>          </outbound-socket-binding>
>      </socket-binding-group>
> -</server>
> \ No newline at end of file
> +</server>
> {noformat}
> Failure in log is:
> {noformat}
> 11:10:23,601 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
>     "Services that were unable to start:" => ["jboss.ws.config"],
>     "Services that may be the cause:" => [
>         "jboss.binding.https",
>         "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
>     ]
> }}
> 11:10:23,602 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]"]}
> 11:10:23,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
>     ("subsystem" => "ejb3"),
>     ("service" => "remote")
> ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]}
> 11:10:23,663 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default] 
>       service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] 
> 11:10:23,674 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 11:10:23,675 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 11:10:23,675 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 3468ms - Started 175 of 231 services (3 services failed or missing dependencies, 81 services are lazy, passive or on-demand)
> {noformat}
> Is this expected behavior?
> *Edit:* due to configuration defaults, see below comments



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)