-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBM_JAVA_COMMAND_LINE environment variable not set #947
Comments
@fengxue-IS Can you take a look at this? At least to figure out what we need to do here. |
the original input is only available to the Java launcher, the best / near identical information can be reconstructed from the |
Another option is to look at the OS and the info it provides:
This will get the exact commandline used to start the process, not just the version passed to the VM as some options get modified by the launcher |
tested with different approaches on all platforms, for unix systems, this info can also be retrieved with |
@zl-wang Is there a way to get the command line from the OS on AIX? The /proc filesystem on linux provides this info and we need the equivalent on AIX.
I agree this isn't a great idea. Let's see if we can find an alternative. One option is to see if we can define an API for the Java launcher to support that provides this info. Might be worth a discussion with @andrew-m-leonard to see what can be added to the launcher. |
@keithc-ca Can you please take a look at this? |
Sure, I'll add it to the list. |
For AIX, this looks promising: https://www.ibm.com/docs/en/aix/7.2?topic=g-getargs-subroutine. |
All the pieces are merged and in 0.32, I expect this can be closed. |
Re-opening due to #14766 |
I find references to the environment variable IBM_JAVA_COMMAND_LINE in OpenJ9 debugtools/DDR_VM, the openj9.dtfj module, rasdump/javadump.cpp, but OpenJ9 does not set this environment variable. I believe for IBM Java the IBM Java launcher would set it to the command line options specified. Since its not set for OpenJ9, the RAS code may not provide these command line details as intended.
The text was updated successfully, but these errors were encountered: