[GEODE-4890] intermittent failure of ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest dataWriterCanStillOnlyWriteAfterFailover

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 1.6.0
• Component/s: client/server, security
• Labels: ci pull-request-available
• Assignee: Jinmei Liao
• Reporter: Darrel Schneider
• Created: 19/Mar/18 17:54
• Updated: 07/Nov/18 23:23
• Resolved: 07/Nov/18 23:23

Description

Looking at this test on line 263 I think we just might need to have the test wait a while for the client pool to detect that it has a new primary on the "assertThat" line in the following block:

server_to_fail.invoke(() -> ClusterStartupRule.getCache().close()); // Confirm failover VMProvider secondaryServer = (server1.equals(server_to_fail)) ? server2 : server1; assertThat(secondaryServer).isEqualTo(determinePrimaryServer(client)); 

dataWriterCanStillOnlyWriteAfterFailover[clientVersion=130]
org.junit.ComparisonFailure: expected:<...unit.rules.MemberVM@[19582245]> but was:<...unit.rules.MemberVM@[23c51fe4]>
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at org.apache.geode.security.ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.dataWriterCanStillOnlyWriteAfterFailover(ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.java:263)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Issue Links

• links to: GitHub Pull Request #1841
• links to: GitHub Pull Request #1914