JDK-8044840 : [TESTBUG] get rid of JMX in com.oracle.java.testlibrary.ProcessTools.getProcessId() for getting current process id
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: emb-8u26,8u20,9
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- Submitted: 2014-06-04
- Updated: 2015-04-27
- Resolved: 2015-04-27
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9Resolved  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
Duplicate :
|
Description
Possible solutions: - jni, jvmti. Write another lib(not monitoring one) which will get pid, but currently we do not have native tests support in hotspot/test - Runtime.exec( "echo $PPID" ).getInputStream()... some platforms may not have shell interpreter - via harness(jtreg?) get pid of the starting test and pass it somehow(via -D java property) to the same test. Example: sh -c 'exec /path/to/bin/java '-Dpid=$$ MyTest' - WB, Unsafe, ... with changes in product - Enhance Process API in JDK-8046092 JEP 102: Process API Updates