RM> Hello Hans,
RM> The turbo switch is an example system property defined by the -D option:
RM> java -DTURBO ...
RM> turbo = System.getProperty("TURBO") == null ? false : true;
RM> I am passing options to java with -D through the VM options dialog under
RM> server configuration. I assume that is the IDE analog to setting the
RM> JAVA_OPTS environment variable that the jboss run script uses. The reason
RM> you got an error with the memory settings is that -Xmx512 is mistyped
RM> (-Xmx512m is correct) but I only used that as another example of VM
RM> arguments not getting passed to java. The key point is that VM arguments are
RM> not being passed on.
RM> I use Show | View | Configuration then select my default server
RM> configuration. You have kindly provided two inputs under the start(x) tab:
RM> Program arguments and VM arguments. The latter is where I am setting the VM
RM> arguments I provided in my example. They are not making it to the java VM
RM> that JBoss is running under when debugging. That's causing my application to
RM> fail. Maybe that input box is not hooked up to pass VM arguments yet? This
RM> is an "alpha" after all :)
It passed the vmargs but some white spaces where missing so that to
the java process two of them appeared as one. This bug has been fixed
and checked in cvs.
See build-howto:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/website/content/src/web/default/developers/projects/jboss/jbosside/build_howto.html
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
