User: mulder
Date: 00/10/25 09:42:29
Modified: manual adv_config.html warning.html
Log:
Update directions for running multiple jBoss instances on the same
server. Will update again if Rickard changes to switch configurations
based on directory instead of file prefix.
Update ports section to include RMI object port (4444).
Revision Changes Path
1.18 +49 -14 jbossweb/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/adv_config.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- adv_config.html 2000/10/25 00:03:04 1.17
+++ adv_config.html 2000/10/25 16:42:29 1.18
@@ -811,21 +811,43 @@
<h2><a NAME="multiple">Running Multiple jBoss Servers on One Machine</a></h2>
<p>It is possible to run jBoss more than once on the same machine.
- You will have to set up multiple jBoss directory structures,
- however - you cannot start it more than once from the same set
- of files. Additionally, you will need to change all the default
+ There are two way to do this: running two instances out of the
+ same installation directory, and setting up separate installation
+ directories. In either case, you will need to change all the default
ports on your second and subsequent servers. You may avoid some
- of this if you elect to disable the management interface and
- use a single JNDI server for all registration, but at a minimum
- you need a separate port for the RMI server. Follow the
- instructions below to change the default ports.<p>
+ of this if you elect to disable the management interface, but at
+ a minimum you need separate ports for the RMI server and JNDI
+ server. Follow the instructions below to change the default
+ ports.<p>
+ <p>If you run jBoss more than once from the same directory
+ structure, you will need to use a second set of configuration
+ files (see <a HREF="config.html#files">Configuration Files</a>).
+ You will also need to remove all the
+ <code><RMIObjectPort></code> tags from
+ <code>conf/standardjboss.xml</code>. This will set the RMI
+ server objects to use anonymous ports (i.e. pick a free one and
+ use it) rather than sharing the same port (which doesn't work
+ across more than one VM). You may choose to change the
+ AutoDeployer directory for subsequent servers, by changing
+ the argument to the <code>AutoDeployer</code> service in
+ <code>conf/jboss.conf</code>:</p>
+<pre>
+ <ARG TYPE="java.lang.String" VALUE="<b>../otherDeployDir/</b>">
+</pre>
+ <p>If you run jBoss more than once from separate directories,
+ you can choose to remove the <code><RMIObjectPort></code>
+ tags as above, or just change the port for all additional
+ servers. You must change it one way or another, because
+ only one VM can use the same port.</p>
+
<h2><a NAME="ports">Changing Defalt Port Assignments</a></h2>
- <p>jBoss uses three ports, by default. The JNDI server listens on
+ <p>jBoss uses four ports, by default. The JNDI server listens on
port 1099 for JNDI requests, the management interface listens on
- port 8082 for JMX requests, and the RMI server listens on port
- 1083 for RMI requests. If you change any of the ports, you must
- restart the jBoss server for the changes to take effect.</p>
+ port 8082 for JMX requests, the RMI server listens on port
+ 1083 for RMI class requests, and the RMI objects listen on port
+ 4444. If you change any of the ports, you must restart the
+ jBoss server for the changes to take effect.</p>
<p>To change the JNDI port, edit the file
<code>jnp.properties</code> in the <strong>conf</strong>
directory. Change the line <code>jnp.port</code> to the port you
@@ -846,14 +868,27 @@
<attribute name="Port"><b>8082</b></attribute>
</mbean>
</pre>
- <p>To change the RMI port, change the following entry in
- <code>jboss.jcml</code> in the <strong>conf</strong> directory.
- Your clients should use the new port automatically.</p>
+ <p>To change the RMI class server port, change the following entry
+ in <code>jboss.jcml</code> in the <strong>conf</strong>
+ directory. Your clients should use the new port
+ automatically.</p>
<pre>
<mbean name="DefaultDomain:service=Webserver">
<attribute name="Port"><b>8083</b></attribute>
</mbean>
</pre>
+ <p>To change the RMI object port, change the
+ <code><RMIObjectPort></code> entries in
+ <code>standardjboss.xml</code> in the <strong>conf</strong>
+ directory. There is one entry for each container
+ configuration. If you remove the tag altogether, the objects
+ will each use a different port (just picking one that's
+ available). You can also override this port setting in
+ custom container configurations declared in the jBoss
+ Deployment Descriptor (see <a HREF="deploying.html#jboss">The
+ jBoss Deployment Descriptor</a>) - but you cannot force it
+ to use anonymous ports, just select a different port to share.
+ Your clients should use the new port automatically.</p>
<h2><a NAME="dynamic">Dynamic Classloading for Clients</a></h2>
<p>Normally, a client must have a number of JARs available. These
1.13 +0 -3 jbossweb/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/warning.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- warning.html 2000/10/22 01:57:22 1.12
+++ warning.html 2000/10/25 16:42:29 1.13
@@ -46,14 +46,11 @@
<li>Need to try dynamic classloading to verify directions
and get an exact procedure with security policy settings
that are required.</li>
- <li>Confirm that multiple jBoss instances can use the same
- JNP JNDI server. Upon reflection, this seems unlikely.</li>
<li>Confirm java.naming.provider.url=server:port syntax
for changing the JNP port.</li>
<li>If you change the port for the webserver on 8083, confirm
that clients can access it automatically. Have verbal
confirmation, need to try.</li>
- <li>Add directions for changing RMI object port 4444</li>
</ul>
</li>
<li>Starting & Stopping jBoss
