Dear Chris, you should not, or I would even say must not, use mod_cluster 1.2.6 It is a vastly obsolete version comprising serious performance and CVE issues.

On the issue of mismatch detected: Contrary to what you found on that Bugzilla, it is actually an issue (with that Bugzilla, it was ascertained that it was OK at the time with that particular version). The problem is mod_cluster relies on mod_proxy's internal (private) APIs that could change with any httpd patch or even more likely with a micro updates. To be safe from intermittent Segfaults caused by a different structure sizes, one has to recompile mod_cluster with any new httpd.  It is O.K. for you to use different versions of mod_cluster on Apache HTTP Server side and JBoss AS/Wildfly side -- the protocol they talk to each other with is the same up to mod_cluster 1.3.2.

If you need assistance with recompiling mod_cluster with your particular version of httpd, tell us the operating system and architecture you use and we will be glad to help you.

Cheers

-K-

Dear Chris, there is nothing dodgy about it. git clone, cmake, make...

The following example is an ASCII recorded terminal session that walks one through on Fedora 24: Examples – mod_cluster

Note that cmake build file wasn't part of the older versions. For them, one has to either copy that CMakeLIsts file or use Autotools: Documentation – mod_cluster

Cheers

-K-

Hi Michal,

I could use some help compiling mod_cluster 1.3.1 Final for Apache 2.2.31 on Windows 32 bit (x86).

Any chance you can guide me through the compile process?

Thank you.

J

See Chapter 4. Building mod_cluster from sources

This is how you compile on Windows: mod_proxy_cluster/README.md at master · modcluster/mod_proxy_cluster · GitHub

Beware of renaming the repo from mod_cluster to mod_proxy_cluster, so one might to adjust  a name or two in the tutorial.

Cheers

-k-

This is probably posted by mistake - it's for Linux and for an obsolete version.