2 Replies Latest reply on May 31, 2012 1:21 PM by Ram S

    Upgrade to Jboss 7.1.2 seems to break mod cluster configuration.

    Ram S Newbie

      Hi

       

      I upgraded to Jboss 7.1.2 from 7.1.1 two weeks back, and it looks like when the container now comes up, it no longer looks for the http server to connect to

      Basically the mod cluste configuration in standalone.xml is not taking effect.

       

      The configuration i had for 7.1.1 was :

       

      <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

          <mod-cluster-config  proxy-list="..." sticky-session="true" sticky-session-force="false" sticky-session-remove="true"/>

      </subsystem>

       

       

      And the http side configuration was

       

       

       

      <VirtualHost 0.0.0.0:8082>

               <Directory />

              Order deny,allow

              Deny from all

              Allow from all

              </Directory>

       

       

              <Location /mod_cluster-manager>

              SetHandler mod_cluster-manager

              Order deny,allow

              Deny from all

              Allow from all

              </Location>

       

       

              KeepAliveTimeout 60

              MaxKeepAliveRequests 0

       

       

              LogLevel debug

       

       

              ProxyPass / balancer://mycluster/ stickysession=DIY|DIY nofailover=On

              ProxyPassReverse / balancer://mycluster/ stickysession=DIY|DIY

       

       

              ManagerBalancerName mycluster

              #AdvertiseFrequency 5

              #ServerAdvertise Off

              AllowDisplay On

              EnableMCPMReceive

       

       

      </VirtualHost>

       

      The version of modcluster i was using before was 1.2.0.Final

      I have not upgraded this version to 1.2.1 yet (it looks like jboss 7.1.2 is using mod cluster 1.2.1)

       

      In the logs, i found :

      service jboss.web.connector.ajp (missing) dependents: [service jboss.mod-cluster]

       

      I am not sure why ajp is suddenly a dependency of modcluster. Any suggestions on what the issue could be would be really helpful

       

      Thanks

        • 1. Re: Upgrade to Jboss 7.1.2 seems to break mod cluster configuration.
          Paul Ferraro Master

          The modcluster subsystem schema was updated to version 1.1 between 7.1.1 and 7.1.2.  The new subsystem schema adds a new proxy-connector attribute which specifies the connector with which mod_cluster should communicate with httpd.  The new attribute is required in version 1.1 of the schema, but for upgrade purposes defaults to "ajp".  It seems you do not have a connector named "ajp" defined in your web subsystem.  You probably want to either add an ajp connector, or set proxy-connector to "http".

          • 2. Re: Upgrade to Jboss 7.1.2 seems to break mod cluster configuration.
            Ram S Newbie

            Hi Paul

             

            Thanks that was very helpful. Yes I was able to set the connector to http and change the version of modcluster subsystem to 1.1 and get it to work.

            There was one thing i noticed:

            In the earlier versions, we have advertise=true by default, but if you specify proxy-list and it is non empty, then the subsystem uses the proxy list

            In the current release, if i do not explicitly set advertise=false, the proxy-list is not used and it thinks we are still using multicasting, and fails when multicast socket binding are not specified.

            So to get this running, i have set advertise=false and then it all works.