Thanks for the reply. I just figured it out. The SSL connector configuration
in server.xml was missing the
address="${jboss.bind.address}"
attribute. I'm not sure why it was missing, but when I added it in, the
different instances are binding to a single address like they used to.
Thanks,
That was a typo on the first message. This is really what was run:
./run.sh --host=ia.dev.seerdms.imsweb.com --configuration=ia
Then,
./run.sh --host=dt.dev.seerdms.imsweb.com --configuration=dt
The error is the same.
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
I found another clue. Even though I launch with:
./run.sh --host=ia.dev.seerdms.imsweb.com --configuration=ia
I can access the server from both the passed address and the machines default
address. So both of these addresses can access the running server.
ia.dev.seerdms.imsweb.com
dev.seerdm
With version 4.0.4, it was easy to get multiple instances running under
different IP addresses on the same machine. Under 4.0.4, we set up a
configuration per deployment and started them like this:
./run.sh --host=ia.dev.seerdms.imsweb.com --configuration=ia
Then,
./run.sh --host=ia.dev.seerd
