Are you really trying on 4.3? Please look at the requirements for mod_cluster:
This old version is unsupported so you are on your own in this :-(
You should look in the access_log for httpd and/or try with curl (or a browser) to reach <hostname>:<port> from the jboss nodes.
In JBoss 4.x, you cannot specify the excludedContexts via a system property (this is only supported in JBoss AS5 and later). Instead define your excludedContexts in the listener itself.
<Listener className="org.jboss.modcluster.catalina.ModClusterListener" advertise="false" excludedContexts="..."/>
Thank you guys, I do see the requirements for jboss 5 the part that i did see in the docs that suprised me was that jboss 4.2 and 4.3 has instructions and they are clearly not 5.x.
I have confirmed there is not a connectivity issue from the JBoss servers to the apache server and there are no issues with a JBoss 5.x instance from the same host connecting to apache given the same command line paramteres. I have configured the listener as the docs state and I see the log message for the mod_cluser 1.1.3 initilize in the logs.
the only part that is missing is the service registering with the apache instance.
I am also seeing that the 1.1.3 on 5.x does publish the ROOT context , even though it is listed in the excludeContexts in config file.
Thanks in advance as always
The registration of the ROOT context when it should be excluded is a regression cause by MODCLUSTER-220. It is fixed by MODCLUSTER-253, which was just reported today.
Cool that is great news I will look to use 1.1.4 when it is released, in the mean time we have added an apache handler for take care of this problem.