Community
Participate
Working Groups
This bug is to port the work of bug 241984 to zOS. This will allow the zOS platform to launch the Java profiler using the -agentpath switch; absolving the need to configure environment variables.
Created attachment 172912 [details] First patch Attaching a patch with the needed changes to support -agentpath: on zOS. It builds on the patch for bug 317444 (you will need to apply the 317444 patch before applying this patch). Adds an implementation of GetDefaultLibPath for zOS which uses w_getpsent() to find the command line of the Java process and parse the location of libJPIBootLoader.so from that. Issues: 1. We don't ship the IBM Toolkit for XML with the RAC so the user still must manually export the install path to the LIBPATH env var. This is already covered in the documentation so may not be a big deal. If we are sure of the install location we could enhance the patch to programmatically add this to the LIBPATH env var. - The system call which provides command line information only returns up to 1023 characters; it is possible that for long invocations the location of libJPIBootLoader.so could be truncated causing this to fail. Comments welcome.
Created attachment 173811 [details] Reworked patch Since w_getpsent() was discovered to only be supported on 31-bit as well as the fact it only returns the first 1024 characters of the command line, it is too unreliable to implement this feature. No other suitable APIs have been found, instead we will look for a new option in the agent string which gives the path to the JPI libs, e.g.: -agentpath:.../libJPIBootLoader.so=JPIAgent:jpi_home=...,server=enabled,.... JPIBootLoader then parses out jpi_home, and uses it to setup the needed library path information before starting the rest of the initialization process. A new patch which implements this approach is attached.
Patch reviewed by Jonathan and patch checked into HEAD.
Obsoleted patch in favour of all-inclusive patch: https://bugs.eclipse.org/bugs/attachment.cgi?id=175108 This is only provided for archival purposes, as it is easier to apply this to 4.7.0 rather than cherry-picking all the individual commits.
This defect had been resolved as FIXED for more than 1 month. Please verify with the latest TPTP 4.7.2 driver. If this defect is still left unverified by February 25, we'll close it on the originator's behalf. TPTP 4.7.2 driver can be downloaded from: http://www.eclipse.org/tptp/home/downloads/?ver=4.7.2
Closing.
