Bill Burcham created GEODE-8101:
-----------------------------------

             Summary: HsetDUnitTest loses connection to one remote process 
(broken pipe)
                 Key: GEODE-8101
                 URL: https://issues.apache.org/jira/browse/GEODE-8101
             Project: Geode
          Issue Type: Bug
          Components: redis
            Reporter: Bill Burcham


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

A test fails trying to communicate to a remote process (through jedis2):

{code}
org.apache.geode.redis.executors.hash.HsetDUnitTest > 
should_distributeDataAmongMultipleServers_givenMultipleClients FAILED

    redis.clients.jedis.exceptions.JedisConnectionException: 
java.net.SocketException: Broken pipe (Write failed)

        at redis.clients.jedis.Connection.flush(Connection.java:308)

        at 
redis.clients.jedis.Connection.getBinaryMultiBulkReply(Connection.java:269)

        at redis.clients.jedis.Jedis.hgetAll(Jedis.java:942)

        at 
org.apache.geode.redis.executors.hash.HsetDUnitTest.should_distributeDataAmongMultipleServers_givenMultipleClients(HsetDUnitTest.java:121)


        Caused by:

        java.net.SocketException: Broken pipe (Write failed)

            at java.net.SocketOutputStream.socketWrite0(Native Method)

            at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)

            at java.net.SocketOutputStream.write(SocketOutputStream.java:150)

            at 
redis.clients.jedis.util.RedisOutputStream.flushBuffer(RedisOutputStream.java:52)

            at 
redis.clients.jedis.util.RedisOutputStream.flush(RedisOutputStream.java:133)

            at redis.clients.jedis.Connection.flush(Connection.java:305)

{code}

and the @After method fails trying to communicate (disconnect) to the same 
remote process (again through jedis2):

{code}
org.apache.geode.redis.executors.hash.HsetDUnitTest > classMethod FAILED

    redis.clients.jedis.exceptions.JedisConnectionException: 
java.net.SocketException: Broken pipe (Write failed)

        at redis.clients.jedis.Connection.disconnect(Connection.java:222)

        at redis.clients.jedis.BinaryClient.disconnect(BinaryClient.java:918)

        at redis.clients.jedis.BinaryJedis.disconnect(BinaryJedis.java:1898)

        at 
org.apache.geode.redis.executors.hash.HsetDUnitTest.tearDown(HsetDUnitTest.java:104)


        Caused by:

        java.net.SocketException: Broken pipe (Write failed)

            at java.net.SocketOutputStream.socketWrite0(Native Method)

            at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)

            at java.net.SocketOutputStream.write(SocketOutputStream.java:150)

            at 
redis.clients.jedis.util.RedisOutputStream.flushBuffer(RedisOutputStream.java:52)

            at 
redis.clients.jedis.util.RedisOutputStream.flush(RedisOutputStream.java:133)

            at redis.clients.jedis.Connection.disconnect(Connection.java:218)

            ... 3 more
{code}

5 tests failed in all:

{code}
2020-05-08 20:46:08.420 +0000 Completed test 
org.apache.geode.redis.executors.hash.HsetDUnitTest 
should_distributeDataAmongMultipleServers_givenMultipleClientsOnSameServer_addingDifferentDataToSameSetConcurrently
 with result: FAILURE

2020-05-08 20:46:15.914 +0000 Completed test 
org.apache.geode.redis.executors.hash.HsetDUnitTest 
should_distributeDataAmongMultipleServers_givenMultipleClients_addingToDifferentHashesConcurrently
 with result: FAILURE

2020-05-08 20:46:18.765 +0000 Completed test 
org.apache.geode.redis.executors.hash.HsetDUnitTest 
should_distributeDataAmongMultipleServers_givenMultipleClients with result: 
FAILURE

2020-05-08 20:46:21.417 +0000 Completed test 
org.apache.geode.redis.executors.hash.HsetDUnitTest 
should_distributeDataAmongMultipleServers_givenMultipleClients_addingDifferentDataToSameHashConcurrently
 with result: FAILURE

2020-05-08 20:46:31.408 +0000 Completed test 
org.apache.geode.redis.executors.hash.HsetDUnitTest classMethod with result: 
FAILURE
{code}

This might be due to a CI infrastructure failure. Or perhaps a crash in that 
remote JVM.



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

Reply via email to