U can go to ubeans technologies web site and there is a document there for using apache as load balancer and serving 2 tomcat ....in ur case u can use jboss instead of tomcat..........
i am doing this also and it is successfully running but i am facing a problem on hot deployment ......when i start my two jboss they both detect each other and when i deploy the ear and jar in farm directory ,it is deployed in the other jboss also ..........that is fine .But if i start with my ear and jar already in farm dierctory then it is deployed in that jboss but in other jboss it starts deploying but struck inthe middle and it doesnot move ahead.
do u have any solution for it.
can you provide a file with either the exception that shows up or a complete stacktrace (press CTRL+BREAK in the console if under windows)
I don't have the logs right now with me. However I could make it to work, I needed to use the following
UDP string (I think for my initial development environment this is ok). The UDP string provided on either JavaGroups site or on the JBoss book were giving me the problems.
Thanks to all for helping me out to resolve the issue.
<!-- Making one Default Cluster by +++Raghu -->
You should be able to run any of the JavaGroups demo programs to see whether a given protocol spec is okay. We recomment using the predefined ones in JG/conf, or at least start from there if you want to modify it. Use Draw or DistributedHashtable tests (the latter for state transfer testing).
last days i have begun the same task.
If you plan to use Apache take a look at the JK2-Dokumentation @ apache.org:
In the workers HowTo you can find the needed informations to set up apache (or better, mod_jk) as an load-balancer in front of some tomcat/catalina clients.
BTW, did you use the AJP13 connector? With 3.0.4 i have had many problems trying to use the new coyote connectors because their config in the service file are ignored by jboss.
And if you dont start jboss as a superuser you should use only ports above 1024.
I had problems with Coyote Connector. The configuration for Apache-Jboss/Tomcat with the AJP13 is working fine. For my development purposes I am running the JBoss on 8080 so there is no problem/issue with the port numbers.