are you using JBoss 2.4 or 3.0?
If 3.0, are you using clustering?
Hi. I'm using JBoss 3.0 and I launch it with
./run.sh -c all
as a matter of fact the first instance starts as
Are you sure you changed ALL ports?
I've tried it with 3.0 and I'm pretty sure I was sucessfull on my attempt. Have you changed the http port setting for jetty? (It's config file comes inside a package in the deployment directory, maybe you forgot about that one)
You would first have to do 1 of 2 different things.
First option) Copy the 'all' configuration to another configuration like 'all2'
Execute jboss1 with -c all and jboss2 with -c all2
Second option) Duplicate the jboss-3.0 directory to create a seperate instance of jboss.
Execute jboss1 from first directory and jboss2 from second directory
The following files in the appropriate server directory would have to be modified. The default port setting is given:
Description: WebServer Service Port: 8083
Description: Naming Service Port: 1099
Description: Invoker, Type=JRMP Port: 4444
Description: OIL Port: 8090
Description: UIL Port: 8091
Description: HA-JNDI Service Port: 1100
Note: uses 1102 for multi-cast IP discovery of other nodes (ok if both are same)
*-- For Jetty --*
Description: Jetty HTTP Listener Port: 8080
Note: (I think port 8082 is used by a service some place, but I'm not entirely sure)
*-- For Tomcat --*
Description: Apache HTTP Adaptor Port: 8080
Both instances should be able to stop and start independantly if configured correctly. Because of issues with RMI and optimization, it is better to individually change all the appropriate ports and not to try binding each process to a seperate IP address.
You should also change
- in conf/jboss-service.xml:
- the port of the AJP listener (default 8009) if you're using one (in Jetty/Tomcat configuration).