JDK-8293335 : sun/management/jmxremote/bootstrap/RmiBootstrapTest.java#id1failed with "Agent communication error: java.io.EOFException"
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 20
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: linux
  • CPU: x86_64
  • Submitted: 2022-09-03
  • Updated: 2024-11-19
  • Resolved: 2022-09-12
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 JDK 20
17.0.10Fixed 20 b15Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Sub Tasks
JDK-8293517 :  
JDK-8293548 :  
Description
The following test failed in the JDK20 CI:

sun/management/jmxremote/bootstrap/RmiBootstrapTest.java#id1

Here's a snippet from the log file:

#section:main
----------messages:(6/360)----------
command: main RmiBootstrapTest .*_ssltest.*.in
reason: User specified action: run main/timeout=300 RmiBootstrapTest .*_ssltest.*.in 
Mode: agentvm
Agent id: 16
Additional exports to unnamed modules from @modules: java.management/sun.management jdk.management.agent/jdk.internal.agent jdk.management.agent/sun.management.jmxremote
elapsed time (seconds): 3.235
----------configuration:(19/2293)----------

<snip>

result: Error. Agent communication error: java.io.EOFException; check console log for any additional details

There's no indication of an error except for the above
" Agent communication error: java.io.EOFException".
No hs_err_pid file, no indication of a problem with the test
execution, no core file.

This same failure happened on two different linux-x64-debug
test machines in jdk-20+14-898-tier3. 
Comments
Fix request [17u] I backport this for parity with 17.0.11-oracle. No risk, only a test change. Omitted change to PRoblemList, rest is clean. Tests pass. SAP nightly testing passed.
22-11-2023

A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/1980 Date: 2023-11-21 12:33:48 +0000
21-11-2023

Here's the logs for my jdk-20+14 stress testing on linux-x64 (just for the record): $ unzip -l jdk-20+14_linux-x64.8293335.zip Archive: jdk-20+14_linux-x64.8293335.zip Length Date Time Name --------- ---------- ----- ---- 17847 2022-09-08 21:41 jdk-20+14_1/failures.linux-x86_64/RmiBootstrapTest_id1.jtr.slowdebug 17825 2022-09-09 21:00 jdk-20+14_2/failures.linux-x86_64/RmiBootstrapTest_id1.jtr.slowdebug 17820 2022-09-11 02:11 jdk-20+14_3/failures.linux-x86_64/RmiBootstrapTest_id1.jtr.fastdebug --------- ------- 53492 3 files
10-11-2022

Changeset: 91c9091d Author: Bill Huang <bill.w.huang@oracle.com> Committer: Kevin Walls <kevinw@openjdk.org> Date: 2022-09-12 13:07:34 +0000 URL: https://git.openjdk.org/jdk/commit/91c9091d7e64ba0bdb257521bd15ff183c6839fa
12-09-2022

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/10224 Date: 2022-09-08 23:20:19 +0000
09-09-2022

Like JDK-8293343 this appears to be an issue since: 8292067: Convert test/sun/management/jmxremote/bootstrap shell tests to java version This one does not reproduce so easily for me, so can't immediately confirm if adding "othervm" works. But they are the kind of tests that need their own VM, e.g. use of System properties.
08-09-2022

Bumping from P4 -> P3 since this failure has happened in three Tier3 build-IDs in a row. All of the failures have happened on Ubuntu 20.04 or Ubuntu 22.04 test machines so far.
03-09-2022