Multiple instances of OC4J on the same machine

Question

Is there a way to cofigure OC4J to have a few processes on the same machine, all listening to the same ports?
My purpose is to develope and deploy a few applications on the same machine, and each application should has its own process, so if onw fails or restarts, it will not effect the other applications and the other programmers.
I don't want to make each application to be bounded to differnt port.
is it possible ?

Answer 1

Two instances of oc4j cannot listen to the same port...you will
get an error.
To do this, you will need to cluster oc4j. This is fairly easy,
but you app needs to be "clusterable". All classes need to be
serializable which are used by your servlets. The
<distributable /> tag needs to be in your web.xml file. No
stateful session beans can be used. (sorry, but oc4j doens't yet
support clustering with sfsb's).
The second step is that your default-web-site.xml or *-web-
site.xml file should be set up for clustering. Do this by
creating a cluster-island attribute in your web-site tag. Also
change the port from 8000 to something like 8080 or 8090 or
something else. It should look like this:
<web-site host="192.168.1.101" port="8080" display-name="some-
name" cluster-island="1">
<default-web-app application="someapp" name="someappname" />
<frontend host="192.168.1.101" port="8000" />
<access-log path="../log/some-web-access.log" />
</web-site>
Your server.xml and application.xml will be the same as when you
don't cluster.
Make sure you have 3 different copies of your j2ee/home
directories...of course with different names....like home1 and
cluster.
Edit the rmi.xml and jms.xml files to change the port number
that the home1 oc4j will listen to. The jms port is usually 9127
by default, so use 9128. The rmi port is 23791, so change it to
21792. This will keep the rmi and jms servers from conflicting.
Make sure that the home1 config/default-web-site.xml uses a
different port than 8080, say 8090, but the cluster-island name
is still 1.
Open terminal windows for each instance of oc4j, and start them
in the normal way.... java -jar orion.jar
Open a terminal window for the j2ee/cluster, and issue this
command:
java -jar loadbalancer.jar -host 192.168.1.101 -port 8000
You should see that each of your oc4j instances are recognized.
There...that wasn't so bad, was it?
regards,
the elephantwalker
www.elephantwalker.com