How to run multiple instances of JBoss in a one single machine?

Question

I need to run multiple(more than 4) instances of JBoss server on a single machine. I am using JBoss 4.2.3 GA.

Answer 1

Copy complete JBOSS setup to new location, and start new server with offset option, which will start server on existing ip and changing port to previously_configured_port+offset

standalone.bat -c standalone-full.xml -Djboss.socket.binding.port-offset=100

This command will make default jboss console 9990 to 10090

Now you can add your war file in new deployments folder and start deployment on new port

Answer 2

I found the answer. We have to configure the jboss-service.xml to run multiple instances in the same machine.

We may need to keep the same "default" instance same as it is under the JBOSS_HOME\Server.

We have to create another folder say "instance2" under JBOSS_HOME\Server. Copy all the contents from JBOSS_HOME\Server\default to this newly created folder.

Now goto conf folder under JBOSS_HOME\Server\instance2 directory. Edit the jboss-service.xml. Search for mbean code="org.jboss.services.binding.ServiceBindingManager" in this configuration file.

By default this xml tag is commented. We have to un comment it and change the value ports-00 to ports-01.

Then start this instance2 jboss instance. We can access this application by using the port number 8180.

We can go for at maximum of 3 instances with this way.

To run more than this we have to add some more running tags in JBOSS_HOME\docs\examples\binding-manager\sample-bindings.xml.

Answer 3

You can make things a lot simpler by simply changing the IP that the server is bound to.

You will need to copy the entire jboss folder several times and configure run.bat to use the -b parameter on startup.

If this is a Windows server and you're running jboss as a service, you might want to edit the service.bat for each instance too so that the servers all have different names in the services control panel.

Part of the problem we ran into when trying to use different HTTP ports was that jboss uses 'lots' of ports for different purposes and it was a pain to edit all of these port numbers to be unique on each instance. By changing the bind address you can avoid this problem entirely.