-
1. Re: 2 JBoss instances on multi-homed machine
"juha@jboss.org" wrote:
Maybe this will help:
<tt>
$ sh run.sh --help
================================================================================
JBoss Bootstrap Environment
JBOSS_HOME: e:\JBoss\jboss-3.2.3
JAVA: /cygdrive/c/j2sdk1.4.2/bin/java
JAVA_OPTS: -server -Dprogram.name=run.sh
CLASSPATH: e:\JBoss\jboss-3.2.3\bin\run.jar;c:\j2sdk1.4.2\lib\tools.jar
================================================================================
usage: run.sh [options]
options:
-h, --help Show this help message
-V, --version Show version information
-- Stop processing options
-D<name>[=<value>] Set a system property
-c, --configuration=<name> Set the server configuration name
-j, --jaxp=<type> Set the JAXP impl type (ie. crimson)
-L, --library=<filename> Add an extra library to the loaders classpath
-C, --classpath=<url> Add an extra url to the loaders classpath
-P, --properties=<url> Load system properties from the given url
<b><font color="red">-b, --host=<host or ip> Bind address for all JBoss services</font></b>
</tt> -
2. Re: 2 JBoss instances on multi-homed machine
"sheckler" wrote:
Hi,
I tried it out, but it comes out as
run.sh: invalid option -- b
I was quite succedssfull with writing a jboss-bindings.xml file and specifiying for each service a binding host based on the sample file, which came with the JBoss 3.1.2 sources. This way I succeeded to start 2 JBoss instances on the same host with the same set of ports. But the testing has not started until now...
Stefan Heckler -
3. Re: 2 JBoss instances on multi-homed machine
"juha@jboss.org" wrote:
Correct, the host option wasn't added until 3.2.2, I missed that you were using 3.2.1 -
4. Re: 2 JBoss instances on multi-homed machine
"sheckler" wrote:
It will be much easier then with 3.2.2 and 3.2.3!
As I have to use 3.2.1 by now and struggle with jboss-bindings an other question:
every service is using the jboss-bindings except Jetty, which conflicts using SocketListener@0.0.0.0:8080.