Correct way to upgrade mod_cluster in JBoss AS/WildFly?

[marcodanti]

What is the proper procedure to install a new version of mod_cluster into JBoss AS7? I already upgraded the httpd part of mod_cluster (.so files), but I am not sure about how to proceed for JBoss...

[rhusar]

Let me note first, that modcluster parts talk to each other via mod_cluster management protocol which does only rarely change. Therefore, it is not mandatory to upgrade mod_cluster in AS as well as HTTPd (note that 1.2.x to 1.3.x upgrade would need that).

To upgrade, look into

jboss-as-7.2.0.Final/modules/system/layers/base/org/jboss/as/modcluster/main/

IIRC the best way would be to

1. copy /main to some backup location in case you want to revert, i.e. to /1.2.3.Final
2. remove mod_cluster-*-1.2.3.Final.jar keeping in integration implementation (i.e. jboss-as-modcluster-7.2.0.Final.jar)
3. copy over updated or custom version container-spi, core, container-catalina, container-jbossweb jars
4. update module.xml with the new file names

HTH

[marcodanti]

Thanks a lot man, I will try.

[marcodanti]

I followed the steps, and it seems to work, but the JBoss log does not display the mod_cluster version properly:

10:30:08,779 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 52) MODCLUSTER000001: Initializing mod_cluster ${project.version}

Before upgrading it said

13:27:01,859 INFO  [org.jboss.modcluster.ModClusterService] (ServerService Thread Pool -- 52) Initializing mod_cluster 1.2.3.Final