-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Allow javaArgs for all Zowe Java processes #3865
Comments
@balhar-jakub I'm going to move this over to api-layer as the biggest source of java, but, here's a thought to spark discussion: Because there's many uses of java, let's continue following the sort of standardization pattern we recently did with things like networking. Idea 1 - Object based YAMLIf we assume all args implicitly have "-", it can be omitted and the object could look like: java:
args:
Dkey: value
components:
gateway:
java:
args:
Dkey: override Where, we have an object for global use, and then an override for a specific server use. Omitting "-" would be helpful because a YAML key starting with "-" could cause user error, parsing error, or env var error. The object format could use some more thought for what is best. Idea 2 - one big ugly stringjava:
args: "-Dkey0=value0 -Dkey1=value1" In your code maybe it would look like
|
let me know what you come up with here because might want to do the same for nodejs. |
z/OSMF has the following |
Has anyone tried using IBM_JAVA_OPTIONS or OPENJ9_JAVA_OPTIONS to see if it has an effect? |
To help me investigate a problem, I've
updated ./components/discovery/bin/start.sh. It allows you to have
component specific Java options.
This is just a bodge to show the concept .. it needs to be done properly
It is based on a java.options.AD file... for the AD component.
*fn="/u/tmp/zowec/java.options.AD <http://java.options.AD>" if [ -f "${fn}"
]; then COLIN="-Xoptionsfile=${fn} -XshowSettings" else COLIN="" fi
- - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - DISCOVERY_CODE=AD _BPXK_AUTOCVT=OFF
_BPX_JOBNAME=${ZWE_zowe_job_prefix}${DISCOVERY_CODE} ${JAVA_BIN_DIR}java \
-Xms${ZWE_configs_heap_init:-32}m -Xmx${ZWE_configs_heap_max:-512}m \
-XX:+ExitOnOutOfMemoryError \ ${QUICK_START} \ ${ADD_OPENS} \
${COLIN} \ *./components/discovery/bin/start.sh
having the -xshowoptions shows what options were specified, so you can see
if the user gave some inappropriate ones.
Colin
…On Mon, Jan 27, 2025 at 4:05 PM nigelvwilliams ***@***.***> wrote:
That's putting the cart before the horse. The problem here is there is no
permanent javaArgs field to put the -DIBM_JAVA_OPTIONS argument.
—
Reply to this email directly, view it on GitHub
<#3865 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJQXLWJFQOYY75U3H37EPID2MZKODAVCNFSM6AAAAABQLHO5E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJWGE3DSMBQGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
UMS uses, in yaml:
so it's an array. then we have a shell hack to concatenate the ZWE_components_izp_javaArgs_0 etc. vars into one space separated string and include $JAVAARGS in the java command. (too bad the pre-concatenated string is comma separated). |
This sounds a complex solution (grin).
As an end user, who only tried using Zowe for the first time last week, I
find the size of the zowe.yaml file is not easy to use <because it is so
big, (does it need the certificate setup info at run time? - I split mine
into two and deleted a lot of stuff I didnt need), and it is hard to find
things [I cant use "find components.izp"] >
I would prefer not to have to use the zowe.yaml file for this information.
Checking the existence of a java options file in the startup script and
using it, feels much easier for the end user.
Colin
…On Tue, Jan 28, 2025 at 3:31 PM Judy Anderson ***@***.***> wrote:
UMS uses, in yaml:
compnents.izp...javaArgs:
- -Dsomething.something=something
- -Dsomething.else=another
so it's an array. then we have a shell hack to concatenate the
ZWE_components_izp_javaArgs_0 etc. vars into one space separated string and
include $JAVAARGS in the java command. (too bad the pre-concatenated string
is comma separated).
—
Reply to this email directly, view it on GitHub
<#3865 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJQXLWN6IVQG7FCC4WSHJUL2M6PFVAVCNFSM6AAAAABQLHO5E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJZGMZTMOBTGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Customers who wish to monitor the JVMs in Zowe, say with OMEGAMON for JVM cannot easily add Java Arguments to the Java configuration.
Describe the experience you'd like
Currently only the Message Service JVM has a javaArgs yaml field. We'd like all the Java process to have that option.
Describe alternatives you've considered
Manually altering the template arguments, but they may get overwritten by maintenance.
The text was updated successfully, but these errors were encountered: