Barrett Oglesby created GEODE-8007:
--------------------------------------

             Summary: CI failure: 
ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.dataReaderCanRegisterAndUnregisterAcrossFailover[clientVersion=1.9.2]
 failed with IllegalArgumentException
                 Key: GEODE-8007
                 URL: https://issues.apache.org/jira/browse/GEODE-8007
             Project: Geode
          Issue Type: Bug
          Components: client queues, client/server
            Reporter: Barrett Oglesby


DistributedTestOpenJDK8 build 76:

https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/76

Failed with:
{noformat}
org.apache.geode.security.ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest
 > dataReaderCanRegisterAndUnregisterAcrossFailover[clientVersion=1.9.2] FAILED
    java.lang.AssertionError: Suspicious strings were written to the log during 
this run.
    Fix the strings or use IgnoredException.addIgnoredException to ignore.
    -----------------------------------------------------------------------
    Found suspect string in log4j at line 1939

    java.lang.IllegalArgumentException: unknown communications mode: 74
        at 
org.apache.geode.internal.cache.tier.CommunicationMode.fromModeNumber(CommunicationMode.java:164)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.getCommunicationModeForNonSelector(AcceptorImpl.java:1563)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1430)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$handOffNewClientConnection$4(AcceptorImpl.java:1341)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

    -----------------------------------------------------------------------
    Found suspect string in log4j at line 2083

    java.lang.IllegalArgumentException: unknown communications mode: 74
        at 
org.apache.geode.internal.cache.tier.CommunicationMode.fromModeNumber(CommunicationMode.java:164)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.getCommunicationModeForNonSelector(AcceptorImpl.java:1563)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1430)
        at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$handOffNewClientConnection$4(AcceptorImpl.java:1341)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
{noformat}
This test starts 2 servers in the latest version and a client in a previous 
version and:

- registers interest with redundancy=1
- kills primary server
- verifies failover occurs

Both servers start successfully and start their listeners:
{noformat}
[vm1] [info 2020/04/21 19:21:59.157 GMT <RMI TCP 
Connection(1)-172.17.0.7> tid=0x20] Cache server connection listener bound 
to address b2f0ba1181ef-0.0.0.0/0.0.0.0:46423 with backlog 1280.
[vm2] [info 2020/04/21 19:21:59.729 GMT <RMI TCP 
Connection(1)-172.17.0.7> tid=0x20] Cache server connection listener bound 
to address b2f0ba1181ef-0.0.0.0/0.0.0.0:38723 with backlog 1280.
{noformat}
The client starts and vm1 throws these exceptions when the client attempts to 
connect:
{noformat}
[vm1] [warn 2020/04/21 19:22:02.371 GMT <Handshaker 0.0.0.0/0.0.0.0:46423 
Thread 1> tid=0xa21] Error processing client connection
[vm1] java.lang.IllegalArgumentException: unknown communications mode: 74
[vm1]   at 
org.apache.geode.internal.cache.tier.CommunicationMode.fromModeNumber(CommunicationMode.java:164)
[vm1]   at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.getCommunicationModeForNonSelector(AcceptorImpl.java:1563)
[vm1]   at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1430)
[vm1]   at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$handOffNewClientConnection$4(AcceptorImpl.java:1341)
[vm1]   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[vm1]   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[vm1]   at java.lang.Thread.run(Thread.java:748)

[vm1] [warn 2020/04/21 19:22:02.371 GMT <Handshaker 0.0.0.0/0.0.0.0:46423 
Thread 1> tid=0xa21] Cache server: failed accepting client connection 
java.io.EOFException
[vm1] java.io.EOFException
[vm1]   at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.handleNewClientConnection(AcceptorImpl.java:1438)
[vm1]   at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$handOffNewClientConnection$4(AcceptorImpl.java:1341)
[vm1]   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[vm1]   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[vm1]   at java.lang.Thread.run(Thread.java:748)
{noformat}
Right after that, the client successfully connects to vm2:
{noformat}
[vm2] [info 2020/04/21 19:22:02.909 GMT <Client Queue Initialization Thread 
1> tid=0x9eb] :Cache server: Initializing secondary server-to-client 
communication socket: Socket[addr=/127.0.0.1,port=44640,localport=38723]
[vm3_v1.9.2] [info 2020/04/21 19:22:02.918 GMT <Cache Client Updater Thread  
on b2f0ba1181ef(server-2:139)<v2>:41002(version:UNKNOWN[ordinal=120]) 
port 38723> tid=0x32] Cache Client Updater Thread  on 
b2f0ba1181ef(server-2:139)<v2>:41002(version:UNKNOWN[ordinal=120]) port 
38723 (localhost:38723) : ready to process messages.
{noformat}
Then it connects to vm1 successfully this time:
{noformat}
[vm1] [info 2020/04/21 19:22:02.919 GMT <Client Queue Initialization Thread 
1> tid=0xa26] :Cache server: Initializing primary server-to-client 
communication socket: Socket[addr=/127.0.0.1,port=58774,localport=46423]
[vm3_v1.9.2] [info 2020/04/21 19:22:02.927 GMT <Cache Client Updater Thread  
on b2f0ba1181ef(server-1:110)<v1>:41001(version:UNKNOWN[ordinal=120]) 
port 46423> tid=0x33] Cache Client Updater Thread  on 
b2f0ba1181ef(server-1:110)<v1>:41001(version:UNKNOWN[ordinal=120]) port 
46423 (localhost:46423) : ready to process messages.
{noformat}
The rest of the test is successful.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to