JDK-8030843 : Test sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh failed with connection failure
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 8
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2013-12-20
  • Updated: 2023-12-14
  • Resolved: 2014-03-13
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
tbdFixed
Related Reports
Relates :  
JDK-7195249 - Some jtreg tests use hard coded ports
Description
TESTFAIL: sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh
sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh failed with connection failure on all runs on Solaris machine. (Failed 67/67 runs) . Same test on Win7 and Linux are all ok.

Based on error message, this bug might be covered by JDK-7195249 which declare that some tests uses hard coded port. However, from the log message itself, we don't see "port already in use" similar error message. 


***
*** Testing configuration (port=51140): /scratch/local/aurora/sandbox/results/workDir/classes/sun/management/jmxremote/bootstrap/management_ssltest07_ok.properties
***
Connection failed for no credentials: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
	javax.net.ssl.SSLException: Received fatal alert: internal_error
Test Failed: Failed to connect to agent {url=service:jmx:rmi://scaaa050.us.oracle.com/jndi/rmi://localhost:51140/jmxrmi}: java.lang.RuntimeException: Test /scratch/local/aurora/sandbox/results/workDir/classes/sun/management/jmxremote/bootstrap/management_ssltest07_ok.properties failed with 1 error(s)
----------System.err:(0/0)----------
result: Failed. Execution failed: exit code 20
Comments
The issue was that a hard coded port was used, the fix of 7195249 must fix this issue, it used Utils.getFreePort() to have a free port. Let's re-open the bug if we see again the failure.
13-03-2014
ILW=MLH=P4, Medium impact as yet more unstable and noisy tests, low likelihood of individual failure, no known workaround.
20-12-2013
For this test, let's see if we could use "port=0" instead to try many specific ports.
20-12-2013