I have a moderately large environment with multiple JBoss clusters. Our general practice has been to use a one to one relationship between Apache instances and JBoss clusters. Our multiple Apache instances share a single set of Apache binaries.

I have found when trying to set up more than one Apache/mod_cluster/JBoss stack, mod_cluster seems to get confused. mod_cluster-manager on any of the instances seems to know about the JBoss nodes that should be connected and visible only to other mod_cluster instances.

It looks like the root of this behavior are the sockets/files that are created under <apache_bin>/logs/

Is there a way to configure mod_cluster to tell it to put these objects in a specific location for each Apache instance, similar to how I already tell each Apache instance to put its access/error logs in a location specific to each instance?

Strange. That directive sure looks like what I was looking for, however it seems like it is being ignored. FWIW, I am using mod_cluster 1.0.4 GA but the docs show that directive is available for 1.0.X also. Maybe something else is wrong with my configs...

Apache server root is /env/atlas.bomba.dev/cust/apache/usr/.

The MemManager files are still showing up in /env/atlas.bomba.dev/cust/apache/usr/logs/ and not at the paths I am defining in each instance config.