Any ideas what to do with RMIServer stub failures in tests? This seems to
be something going wrong in the JDK code that's outside of our control.
Moving these JMX tests to FlakyTest category will have no effect. We'll
simply have all JMX tests in FlakyTest instead of IntegrationTest. I can't
see a way to "fix" it unless the community wants to use RetryRule on these
tests. We would have to apply it to every single JMX test.
:geode-core:integrationTest
org.apache.geode.management.internal.security.DiskStoreMXBeanSecurityJUnitTest
> testNoAccess FAILED
java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.254.0.238; nested
exception is:
java.net.ConnectException: Connection refused (Connection refused)]
Caused by:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 10.254.0.238; nested
exception is:
java.net.ConnectException: Connection refused (Connection refused)]
Caused by:
java.rmi.ConnectException: Connection refused to host:
10.254.0.238; nested exception is:
java.net.ConnectException: Connection refused (Connection
refused)
Caused by:
java.net.ConnectException: Connection refused (Connection
refused)
3598 tests completed, 1 failed, 163 skipped
:geode-core:integrationTest FAILED
