I got the 2 server instances running but I had to change quite a few ports in the config-substitutions.properties file. Why is it saying the ports are in use when the 2 servers instances are bound to different IP addresses?
I have nothing running on this box except for the 2 instances of geronimo? Is this a known issue? Is there a way to fix this?
----- Original Message ----
From: Donald Woods <firstname.lastname@example.org>
Sent: Thursday, February 7, 2008 12:33:28 PM
Subject: Re: Can you bind 2 separate geronimo server instances to 2 different ip addresses?
Any component listening on 0.0.0.0 could be causing this....
Can you run "netstat -a" and see if any of the first server instance's
ports are still bound to 0.0.0.0 and post the results? It could just be
a simple matter of updating config.xml to override some default
configuration settings (and then fixing it with a JIRA for which ever
version of Geronimo you are using.)
> Can you bind 2 separate geronimo server instances to 2 different ip
> I changed the all IPs and host names in the
config-substitutions.properties file for the new instance. I even
> changed the BASE_DIR to point to the new geronimo installation
> directory. But when I try to start up the server it gives the port in
> use error.
> Is this possible at all running to instances of the server on 2
> different IPs on the box?
> I have seen the following setup, but our configuration thus far has been
> to use different IPs for different server installs.
> Any inputs will be much appreciated.
> Multiple Server Instances
> A server instance is easy to create in Geronimo:
> 1. Set the org.apache.geronimo.server.name
system property to the
> instance name before you
start the server.
> * Use the syntax -Dorg.apache.geronimo.server.name=foo to name
> your instance foo.
> * There are two ways to do this:
> 1. Add this to your GERONIMO_OPTS environment variable, or
> 2. Pass it on the java command-line invocation of the
> * This server's var and deploy directory will then be under
> * org.apache.geronimo.server.name
may be any pathname relative
to (descending from) <geronimo_home>. For example,
> servers/bar would put the server's var directory under
> * The org.apache.geronimo.server.dir system property may also
> be used, and it overrides org.apache.geronimo.server.name
> * Use org.apache.geronimo.server.dir to specify an absolute
> path, which need not be relative to <geronimo_home>. For
> example, /ag20/servers/bar would put the server's var
> directory under /ag20/servers/bar. Otherwise, the two
> properties behave the same.
> 2. *mkdir foo*
> 3. Copy var/* to foo/var/
> 4. Edit foo/var/config/config-substitutions.properties, uncomment
> PortOffset and change it to a value like 1,2,10,11,12,20,21,22,...
> so the ports in the new server instance will not conflict with
> existing server instances you already have defined and/or started.
> (Alternatively start the server with the property
> -Dorg.apache.geronimo.config.substitution.PortOffset=3 in the
> command line)
> 5. Start the server.
> To deploy applications to the new server instance, you need to specify
> the NamingPort+PortOffset used, such as for PortOffset=1:
* deploy -port 1100 list-modules
> Looking for last minute shopping deals? Find them fast with Yahoo!