After struggling with my own httpd setup I finally removed and installed mod_cluster-1.2.0.Final-linux2-x64-ssl.tar.gz
That solved a lot of issues
I see the welcome on port 8000 (httpd has Listen 8000)
I also see the JBoss console on port 9990
httpd.conf has the following directives:
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
# MOD_CLUSTER_ADDS
# Adjust to you hostname and subnet.
<IfModule manager_module>
Listen 127.0.0.1:6666
ManagerBalancerName other-server-group
<VirtualHost 127.0.0.1:6666>
<Location />
Order deny,allow
Deny from all
Allow from 127.0.0.
</Location>
KeepAliveTimeout 300
MaxKeepAliveRequests 0
ServerAdvertise on
AdvertiseFrequency 5
#AdvertiseSecurityKey secret
#AdvertiseGroup @ADVIP@:23364
EnableMCPMReceive
<Location /mod_cluster_manager>
SetHandler mod_cluster-manager
Order deny,allow
Deny from all
Allow from 127.0.0.
</Location>
</VirtualHost>
</IfModule>
My question is, how do I get to the web service from my front end
The front end is a c sharp application that connects with:
<client>
<endpoint address="http://192.168.2.3:8082/beans/XMLTranServiceBean/XMLTranServiceBean"
binding="basicHttpBinding" bindingConfiguration="XMLTranServiceBeanSoapBinding"
contract="CapitalWebService.XMLTranServiceBean" name="XMLTranServiceBeanPort" />
</client>
The above example works because it goes straight to JBoss http port defined as 8082 (as defined in domain.xml).
The question is: how do I play this into the cluster via httpd ?
To put it simply, I am looking for the mod_cluster equivalent of the mod_jk config file workers.properties
It had this directive inside: /*XMLTranServiceBean/*=loadbalancer
That fished out my front end transactions in httpd before, any URL with the above strings inside would go to JBoss 4 via Tomcat 8009
How does that work with mod_cluster ?
Thanks and best regards
Johan Vermeij
Jakarta
