JDK-8165727 : sun/tools/jstatd/TestJstatdExternalRegistry.java failure: Could not read data for remote JVM
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 9,10
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • Submitted: 2016-09-08
  • Updated: 2019-03-29
  • Resolved: 2019-03-29
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.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8203026 - java.rmi.NoSuchObjectException: no such object in table
Relates :  
JDK-8216543 - sun/tools/jstatd/TestJstatdDefaults.java failed with no such object in table
Description
RULE "sun/tools/jstatd/TestJstatdExternalRegistry.java" Exception java.rmi.NoSuchObjectException: no such object in table

RULE "sun/tools/jstatd/TestJstatdExternalRegistry.java" Exception stderr: [sun.jvmstat.monitor.MonitorException: Could not read data for remote JVM ...

RULE "sun/tools/jstatd/TestJstatdExternalRegistry.java" Exception sun.jvmstat.monitor.MonitorException: Could not read data for remote JVM ...
Comments
I spotted this failure in my stress testing for 8153224 on Linux-X64: sun/tools/jstatd/TestJstatdDefaults.java $ unzip -l 8153224.v2.00_linux.8165727.zip Archive: 8153224.v2.00_linux.8165727.zip Length Date Time Name --------- ---------- ----- ---- 23437 2019-03-26 15:13 8153224.v2.00_2/failures.linux-x86_64/TestJstatdDefaults.jtr.slowdebug --------- ------- 23437 1 file
27-03-2019
Here are the logs for my jdk-12+28 Solaris-X64 sightings for test: sun/tools/jstatd/TestJstatdPort.java $ unzip -l jdk-12+28_solx64.8165727.zip Archive: jdk-12+28_solx64.8165727.zip Length Date Time Name --------- ---------- ----- ---- 22845 01-18-2019 01:17 jdk-12+28_1/failures.solaris-x86_64/TestJstatdPort.jtr.fastdebug --------- ------- 22845 1 file
20-01-2019
Here are the logs for my jdk-12+11 Solaris-X64 sightings: $ unzip -l jdk-12+11_solx64.8165727.zip Archive: jdk-12+11_solx64.8165727.zip Length Date Time Name --------- ---------- ----- ---- 25978 09-14-2018 22:38 jdk-12+11_2/TestJstatdServer.jtr.slowdebug --------- ------- 25978 1 file
16-09-2018
Here are the logs for my jdk11+24 linux sightings: $ unzip -l jdk-11+24_linux.8165727.zip Archive: jdk-11+24_linux.8165727.zip Length Date Time Name --------- ---------- ----- ---- 23876 2018-07-29 05:14 jdk-11+24_3/TestJstatdDefaults.jtr.release --------- ------- 23876 1 file
29-07-2018
The following test failed due to an exception on Linux X64 in the release config using jdk11+24 bits: sun/tools/jstatd/TestJstatdDefaults.java The test only failed in 1 of 3 'release' bits runs so I'm tagging this bug as intermittent. It did not fail at all in the 'fastdebug' or 'slowdebug' bits runs. Here is a snippet from the log file: ----------System.out:(40/2699)---------- Start jstatd: [/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/build/linux-x86_64-normal-server-release/images/jdk/bin/jstatd -J-XX:+UsePerfData -J-Djava.security.policy=/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/open/test/jdk/sun/tools/jstatd/all.policy] [Jstatd-Thread]:/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/build/linux-x86_64-normal-server-release/images/jdk/bin/jstatd -J-XX:+UsePerfData -J-Djava.security.policy=/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/open/test/jdk/sun/tools/jstatd/all.policy [Jstatd-Thread] jstatd started (bound to /JStatRemoteHost) Jstatd-Thread pid: 30308 Start jps: [/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/build/linux-x86_64-normal-server-release/images/jdk/bin/jps -J-XX:+UsePerfData ddaugher-twvpn-dhcp-10-159-209-60] 17312 jtreg.jar 30346 Jps 30308 Jstatd 30285 MainWrapper Start jstat: [/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/build/linux-x86_64-normal-server-release/images/jdk/bin/jstat -J-XX:+UsePerfData -J-Duser.language=en -gcutil 30308@ddaugher-twvpn-dhcp-10-159-209-60 250 5] sun.jvmstat.monitor.MonitorException: Could not read data for remote JVM 30308 at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.PerfDataBuffer.<init>(PerfDataBuffer.java:68) at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.RemoteMonitoredVm.<init>(RemoteMonitoredVm.java:71) at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:146) at jdk.jcmd/sun.tools.jstat.Jstat.logSamples(Jstat.java:107) at jdk.jcmd/sun.tools.jstat.Jstat.main(Jstat.java:70) Caused by: java.rmi.NoSuchObjectException: no such object in table at java.rmi/sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:283) at java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:260) at java.rmi/sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209) at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161) at jdk.proxy1/com.sun.proxy.jdk.proxy1.$Proxy1.getCapacity(Unknown Source) at jdk.jstatd/sun.jvmstat.perfdata.monitor.protocol.rmi.PerfDataBuffer.<init>(PerfDataBuffer.java:63) ... 4 more ProcessThread.stopProcess() will kill process --- ProcessLog --- cmd: /work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/build/linux-x86_64-normal-server-release/images/jdk/bin/jstatd -J-XX:+UsePerfData -J-Djava.security.policy=/work/shared/bug_hunt/thread_SMR_stress/jdk11_exp/open/test/jdk/sun/tools/jstatd/all.policy exitvalue: 143 stderr: stdout: ----------System.err:(62/4064)----------
29-07-2018
ILW ML? = P4 I: Medium, Noise in nightly L: Low, Has happened a handful of times in the last 2 years W: Unknown (High), No known workaround at this time
12-09-2016