Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-467

ExcludedContexts are ignored if modcluster subsystem initialize before default-host

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide

      Take a fresh build of JBoss 7.2.0.Final, modcluster 1.2.11.Final and the jmx-console.war deployed.

      In the standalone.xml :

      <subsystem xmlns="urn:jboss:domain:modcluster:1.1">
      <mod-cluster-config advertise="false"
      proxy-list="127.0.0.1:8666,"
      connector="https"
      balancer="app-cluster"
      sticky-session-force="true"
      sticky-session-remove="false"
      sticky-session="true"
      auto-enable-contexts="true"
      excluded-contexts="ROOT,jmx-console">
      </mod-cluster-config>
      </subsystem>

      Show
      Take a fresh build of JBoss 7.2.0.Final, modcluster 1.2.11.Final and the jmx-console.war deployed. In the standalone.xml : <subsystem xmlns="urn:jboss:domain:modcluster:1.1"> <mod-cluster-config advertise="false" proxy-list="127.0.0.1:8666," connector="https" balancer="app-cluster" sticky-session-force="true" sticky-session-remove="false" sticky-session="true" auto-enable-contexts="true" excluded-contexts="ROOT,jmx-console"> </mod-cluster-config> </subsystem>
    • Affects:
      Compatibility/Configuration

      Description

      With JBoss 7.2.0.Final, modcluster will ignore excludedContexts defined in modcluster subsystem (ie jmx-console, ROOT). This is caused by engine.getHosts() not yet available when org.jboss.modcluster.ModClusterService.init(Server) try to setup his list of excludedContexts.

        Attachments

          Activity

            People

            Assignee:
            rhusar Radoslav Husar
            Reporter:
            plgregoire Pierre-Luc Gregoire (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: