It's a bit of a hack but I submitted https://reviews.apache.org/r/60977/
Something in the JMX RMI startup seems to be asynchronous, so our JMX junit rules "await" this startup before letting the test start. I added a check for "Failed to retrieve RMIServer stub" to this await step. If anyone has further ideas, please send them my way... On Wed, Jul 19, 2017 at 10:01 AM, Kirk Lund <kl...@apache.org> wrote: > 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 >
