[
https://issues.apache.org/jira/browse/GEODE-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reopened GEODE-7617:
------------------------------
I hit this issue again, even with Bruce's fix.
I think the problem is that Awaitility.await only retries on AssertionError. In
this case the code throws an IllegalStateException and fails immediately.
{noformat}
org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest >
getServiceUseClientSSLConfig FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest$$Lambda$160/0x00000008407e8440.run
in VM 1 running on Host 8750b0d5e5fe with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
at
org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
at
org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest.getServiceUseClientSSLConfig(GeodeClientClusterManagementSSLTest.java:68)
Caused by:
java.lang.IllegalStateException: Unable to discover a locator that has
ClusterManagementService running.
at
org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setClientCache(GeodeClusterManagementServiceBuilder.java:149)
at
org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setCache(GeodeClusterManagementServiceBuilder.java:89)
at
org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setCache(GeodeClusterManagementServiceBuilder.java:58)
at
org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest.lambda$null$0(GeodeClientClusterManagementSSLTest.java:71)
{noformat}
> CI failure: GeodeClientClusterManagementSSLTest. getServiceUseClientSSLConfig
> -----------------------------------------------------------------------------
>
> Key: GEODE-7617
> URL: https://issues.apache.org/jira/browse/GEODE-7617
> Project: Geode
> Issue Type: Test
> Components: tests
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This test creates a locator and then creates a cache in another JVM and then
> asserts that it can find the cluster configuration service. The problem is
> that the cluster configuration service is initialized in the background and
> isn't ready when locator startup completes. Until that guarantee is in place
> this test is going to fail periodically because it makes the assertion
> immediately after starting the locator.
> {noformat}
> org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest
> > getServiceUseClientSSLConfig FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest$$Lambda$29/1016886377.run
> in VM 1 running on Host 3984d60ce841 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> at
> org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest.getServiceUseClientSSLConfig(GeodeClientClusterManagementSSLTest.java:67)
> Caused by:
> java.lang.IllegalStateException: Unable to discover a locator that
> has ClusterManagementService running.
> at
> org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setClientCache(GeodeClusterManagementServiceBuilder.java:149)
> at
> org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setCache(GeodeClusterManagementServiceBuilder.java:89)
> at
> org.apache.geode.management.internal.api.GeodeClusterManagementServiceBuilder.setCache(GeodeClusterManagementServiceBuilder.java:58)
> at
> org.apache.geode.management.internal.rest.GeodeClientClusterManagementSSLTest.lambda$getServiceUseClientSSLConfig$bb17a952$1(GeodeClientClusterManagementSSLTest.java:69)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
