JDK-8333698 : [17u] TestJstatdRmiPort fails after JDK-8333667
  • Type: Bug
  • Component: core-libs
  • Affected Version: 17.0.13
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-06-06
  • Updated: 2024-06-24
  • Resolved: 2024-06-07
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.
JDK 17
17.0.13 masterFixed
Related Reports
Duplicate :  
JDK-8333765 - [17u] Six sun/tools/jstatd testcases fail after JDK-8233725
Relates :  
JDK-8333667 - ProcessTools.startProcess() has output issues when using an OutputAnalyzer at the same time
Relates :  
JDK-8272317 - jstatd has dependency on Security Manager which needs to be removed
Description
The backport of JDK-8233725 together with JDK-8306946 causes sun/tools/jstatd/TestJstatdRmiPort.java to fail:
java.lang.RuntimeException: Output should contain one line: expected 5 to equal 1
Comments
Changeset: bcd19a5b Author: Aleksey Shipilev <shade@openjdk.org> Date: 2024-06-07 19:19:08 +0000 URL: https://git.openjdk.org/jdk17u-dev/commit/bcd19a5b12651ca0ae8e1a35a2838738e119c730
07-06-2024
[jdk17u-fix-request] Approval Request from Aleksey Shipilëv Works around a recent regression after JDK-8233725. The real fix is backporting JDK-8272317, but it would take a while. 17u-specific patch. Tests now pass. Low risk, test-only change. We will revert it when JDK-8272317 lands.
06-06-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/2543 Date: 2024-06-06 10:03:05 +0000
06-06-2024
JDK-8272317 backport is out for jdk17u-dev: https://github.com/openjdk/jdk17u-dev/pull/2542 It needs CSR approvals, so it would take a while. Meanwhile, I'll patch up the test itself.
06-06-2024
We are likely "just" missing JDK-8272317.
06-06-2024
The actual output includes SM deprecation message: ``` [2024-06-06T09:31:16.105374Z] Waiting for completion for process 64693 [2024-06-06T09:31:16.105448Z] Waiting for completion finished for process 64693 STDERR: [Jstatd-Thread] WARNING: A terminally deprecated method in java.lang.System has been called [Jstatd-Thread] WARNING: System::setSecurityManager has been called by sun.tools.jstatd.Jstatd (jrt:/jdk.jstatd) [Jstatd-Thread] WARNING: Please consider reporting this to the maintainers of sun.tools.jstatd.Jstatd [Jstatd-Thread] WARNING: System::setSecurityManager will be removed in a future release stdout: [jstatd started (bound to /TestJstatdServer) ]; stderr: [WARNING: A terminally deprecated method in java.lang.System has been called WARNING: System::setSecurityManager has been called by sun.tools.jstatd.Jstatd (jrt:/jdk.jstatd) WARNING: Please consider reporting this to the maintainers of sun.tools.jstatd.Jstatd WARNING: System::setSecurityManager will be removed in a future release ] exitValue = 143 ```
06-06-2024
Confirmed. As the committer for JDK-8233725, I am taking care of this.
06-06-2024