If you look more carefully, the processing of the -D option will set back the jboss.bind.address to the one you specified.
Maybe there are other issues, since -b will execute additional setup logic.
But the -D option isn't an argument to org.jboss.Main. It's only an argument to the JVM. The Java class never sees it as a command line argument. All that happens is the system property gets set. I don't see how it could be preserved in that code. And my tests show -Djboss.bind.adress has no effect.
It will be an argument to org.jboss.Main if you include it with your ./run.sh command line, e.g.:
run -c minimal -Dorg.jboss.bind.address=X.Y.Z.W
I suppose you've tested adding it to JAVA_OPTS.
Yes, I've added it to JAVA_OPTS, and it doesn't do anything. -D makes it seem like a System property, but it looks like org.jboss.Main doesn't want it provided as a system property.
Unfortunately, in run.conf, you can only add things to JAVA_OPTS. There's nothing in there to add arguments for org.jboss.Main. It would be really handy to have a way to do that so I can put the bind address in a file, and then I can start the thing without worrying about "did I put the -b arg in there".
Of course I can modify run.sh itself.
Any other good ways to do this?
Anyone find a solution?