×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Technically this may be an RPG question because I only care about this
when calling Java from an RPG program, but I'll start here. I seem to be
losing my mind, because I've been unable to find a simple way to force
the JVM that's created to be a 64-bit with 3G of heap space. I managed
to do it, but it wasn't simple. I had to make configuration changes in
two different places and that never sits well.
To change the default JVM, I used the JAVA_HOME property and pointed it
to (...)/jdk80/64bit.
To change the max heap size, I had to use SystemDefault.properties with
an #AllowOptions and then -Xmx3G.
This isn't the end of the world, obviously - it functions. But I'd like
to make it a bit simpler, and I'd really prefer to not create a
SystemDefault.properties file. I don't mind JAVA_HOME; I can do that at
the job level. But SystemDefault.properties is a more user-level thing
and that could get messy if only one program needs that setting.
Did I just miss a simpler way to do this?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
