JDK-7158614 : JMXStartStopTest.sh failing intermittently
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 7u4,7u6,8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,linux
  • CPU: generic
  • Submitted: 2012-04-03
  • Updated: 2023-09-01
  • Resolved: 2012-12-19
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 8
8 b71Fixed
Related Reports
Relates :  
Relates :  
Sub Tasks
JDK-8005325 :  
Description
Test name:
sun/management/jmxremote/startstop/JMXStartStopTest.sh

This test may fail if the "do nothing" vm does not come up after "sleep 1" then the test does not discover the pid of the process and the test fails and leaves stray java processes which block other runs of the test since they use a fixed tcp port number.

Comments
URL: http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/c79b26b8efe0 User: lana Date: 2012-12-31 05:48:05 +0000
31-12-2012

URL: http://hg.openjdk.java.net/jdk8/tl/jdk/rev/c79b26b8efe0 User: sjiang Date: 2012-12-19 10:32:39 +0000
19-12-2012

It sleeps only one millisecond (Thread.sleep(1) ) in the while cycle of the class JMXStartStopDoSomething, that is too heavy for a test machine, it is better to change to at least 100 ms, the waiting time for JMXStartStopTest.sh is 1 second.
30-11-2012

The function _app_stop should verify at first that the lock file has been created, then deletes it to inform JMXStartStopDoSomething to stop.
30-11-2012

Shanliang, can you please look at this bug?
30-11-2012

Affects older version of 7 updates also. removing 7u10.
21-11-2012

This is failing intermittently in JPRT, here's example output for a build of jdk8/tl that is essentially jdk8-b67. -------------------------------------------------- TEST: sun/management/jmxremote/startstop/JMXStartStopTest.sh JDK under test: (/tmp/jprt/P1/065316.swmarks/testproduct/linux_i586_2.6-product) java version "1.8.0-internal" Java(TM) SE Runtime Environment (build 1.8.0-internal-201211210653.swmarks.jdk8-tl-jdk-b00) Java HotSpot(TM) Server VM (build 25.0-b09, mixed mode) ACTION: build -- Passed. Build successful REASON: User specified action: run build JMXStartStopTest JMXStartStopDoSomething TIME: 0.721 seconds messages: command: build JMXStartStopTest JMXStartStopDoSomething reason: User specified action: run build JMXStartStopTest JMXStartStopDoSomething elapsed time (seconds): 0.721 ACTION: compile -- Passed. Compilation successful REASON: .class file out of date or does not exist TIME: 0.72 seconds messages: command: compile /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopTest.java /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopDoSomething.java reason: .class file out of date or does not exist elapsed time (seconds): 0.72 STDOUT: STDERR: /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopTest.java:43: warning: AgentConfigurationError is internal proprietary API and may be removed in a future release import sun.management.AgentConfigurationError; ^ /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopTest.java:44: warning: ConnectorBootstrap is internal proprietary API and may be removed in a future release import sun.management.jmxremote.ConnectorBootstrap; ^ /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopTest.java:93: warning: ConnectorAddressLink is internal proprietary API and may be removed in a future release jmxUrlStr = sun.management.ConnectorAddressLink.importFrom(pid); ^ Note: /tmp/jprt/P1/065316.swmarks/s/test/sun/management/jmxremote/startstop/JMXStartStopTest.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 3 warnings ACTION: shell -- Failed. Execution failed: exit code 255 REASON: User specified action: run shell JMXStartStopTest.sh --jtreg --no-compile TIME: 29.361 seconds messages: command: shell JMXStartStopTest.sh [--jtreg, --no-compile] reason: User specified action: run shell JMXStartStopTest.sh --jtreg --no-compile elapsed time (seconds): 29.361 STDOUT: **** Test one **** Passed **** Test two **** Passed **** Test three **** Passed 50234 Passed 50235 **** Test four **** Passed 50234 50235 **** Test five **** Passed 50234 50235 **** Test six **** Passed 50234 50235 **** Test seven **** Passed **** Test eight **** Passed **** Test nine **** Passed **** Test ten **** ERROR: Test app not started STDERR: TEST RESULT: Failed. Execution failed: exit code 255 --------------------------------------------------
21-11-2012

This test has significant revamped as part of JDK-7186723. It would be useful to check if it is still causing problems on slow machines.
29-10-2012