[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-459) mod_cluster subsystem remains silent if connector set to http

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek moved JBEAP-224 to MODCLUSTER-459:
-------------------------------------------------

              Project: mod_cluster  (was: JBoss Enterprise Application Platform)
                  Key: MODCLUSTER-459  (was: JBEAP-224)
             Workflow: GIT Pull Request workflow   (was: CDW v1)
    Affects Version/s: 1.3.1.Final
                           (was: EAP 7.0.0.DR2)
        Fix Version/s: 1.3.2.Alpha1
                           (was: EAP 7.0.0.DR3)
       Target Release:   (was: EAP 7.0.0.GA)


> mod_cluster subsystem remains silent if connector set to http
> -------------------------------------------------------------
>
>                 Key: MODCLUSTER-459
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-459
>             Project: mod_cluster
>          Issue Type: Bug
>    Affects Versions: 1.3.1.Final
>            Reporter: Michal Babacek
>            Assignee: Paul Ferraro
>             Fix For: 1.3.2.Alpha1
>
>
> If one sets mod_cluster subsystem {{connector="http"}} there is nothing in the log about any mod_cluster subsystem being initialized, no warning, nothing. It appears to be dead silent even with log level DEBUG.
> When switched back to {{connector="ajp"}}, there are the well known comforting messages:
> {noformat}
> INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000001: Initializing mod_cluster version 1.3.1.Final
> INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 62) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364
> {noformat}
> Weird. Any obvious misconfiguration or explanation? The config is the default standalone-ha.xml otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)