This implies then two separate files for setting these things, given
that we want setting them to be externalized from
standalone.sh/domain.sh itself.
On 2/3/12 4:52 AM, Max Rydahl Andersen wrote:
> I am very much in favor of a shared file for win and linux. I
just don't have any bandwidth to do it for 7.1.0 (1.1 maybe). Such a solution would
require that JBoss Tools parse the file since we have a chicken/egg problem with VM
launching on standalone, and we don't want to have a JVM launching a JVM in a
standalone setup (adds too much time to boot). It might also require that we write a
native launcher on windows.
>
> Although keep in mind that none of those JVM parameters are absolutely necessary. We
got rid of logmodule, which was the only required one. There is a couple of settings for
bootstrap logging, but the system will still work without it.
For me there are two different kind of arguments/parameters.
The one that are JVM specific/required at Java VM startup and those that are non-JVM
specific and can be read by the launcher it self.
It is the latter I'm suggesting to externalize.
OS specific/required at Java VM is currently for standalone.sh (as far as I can see?):
-d32
-client
-Xms64m
-Xmx512m
-XX:MaxPermSize=256m
-Djava.net.preferIPv4Stack=true
-Dsun.rmi.dgc.client.gcInterval=3600000*
-Dsun.rmi.dgc.server.gcInterval=3600000*
-Djava.awt.headless=true*
-jar
"/Users/max/jboss-runtimes/jboss-as-7.1.0.Final-SNAPSHOT/jboss-modules.jar"
*=might not be necessary to setup - depend if those are not getting activated during
jboss modules.
Arguments that I would think could be derived by the java launch instead of at command
line:
-Dorg.jboss.resolver.warning=true
-Djboss.modules.system.pkgs=org.jboss.byteman
"-Dorg.jboss.boot.log.file=/Users/max/jboss-runtimes/jboss-as-7.1.0.Final-SNAPSHOT/standalone/log/boot.log"
"-Dlogging.configuration=file:/Users/max/jboss-runtimes/jboss-as-7.1.0.Final-SNAPSHOT/standalone/configuration/logging.properties"
-mp "/Users/max/jboss-runtimes/jboss-as-7.1.0.Final-SNAPSHOT/modules"
-jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone
-Djboss.home.dir="/Users/max/jboss-runtimes/jboss-as-7.1.0.Final-SNAPSHOT"
Most of these could just be calculated based on jboss.home.dir as a nice default.
Leaving us with:
-Dorg.jboss.resolver.warning=true
-Djboss.modules.system.pkgs=org.jboss.byteman
-jaxpmodule javax.xml.jaxp-provider
Which could be read in via a properties file or even defaulted?
But Jason, I'm reading your mail as you even want to go to the length of having the
vm arguments externalized?
/max
http://about.me/maxandersen
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat