-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b103
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8156315 | 8u111 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
JDK-8149808 | 8u102 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
JDK-8162153 | emb-8u111 | Jaroslav Bachorík | P3 | Resolved | Fixed | b01 |
JDK-8153092 | 7u171 | Shafi Ahmad | P3 | Resolved | Fixed | b01 |
JDK-8150477 | openjdk7u | Jaroslav Bachorík | P3 | Resolved | Fixed | master |
test result: Failed. Unexpected exit from test [exit code: 0]
The underlying reason is that the test is only valid on setups with 2 or more IPs configured for the localhost. If that's not the case the test exits via System.exit(0) - and this being disallowed by JTreg harness will cause the test to fail.
- backported by
-
JDK-8149808 JMXInterfaceBindingTest is failing intermittently
- Resolved
-
JDK-8150477 JMXInterfaceBindingTest is failing intermittently
- Resolved
-
JDK-8153092 JMXInterfaceBindingTest is failing intermittently
- Resolved
-
JDK-8156315 JMXInterfaceBindingTest is failing intermittently
- Resolved
-
JDK-8162153 JMXInterfaceBindingTest is failing intermittently
- Resolved
- relates to
-
JDK-6425769 Allow specifying an address to bind JMX remote connector
- Resolved
-
JDK-8219585 [TESTBUG] sun/management/jmxremote/bootstrap/JMXInterfaceBindingTest.java passes trivially when it shouldn't
- Resolved
-
JDK-8157593 Allow specifying an address to bind JMX remote connector
- Closed