Thanks Peter.
But that's potentially a huge number of system properties to be set via a
command line if you heavily customise JBAS configuration.
I could exceed the command line length on some operating systems...
Shame you can't specify something like a properties bundle to the deployers.
Then use the properties service - it lets you identify a file containing system
properties - and you can even specify the filename as a property. Look at
server/default/deploy/properties-service.xml.
View the original post :
Oh, and one other thought - the correct way to specify different port number is
to use the binding service. See
server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml.
This file defines groups of port bindings that you can select from the command
line like this:
run
Thanks again Peter.
...feeling a little embarrassed now I found further details of this in the book
JBOSS in Action. A book I'm finding really useful BTW, although it looks like
I need to study it some more ;-)
View the original post :
The jboss.jgroups.udp_async.mcast_port is a system property, you can set it on
the command line:
run -Djboss.jgroups.udp_async.mcast_port=12345
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243588#4243588
Reply to the post :
The general syntax is:
${system-property[:default-value]}
As far as I know, it applies to all configuration files.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243589#4243589
Reply to the post :
