Hi Ricardo,
On 28 Oct 2025, at 23:01, Ricardo Parada via Webobjects-dev
<[email protected]> wrote:
> The bundle it builds, let’s assume it’s called ERXApp.woa has a launcher
> script inside called ERXApp. When I run it I can see it’s running java with
> -Xmx64m -Xms32m and then everything else like the classpath and the class of
> the application to run.
>
> My question is, can I control the Xmx and Xms options injected in the script?
>
> I tried using jvmOptions property inside build.properties but they get added
> in addition to the ones already there: -Xmx64m -Xms32m.
Interesting. Firstly, I set heap size using "Additional Arguments" in
JavaMonitor, because I might want to vary it based on the deployment
environment. In any case, I can see in the launch script that the only place
it's setting those values is where "${PLATFORM_TYPE}" = "Darwin", and it's
adding them to $DEFAULT_JVM_OPTIONS. I assume later when $JVM_OPTIONS are
appended that your heap settings override the default ones—check the running
JVM. I imagine you could just ignore this. (That whole block of default options
for launching on macOS could probably be deleted.)
--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/
