You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2017/07/19 17:10:00 UTC
[jira] [Created] (GEODE-3251) DiskStoreMXBeanSecurityJUnitTest
fails with IOException: Failed to retrieve RMIServer stub
Kirk Lund created GEODE-3251:
--------------------------------
Summary: DiskStoreMXBeanSecurityJUnitTest fails with IOException: Failed to retrieve RMIServer stub
Key: GEODE-3251
URL: https://issues.apache.org/jira/browse/GEODE-3251
Project: Geode
Issue Type: Bug
Components: jmx, tests
Reporter: Kirk Lund
I'm not sure if the JMX RMI startup is asynchronous in some way or not, but at some point any of the JMX tests seem to be prone to hitting this failure:
"java.io.IOException: Failed to retrieve RMIServer stub"
{noformat}
: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
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)