[jira] [Assigned] (GEODE-6981) CF CLI: decouple CF CLI with PCC/Geode - command mapping
[ https://issues.apache.org/jira/browse/GEODE-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-6981: -- Assignee: (was: Shelley Lynn Hughes-Godfrey) > CF CLI: decouple CF CLI with PCC/Geode - command mapping > > > Key: GEODE-6981 > URL: https://issues.apache.org/jira/browse/GEODE-6981 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Gang Yan >Priority: Major > > things to do: > remove the command mapping component from CF CLI plugin for PCC > add a new general command mapping component on PCC side > this new general command mapping component will do: > # deal with the string input from CF CLI > # find the right endpoint and pass parameters to it > # the endpoint will deal with input and parameters , and return output to > the CF CLI -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (GEODE-6981) CF CLI: decouple CF CLI with PCC/Geode - command mapping
[ https://issues.apache.org/jira/browse/GEODE-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-6981: -- Assignee: Shelley Lynn Hughes-Godfrey > CF CLI: decouple CF CLI with PCC/Geode - command mapping > > > Key: GEODE-6981 > URL: https://issues.apache.org/jira/browse/GEODE-6981 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Gang Yan >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > things to do: > remove the command mapping component from CF CLI plugin for PCC > add a new general command mapping component on PCC side > this new general command mapping component will do: > # deal with the string input from CF CLI > # find the right endpoint and pass parameters to it > # the endpoint will deal with input and parameters , and return output to > the CF CLI -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (GEODE-6976) CI Failure: org.apache.geode.internal.net.SSLSocketIntegrationTest > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6976: -- Summary: CI Failure: org.apache.geode.internal.net.SSLSocketIntegrationTest > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED Key: GEODE-6976 URL: https://issues.apache.org/jira/browse/GEODE-6976 Project: Geode Issue Type: Bug Components: messaging Reporter: Shelley Lynn Hughes-Godfrey This failure occurred during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/883 {noformat} org.apache.geode.internal.net.SSLSocketIntegrationTest > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED java.lang.AssertionError: expected null, but was: but was:<"[]">> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotNull(Assert.java:755) at org.junit.Assert.assertNull(Assert.java:737) at org.junit.Assert.assertNull(Assert.java:747) at org.apache.geode.internal.net.SSLSocketIntegrationTest.testSecuredSocketTransmissionShouldWorkUsingNIO(SSLSocketIntegrationTest.java:230) {noformat} Artifacts are located here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0453/test-results/integrationTest/1563324048/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0453/test-artifacts/1563324048/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0453.tgz {noformat} stdout for the test: {noformat} [info 2019/07/17 00:24:29.828 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out [info 2019/07/17 00:24:30.287 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out server thread accepted a connection [info 2019/07/17 00:24:30.480 GMT tid=0x1d] Your SSL configuration disables hostname validation. ssl-endpoint-identification-enabled should be set to true when SSL is enabled. Please refer to the Apache GEODE SSL Documentation for SSL Property: ssl‑endpoint‑identification‑enabled client connect attempt timed out - checking stack trace client connect attempt timed out in the appropriate method server thread is exiting [info 2019/07/17 00:24:30.995 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out [info 2019/07/17 00:24:31.023 GMT tid=0x19] Your SSL configuration disables hostname validation. ssl-endpoint-identification-enabled should be set to true when SSL is enabled. Please refer to the Apache GEODE SSL Documentation for SSL Property: ssl‑endpoint‑identification‑enabled [info 2019/07/17 00:24:31.330 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out [info 2019/07/17 00:24:32.363 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out client sending Hello World message to server client buffer position is 0 and limit is 13 client wrapped buffer position is 0 and limit is 85 client bytes written is 85 client sending Hello World message to server client buffer position is 0 and limit is 13 client wrapped buffer position is 0 and limit is 85 client bytes written is 85 client sending Hello World message to server server bytes read is 170: buffer position is 0 and limit is 170 server unwrapped buffer position is 0 and limit is 26 server read Hello World message from client server read Hello World message from client client buffer position is 0 and limit is 13 client wrapped buffer position is 0 and limit is 85 client bytes written is 85 org.junit.ComparisonFailure: expected:<"[Hello world]"> but was:<"[]"> 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.internal.net.SSLSocketIntegrationTest.readMessageFromNIOSSLClient(SSLSocketIntegrationTest.java:316) at org.apache.geode.internal.net.SSLSocketIntegrationTest.lambda$startServerNIO$5(SSLSocketIntegrationTest.java:271) at java.lang.Thread.run(Thread.java:748) [info 2019/07/17 00:24:35.230 GMT tid=0x19] javax.net.ssl.SSLException: Read timed out [info 2019/07/17 00:24:36.367 GMT tid=0x26] TLS handshake is timing out java.net.SocketTimeoutException: handshake timed out at org.apache.geode.internal.net.NioSslEngine.handshake(NioSslEngine.java:133) at org.apache.geode.internal.net.SocketCreator.handshakeSSLSocketChannel(SocketCreator.java:955) at org.apache.geode.internal.net.SSLSocketIntegrationTest.lambda$startServerNIO$5(SSLSocketIntegrationTest.java:263) at java.lang.Thread.run(Thread.java:748) [info 2019/07/17
[jira] [Updated] (GEODE-6976) CI Failure: org.apache.geode.internal.net.SSLSocketIntegrationTest > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED
[ https://issues.apache.org/jira/browse/GEODE-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6976: --- Affects Version/s: 1.10.0 > CI Failure: org.apache.geode.internal.net.SSLSocketIntegrationTest > > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED > --- > > Key: GEODE-6976 > URL: https://issues.apache.org/jira/browse/GEODE-6976 > Project: Geode > Issue Type: Bug > Components: messaging >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred during CI: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/883 > {noformat} > org.apache.geode.internal.net.SSLSocketIntegrationTest > > testSecuredSocketTransmissionShouldWorkUsingNIO FAILED > java.lang.AssertionError: expected null, but > was: but was:<"[]">> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotNull(Assert.java:755) > at org.junit.Assert.assertNull(Assert.java:737) > at org.junit.Assert.assertNull(Assert.java:747) > at > org.apache.geode.internal.net.SSLSocketIntegrationTest.testSecuredSocketTransmissionShouldWorkUsingNIO(SSLSocketIntegrationTest.java:230) > {noformat} > Artifacts are located here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0453/test-results/integrationTest/1563324048/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0453/test-artifacts/1563324048/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0453.tgz > {noformat} > stdout for the test: > {noformat} > [info 2019/07/17 00:24:29.828 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out > [info 2019/07/17 00:24:30.287 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out > server thread accepted a connection > [info 2019/07/17 00:24:30.480 GMT > tid=0x1d] Your SSL configuration disables hostname validation. > ssl-endpoint-identification-enabled should be set to true when SSL is > enabled. Please refer to the Apache GEODE SSL Documentation for SSL Property: > ssl‑endpoint‑identification‑enabled > client connect attempt timed out - checking stack trace > client connect attempt timed out in the appropriate method > server thread is exiting > [info 2019/07/17 00:24:30.995 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out > [info 2019/07/17 00:24:31.023 GMT tid=0x19] Your SSL > configuration disables hostname validation. > ssl-endpoint-identification-enabled should be set to true when SSL is > enabled. Please refer to the Apache GEODE SSL Documentation for SSL Property: > ssl‑endpoint‑identification‑enabled > [info 2019/07/17 00:24:31.330 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out > [info 2019/07/17 00:24:32.363 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out > client sending Hello World message to server > client buffer position is 0 and limit is 13 > client wrapped buffer position is 0 and limit is 85 > client bytes written is 85 > client sending Hello World message to server > client buffer position is 0 and limit is 13 > client wrapped buffer position is 0 and limit is 85 > client bytes written is 85 > client sending Hello World message to server > server bytes read is 170: buffer position is 0 and limit is 170 > server unwrapped buffer position is 0 and limit is 26 > server read Hello World message from client > server read Hello World message from client > client buffer position is 0 and limit is 13 > client wrapped buffer position is 0 and limit is 85 > client bytes written is 85 > org.junit.ComparisonFailure: expected:<"[Hello world]"> but was:<"[]"> > 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.internal.net.SSLSocketIntegrationTest.readMessageFromNIOSSLClient(SSLSocketIntegrationTest.java:316) > at > org.apache.geode.internal.net.SSLSocketIntegrationTest.lambda$startServerNIO$5(SSLSocketIntegrationTest.java:271) > at java.lang.Thread.run(Thread.java:748) > [info 2019/07/17 00:24:35.230 GMT tid=0x19] action=add>javax.net.ssl.SSLException: Read timed out >
[jira] [Updated] (GEODE-6967) CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED
[ https://issues.apache.org/jira/browse/GEODE-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6967: --- Description: This failure occurred during CI on develop: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/882 {noformat} org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host dfe4c2133987 with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.testClientServerCompiledQueryTimeBasedCleanup(QueryUsingPoolDUnitTest.java:963) Caused by: java.lang.AssertionError: expected:<0> but was:<5> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.lambda$testClientServerCompiledQueryTimeBasedCleanup$bb17a952$6(QueryUsingPoolDUnitTest.java:966) {noformat} Artifacts can be found here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-results/distributedTest/1563239162/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-artifacts/1563239162/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0448.tgz {noformat} In this test, vm0 is a cacheServer vm1 and vm2 are clients. The test sets the clearQueryTimeout to 2 seconds. {noformat} DefaultQuery.setTestCompiledQueryClearTime(2 * 1000); {noformat} The test successfully executes compiled queries from both clients and then the server validates that compiledQueryCount is reset (compiled queries are cleared in the server ) within 60 seconds. vm1 then re-executes compiled queries and vm2 asynchronously executes queries while both clients close their cache. After the clients complete their cache close, the server fails when it attempts to verify the compiledQueryCount stat has been reset to 0 (due to client cache close). While the vm2 is attempting to close the cache, we still see async queries for vm2; the servers compileQueryCount is not 0 (but 5). Also, we see a 3 second delay in taking statSamples in the server which may have contributed to this timing issue. {noformat} [vm2] [info 2019/07/16 00:46:48.558 GMT tid=0x22] ### Executing Query :SELECT DISTINCT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 ORDER BY id [vm2] [info 2019/07/16 00:46:48.561 GMT tid=0x22] ### Executing Query :(SELECT DISTINCT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1).size [vm2] [info 2019/07/16 00:46:48.563 GMT tid=0x22] ### Executing Query :SELECT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id = $1 and Ticker = $2 [vm2] [info 2019/07/16 00:46:48.564 GMT tid=0x22] ### Executing Query :SELECT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 and Ticker = $2 [vm0] [warn 2019/07/16 00:46:52.724 GMT tid=0x1cf] Statistics sampling thread detected a wakeup delay of 3093 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. [vm2] [info 2019/07/16 00:46:52.694 GMT tid=0x22] ### Executing Query :SELECT itr.value FROM /root/testClientServerCompiledQueryTimeBasedCleanup.entries itr where itr.key = $1 [vm0] [info 2019/07/16 00:46:53.289 GMT tid=0x22] Got result: null [vm0] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on object: runnable(validate Compiled query) (took 5663 ms) [vm1] [info 2019/07/16 00:46:53.470 GMT tid=0x22] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0 args on object: runnable(closeClient) [vm1] [info 2019/07/16 00:46:53.495 GMT tid=0x22] ### Close Client. ### [vm1] [info 2019/07/16 00:46:53.496 GMT tid=0x22] GemFireCache[id = 461736604; isClosing = true; isShutDownAll = false; created = Tue Jul 16 00:46:43 GMT 2019; server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing. [vm1] [info 2019/07/16 00:46:53.508 GMT tid=0x22] Destroying connection pool testClientServerQueriesWithParams [vm2] [info 2019/07/16 00:46:53.525 GMT tid=0x22] ### Executing Query :SELECT DISTINCT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup
[jira] [Assigned] (GEODE-6967) CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED
[ https://issues.apache.org/jira/browse/GEODE-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-6967: -- Assignee: nabarun > CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > > testClientServerCompiledQueryTimeBasedCleanup FAILED > - > > Key: GEODE-6967 > URL: https://issues.apache.org/jira/browse/GEODE-6967 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: nabarun >Priority: Major > > This failure occurred during CI on develop: > {noformat} > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > > testClientServerCompiledQueryTimeBasedCleanup FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > dfe4c2133987 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.testClientServerCompiledQueryTimeBasedCleanup(QueryUsingPoolDUnitTest.java:963) > Caused by: > java.lang.AssertionError: expected:<0> but was:<5> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.lambda$testClientServerCompiledQueryTimeBasedCleanup$bb17a952$6(QueryUsingPoolDUnitTest.java:966) > {noformat} > Artifacts can be found here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-results/distributedTest/1563239162/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-artifacts/1563239162/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0448.tgz > {noformat} > In this test, vm0 is a cacheServer vm1 and vm2 are clients. > The test sets the clearQueryTimeout to 2 seconds. > {noformat} > DefaultQuery.setTestCompiledQueryClearTime(2 * 1000); > {noformat} > The test successfully executes compiled queries from both clients and then > the server validates that compiledQueryCount is reset (compiled queries are > cleared in the server ) within 60 seconds. > vm1 then re-executes compiled queries and vm2 asynchronously executes queries > while both clients close their cache. After the clients complete their cache > close, the server fails when it attempts to verify the compiledQueryCount > stat has been reset to 0 (due to client cache close). > While the vm2 is attempting to close the cache, we still see async queries > for vm2; the servers compileQueryCount is not 0 (but 5). Also, we see a 3 > second delay in taking statSamples in the server which may have contributed > to this timing issue. > {noformat} > [vm2] [info 2019/07/16 00:46:48.558 GMT > tid=0x22] ### Executing Query :SELECT DISTINCT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 ORDER BY id > [vm2] [info 2019/07/16 00:46:48.561 GMT > tid=0x22] ### Executing Query :(SELECT DISTINCT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1).size > [vm2] [info 2019/07/16 00:46:48.563 GMT > tid=0x22] ### Executing Query :SELECT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id = $1 and Ticker > = $2 > [vm2] [info 2019/07/16 00:46:48.564 GMT > tid=0x22] ### Executing Query :SELECT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 and Ticker > = $2 > [vm0] [warn 2019/07/16 00:46:52.724 GMT tid=0x1cf] Statistics > sampling thread detected a wakeup delay of 3093 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm2] [info 2019/07/16 00:46:52.694 GMT > tid=0x22] ### Executing Query :SELECT itr.value FROM > /root/testClientServerCompiledQueryTimeBasedCleanup.entries itr where itr.key > = $1 > [vm0] [info 2019/07/16 00:46:53.289 GMT > tid=0x22] Got result: null > [vm0] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on > object: runnable(validate Compiled query) (took 5663 ms) > [vm1] [info 2019/07/16 00:46:53.470 GMT > tid=0x22] Received method: org.apache.geode.test.dunit.NamedRunnable.run with > 0 args
[jira] [Updated] (GEODE-6967) CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED
[ https://issues.apache.org/jira/browse/GEODE-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6967: --- Affects Version/s: 1.10.0 > CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > > testClientServerCompiledQueryTimeBasedCleanup FAILED > - > > Key: GEODE-6967 > URL: https://issues.apache.org/jira/browse/GEODE-6967 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred during CI on develop: > {noformat} > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > > testClientServerCompiledQueryTimeBasedCleanup FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host > dfe4c2133987 with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.testClientServerCompiledQueryTimeBasedCleanup(QueryUsingPoolDUnitTest.java:963) > Caused by: > java.lang.AssertionError: expected:<0> but was:<5> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.lambda$testClientServerCompiledQueryTimeBasedCleanup$bb17a952$6(QueryUsingPoolDUnitTest.java:966) > {noformat} > Artifacts can be found here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-results/distributedTest/1563239162/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-artifacts/1563239162/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0448.tgz > {noformat} > In this test, vm0 is a cacheServer vm1 and vm2 are clients. > The test sets the clearQueryTimeout to 2 seconds. > {noformat} > DefaultQuery.setTestCompiledQueryClearTime(2 * 1000); > {noformat} > The test successfully executes compiled queries from both clients and then > the server validates that compiledQueryCount is reset (compiled queries are > cleared in the server ) within 60 seconds. > vm1 then re-executes compiled queries and vm2 asynchronously executes queries > while both clients close their cache. After the clients complete their cache > close, the server fails when it attempts to verify the compiledQueryCount > stat has been reset to 0 (due to client cache close). > While the vm2 is attempting to close the cache, we still see async queries > for vm2; the servers compileQueryCount is not 0 (but 5). Also, we see a 3 > second delay in taking statSamples in the server which may have contributed > to this timing issue. > {noformat} > [vm2] [info 2019/07/16 00:46:48.558 GMT > tid=0x22] ### Executing Query :SELECT DISTINCT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 ORDER BY id > [vm2] [info 2019/07/16 00:46:48.561 GMT > tid=0x22] ### Executing Query :(SELECT DISTINCT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1).size > [vm2] [info 2019/07/16 00:46:48.563 GMT > tid=0x22] ### Executing Query :SELECT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id = $1 and Ticker > = $2 > [vm2] [info 2019/07/16 00:46:48.564 GMT > tid=0x22] ### Executing Query :SELECT * FROM > /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 and Ticker > = $2 > [vm0] [warn 2019/07/16 00:46:52.724 GMT tid=0x1cf] Statistics > sampling thread detected a wakeup delay of 3093 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm2] [info 2019/07/16 00:46:52.694 GMT > tid=0x22] ### Executing Query :SELECT itr.value FROM > /root/testClientServerCompiledQueryTimeBasedCleanup.entries itr where itr.key > = $1 > [vm0] [info 2019/07/16 00:46:53.289 GMT > tid=0x22] Got result: null > [vm0] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on > object: runnable(validate Compiled query) (took 5663 ms) > [vm1] [info 2019/07/16 00:46:53.470 GMT > tid=0x22] Received method: org.apache.geode.test.dunit.NamedRunnable.run with > 0 args on object:
[jira] [Created] (GEODE-6967) CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6967: -- Summary: CI Failure: org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED Key: GEODE-6967 URL: https://issues.apache.org/jira/browse/GEODE-6967 Project: Geode Issue Type: Bug Components: querying Reporter: Shelley Lynn Hughes-Godfrey This failure occurred during CI on develop: {noformat} org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest > testClientServerCompiledQueryTimeBasedCleanup FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host dfe4c2133987 with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.testClientServerCompiledQueryTimeBasedCleanup(QueryUsingPoolDUnitTest.java:963) Caused by: java.lang.AssertionError: expected:<0> but was:<5> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.cache.query.dunit.QueryUsingPoolDUnitTest.lambda$testClientServerCompiledQueryTimeBasedCleanup$bb17a952$6(QueryUsingPoolDUnitTest.java:966) {noformat} Artifacts can be found here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-results/distributedTest/1563239162/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0448/test-artifacts/1563239162/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0448.tgz {noformat} In this test, vm0 is a cacheServer vm1 and vm2 are clients. The test sets the clearQueryTimeout to 2 seconds. {noformat} DefaultQuery.setTestCompiledQueryClearTime(2 * 1000); {noformat} The test successfully executes compiled queries from both clients and then the server validates that compiledQueryCount is reset (compiled queries are cleared in the server ) within 60 seconds. vm1 then re-executes compiled queries and vm2 asynchronously executes queries while both clients close their cache. After the clients complete their cache close, the server fails when it attempts to verify the compiledQueryCount stat has been reset to 0 (due to client cache close). While the vm2 is attempting to close the cache, we still see async queries for vm2; the servers compileQueryCount is not 0 (but 5). Also, we see a 3 second delay in taking statSamples in the server which may have contributed to this timing issue. {noformat} [vm2] [info 2019/07/16 00:46:48.558 GMT tid=0x22] ### Executing Query :SELECT DISTINCT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 ORDER BY id [vm2] [info 2019/07/16 00:46:48.561 GMT tid=0x22] ### Executing Query :(SELECT DISTINCT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1).size [vm2] [info 2019/07/16 00:46:48.563 GMT tid=0x22] ### Executing Query :SELECT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id = $1 and Ticker = $2 [vm2] [info 2019/07/16 00:46:48.564 GMT tid=0x22] ### Executing Query :SELECT * FROM /root/testClientServerCompiledQueryTimeBasedCleanup WHERE id < $1 and Ticker = $2 [vm0] [warn 2019/07/16 00:46:52.724 GMT tid=0x1cf] Statistics sampling thread detected a wakeup delay of 3093 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. [vm2] [info 2019/07/16 00:46:52.694 GMT tid=0x22] ### Executing Query :SELECT itr.value FROM /root/testClientServerCompiledQueryTimeBasedCleanup.entries itr where itr.key = $1 [vm0] [info 2019/07/16 00:46:53.289 GMT tid=0x22] Got result: null [vm0] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on object: runnable(validate Compiled query) (took 5663 ms) [vm1] [info 2019/07/16 00:46:53.470 GMT tid=0x22] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0 args on object: runnable(closeClient) [vm1] [info 2019/07/16 00:46:53.495 GMT tid=0x22] ### Close Client. ### [vm1] [info 2019/07/16 00:46:53.496 GMT tid=0x22] GemFireCache[id = 461736604; isClosing = true; isShutDownAll = false; created = Tue Jul 16 00:46:43 GMT 2019; server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing. [vm1] [info 2019/07/16 00:46:53.508 GMT tid=0x22] Destroying connection pool testClientServerQueriesWithParams [vm2] [info 2019/07/16
[jira] [Commented] (GEODE-6919) CI Failure: org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > testAcceptorImplCloseCleansUpWithHangingConnection FAILED
[ https://issues.apache.org/jira/browse/GEODE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872791#comment-16872791 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6919: This looks like a fairly simple test ... The controller vm is the server ... which creates a PR region "region1" with a SleepyCacheWriter() ... basically it sets a field to say it has started ... then waits to be told to stop. The client creates a PROXY of the same region and does a single put. We expect this to invoke the cacheWriter in the server, but it looks like the client put fails: {noformat} [vm0] [info 2019/06/25 21:20:48.591 GMT RMI TCP Connection(1)-172.17.0.19 tid=0x20] Got result: EXCEPTION_OCCURRED [vm0] org.apache.geode.cache.client.AllConnectionsInUseException [vm0] at org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:297) [vm0] at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:125) [vm0] at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) [vm0] at org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) [vm0] at org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:89) [vm0] at org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:156) [vm0] at org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3024) [vm0] at org.apache.geode.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3141) [vm0] at org.apache.geode.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:238) [vm0] at org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5572) [vm0] at org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:162) [vm0] at org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5031) [vm0] at org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1623) [vm0] at org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1610) [vm0] at org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:429) [vm0] at org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest.lambda$testAcceptorImplCloseCleansUpWithHangingConnection$b2a1707f$1(AcceptorImplDUnitTest.java:178) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.lang.reflect.Method.invoke(Method.java:498) [vm0] at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) [vm0] at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.lang.reflect.Method.invoke(Method.java:498) [vm0] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) [vm0] at java.security.AccessController.doPrivileged(Native Method) [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [vm0] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [vm0] at java.security.AccessController.doPrivileged(Native Method) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [vm0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [vm0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [vm0] at java.lang.Thread.run(Thread.java:748) [vm0] from org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest$$Lambda$17/148174679.run with 0 args on object: org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest$$Lambda$17/148174679@167c163b (took 6118 ms) {noformat} Perhaps there are still connections waiting from a previously run test: {noformat} Previously run tests: [AcceptorImplDUnitTest.testAcceptorImplCloseCleansUp] {noformat} > CI Failure: > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > > testAcceptorImplCloseCleansUpWithHangingConnection FAILED >
[jira] [Updated] (GEODE-6919) CI Failure: org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > testAcceptorImplCloseCleansUpWithHangingConnection FAILED
[ https://issues.apache.org/jira/browse/GEODE-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6919: --- Affects Version/s: 1.10.0 > CI Failure: > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > > testAcceptorImplCloseCleansUpWithHangingConnection FAILED > -- > > Key: GEODE-6919 > URL: https://issues.apache.org/jira/browse/GEODE-6919 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred in CI: > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/837 > {noformat} > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > > testAcceptorImplCloseCleansUpWithHangingConnection FAILED > org.awaitility.core.ConditionTimeoutException: Condition with alias > 'Cache writer starts' didn't complete within 300 seconds because condition > with lambda expression in > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest that uses > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest$SleepyCacheWriter > was not fulfilled. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:79) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:27) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860) > at > org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest.testAcceptorImplCloseCleansUpWithHangingConnection(AcceptorImplDUnitTest.java:182) > {noformat} > Artifacts are available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0403/test-results/distributedTest/1561499094/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0403/test-artifacts/1561499094/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0403.tgz > {noformat} > Test description: > {noformat} > /** >* GEODE-2324. There was a bug where, due to an uncaught exception, > `AcceptorImpl.close()` was >* short-circuiting and failing to clean up properly. >* >* What this test does is start a Cache and hook the Acceptor to interrupt > the thread before the >* place where an InterruptedException could be thrown. It interrupts the > thread, and checks that >* the thread has terminated normally without short-circuiting. It doesn't > check that every part >* of the AcceptorImpl has shut down properly -- that seems both difficult > to check (especially >* since the fields are private) and implementation-dependent. >*/ > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6919) CI Failure: org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > testAcceptorImplCloseCleansUpWithHangingConnection FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6919: -- Summary: CI Failure: org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > testAcceptorImplCloseCleansUpWithHangingConnection FAILED Key: GEODE-6919 URL: https://issues.apache.org/jira/browse/GEODE-6919 Project: Geode Issue Type: Bug Components: client/server Reporter: Shelley Lynn Hughes-Godfrey This failure occurred in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/837 {noformat} org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest > testAcceptorImplCloseCleansUpWithHangingConnection FAILED org.awaitility.core.ConditionTimeoutException: Condition with alias 'Cache writer starts' didn't complete within 300 seconds because condition with lambda expression in org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest that uses org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest$SleepyCacheWriter was not fulfilled. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.CallableCondition.await(CallableCondition.java:79) at org.awaitility.core.CallableCondition.await(CallableCondition.java:27) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860) at org.apache.geode.internal.cache.tier.sockets.AcceptorImplDUnitTest.testAcceptorImplCloseCleansUpWithHangingConnection(AcceptorImplDUnitTest.java:182) {noformat} Artifacts are available here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0403/test-results/distributedTest/1561499094/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0403/test-artifacts/1561499094/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0403.tgz {noformat} Test description: {noformat} /** * GEODE-2324. There was a bug where, due to an uncaught exception, `AcceptorImpl.close()` was * short-circuiting and failing to clean up properly. * * What this test does is start a Cache and hook the Acceptor to interrupt the thread before the * place where an InterruptedException could be thrown. It interrupts the thread, and checks that * the thread has terminated normally without short-circuiting. It doesn't check that every part * of the AcceptorImpl has shut down properly -- that seems both difficult to check (especially * since the fields are private) and implementation-dependent. */ {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-6284) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0, with reindex=false]
[ https://issues.apache.org/jira/browse/GEODE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839898#comment-16839898 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-6284 at 5/15/19 1:25 AM: - We've seen additional failures on this test in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/712 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/572 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/414 {noformat} Task :geode-lucene:upgradeTest org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v170, with reindex=true] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit$10.run in VM 3 running on Host ab2bcf8629bf with 4 VMs with version 170 at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.putSerializableObject(LuceneSearchWithRollingUpgradeDUnit.java:358) at org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:114) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException Caused by: java.lang.reflect.InvocationTargetException Caused by: org.apache.geode.cache.client.NoAvailableServersException org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v170, with reindex=false] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v180, with reindex=true] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v180, with reindex=false] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4
[jira] [Commented] (GEODE-6284) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test[from_v1X0, with reindex=false]
[ https://issues.apache.org/jira/browse/GEODE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839898#comment-16839898 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6284: We've seen additional failures on this test in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/712 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/572 https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/414 These failures are not a hang/timeout exceeded, but look like this: {noformat} Task :geode-lucene:upgradeTest org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v170, with reindex=true] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit$10.run in VM 3 running on Host ab2bcf8629bf with 4 VMs with version 170 at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.putSerializableObject(LuceneSearchWithRollingUpgradeDUnit.java:358) at org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:114) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException Caused by: java.lang.reflect.InvocationTargetException Caused by: org.apache.geode.cache.client.NoAvailableServersException org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v170, with reindex=false] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v180, with reindex=true] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host ab2bcf8629bf with 4 VMs with version 170 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.17; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v180, with reindex=false] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host
[jira] [Resolved] (GEODE-4650) DLockService.clearGrantor can potentially hang
[ https://issues.apache.org/jira/browse/GEODE-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-4650. Resolution: Fixed > DLockService.clearGrantor can potentially hang > -- > > Key: GEODE-4650 > URL: https://issues.apache.org/jira/browse/GEODE-4650 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Jason Huynh >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Attachments: callstacks-2018-02-10-05-25-15.txt, > callstacks-2018-02-10-05-25-23.txt, callstacks-2018-02-10-05-25-30.txt > > Time Spent: 6h 20m > Remaining Estimate: 0h > > There was a test run in the precheckin pipeline that hung with the following > stack: > > {code:java} > "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 > tid=0x7f4560001800 nid=0x191 waiting on condition [0x7f45771c] > java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xe082d298> (a > java.util.concurrent.CountDownLatch$Sync) > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at > org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) > at > org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) > at > org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) > at > org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318) > at > org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872) > at > org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227) > - locked <0xe0837ff0> (a > org.apache.geode.distributed.internal.locks.DLockGrantor) > at > org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:646) > at > org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2358) > at > org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2276) > - locked <0xe05c7468> (a java.lang.Object) > at > org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2214) > at > org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:84) > at > org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:2043) > at > org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2180) > - locked <0xe04653e0> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > at > org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1960) > at > org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1950) > at > org.apache.geode.test.junit.rules.ServerStarterRule.stopMember(ServerStarterRule.java:99) > at > org.apache.geode.test.junit.rules.MemberStarterRule.after(MemberStarterRule.java:81) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.stopElementInsideVM(ClusterStartupRule.java:412) > at > org.apache.geode.test.junit.rules.VMProvider.lambda$stopVM$fe0d42dc$1(VMProvider.java:35)
[jira] [Comment Edited] (GEODE-4650) DLockService.clearGrantor can potentially hang
[ https://issues.apache.org/jira/browse/GEODE-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837720#comment-16837720 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-4650 at 5/13/19 5:11 PM: - Note that this hang reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/707 Since this was fixed in 1.8, perhaps we should expect to see it in rolling upgrade tests from older versions ... so just noting that it reproduced (without reopening). Hung Test: 2019-05-10 22:41:28.511 + org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterCurrentSiteMemberFailoverWithOldClient testSecondaryEventsNotReprocessedAfterCurrentSiteMemberFailoverWithOldClient[from_v100] Stack dump (from callstacks): {noformat} "RMI TCP Connection(3)-172.17.0.4" #35 daemon prio=5 os_prio=0 cpu=5492.78ms elapsed=2867.65s tid=0x7f23f8001800 nid=0x212 waiting on condition [0x7f244dab5000] java.lang.Thread.State: TIMED_WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@11.0.2/Native Method) - parking to wait for <0xe0804d68> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(java.base@11.0.2/LockSupport.java:234) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(java.base@11.0.2/AbstractQueuedSynchronizer.java:1079) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(java.base@11.0.2/AbstractQueuedSynchronizer.java:1369) at java.util.concurrent.CountDownLatch.await(java.base@11.0.2/CountDownLatch.java:278) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:736) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:812) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:789) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:879) at org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:76) at org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:57) at org.apache.geode.distributed.internal.DistributionManager.getElderStateWithTryLock(DistributionManager.java:3628) at org.apache.geode.distributed.internal.DistributionManager.getElderState(DistributionManager.java:3574) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:254) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:377) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:352) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:340) at org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:885) at org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1274) - locked <0xe0b17d48> (a org.apache.geode.distributed.internal.locks.DLockGrantor) at org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:663) at org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2606) at org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2521) - locked <0xe0b17e78> (a java.lang.Object) at org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2420) at org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:98) at org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:1943) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2088) - locked <0xe0922ad8> (a java.lang.Class for org.apache.geode.internal.cache.GemFireCacheImpl) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1862) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1858) at org.apache.geode.test.dunit.cache.internal.JUnit4CacheTestCase.closeCache(JUnit4CacheTestCase.java:327) {noformat} Test report artifacts from this job are available at: {noformat}
[jira] [Reopened] (GEODE-4650) DLockService.clearGrantor can potentially hang
[ https://issues.apache.org/jira/browse/GEODE-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reopened GEODE-4650: Assignee: (was: Helena Bales) Re-opening as this hang reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/707 Since this was fixed in 1.8, perhaps we should expect to see it in rolling upgrade tests from older versions (but we need a marker for that for CI). Hung Test: 2019-05-10 22:41:28.511 + org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterCurrentSiteMemberFailoverWithOldClient testSecondaryEventsNotReprocessedAfterCurrentSiteMemberFailoverWithOldClient[from_v100] Stack dump (from callstacks): {noformat} "RMI TCP Connection(3)-172.17.0.4" #35 daemon prio=5 os_prio=0 cpu=5492.78ms elapsed=2867.65s tid=0x7f23f8001800 nid=0x212 waiting on condition [0x7f244dab5000] java.lang.Thread.State: TIMED_WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@11.0.2/Native Method) - parking to wait for <0xe0804d68> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(java.base@11.0.2/LockSupport.java:234) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(java.base@11.0.2/AbstractQueuedSynchronizer.java:1079) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(java.base@11.0.2/AbstractQueuedSynchronizer.java:1369) at java.util.concurrent.CountDownLatch.await(java.base@11.0.2/CountDownLatch.java:278) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:736) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:812) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:789) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:879) at org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:76) at org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:57) at org.apache.geode.distributed.internal.DistributionManager.getElderStateWithTryLock(DistributionManager.java:3628) at org.apache.geode.distributed.internal.DistributionManager.getElderState(DistributionManager.java:3574) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:254) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:377) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:352) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:340) at org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:885) at org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1274) - locked <0xe0b17d48> (a org.apache.geode.distributed.internal.locks.DLockGrantor) at org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:663) at org.apache.geode.distributed.internal.locks.DLockService.basicDestroy(DLockService.java:2606) at org.apache.geode.distributed.internal.locks.DLockService.destroyAndRemove(DLockService.java:2521) - locked <0xe0b17e78> (a java.lang.Object) at org.apache.geode.distributed.internal.locks.DLockService.destroyServiceNamed(DLockService.java:2420) at org.apache.geode.distributed.DistributedLockService.destroy(DistributedLockService.java:98) at org.apache.geode.internal.cache.GemFireCacheImpl.destroyGatewaySenderLockService(GemFireCacheImpl.java:1943) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2088) - locked <0xe0922ad8> (a java.lang.Class for org.apache.geode.internal.cache.GemFireCacheImpl) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1862) at org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1858) at org.apache.geode.test.dunit.cache.internal.JUnit4CacheTestCase.closeCache(JUnit4CacheTestCase.java:327) {noformat} Test report artifacts from this job are available at: {noformat}
[jira] [Comment Edited] (GEODE-6646) CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[ https://issues.apache.org/jira/browse/GEODE-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816695#comment-16816695 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-6646 at 4/12/19 10:35 PM: -- In this test, we start a locator and 2 servers (server-1 and server-2). Then we forcefully disconnect server-2 and the locator before waiting for the locator to reconnect + start server-3. We must also expect server2 to reconnect; but it looks like the locator, server-2 and server-3 form a new DS (without server-1). {noformat} @Test public void serverRestartsAfterLocatorReconnects() throws Exception { IgnoredException.addIgnoredException("org.apache.geode.ForcedDisconnectException: for testing"); IgnoredException.addIgnoredException("cluster configuration service not available"); IgnoredException.addIgnoredException("This thread has been stalled"); IgnoredException .addIgnoredException("member unexpectedly shut down shared, unordered connection"); IgnoredException.addIgnoredException("Connection refused"); MemberVM locator0 = rule.startLocatorVM(0); rule.startServerVM(1, locator0.getPort()); MemberVM server2 = rule.startServerVM(2, locator0.getPort()); addDisconnectListener(locator0); server2.forceDisconnect(); locator0.forceDisconnect(); waitForLocatorToReconnect(locator0); rule.startServerVM(3, locator0.getPort()); gfsh.connectAndVerify(locator0); await() .untilAsserted(() -> gfsh.executeAndAssertThat("list members").statusIsSuccess() .tableHasColumnOnlyWithValues("Name", "locator-0", "server-1", "server-2", "server-3")); } {noformat} locator and server-2 are forcefully disconnected at 19:30:45 and it looks like server-1 tried to become the coordinator ... but in the end, he didn't get any responses from the others and they seems to create their own DS. {noformat} [vm2] [info 2019/04/12 19:30:45.491 UTC RMI TCP Connection(1)-172.17.0.2 tid=0x20] GroupMembershipService.beSick invoked for 172.17.0.2(server-2:249)v2:41003 - simulating sickness [vm2] [info 2019/04/12 19:30:45.491 UTC RMI TCP Connection(1)-172.17.0.2 tid=0x20] GroupMembershipService.playDead invoked for 172.17.0.2(server-2:249)v2:41003 [vm0] [info 2019/04/12 19:30:45.716 UTC RMI TCP Connection(1)-172.17.0.2 tid=0x20] GroupMembershipService.beSick invoked for 172.17.0.2(locator-0:1011:locator)ecv0:41001 - simulating sickness [vm0] [info 2019/04/12 19:30:45.716 UTC RMI TCP Connection(1)-172.17.0.2 tid=0x20] GroupMembershipService.playDead invoked for 172.17.0.2(locator-0:1011:locator)ecv0:41001 {noformat} vm1 reports the locator and server-2 as suspect and becomes the membership coordinator {noformat} [vm1] [info 2019/04/12 19:30:50.772 UTC Geode Failure Detection thread 3 tid=0xca] Availability check failed for member 172.17.0.2(server-2:249)v2:41003 [vm1] [info 2019/04/12 19:30:50.773 UTC Geode Failure Detection thread 3 tid=0xca] Requesting removal of suspect member 172.17.0.2(server-2:249)v2:41003 [vm1] [info 2019/04/12 19:30:50.772 UTC Geode Failure Detection thread 2 tid=0xc9] Availability check failed for member 172.17.0.2(locator-0:1011:locator)ecv0:41001 [vm1] [info 2019/04/12 19:30:50.776 UTC Geode Failure Detection thread 2 tid=0xc9] Requesting removal of suspect member 172.17.0.2(locator-0:1011:locator)ecv0:41001 [vm1] [info 2019/04/12 19:30:50.776 UTC Geode Failure Detection thread 2 tid=0xc9] This member is becoming the membership coordinator with address 172.17.0.2(server-1:245)v1:41002 [vm1] [info 2019/04/12 19:30:50.777 UTC Geode Failure Detection thread 2 tid=0xc9] ViewCreator starting on:172.17.0.2(server-1:245)v1:41002 [vm1] [info 2019/04/12 19:30:50.777 UTC Geode Membership View Creator tid=0xcb] View Creator thread is starting [vm1] [info 2019/04/12 19:30:50.779 UTC Geode Membership View Creator tid=0xcb] preparing new view View[172.17.0.2(server-1:245)v1:41002|9] members: [172.17.0.2(server-1:245)v1:41002{lead}, 172.17.0.2(server-2:249)v2:41003] crashed: [172.17.0.2(locator-0:1011:locator)ecv0:41001] ... [vm1] [info 2019/04/12 19:31:41.970 UTC Geode Membership View Creator tid=0xcb] sending new view View[172.17.0.2(server-1:245)v1:41002|12] members: [172.17.0.2(server-1:245)v1:41002{lead}] crashed: [172.17.0.2(locator-0:1011:locator)ecv11:41001, 172.17.0.2(server-2:249)v11:41003] [vm2] [info 2019/04/12 19:31:41.970 UTC unicast receiver,bba57c926507-60306 tid=0x8a] Ignoring the view View[172.17.0.2(server-1:245)v1:41002|12] members: [172.17.0.2(server-1:245)v1:41002{lead}] crashed: [172.17.0.2(server-2:249)v11:41003, 172.17.0.2(locator-0:1011:locator)ecv11:41001] from member 172.17.0.2v1:41002, which is not in my current view View[172.17.0.2(locator-0:1011:locator)ecv0:41001|1] members: [172.17.0.2(locator-0:1011:locator)ecv0:41001,
[jira] [Commented] (GEODE-6646) CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[ https://issues.apache.org/jira/browse/GEODE-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816695#comment-16816695 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6646: In this test, we start a locator and 2 servers (server-1 and server-2). Then we forcefully disconnect server-2 and the locator before waiting for the locator to reconnect + start server-3. We must also expect server2 to reconnect; but it looks like the locator, server-2 and server-3 form a new DS (without server-1). {noformat} @Test public void serverRestartsAfterLocatorReconnects() throws Exception { IgnoredException.addIgnoredException("org.apache.geode.ForcedDisconnectException: for testing"); IgnoredException.addIgnoredException("cluster configuration service not available"); IgnoredException.addIgnoredException("This thread has been stalled"); IgnoredException .addIgnoredException("member unexpectedly shut down shared, unordered connection"); IgnoredException.addIgnoredException("Connection refused"); MemberVM locator0 = rule.startLocatorVM(0); rule.startServerVM(1, locator0.getPort()); MemberVM server2 = rule.startServerVM(2, locator0.getPort()); addDisconnectListener(locator0); server2.forceDisconnect(); locator0.forceDisconnect(); waitForLocatorToReconnect(locator0); rule.startServerVM(3, locator0.getPort()); gfsh.connectAndVerify(locator0); await() .untilAsserted(() -> gfsh.executeAndAssertThat("list members").statusIsSuccess() .tableHasColumnOnlyWithValues("Name", "locator-0", "server-1", "server-2", "server-3")); } {noformat} > CI: > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > - > > Key: GEODE-6646 > URL: https://issues.apache.org/jira/browse/GEODE-6646 > Project: Geode > Issue Type: Bug > Components: gfsh, membership >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: CI > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/617 > {noformat} > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:81) > Caused by: > java.lang.AssertionError: > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnOnlyWithValues(CommandResultAssert.java:308) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$serverRestartsAfterLocatorReconnects$0(ClusterConfigLocatorRestartDUnitTest.java:82) > {noformat} > Artifacts available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-results/distributedTest/1555101232/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-artifacts/1555101232/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0177.tgz > {noformat} -- This message was sent by Atlassian JIRA
[jira] [Updated] (GEODE-6646) CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[ https://issues.apache.org/jira/browse/GEODE-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6646: --- Affects Version/s: 1.10.0 > CI: > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > - > > Key: GEODE-6646 > URL: https://issues.apache.org/jira/browse/GEODE-6646 > Project: Geode > Issue Type: Bug > Components: gfsh, membership >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/617 > {noformat} > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:81) > Caused by: > java.lang.AssertionError: > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnOnlyWithValues(CommandResultAssert.java:308) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$serverRestartsAfterLocatorReconnects$0(ClusterConfigLocatorRestartDUnitTest.java:82) > {noformat} > Artifacts available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-results/distributedTest/1555101232/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-artifacts/1555101232/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0177.tgz > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6646) CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6646: -- Summary: CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED Key: GEODE-6646 URL: https://issues.apache.org/jira/browse/GEODE-6646 Project: Geode Issue Type: Bug Components: gfsh, membership Reporter: Shelley Lynn Hughes-Godfrey https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/617 {noformat} org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest Expecting: <["locator-0", "server-2", "server-3"]> to contain only: <["locator-0", "server-1", "server-2", "server-3"]> but could not find the following elements: <["server-1"]> within 300 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) at org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:81) Caused by: java.lang.AssertionError: Expecting: <["locator-0", "server-2", "server-3"]> to contain only: <["locator-0", "server-1", "server-2", "server-3"]> but could not find the following elements: <["server-1"]> at org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnOnlyWithValues(CommandResultAssert.java:308) at org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$serverRestartsAfterLocatorReconnects$0(ClusterConfigLocatorRestartDUnitTest.java:82) {noformat} Artifacts available here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-results/distributedTest/1555101232/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-artifacts/1555101232/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0177.tgz {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6646) CI: org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects FAILED
[ https://issues.apache.org/jira/browse/GEODE-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6646: --- Labels: CI (was: ) > CI: > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > - > > Key: GEODE-6646 > URL: https://issues.apache.org/jira/browse/GEODE-6646 > Project: Geode > Issue Type: Bug > Components: gfsh, membership >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: CI > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/617 > {noformat} > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects(ClusterConfigLocatorRestartDUnitTest.java:81) > Caused by: > java.lang.AssertionError: > Expecting: > <["locator-0", "server-2", "server-3"]> > to contain only: > <["locator-0", "server-1", "server-2", "server-3"]> > but could not find the following elements: > <["server-1"]> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnOnlyWithValues(CommandResultAssert.java:308) > at > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest.lambda$serverRestartsAfterLocatorReconnects$0(ClusterConfigLocatorRestartDUnitTest.java:82) > {noformat} > Artifacts available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-results/distributedTest/1555101232/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0177/test-artifacts/1555101232/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0177.tgz > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6645) CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED
[ https://issues.apache.org/jira/browse/GEODE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6645: --- Labels: CI (was: ) > CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > > testDataStoreEntryCount FAILED > > > Key: GEODE-6645 > URL: https://issues.apache.org/jira/browse/GEODE-6645 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: CI > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/617 > {noformat} > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > > testDataStoreEntryCount FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run > in VM 2 running on Host 1ee860aba5ac with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) > Caused by: > org.junit.ComparisonFailure: expected:<[3]L> but was:<[2]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.validateEntryCount(PartitionedRegionStatsDUnitTest.java:267) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.lambda$testDataStoreEntryCount$bb17a952$18(PartitionedRegionStatsDUnitTest.java:198) > {noformat} > Artifacts are available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-results/distributedTest/1555097363/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-artifacts/1555097363/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0176.tgz > {noformat} > Looking at this test, it goes through several phases of entry creation, > destroy, destroy + put and GII (after adding a new member) for a partitioned > region with redundantCopies=2. After adding the new member and forcing > tombstone expiration, the newly created vm ends up with 1 less entry than > expected (but the original two vms appear to have the expected number of > entries (3)). > Full stack > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run > in VM 2 running on Host 1ee860aba5ac with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at >
[jira] [Updated] (GEODE-6645) CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED
[ https://issues.apache.org/jira/browse/GEODE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6645: --- Affects Version/s: 1.10.0 > CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > > testDataStoreEntryCount FAILED > > > Key: GEODE-6645 > URL: https://issues.apache.org/jira/browse/GEODE-6645 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/617 > {noformat} > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > > testDataStoreEntryCount FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run > in VM 2 running on Host 1ee860aba5ac with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) > Caused by: > org.junit.ComparisonFailure: expected:<[3]L> but was:<[2]L> > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.validateEntryCount(PartitionedRegionStatsDUnitTest.java:267) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.lambda$testDataStoreEntryCount$bb17a952$18(PartitionedRegionStatsDUnitTest.java:198) > {noformat} > Artifacts are available here: > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-results/distributedTest/1555097363/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-artifacts/1555097363/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0176.tgz > {noformat} > Looking at this test, it goes through several phases of entry creation, > destroy, destroy + put and GII (after adding a new member) for a partitioned > region with redundantCopies=2. After adding the new member and forcing > tombstone expiration, the newly created vm ends up with 1 less entry than > expected (but the original two vms appear to have the expected number of > entries (3)). > Full stack > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run > in VM 2 running on Host 1ee860aba5ac with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at >
[jira] [Created] (GEODE-6645) CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6645: -- Summary: CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED Key: GEODE-6645 URL: https://issues.apache.org/jira/browse/GEODE-6645 Project: Geode Issue Type: Bug Components: regions Reporter: Shelley Lynn Hughes-Godfrey https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/617 {noformat} org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run in VM 2 running on Host 1ee860aba5ac with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) Caused by: org.junit.ComparisonFailure: expected:<[3]L> but was:<[2]L> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.validateEntryCount(PartitionedRegionStatsDUnitTest.java:267) at org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.lambda$testDataStoreEntryCount$bb17a952$18(PartitionedRegionStatsDUnitTest.java:198) {noformat} Artifacts are available here: {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-results/distributedTest/1555097363/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-artifacts/1555097363/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0176.tgz {noformat} Looking at this test, it goes through several phases of entry creation, destroy, destroy + put and GII (after adding a new member) for a partitioned region with redundantCopies=2. After adding the new member and forcing tombstone expiration, the newly created vm ends up with 1 less entry than expected (but the original two vms appear to have the expected number of entries (3)). Full stack {noformat} org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run in VM 2 running on Host 1ee860aba5ac with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
[ https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-5816: --- Labels: CI swat (was: swat) > ClusterStartupRule fails to launch JMX manager (port already in use) > > > Key: GEODE-5816 > URL: https://issues.apache.org/jira/browse/GEODE-5816 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Bill Burcham >Assignee: Dan Smith >Priority: Major > Labels: CI, swat > > We see these related failures on a couple tests in > RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run. > From looking at the stack traces though, we surmise that the problem occurs > in the ClusterStartupRule _before_ the actual tests run. Since it occurs > before the tests run, we think the problem lies outside the > RegionMembershipMBeanOverHttpDUnitTest class. > {noformat} > 4 failures (99.600% success > rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest > | .testAddRmNewMemberWithReplicatedRegionsAndSubregions: 1 failures > (99.900% success rate) > | | Failed build 24 at > https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24 > | .testMultiplePartitionedRegions: 3 failures (99.700% success rate) > | | Failed build 982 at > https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982 > | | Failed build 256 at > https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256 > {noformat} > Here's a stack trace: > {noformat} > 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 358 > [error 2018/10/01 06:28:30.869 UTC > tid=0x20] Jmx manager could not be started because > java.rmi.server.ExportException: Port already in use: 25305; nested exception > is: > java.net.BindException: Failed to create server socket on > ffd50f3577c5/172.17.0.20[25305] > org.apache.geode.management.ManagementException: > java.rmi.server.ExportException: Port already in use: 25305; nested exception > is: > java.net.BindException: Failed to create server socket on > ffd50f3577c5/172.17.0.20[25305] > at > org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162) > at > org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435) > at > org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173) > at > org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591) > at > org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218) > at > org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793) > at > org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224) > at > org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662) > at > org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649) > at > org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311) > at org.apache.geode.distributed.Locator.startLocator(Locator.java:253) > at > org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140) > at > org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87) > at > org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at >
[jira] [Updated] (GEODE-6376) PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED
[ https://issues.apache.org/jira/browse/GEODE-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6376: --- Labels: CI (was: ) > PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED > > > Key: GEODE-6376 > URL: https://issues.apache.org/jira/browse/GEODE-6376 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Assignee: Kirk Lund >Priority: Major > Labels: CI > > Failure Link > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/373 > Log Archives: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0412/test-results/distributedTest/1549403523/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0412/test-artifacts/1549403523/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0412.tgz > Stack Trace: > {code} > java.lang.RuntimeException: java.lang.IllegalStateException: Disk store > PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not > found > at > org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:194) > at > org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:180) > at > org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1325) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) >
[jira] [Updated] (GEODE-6644) CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > expectConnectionFailureWhenNoHostNameInServerKey FAILED
[ https://issues.apache.org/jira/browse/GEODE-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6644: --- Labels: CI (was: ) > CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > > expectConnectionFailureWhenNoHostNameInServerKey FAILED > - > > Key: GEODE-6644 > URL: https://issues.apache.org/jira/browse/GEODE-6644 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: CI > > This failure may be similar to GEODE-6008 (already closed) in that there may > be more Exceptions that need to be added to IgnoredExceptions (with JDK11). > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/610 > {noformat} > org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > > expectConnectionFailureWhenNoHostNameInServerKey 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 1832 > javax.net.ssl.SSLException: readHandshakeRecord > {noformat} > Full stack: > {noformat} > expectConnectionFailureWhenNoHostNameInServerKey > 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 1832 > javax.net.ssl.SSLException: readHandshakeRecord > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:380) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:192) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:148) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) > at
[jira] [Updated] (GEODE-6644) CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > expectConnectionFailureWhenNoHostNameInServerKey FAILED
[ https://issues.apache.org/jira/browse/GEODE-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6644: --- Affects Version/s: 1.10.0 > CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > > expectConnectionFailureWhenNoHostNameInServerKey FAILED > - > > Key: GEODE-6644 > URL: https://issues.apache.org/jira/browse/GEODE-6644 > Project: Geode > Issue Type: Bug > Components: client/server >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure may be similar to GEODE-6008 (already closed) in that there may > be more Exceptions that need to be added to IgnoredExceptions (with JDK11). > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/610 > {noformat} > org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > > expectConnectionFailureWhenNoHostNameInServerKey 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 1832 > javax.net.ssl.SSLException: readHandshakeRecord > {noformat} > Full stack: > {noformat} > expectConnectionFailureWhenNoHostNameInServerKey > 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 1832 > javax.net.ssl.SSLException: readHandshakeRecord > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:380) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:192) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:148) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:566) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at
[jira] [Created] (GEODE-6644) CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > expectConnectionFailureWhenNoHostNameInServerKey FAILED
Shelley Lynn Hughes-Godfrey created GEODE-6644: -- Summary: CI: org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > expectConnectionFailureWhenNoHostNameInServerKey FAILED Key: GEODE-6644 URL: https://issues.apache.org/jira/browse/GEODE-6644 Project: Geode Issue Type: Bug Components: client/server Reporter: Shelley Lynn Hughes-Godfrey This failure may be similar to GEODE-6008 (already closed) in that there may be more Exceptions that need to be added to IgnoredExceptions (with JDK11). https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/610 {noformat} org.apache.geode.cache.client.internal.CustomSSLProviderDistributedTest > expectConnectionFailureWhenNoHostNameInServerKey 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 1832 javax.net.ssl.SSLException: readHandshakeRecord {noformat} Full stack: {noformat} expectConnectionFailureWhenNoHostNameInServerKey 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 1832 javax.net.ssl.SSLException: readHandshakeRecord at org.junit.Assert.fail(Assert.java:88) at org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:380) at org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:192) at org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70) at org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:148) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at
[jira] [Commented] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
[ https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816452#comment-16816452 ] Shelley Lynn Hughes-Godfrey commented on GEODE-5816: This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/610 {noformat} org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest > testReplicatedRegionOnOneMember 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 648 [error 2019/04/11 23:42:07.139 UTC tid=34] Jmx manager could not be started because java.rmi.server.ExportException: Port already in use: 22507; nested exception is: java.net.BindException: Failed to create server socket on 7e89c2247c49/172.17.0.10[22507] org.apache.geode.management.ManagementException: java.rmi.server.ExportException: Port already in use: 22507; nested exception is: java.net.BindException: Failed to create server socket on 7e89c2247c49/172.17.0.10[22507] at org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133) at org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432) at org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181) at org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127) at org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2073) at org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:605) at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1200) at org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:219) at org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:675) at org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:661) at org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:345) at org.apache.geode.distributed.Locator.startLocator(Locator.java:252) at org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139) at org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:85) at org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:66) at org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:236) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) at jdk.internal.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at
[jira] [Commented] (GEODE-6376) PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED
[ https://issues.apache.org/jira/browse/GEODE-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816442#comment-16816442 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6376: This reproduced during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/613 {noformat} Task :geode-core:distributedTest org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest > testCrashDuringPreparePersistentId FAILED java.lang.RuntimeException: java.lang.IllegalStateException: Disk store PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not found at org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:194) at org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:180) at org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1314) Caused by: java.lang.IllegalStateException: Disk store PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not found {noformat} {noformat} java.lang.RuntimeException: java.lang.IllegalStateException: Disk store PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not found at org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:194) at org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:180) at org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1314) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:566) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at
[jira] [Commented] (GEODE-5231) CI Failure: PersistentRecoveryOrderDUnitTest.testRecoverAfterConflict fails in teardown
[ https://issues.apache.org/jira/browse/GEODE-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16816405#comment-16816405 ] Shelley Lynn Hughes-Godfrey commented on GEODE-5231: This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/611 {noformat} testRecoverAfterConflict java.io.FileNotFoundException: File does not exist: /home/geode/geode/geode-core/build/distributedTest729/diskDir-testRecoverAfterConflict/1/DRLK_IFPersistentRecoveryOrderDUnitTest_testRecoverAfterConflictRegion.lk at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2396) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1721) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1617) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2391) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1721) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1617) at org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.postTearDownCacheTestCase(PersistentReplicatedTestBase.java:66) at org.apache.geode.test.dunit.cache.internal.JUnit4CacheTestCase.preTearDown(JUnit4CacheTestCase.java:351) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:483) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[jira] [Commented] (GEODE-4240) DeprecatedCacheServerLauncherIntegrationTest fails sporadically with execution timeout
[ https://issues.apache.org/jira/browse/GEODE-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785903#comment-16785903 ] Shelley Lynn Hughes-Godfrey commented on GEODE-4240: Reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK8/builds/320 {noformat} > Task :geode-core:integrationTest org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest > testRebalance FAILED java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ status: running" after 12 ms. Output: Starting CacheServer with pid: 0 at org.junit.Assert.fail(Assert.java:88) at org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:240) at org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.execAndValidate(DeprecatedCacheServerLauncherIntegrationTest.java:438) at org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.testRebalance(DeprecatedCacheServerLauncherIntegrationTest.java:259) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0018/test-results/integrationTest/1551839157/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0018/test-artifacts/1551839157/windows-integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0018.tgz > DeprecatedCacheServerLauncherIntegrationTest fails sporadically with > execution timeout > -- > > Key: GEODE-4240 > URL: https://issues.apache.org/jira/browse/GEODE-4240 > Project: Geode > Issue Type: Bug >Reporter: Patrick Rhomberg >Assignee: Dan Smith >Priority: Major > > While possibly unrelated, it is worth noting other recent failures due to > startup timeouts. > ([GEODE-4236](https://issues.apache.org/jira/browse/GEODE-4236) comes to > mind.) > I have recently seen a failure in this test timing out with the following > stacktrace: > {noformat} > java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ > status: running" after 12 ms. Output: > Starting CacheServer with pid: 0 > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:222) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.execAndValidate(DeprecatedCacheServerLauncherIntegrationTest.java:437) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.testStartStatusStop(DeprecatedCacheServerLauncherIntegrationTest.java:164) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at
[jira] [Resolved] (GEODE-5749) DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer
[ https://issues.apache.org/jira/browse/GEODE-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5749. Resolution: Duplicate > DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer > > > Key: GEODE-5749 > URL: https://issues.apache.org/jira/browse/GEODE-5749 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Mark Hanson >Assignee: Dan Smith >Priority: Major > Labels: swat > Attachments: run.log > > > PR-Develop failed with this error in > https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/1078 > java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ > status: running" after 12 ms. Output: Starting CacheServer with pid: 0 at > org.junit.Assert.fail(Assert.java:88) at > org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:238) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.execAndValidate(DeprecatedCacheServerLauncherIntegrationTest.java:439) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer(DeprecatedCacheServerLauncherIntegrationTest.java:367) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at > org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at > org.junit.rules.RunRules.evaluate(RunRules.java:20) at > org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at > org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at > org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at > org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at > org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at >
[jira] [Commented] (GEODE-6390) CI Failure: gfsh command test failed due to BindException: Address already in use: NET_Bind
[ https://issues.apache.org/jira/browse/GEODE-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785891#comment-16785891 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6390: This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/316 {noformat} org.apache.geode.management.internal.cli.commands.ListClientCommandDUnitTest > classMethod 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 1103 [error 2019/03/06 01:56:34.406 GMT tid=64] Jmx manager could not be started because java.rmi.server.ExportException: Port already in use: 22501; nested exception is: java.net.BindException: Failed to create server socket on packer-5c7719d9-c670-0e8b-9962-211be4982c13/10.0.0.80[22501] org.apache.geode.management.ManagementException: java.rmi.server.ExportException: Port already in use: 22501; nested exception is: java.net.BindException: Failed to create server socket on packer-5c7719d9-c670-0e8b-9962-211be4982c13/10.0.0.80[22501] at org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133) at org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432) at org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181) at org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127) at org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2162) at org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:704) at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1182) at org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:181) at org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:147) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:138) at org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:672) at org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:659) at org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:343) at org.apache.geode.distributed.Locator.startLocator(Locator.java:252) at org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139) at org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:85) at org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:66) at org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:239) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) at
[jira] [Created] (GEODE-6489) CI Failures with testDistributedDeadlock
Shelley Lynn Hughes-Godfrey created GEODE-6489: -- Summary: CI Failures with testDistributedDeadlock Key: GEODE-6489 URL: https://issues.apache.org/jira/browse/GEODE-6489 Project: Geode Issue Type: Bug Components: gfsh Reporter: Shelley Lynn Hughes-Godfrey In an single CI run, we see 3 failures all related to testDistributedDeadlock: ``` org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED ``` https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469 ``` org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. 137 tests completed, 2 failed > Task :geode-web:distributedTest FAILED > Task :geode-core:distributedTest org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201) ``` =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6489) CI Failures with testDistributedDeadlock
[ https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6489: --- Description: In an single CI run, we see 3 failures all related to testDistributedDeadlock: {noformat} org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED {noformat} https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469 {noformat} org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. 137 tests completed, 2 failed > Task :geode-web:distributedTest FAILED > Task :geode-core:distributedTest org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz was: In an single CI run, we see 3 failures all related to testDistributedDeadlock: ``` org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED ``` https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469 ``` org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testDistributedDeadlockWithFunction FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > testNoDeadlock FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run in VM 1 running on Host ceb4d948b5be with 4 VMs Caused by: org.awaitility.core.ConditionTimeoutException: Condition with org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase was not fulfilled within 300 seconds. 137 tests completed, 2 failed > Task :geode-web:distributedTest FAILED > Task :geode-core:distributedTest org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > testDistributedDeadlockWithDLock FAILED java.lang.AssertionError at
[jira] [Updated] (GEODE-6489) CI Failures with testDistributedDeadlock
[ https://issues.apache.org/jira/browse/GEODE-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6489: --- Affects Version/s: 1.10.0 > CI Failures with testDistributedDeadlock > > > Key: GEODE-6489 > URL: https://issues.apache.org/jira/browse/GEODE-6489 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.10.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > In an single CI run, we see 3 failures all related to testDistributedDeadlock: > ``` > org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > > testDistributedDeadlockWithFunction FAILED > org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > > testNoDeadlock FAILED > org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > > testDistributedDeadlockWithDLock FAILED > ``` > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/469 > ``` > org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > > testDistributedDeadlockWithFunction FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run > in VM 1 running on Host ceb4d948b5be with 4 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase > was not fulfilled within 300 seconds. > org.apache.geode.management.internal.cli.commands.ShowDeadlockOverHttpDUnitTest > > testNoDeadlock FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase$$Lambda$68/829260532.run > in VM 1 running on Host ceb4d948b5be with 4 VMs > Caused by: > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.management.internal.cli.commands.ShowDeadlockDistributedTestBase > was not fulfilled within 300 seconds. > 137 tests completed, 2 failed > > Task :geode-web:distributedTest FAILED > > Task :geode-core:distributedTest > org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest > > testDistributedDeadlockWithDLock FAILED > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > org.apache.geode.distributed.internal.deadlock.GemFireDeadlockDetectorDUnitTest.testDistributedDeadlockWithDLock(GemFireDeadlockDetectorDUnitTest.java:201) > ``` > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-results/distributedTest/1551833386/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0019/test-artifacts/1551833386/distributedtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0019.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6390) CI Failure: gfsh command test failed due to BindException: Address already in use: NET_Bind
[ https://issues.apache.org/jira/browse/GEODE-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-6390: -- Assignee: Jens Deppe (was: Kenneth Howe) > CI Failure: gfsh command test failed due to BindException: Address already in > use: NET_Bind > --- > > Key: GEODE-6390 > URL: https://issues.apache.org/jira/browse/GEODE-6390 > Project: Geode > Issue Type: Bug > Components: management, tests >Reporter: Eric Shu >Assignee: Jens Deppe >Priority: Major > > at > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/268 > {noformat} > org.apache.geode.management.internal.cli.commands.DescribeClientCommandDUnitTest > > describeClient 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 1099 > [error 2019/02/11 19:14:46.795 GMT > tid=63] Jmx manager could not be started because > java.rmi.server.ExportException: Port already in use: 22500; nested exception > is: > java.net.BindException: Failed to create server socket on > packer-5c12143f-1186-eea0-0c8e-a47ad2ff3d14/10.0.0.109[22500] > org.apache.geode.management.ManagementException: > java.rmi.server.ExportException: Port already in use: 22500; nested exception > is: > java.net.BindException: Failed to create server socket on > packer-5c12143f-1186-eea0-0c8e-a47ad2ff3d14/10.0.0.109[22500] > at > org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133) > at > org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432) > at > org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173) > at > org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2117) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:670) > at > org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1234) > at > org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:803) > at > org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:789) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:218) > at > org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:672) > at > org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:659) > at > org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:343) > at org.apache.geode.distributed.Locator.startLocator(Locator.java:252) > at > org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139) > at > org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:85) > at > org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:66) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:208) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at >
[jira] [Commented] (GEODE-6390) CI Failure: gfsh command test failed due to BindException: Address already in use: NET_Bind
[ https://issues.apache.org/jira/browse/GEODE-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784891#comment-16784891 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6390: This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/466 =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0016/test-results/distributedTest/1551812301/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0016/test-artifacts/1551812301/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0016.tgz {noformat} org.apache.geode.distributed.LocatorDUnitTest > testStartTwoLocators FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host 4595ce47d3c3 with 6 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.distributed.LocatorDUnitTest.startVerifyAndStopLocator(LocatorDUnitTest.java:1800) at org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:317) Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.distributed.LocatorDUnitTest that uses int expected:<2> but was:<1> within 300 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) at org.apache.geode.distributed.LocatorDUnitTest.expectSystemToContainThisManyMembers(LocatorDUnitTest.java:140) at org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$2ba733bc$1(LocatorDUnitTest.java:1801) Caused by: java.lang.AssertionError: expected:<2> but was:<1> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.distributed.LocatorDUnitTest.lambda$expectSystemToContainThisManyMembers$0(LocatorDUnitTest.java:140) {noformat} > CI Failure: gfsh command test failed due to BindException: Address already in > use: NET_Bind > --- > > Key: GEODE-6390 > URL: https://issues.apache.org/jira/browse/GEODE-6390 > Project: Geode > Issue Type: Bug > Components: management, tests >Reporter: Eric Shu >Assignee: Kenneth Howe >Priority: Major > > at > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/268 > {noformat} > org.apache.geode.management.internal.cli.commands.DescribeClientCommandDUnitTest > > describeClient 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 1099 > [error 2019/02/11 19:14:46.795 GMT > tid=63] Jmx manager could not be started because > java.rmi.server.ExportException: Port already in use: 22500; nested exception > is: > java.net.BindException: Failed to create server socket on > packer-5c12143f-1186-eea0-0c8e-a47ad2ff3d14/10.0.0.109[22500] > org.apache.geode.management.ManagementException: > java.rmi.server.ExportException: Port already in use: 22500; nested exception > is: > java.net.BindException: Failed to create server socket on > packer-5c12143f-1186-eea0-0c8e-a47ad2ff3d14/10.0.0.109[22500] > at > org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133) > at > org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432) > at > org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173) > at >
[jira] [Commented] (GEODE-6421) CI failure: org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784845#comment-16784845 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6421: This failure (same test as the first occurrence) reproduced in CI (JDK11): https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/466 {noformat} org.apache.geode.distributed.LocatorDUnitTest > testStartTwoLocators FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host 4595ce47d3c3 with 6 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.distributed.LocatorDUnitTest.startVerifyAndStopLocator(LocatorDUnitTest.java:1800) at org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:317) Caused by: org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.distributed.LocatorDUnitTest that uses int expected:<2> but was:<1> within 300 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) at org.apache.geode.distributed.LocatorDUnitTest.expectSystemToContainThisManyMembers(LocatorDUnitTest.java:140) at org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$2ba733bc$1(LocatorDUnitTest.java:1801) Caused by: java.lang.AssertionError: expected:<2> but was:<1> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.distributed.LocatorDUnitTest.lambda$expectSystemToContainThisManyMembers$0(LocatorDUnitTest.java:140) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0016/test-results/distributedTest/1551812301/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0016/test-artifacts/1551812301/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0016.tgz > CI failure: > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed > with AssertionError > - > > Key: GEODE-6421 > URL: https://issues.apache.org/jira/browse/GEODE-6421 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Priority: Major > Fix For: 1.10.0 > > > org.apache.geode.distributed.LocatorDUnitTest > testStartTwoLocators FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host > f44e8e23cdaf with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at > org.apache.geode.distributed.LocatorDUnitTest.startVerifyAndStopLocator(LocatorDUnitTest.java:1799) > at > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:317) > Caused by: > java.lang.AssertionError: expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.distributed.LocatorDUnitTest.expectSystemToContainThisManyMembers(LocatorDUnitTest.java:139) > at > org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$2ba733bc$1(LocatorDUnitTest.java:1800) > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/405 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-6421) CI failure: org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reopened GEODE-6421: Assignee: Bruce Schuchardt > CI failure: > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators failed > with AssertionError > - > > Key: GEODE-6421 > URL: https://issues.apache.org/jira/browse/GEODE-6421 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.10.0 > > > org.apache.geode.distributed.LocatorDUnitTest > testStartTwoLocators FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.NamedRunnable.run in VM 2 running on Host > f44e8e23cdaf with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at > org.apache.geode.distributed.LocatorDUnitTest.startVerifyAndStopLocator(LocatorDUnitTest.java:1799) > at > org.apache.geode.distributed.LocatorDUnitTest.testStartTwoLocators(LocatorDUnitTest.java:317) > Caused by: > java.lang.AssertionError: expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.distributed.LocatorDUnitTest.expectSystemToContainThisManyMembers(LocatorDUnitTest.java:139) > at > org.apache.geode.distributed.LocatorDUnitTest.lambda$startVerifyAndStopLocator$2ba733bc$1(LocatorDUnitTest.java:1800) > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/405 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6419) CI Failure: ClusterConfigurationDUnitTest.testStartServerAndExecuteCommands fails with BindException
[ https://issues.apache.org/jira/browse/GEODE-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784768#comment-16784768 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6419: This failure reproduced during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsGfshDistributedTestOpenJDK11/builds/311 {noformat} > Task :geode-web:distributedTest org.apache.geode.management.internal.cli.commands.ClusterConfigurationDUnitTest > testStartServerAndExecuteCommands[0] 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 1141 [error 2019/03/04 21:54:39.593 GMT tid=63] Jmx manager could not be started because HTTP service failed to start org.apache.geode.management.ManagementException: HTTP service failed to start at org.apache.geode.management.internal.ManagementAgent.loadWebApplications(ManagementAgent.java:240) at org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:127) at org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432) at org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181) at org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127) at org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2138) at org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:680) at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1241) at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:809) at org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:795) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:218) at org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:672) at org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:659) at org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:343) at org.apache.geode.distributed.Locator.startLocator(Locator.java:252) at org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:139) at org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:85) at org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:66) at org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:239) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) at java.base/java.security.AccessController.doPrivileged(Native Method) at
[jira] [Updated] (GEODE-6352) CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones
[ https://issues.apache.org/jira/browse/GEODE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6352: --- Affects Version/s: 1.4.0 > CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones > > > Key: GEODE-6352 > URL: https://issues.apache.org/jira/browse/GEODE-6352 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.4.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/23 > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.3/distributedTest/1548995701/index.html > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > To download the test artifacts from this job, execute the following command > after the job has completed: > aws s3 cp > s3://gemfire-build-artifacts/9.3/9.3.3-build.6/1548995701/distributedtestfiles-9.3.3-build.6.tgz > . > {noformat} > Test failure: > {noformat} > org.apache.geode.cache30.GlobalRegionCCEDUnitTest > testTombstones FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache30.MultiVMRegionTestCase$277.run in VM 1 running on > Host 01e2b31fd72b with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at org.apache.geode.test.dunit.VM.invoke(VM.java:363) > at org.apache.geode.test.dunit.VM.invoke(VM.java:308) > at > org.apache.geode.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8494) > at > org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones(GlobalRegionCCEDUnitTest.java:155) > Caused by: > java.lang.AssertionError: after destroys in other vm region > tombstone count was 0 expected=100 TombstoneService=Destroyed entries GC > service. Replicate Queue=[0] [] batchedExpiredTombstones[0] = [] > Non-replicate Queue=[0] [] expected:<100> but was:<0> > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6352) CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones
[ https://issues.apache.org/jira/browse/GEODE-6352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6352: --- Description: http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/23 {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.3/distributedTest/1548995701/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To download the test artifacts from this job, execute the following command after the job has completed: aws s3 cp s3://gemfire-build-artifacts/9.3/9.3.3-build.6/1548995701/distributedtestfiles-9.3.3-build.6.tgz . {noformat} Test failure: {noformat} org.apache.geode.cache30.GlobalRegionCCEDUnitTest > testTombstones FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache30.MultiVMRegionTestCase$277.run in VM 1 running on Host 01e2b31fd72b with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.test.dunit.VM.invoke(VM.java:363) at org.apache.geode.test.dunit.VM.invoke(VM.java:308) at org.apache.geode.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8494) at org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones(GlobalRegionCCEDUnitTest.java:155) Caused by: java.lang.AssertionError: after destroys in other vm region tombstone count was 0 expected=100 TombstoneService=Destroyed entries GC service. Replicate Queue=[0] [] batchedExpiredTombstones[0] = [] Non-replicate Queue=[0] [] expected:<100> but was:<0> {noformat} was: http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/23 ``` =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.3/distributedTest/1548995701/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To download the test artifacts from this job, execute the following command after the job has completed: aws s3 cp s3://gemfire-build-artifacts/9.3/9.3.3-build.6/1548995701/distributedtestfiles-9.3.3-build.6.tgz . ``` Test failure: ``` org.apache.geode.cache30.GlobalRegionCCEDUnitTest > testTombstones FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache30.MultiVMRegionTestCase$277.run in VM 1 running on Host 01e2b31fd72b with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.test.dunit.VM.invoke(VM.java:363) at org.apache.geode.test.dunit.VM.invoke(VM.java:308) at org.apache.geode.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8494) at org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones(GlobalRegionCCEDUnitTest.java:155) Caused by: java.lang.AssertionError: after destroys in other vm region tombstone count was 0 expected=100 TombstoneService=Destroyed entries GC service. Replicate Queue=[0] [] batchedExpiredTombstones[0] = [] Non-replicate Queue=[0] [] expected:<100> but was:<0> ``` > CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones > > > Key: GEODE-6352 > URL: https://issues.apache.org/jira/browse/GEODE-6352 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/23 > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.3/distributedTest/1548995701/index.html > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > To download the test artifacts from this job, execute the following command > after the job has completed: > aws s3 cp > s3://gemfire-build-artifacts/9.3/9.3.3-build.6/1548995701/distributedtestfiles-9.3.3-build.6.tgz > . > {noformat} > Test failure: > {noformat} > org.apache.geode.cache30.GlobalRegionCCEDUnitTest > testTombstones FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache30.MultiVMRegionTestCase$277.run in VM 1 running on > Host 01e2b31fd72b with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:393) > at org.apache.geode.test.dunit.VM.invoke(VM.java:363) > at org.apache.geode.test.dunit.VM.invoke(VM.java:308) > at >
[jira] [Created] (GEODE-6352) CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones
Shelley Lynn Hughes-Godfrey created GEODE-6352: -- Summary: CI Failure: org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones Key: GEODE-6352 URL: https://issues.apache.org/jira/browse/GEODE-6352 Project: Geode Issue Type: Bug Components: regions Reporter: Shelley Lynn Hughes-Godfrey http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/23 ``` =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.3/distributedTest/1548995701/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To download the test artifacts from this job, execute the following command after the job has completed: aws s3 cp s3://gemfire-build-artifacts/9.3/9.3.3-build.6/1548995701/distributedtestfiles-9.3.3-build.6.tgz . ``` Test failure: ``` org.apache.geode.cache30.GlobalRegionCCEDUnitTest > testTombstones FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache30.MultiVMRegionTestCase$277.run in VM 1 running on Host 01e2b31fd72b with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:393) at org.apache.geode.test.dunit.VM.invoke(VM.java:363) at org.apache.geode.test.dunit.VM.invoke(VM.java:308) at org.apache.geode.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8494) at org.apache.geode.cache30.GlobalRegionCCEDUnitTest.testTombstones(GlobalRegionCCEDUnitTest.java:155) Caused by: java.lang.AssertionError: after destroys in other vm region tombstone count was 0 expected=100 TombstoneService=Destroyed entries GC service. Replicate Queue=[0] [] batchedExpiredTombstones[0] = [] Non-replicate Queue=[0] [] expected:<100> but was:<0> ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6344) should revert GEODE-1183 before a better fix
[ https://issues.apache.org/jira/browse/GEODE-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6344: --- Description: GEODE-1183 was introduced for a scenario that there're 2 cache-servers at the same jvm, the client will try to create 2 proxy to the server, but since it's the same proxy id, it would end up close/recreate forever. GEODE-1183 will reject an incoming create-proxy request if the server found there's an existing proxy with the same id and its socket is still connected. However, this fix caused some side effects. For example, if the client read time out, it requested the server to recreate the proxy, the server will reject this request and the client will never reconnect. This is due to that at the server side, it cannot determine it's a reconnect request or the same client requests to connect to the 2nd cache-server on the same jvm. There's a proposal to introduce a parameter at the client to fix it. However, before this new re-fix, we decided to revert the original GEODE-1183 to avoid its side-effect. was: GEODE-1183 was introduced for a scenario that there're 2 cache-servers at the same jvm, the client will try to create 2 proxy to the server, but since it's the same proxy id, it would end up close/recreate forever. GEODE-1183 will reject an incoming create-proxy request if the server found there's an existing proxy with the same id and its socket is still connected. However, this fix caused some side effects. For example, if the client read time out, it requested the server to recreate the proxy, the server will reject this request and the client will never reconnect. This is due to that at the server side, it cannot determine it's a reconnect request or the same client requests to connect to the 2nd cache-server on the same jvm. There's a proposal to introduce a parameter at the client to fix it. However, before this new re-fix, we decided to revert the original GEODE-1183 to avoid its side-effect. This will be applied to geode 1.9.0, then cherrypick to 1.8, 1.7, 1.6, and 1.4. > should revert GEODE-1183 before a better fix > > > Key: GEODE-6344 > URL: https://issues.apache.org/jira/browse/GEODE-6344 > Project: Geode > Issue Type: Bug >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > GEODE-1183 was introduced for a scenario that there're 2 cache-servers at the > same jvm, the client will try to create 2 proxy to the server, but since it's > the same proxy id, it would end up close/recreate forever. > GEODE-1183 will reject an incoming create-proxy request if the server found > there's an existing proxy with the same id and its socket is still connected. > However, this fix caused some side effects. For example, if the client read > time out, it requested the server to recreate the proxy, the server will > reject this request and the client will never reconnect. > This is due to that at the server side, it cannot determine it's a reconnect > request or the same client requests to connect to the 2nd cache-server on the > same jvm. > There's a proposal to introduce a parameter at the client to fix it. However, > before this new re-fix, we decided to revert the original GEODE-1183 to avoid > its side-effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6344) should revert GEODE-1183 before a better fix
[ https://issues.apache.org/jira/browse/GEODE-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6344: --- Fix Version/s: (was: 1.8.0) (was: 1.7.0) (was: 1.6.0) (was: 1.4.0) > should revert GEODE-1183 before a better fix > > > Key: GEODE-6344 > URL: https://issues.apache.org/jira/browse/GEODE-6344 > Project: Geode > Issue Type: Bug >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > GEODE-1183 was introduced for a scenario that there're 2 cache-servers at the > same jvm, the client will try to create 2 proxy to the server, but since it's > the same proxy id, it would end up close/recreate forever. > GEODE-1183 will reject an incoming create-proxy request if the server found > there's an existing proxy with the same id and its socket is still connected. > However, this fix caused some side effects. For example, if the client read > time out, it requested the server to recreate the proxy, the server will > reject this request and the client will never reconnect. > This is due to that at the server side, it cannot determine it's a reconnect > request or the same client requests to connect to the 2nd cache-server on the > same jvm. > There's a proposal to introduce a parameter at the client to fix it. However, > before this new re-fix, we decided to revert the original GEODE-1183 to avoid > its side-effect. > This will be applied to geode 1.9.0, then cherrypick to 1.8, 1.7, 1.6, and > 1.4. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4089) Lucene create index can fail due to comparison of indexedFields as an array (if order of indexes is different)
[ https://issues.apache.org/jira/browse/GEODE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-4089: -- Assignee: (was: Shelley Lynn Hughes-Godfrey) > Lucene create index can fail due to comparison of indexedFields as an array > (if order of indexes is different) > -- > > Key: GEODE-4089 > URL: https://issues.apache.org/jira/browse/GEODE-4089 > Project: Geode > Issue Type: Bug > Components: lucene >Affects Versions: 1.4.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This issue was fixed in geode 1.4 (GEODE-3953: Incorrect use of .equals() for > comparison of fieldname arrays), but given that this issue exists in earlier > versions, re-initialization of members creating lucene indexes can fail when > upgrading from 1.2 and 1.3 to 1.4 when there is a mix of old and new version > members in the Distributed System. > {noformat} > Cannot create Lucene index index on region /region with fields [field2, > field1] because another member defines the same index with fields [field1, > field2]. > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.cache.lucene.internal.LuceneIndexCreationProfileJUnitTest.testCheckCompatibility(LuceneIndexCreationProfileJUnitTest.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > junitparams.internal.InvokeParameterisedMethod.evaluate(InvokeParameterisedMethod.java:234) > at > junitparams.internal.ParameterisedTestMethodRunner.runMethodInvoker(ParameterisedTestMethodRunner.java:47) > at > junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40) > at > junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:146) > at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:417) > at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:386) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:51) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6278) CI failure: org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. testRangeIndex
[ https://issues.apache.org/jira/browse/GEODE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-6278. Resolution: Duplicate Fix Version/s: 1.7.0 > CI failure: > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. > testRangeIndex > -- > > Key: GEODE-6278 > URL: https://issues.apache.org/jira/browse/GEODE-6278 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.4.0 >Reporter: Aditya Anchuri >Priority: Major > Fix For: 1.7.0 > > > {code:java} > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest > > testRangeIndex FAILED > > java.lang.AssertionError: Thread did not terminate after 200 ms: Thread[run > invoked on an instance of > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest$6,5,] > > at org.junit.Assert.fail(Assert.java:88) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:147) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:110) > > at > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndex(QueryDataInconsistencyDUnitTest.java:304){code} > Seems like a flakey test. > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/18 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6278) CI failure: org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. testRangeIndex
[ https://issues.apache.org/jira/browse/GEODE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745290#comment-16745290 ] Shelley Lynn Hughes-Godfrey commented on GEODE-6278: Closing as a duplicate of GEODE-925 (fixed in 1.7). > CI failure: > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. > testRangeIndex > -- > > Key: GEODE-6278 > URL: https://issues.apache.org/jira/browse/GEODE-6278 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.4.0 >Reporter: Aditya Anchuri >Priority: Major > > {code:java} > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest > > testRangeIndex FAILED > > java.lang.AssertionError: Thread did not terminate after 200 ms: Thread[run > invoked on an instance of > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest$6,5,] > > at org.junit.Assert.fail(Assert.java:88) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:147) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:110) > > at > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndex(QueryDataInconsistencyDUnitTest.java:304){code} > Seems like a flakey test. > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/18 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6278) CI failure: org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. testRangeIndex
[ https://issues.apache.org/jira/browse/GEODE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6278: --- Affects Version/s: 1.4.0 > CI failure: > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest. > testRangeIndex > -- > > Key: GEODE-6278 > URL: https://issues.apache.org/jira/browse/GEODE-6278 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.4.0 >Reporter: Aditya Anchuri >Priority: Major > > {code:java} > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest > > testRangeIndex FAILED > > java.lang.AssertionError: Thread did not terminate after 200 ms: Thread[run > invoked on an instance of > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest$6,5,] > > at org.junit.Assert.fail(Assert.java:88) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:147) > > at org.apache.geode.test.dunit.ThreadUtils.join(ThreadUtils.java:110) > > at > org.apache.geode.cache.query.dunit.QueryDataInconsistencyDUnitTest.testRangeIndex(QueryDataInconsistencyDUnitTest.java:304){code} > Seems like a flakey test. > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.3/jobs/DistributedTest/builds/18 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6248) Misspelling in warning ""PartitionedRegion#cleanupFailedInitialization: Failed to clean the PartionRegion allPartitionedRegions"
[ https://issues.apache.org/jira/browse/GEODE-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6248: --- Affects Version/s: 1.9.0 > Misspelling in warning ""PartitionedRegion#cleanupFailedInitialization: > Failed to clean the PartionRegion allPartitionedRegions" > > > Key: GEODE-6248 > URL: https://issues.apache.org/jira/browse/GEODE-6248 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.9.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This warning occurs 3 times in a single method (all misspelled): > geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegion.java > {noformat} > 5463 public void cleanupFailedInitialization() { > 5464 super.cleanupFailedInitialization(); > 5465 // Fix for 44551 - make sure persistent buckets > 5466 // are done recoverying from disk before sending the > 5467 // destroy region message. > 5468 this.redundancyProvider.waitForPersistentBucketRecovery(); > 5469 this.cache.removePartitionedRegion(this); > 5470 > this.cache.getInternalResourceManager(false).removeResourceListener(this); > 5471 this.redundancyProvider.shutdown(); // see bug 41094 > 5472 int serials[] = getRegionAdvisor().getBucketSerials(); > 5473 RegionEventImpl event = new RegionEventImpl(this, > Operation.REGION_CLOSE, null, false, > 5474 getMyId(), generateEventID()/* generate EventID */); > 5475 try { > 5476 sendDestroyRegionMessage(event, serials); > 5477 } catch (Exception ex) { > 5478 logger.warn( > 5479 "PartitionedRegion#cleanupFailedInitialization(): Failed to > clean the PartionRegion data store", > 5480 ex); > 5481 } > 5482 if (null != this.dataStore) { > 5483 try { > 5484 this.dataStore.cleanUp(true, false); > 5485 } catch (Exception ex) { > 5486 logger.warn( > 5487 "PartitionedRegion#cleanupFailedInitialization(): Failed to > clean the PartionRegion data store", > 5488 ex); > 5489 } > 5490 } > 5491 > 5492 if (this.cleanPRRegistration) { > 5493 try { > 5494 synchronized (prIdToPR) { > 5495 if (prIdToPR.containsKey(this.partitionedRegionId)) { > 5496 prIdToPR.put(this.partitionedRegionId, > PRIdMap.FAILED_REGISTRATION, false); > 5497 if (logger.isDebugEnabled()) { > 5498 logger.debug("cleanupFailedInitialization: set failed for > prId={} named {}", > 5499 this.partitionedRegionId, this.getName()); > 5500 } > 5501 } > 5502 } > 5503 > 5504 > PartitionedRegionHelper.removeGlobalMetadataForFailedNode(this.node, > 5505 this.getRegionIdentifier(), getGemFireCache(), true); > 5506 } catch (Exception ex) { > 5507 logger.warn( > 5508 "PartitionedRegion#cleanupFailedInitialization: Failed to > clean the PartionRegion allPartitionedRegions", > 5509 ex); > 5510 } > 5511 } > 5512 this.distAdvisor.close(); > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6248) Misspelling in warning ""PartitionedRegion#cleanupFailedInitialization: Failed to clean the PartionRegion allPartitionedRegions"
Shelley Lynn Hughes-Godfrey created GEODE-6248: -- Summary: Misspelling in warning ""PartitionedRegion#cleanupFailedInitialization: Failed to clean the PartionRegion allPartitionedRegions" Key: GEODE-6248 URL: https://issues.apache.org/jira/browse/GEODE-6248 Project: Geode Issue Type: Bug Components: regions Reporter: Shelley Lynn Hughes-Godfrey This warning occurs 3 times in a single method (all misspelled): geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegion.java {noformat} 5463 public void cleanupFailedInitialization() { 5464 super.cleanupFailedInitialization(); 5465 // Fix for 44551 - make sure persistent buckets 5466 // are done recoverying from disk before sending the 5467 // destroy region message. 5468 this.redundancyProvider.waitForPersistentBucketRecovery(); 5469 this.cache.removePartitionedRegion(this); 5470 this.cache.getInternalResourceManager(false).removeResourceListener(this); 5471 this.redundancyProvider.shutdown(); // see bug 41094 5472 int serials[] = getRegionAdvisor().getBucketSerials(); 5473 RegionEventImpl event = new RegionEventImpl(this, Operation.REGION_CLOSE, null, false, 5474 getMyId(), generateEventID()/* generate EventID */); 5475 try { 5476 sendDestroyRegionMessage(event, serials); 5477 } catch (Exception ex) { 5478 logger.warn( 5479 "PartitionedRegion#cleanupFailedInitialization(): Failed to clean the PartionRegion data store", 5480 ex); 5481 } 5482 if (null != this.dataStore) { 5483 try { 5484 this.dataStore.cleanUp(true, false); 5485 } catch (Exception ex) { 5486 logger.warn( 5487 "PartitionedRegion#cleanupFailedInitialization(): Failed to clean the PartionRegion data store", 5488 ex); 5489 } 5490 } 5491 5492 if (this.cleanPRRegistration) { 5493 try { 5494 synchronized (prIdToPR) { 5495 if (prIdToPR.containsKey(this.partitionedRegionId)) { 5496 prIdToPR.put(this.partitionedRegionId, PRIdMap.FAILED_REGISTRATION, false); 5497 if (logger.isDebugEnabled()) { 5498 logger.debug("cleanupFailedInitialization: set failed for prId={} named {}", 5499 this.partitionedRegionId, this.getName()); 5500 } 5501 } 5502 } 5503 5504 PartitionedRegionHelper.removeGlobalMetadataForFailedNode(this.node, 5505 this.getRegionIdentifier(), getGemFireCache(), true); 5506 } catch (Exception ex) { 5507 logger.warn( 5508 "PartitionedRegion#cleanupFailedInitialization: Failed to clean the PartionRegion allPartitionedRegions", 5509 ex); 5510 } 5511 } 5512 this.distAdvisor.close(); {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles and aboveZeroDeletesPreviousFiles_nameWithHyphen
[ https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720429#comment-16720429 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-3205 at 12/13/18 10:04 PM: --- Reopening as this failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/232 {noformat} org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest > aboveZeroDeletesPreviousFiles_nameWithHyphen FAILED java.lang.AssertionError: Expecting file: to exist. at org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles_nameWithHyphen(DiskSpaceLimitIntegrationTest.java:255) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.275/test-results/integrationTest/1544663063/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.275/test-artifacts/1544663063/integrationtestfiles-OpenJDK8-1.9.0-build.275.tgz See also: GEODE-2790, GEODE-2786 (both closed as duplicates of one another) >From stdout: {noformat} [warn 2018/12/13 00:57:45.682 UTC tid=0x19] Use of java.lang.System.nanoTime() resulted in a non-positive timestamp delta. Skipping archival of statistics sample. java.lang.IllegalArgumentException: Sample timestamp must be greater than previous timestamp (millisTimeStamp is 420894, previousMillis is 420894 and delta is 0). at org.apache.geode.internal.statistics.StatArchiveWriter.calcDelta(StatArchiveWriter.java:412) at org.apache.geode.internal.statistics.StatArchiveWriter.writeTimeStamp(StatArchiveWriter.java:422) at org.apache.geode.internal.statistics.StatArchiveWriter.sampled(StatArchiveWriter.java:501) at org.apache.geode.internal.statistics.StatArchiveHandler.sampled(StatArchiveHandler.java:137) at org.apache.geode.internal.statistics.SampleCollector$MarkableSampleHandler.sampled(SampleCollector.java:627) at org.apache.geode.internal.statistics.SampleCollector.notifyAllHandlersOfSample(SampleCollector.java:484) at org.apache.geode.internal.statistics.SampleCollector.sample(SampleCollector.java:252) at org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.sample(DiskSpaceLimitIntegrationTest.java:337) at org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.sampleUntilFileExists(DiskSpaceLimitIntegrationTest.java:298) at org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.zeroKeepsAllFiles(DiskSpaceLimitIntegrationTest.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
[jira] [Resolved] (GEODE-6200) CI: netstat --with-lsof fails with OOME (when netstat command not found)
[ https://issues.apache.org/jira/browse/GEODE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-6200. Resolution: Invalid > CI: netstat --with-lsof fails with OOME (when netstat command not found) > > > Key: GEODE-6200 > URL: https://issues.apache.org/jira/browse/GEODE-6200 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This test fails in CI: > http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.5/jobs/DistributedTest/builds/62 > org.apache.geode.management.internal.cli.NetstatDUnitTest > > testOutputToConsoleWithLsofForOneMember FAILED > {noformat} > java.lang.OutOfMemoryError: Java heap space > Dumping heap to java_pid1.hprof ... > org.apache.geode.management.internal.cli.NetstatDUnitTest > > testOutputToConsoleWithLsofForOneMember FAILED > java.lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:3332) > at > java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124) > at > java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:649) > at java.lang.StringBuilder.append(StringBuilder.java:202) > at org.json.JSONStringer.string(JSONStringer.java:369) > at org.json.JSONStringer.value(JSONStringer.java:262) > at org.json.JSONArray.writeTo(JSONArray.java:732) > at org.json.JSONStringer.value(JSONStringer.java:231) > at org.json.JSONObject.writeTo(JSONObject.java:882) > at org.json.JSONStringer.value(JSONStringer.java:235) > at org.json.JSONObject.writeTo(JSONObject.java:882) > at org.json.JSONObject.toString(JSONObject.java:849) > at > org.apache.geode.management.internal.cli.json.GfJsonObject.toString(GfJsonObject.java:301) > at java.lang.String.valueOf(String.java:2994) > at java.lang.StringBuilder.append(StringBuilder.java:131) > at > org.apache.geode.management.internal.cli.result.CommandResult.toString(CommandResult.java:508) > at > org.apache.geode.management.internal.cli.NetstatDUnitTest.testOutputToConsoleWithLsofForOneMember(NetstatDUnitTest.java:104) > {noformat} > =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.5/distributedTest/1544666867/index.html > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > To download the test artifacts from this job, execute the following command > after the job has completed: > aws s3 cp > s3://gemfire-build-artifacts/9.5/9.5.3-build.2/1544666867/distributedtestfiles-9.5.3-build.2.tgz > . > This failure initially looks like GEODE-2488 ... which was fixed in March > 2018. GEODE-2488 marked the --with-lsof tests as @Ignore (tagged with this > bug). Later, the commit below added the following test > (testOutputToConsoleWithLsofForOneMember) ... so once again we are doing a > netstat --with-lsof which is producing a huge amount of output ... all read > into a single buffer for parsing which leads us to declare OOME. I don't > think this output is from a successful execution of the netstat command > though -- the test output shows the netstat command is not found (see below). > {noformat} > commit d2b263f9053f293a409c527d9c8b5ae17b745041 > Author: Jens Deppe > Date: Fri Jun 22 15:33:20 2018 -0700 > GEODE-5335: Do not resolve addresses when calling netstat and lsof (#2070) > - This avoids long command pauses (or failures) if DNS is slow or > misconfigured. > - Add more netstat tests > > (cherry picked from commit 908a5efe59c4a81be647bb82ba58a4ccba98e1ac) > {noformat} > {noformat} > + public void testOutputToConsoleWithLsofForOneMember() throws Exception { > +CommandResult result = gfsh.executeCommand("netstat --member=server-1 > --with-lsof"); > +assertThat(result.getStatus()).isEqualTo(Result.Status.OK); > + > +String rawOutput = result.getMessageFromContent(); > +String[] lines = rawOutput.split("\n"); > + > +assertThat(lines.length).isGreaterThan(5); > + > assertThat(lines[4].trim().split("[,\\s]+")).containsExactlyInAnyOrder("server-1"); > +assertThat(lines).filteredOn(e -> e.contains("## lsof output > ##")).hasSize(1); > + } > {noformat} > Interestingly, it looks like netstat fails here (from test output): > {noformat} > Command result for : > ## > Host: ebc7313d51a3 > OS: Linux 4.15.0-38-generic amd64 > Member(s): > server-1 > ## > Could not execute "netstat". Reason: Cannot
[jira] [Updated] (GEODE-6200) CI: netstat --with-lsof fails with OOME (when netstat command not found)
[ https://issues.apache.org/jira/browse/GEODE-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-6200: --- Description: This test fails in CI: http://concourse.gemfire.pivotal.io/teams/main/pipelines/gemfire-9.5/jobs/DistributedTest/builds/62 org.apache.geode.management.internal.cli.NetstatDUnitTest > testOutputToConsoleWithLsofForOneMember FAILED {noformat} java.lang.OutOfMemoryError: Java heap space Dumping heap to java_pid1.hprof ... org.apache.geode.management.internal.cli.NetstatDUnitTest > testOutputToConsoleWithLsofForOneMember FAILED java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:649) at java.lang.StringBuilder.append(StringBuilder.java:202) at org.json.JSONStringer.string(JSONStringer.java:369) at org.json.JSONStringer.value(JSONStringer.java:262) at org.json.JSONArray.writeTo(JSONArray.java:732) at org.json.JSONStringer.value(JSONStringer.java:231) at org.json.JSONObject.writeTo(JSONObject.java:882) at org.json.JSONStringer.value(JSONStringer.java:235) at org.json.JSONObject.writeTo(JSONObject.java:882) at org.json.JSONObject.toString(JSONObject.java:849) at org.apache.geode.management.internal.cli.json.GfJsonObject.toString(GfJsonObject.java:301) at java.lang.String.valueOf(String.java:2994) at java.lang.StringBuilder.append(StringBuilder.java:131) at org.apache.geode.management.internal.cli.result.CommandResult.toString(CommandResult.java:508) at org.apache.geode.management.internal.cli.NetstatDUnitTest.testOutputToConsoleWithLsofForOneMember(NetstatDUnitTest.java:104) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.5/distributedTest/1544666867/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To download the test artifacts from this job, execute the following command after the job has completed: aws s3 cp s3://gemfire-build-artifacts/9.5/9.5.3-build.2/1544666867/distributedtestfiles-9.5.3-build.2.tgz . This failure initially looks like GEODE-2488 ... which was fixed in March 2018. GEODE-2488 marked the --with-lsof tests as @Ignore (tagged with this bug). Later, the commit below added the following test (testOutputToConsoleWithLsofForOneMember) ... so once again we are doing a netstat --with-lsof which is producing a huge amount of output ... all read into a single buffer for parsing which leads us to declare OOME. I don't think this output is from a successful execution of the netstat command though -- the test output shows the netstat command is not found (see below). {noformat} commit d2b263f9053f293a409c527d9c8b5ae17b745041 Author: Jens Deppe Date: Fri Jun 22 15:33:20 2018 -0700 GEODE-5335: Do not resolve addresses when calling netstat and lsof (#2070) - This avoids long command pauses (or failures) if DNS is slow or misconfigured. - Add more netstat tests (cherry picked from commit 908a5efe59c4a81be647bb82ba58a4ccba98e1ac) {noformat} {noformat} + public void testOutputToConsoleWithLsofForOneMember() throws Exception { +CommandResult result = gfsh.executeCommand("netstat --member=server-1 --with-lsof"); +assertThat(result.getStatus()).isEqualTo(Result.Status.OK); + +String rawOutput = result.getMessageFromContent(); +String[] lines = rawOutput.split("\n"); + +assertThat(lines.length).isGreaterThan(5); + assertThat(lines[4].trim().split("[,\\s]+")).containsExactlyInAnyOrder("server-1"); +assertThat(lines).filteredOn(e -> e.contains("## lsof output ##")).hasSize(1); + } {noformat} Interestingly, it looks like netstat fails here (from test output): {noformat} Command result for : ## Host: ebc7313d51a3 OS: Linux 4.15.0-38-generic amd64 Member(s): server-1 ## Could not execute "netstat". Reason: Cannot run program "netstat": error=2, No such file or directory {noformat} The output seems to be a huge listing ... starting with this: {noformat} lsof output ### COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 1 root cwd DIR 0,59 44 280305 /tmp/build/ae3c03f4/built-gemfire/test/geode/geode-core/build/distributedTest1562 java 1 root rtd DIR 0,102 80 234603 / java 1 root txt REG 0,102 8464 161745
[jira] [Created] (GEODE-6200) CI: netstat --with-lsof fails with OOME (when netstat command not found)
Shelley Lynn Hughes-Godfrey created GEODE-6200: -- Summary: CI: netstat --with-lsof fails with OOME (when netstat command not found) Key: GEODE-6200 URL: https://issues.apache.org/jira/browse/GEODE-6200 Project: Geode Issue Type: Bug Components: gfsh Reporter: Shelley Lynn Hughes-Godfrey org.apache.geode.management.internal.cli.NetstatDUnitTest > testOutputToConsoleWithLsofForOneMember FAILED {noformat} java.lang.OutOfMemoryError: Java heap space Dumping heap to java_pid1.hprof ... org.apache.geode.management.internal.cli.NetstatDUnitTest > testOutputToConsoleWithLsofForOneMember FAILED java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:3332) at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124) at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:649) at java.lang.StringBuilder.append(StringBuilder.java:202) at org.json.JSONStringer.string(JSONStringer.java:369) at org.json.JSONStringer.value(JSONStringer.java:262) at org.json.JSONArray.writeTo(JSONArray.java:732) at org.json.JSONStringer.value(JSONStringer.java:231) at org.json.JSONObject.writeTo(JSONObject.java:882) at org.json.JSONStringer.value(JSONStringer.java:235) at org.json.JSONObject.writeTo(JSONObject.java:882) at org.json.JSONObject.toString(JSONObject.java:849) at org.apache.geode.management.internal.cli.json.GfJsonObject.toString(GfJsonObject.java:301) at java.lang.String.valueOf(String.java:2994) at java.lang.StringBuilder.append(StringBuilder.java:131) at org.apache.geode.management.internal.cli.result.CommandResult.toString(CommandResult.java:508) at org.apache.geode.management.internal.cli.NetstatDUnitTest.testOutputToConsoleWithLsofForOneMember(NetstatDUnitTest.java:104) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results Website =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://s3proxy.gemfire.pivotal.io/gemfire-test-results/9.5/distributedTest/1544666867/index.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To download the test artifacts from this job, execute the following command after the job has completed: aws s3 cp s3://gemfire-build-artifacts/9.5/9.5.3-build.2/1544666867/distributedtestfiles-9.5.3-build.2.tgz . This failure initially looks like GEODE-2488 ... which was fixed in March 2018. GEODE-2488 marked the --with-lsof tests as @Ignore (tagged with this bug). Later, the commit below added the following test (testOutputToConsoleWithLsofForOneMember) ... so once again we are doing a netstat --with-lsof which is producing a huge amount of output ... all read into a single buffer for parsing which leads us to declare OOME. I don't think this output is from a successful execution of the netstat command though -- the test output shows the netstat command is not found (see below). {noformat} commit d2b263f9053f293a409c527d9c8b5ae17b745041 Author: Jens Deppe Date: Fri Jun 22 15:33:20 2018 -0700 GEODE-5335: Do not resolve addresses when calling netstat and lsof (#2070) - This avoids long command pauses (or failures) if DNS is slow or misconfigured. - Add more netstat tests (cherry picked from commit 908a5efe59c4a81be647bb82ba58a4ccba98e1ac) {noformat} {noformat} + public void testOutputToConsoleWithLsofForOneMember() throws Exception { +CommandResult result = gfsh.executeCommand("netstat --member=server-1 --with-lsof"); +assertThat(result.getStatus()).isEqualTo(Result.Status.OK); + +String rawOutput = result.getMessageFromContent(); +String[] lines = rawOutput.split("\n"); + +assertThat(lines.length).isGreaterThan(5); + assertThat(lines[4].trim().split("[,\\s]+")).containsExactlyInAnyOrder("server-1"); +assertThat(lines).filteredOn(e -> e.contains("## lsof output ##")).hasSize(1); + } {noformat} Interestingly, it looks like netstat fails here (from test output): {noformat} Command result for : ## Host: ebc7313d51a3 OS: Linux 4.15.0-38-generic amd64 Member(s): server-1 ## Could not execute "netstat". Reason: Cannot run program "netstat": error=2, No such file or directory {noformat} The output seems to be a huge listing ... starting with this: {noformat} lsof output ### COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 1 root cwd DIR 0,59 44 280305 /tmp/build/ae3c03f4/built-gemfire/test/geode/geode-core/build/distributedTest1562 java 1 root rtd DIR 0,102 80 234603 / java 1 root txt
[jira] [Reopened] (GEODE-5817) Acceptance test fails with org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
[ https://issues.apache.org/jira/browse/GEODE-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reopened GEODE-5817: Assignee: (was: Brian Rowe) Reopened as this failure reproduced (in 3 tests) during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/229 I should also note that a failure was logged against this JIRA on 11/2/1028 (but it was not reopened at that time). See previous comment on this JIRA. {noformat} org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest > cannotStopServerAsDataReaderOverHttp FAILED org.junit.ComparisonFailure: expected:<[0]> but was:<[1]> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.startCluster(StopServerWithSecurityAcceptanceTest.java:110) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.cannotStopServerAsDataReaderOverHttp(StopServerWithSecurityAcceptanceTest.java:57) org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest > cannotStopServerAsDataReaderOverJmx FAILED org.junit.ComparisonFailure: expected:<[0]> but was:<[1]> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.startCluster(StopServerWithSecurityAcceptanceTest.java:110) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.cannotStopServerAsDataReaderOverJmx(StopServerWithSecurityAcceptanceTest.java:72) org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest > canStopServerAsClusterAdminOverHttp FAILED org.junit.ComparisonFailure: expected:<[0]> but was:<[1]> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125) at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.startCluster(StopServerWithSecurityAcceptanceTest.java:110) at org.apache.geode.management.internal.cli.commands.StopServerWithSecurityAcceptanceTest.canStopServerAsClusterAdminOverHttp(StopServerWithSecurityAcceptanceTest.java:65) {noformat} Logs show the BindException for all 3 tests: {noformat} The Cache Server process terminated unexpectedly with exit status 1. Please refer to the log file in /tmp/junit15351062834469043980/cluster-setup/server for full details. Exception in thread "main" java.lang.RuntimeException: An IO error occurred while starting a Server in /tmp/junit15351062834469043980/cluster-setup/server on heavy-lifter-f478f2b5-323d-52fb-87c4-9e76a785e591.c.apachegeode-ci.internal[40404]: Network is unreachable; port (40404) is not available on localhost. at org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:819) at org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:707) at org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:227) Caused by: java.net.BindException: Network is unreachable; port (40404) is not available on localhost. at
[jira] [Updated] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles and aboveZeroDeletesPreviousFiles_nameWithHyphen
[ https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-3205: --- Summary: CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles and aboveZeroDeletesPreviousFiles_nameWithHyphen (was: CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles) > CI failure: > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles > and aboveZeroDeletesPreviousFiles_nameWithHyphen > - > > Key: GEODE-3205 > URL: https://issues.apache.org/jira/browse/GEODE-3205 > Project: Geode > Issue Type: Bug > Components: statistics, tests >Reporter: Lynn Gallinat >Priority: Major > Labels: Flaky, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > {noformat} > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest > > aboveZeroDeletesPreviousFiles FAILED > org.junit.ComparisonFailure: [Unexpected files: > [/tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-01.gfs, > /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-02.gfs, > /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles.gfs]] > expected:<[2]> but was:<[3]> > 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.internal.statistics.DiskSpaceLimitIntegrationTest.validateNumberFiles(DiskSpaceLimitIntegrationTest.java:263) > at > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:202) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles
[ https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reopened GEODE-3205: Assignee: (was: Kirk Lund) Reopening as this failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/232 {noformat} org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest > aboveZeroDeletesPreviousFiles_nameWithHyphen FAILED java.lang.AssertionError: Expecting file: to exist. at org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles_nameWithHyphen(DiskSpaceLimitIntegrationTest.java:255) {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.275/test-results/integrationTest/1544663063/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.275/test-artifacts/1544663063/integrationtestfiles-OpenJDK8-1.9.0-build.275.tgz See also: GEODE-2790, GEODE-2786 (both closed as duplicates of one another) > CI failure: > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles > > > Key: GEODE-3205 > URL: https://issues.apache.org/jira/browse/GEODE-3205 > Project: Geode > Issue Type: Bug > Components: statistics, tests >Reporter: Lynn Gallinat >Priority: Major > Labels: Flaky, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > {noformat} > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest > > aboveZeroDeletesPreviousFiles FAILED > org.junit.ComparisonFailure: [Unexpected files: > [/tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-01.gfs, > /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-02.gfs, > /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles.gfs]] > expected:<[2]> but was:<[3]> > 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.internal.statistics.DiskSpaceLimitIntegrationTest.validateNumberFiles(DiskSpaceLimitIntegrationTest.java:263) > at > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:202) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI
[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719275#comment-16719275 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-5676 at 12/12/18 6:24 PM: -- Reopening as this test hung again during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/230 {noformat} Started @ 2018-12-12 01:21:28.167 + 2018-12-12 01:39:26.161 + org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest serverRestartsAfterLocatorReconnects Ended @ 2018-12-12 02:08:40.629 + {noformat} Unfortunately, the callstacks tools doesn't seem to be working here ... so I don't have the stack dumps (mentioned in earlier failures): callstacks*.txt look like this: {noformat} Container: silly_hopper * Dumping stack for process OCI: Attaching to remote server OCI, please wait... {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.272/test-results/distributedTest/1544585041/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.272/test-artifacts/1544585041/distributedtestfiles-OpenJDK8-1.9.0-build.272.tgz was (Author: lhughesgodfrey): Reopening as this test hung again during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/230 {noformat} Started @ 2018-12-12 01:21:28.167 + 2018-12-12 01:39:26.161 + org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest serverRestartsAfterLocatorReconnects Ended @ 2018-12-12 02:08:40.629 + {noformat} Unfortunately, the callstacks tools doesn't seem to be working here ... so I don't have the stack dumps (mentioned in earlier failures): callstacks*.txt look like this: {noformat} Container: silly_hopper * Dumping stack for process OCI: Attaching to remote server OCI, please wait... {noformat} > ClusterConfigLocatorRestartDUnitTest hung in CI > --- > > Key: GEODE-5676 > URL: https://issues.apache.org/jira/browse/GEODE-5676 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Attachments: callstacks.txt > > Time Spent: 20m > Remaining Estimate: 0h > > This test hung in a couple of runs of DistributedTest > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//430 > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//370 > {noformat} > Started @ 2018-08-30 04:23:46.599 + > 2018-08-30 04:48:33.135 + > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects > Ended @ 2018-08-30 05:21:34.897 + > {noformat} > It seems to be stuck in tear down > {noformat} > "ReconnectThread" #416 prio=5 os_prio=0 tid=0x7fa86cad2000 nid=0xd07 in > Object.wait() [0x7fa744ecd000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2697) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558) > - locked <0xe00bedc8> (a java.lang.Object) > - locked <0xe07af498> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > - locked <0xe00bedd8> (a java.lang.Class for > org.apache.geode.cache.CacheFactory) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1041) > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:3987) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1552) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2564) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$$Lambda$81/1816825082.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:748) >Locked ownable synchronizers: > -
[jira] [Reopened] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI
[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reopened GEODE-5676: > ClusterConfigLocatorRestartDUnitTest hung in CI > --- > > Key: GEODE-5676 > URL: https://issues.apache.org/jira/browse/GEODE-5676 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Attachments: callstacks.txt > > Time Spent: 20m > Remaining Estimate: 0h > > This test hung in a couple of runs of DistributedTest > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//430 > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//370 > {noformat} > Started @ 2018-08-30 04:23:46.599 + > 2018-08-30 04:48:33.135 + > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects > Ended @ 2018-08-30 05:21:34.897 + > {noformat} > It seems to be stuck in tear down > {noformat} > "ReconnectThread" #416 prio=5 os_prio=0 tid=0x7fa86cad2000 nid=0xd07 in > Object.wait() [0x7fa744ecd000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2697) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558) > - locked <0xe00bedc8> (a java.lang.Object) > - locked <0xe07af498> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > - locked <0xe00bedd8> (a java.lang.Class for > org.apache.geode.cache.CacheFactory) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1041) > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:3987) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1552) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2564) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$$Lambda$81/1816825082.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:748) >Locked ownable synchronizers: > - None > "RMI TCP Connection(8)-172.17.0.13" #32 daemon prio=5 os_prio=0 > tid=0x7fa874001800 nid=0x2ff waiting for monitor entry > [0x7fa8f0d15000] >java.lang.Thread.State: BLOCKED (on object monitor) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1367) > - waiting to lock <0xe07af498> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022) > at > org.apache.geode.test.junit.rules.MemberStarterRule.disconnectDSIfAny(MemberStarterRule.java:182) > at > org.apache.geode.test.junit.rules.MemberStarterRule.after(MemberStarterRule.java:129) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.stopElementInsideVM(ClusterStartupRule.java:385) > at > org.apache.geode.test.junit.rules.VMProvider.lambda$stop$fe0d42dc$1(VMProvider.java:42) > at > org.apache.geode.test.junit.rules.VMProvider$$Lambda$77/1844235204.run(Unknown > Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at hydra.MethExecutor.executeObject(MethExecutor.java:244) > at > org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70) > at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > at sun.rmi.transport.Transport$1.run(Transport.java:200) > at sun.rmi.transport.Transport$1.run(Transport.java:197) >
[jira] [Commented] (GEODE-5676) ClusterConfigLocatorRestartDUnitTest hung in CI
[ https://issues.apache.org/jira/browse/GEODE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719275#comment-16719275 ] Shelley Lynn Hughes-Godfrey commented on GEODE-5676: Reopening as this test hung again during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/230 {noformat} Started @ 2018-12-12 01:21:28.167 + 2018-12-12 01:39:26.161 + org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest serverRestartsAfterLocatorReconnects Ended @ 2018-12-12 02:08:40.629 + {noformat} Unfortunately, the callstacks tools doesn't seem to be working here ... so I don't have the stack dumps (mentioned in earlier failures): callstacks*.txt look like this: {noformat} Container: silly_hopper * Dumping stack for process OCI: Attaching to remote server OCI, please wait... {noformat} > ClusterConfigLocatorRestartDUnitTest hung in CI > --- > > Key: GEODE-5676 > URL: https://issues.apache.org/jira/browse/GEODE-5676 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Attachments: callstacks.txt > > Time Spent: 20m > Remaining Estimate: 0h > > This test hung in a couple of runs of DistributedTest > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//430 > > https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds//370 > {noformat} > Started @ 2018-08-30 04:23:46.599 + > 2018-08-30 04:48:33.135 + > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects > Ended @ 2018-08-30 05:21:34.897 + > {noformat} > It seems to be stuck in tear down > {noformat} > "ReconnectThread" #416 prio=5 os_prio=0 tid=0x7fa86cad2000 nid=0xd07 in > Object.wait() [0x7fa744ecd000] >java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2697) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558) > - locked <0xe00bedc8> (a java.lang.Object) > - locked <0xe07af498> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > - locked <0xe00bedd8> (a java.lang.Class for > org.apache.geode.cache.CacheFactory) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1041) > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:3987) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1552) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2564) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$$Lambda$81/1816825082.run(Unknown > Source) > at java.lang.Thread.run(Thread.java:748) >Locked ownable synchronizers: > - None > "RMI TCP Connection(8)-172.17.0.13" #32 daemon prio=5 os_prio=0 > tid=0x7fa874001800 nid=0x2ff waiting for monitor entry > [0x7fa8f0d15000] >java.lang.Thread.State: BLOCKED (on object monitor) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1367) > - waiting to lock <0xe07af498> (a java.lang.Class for > org.apache.geode.internal.cache.GemFireCacheImpl) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022) > at > org.apache.geode.test.junit.rules.MemberStarterRule.disconnectDSIfAny(MemberStarterRule.java:182) > at > org.apache.geode.test.junit.rules.MemberStarterRule.after(MemberStarterRule.java:129) > at > org.apache.geode.test.dunit.rules.ClusterStartupRule.stopElementInsideVM(ClusterStartupRule.java:385) > at > org.apache.geode.test.junit.rules.VMProvider.lambda$stop$fe0d42dc$1(VMProvider.java:42) > at > org.apache.geode.test.junit.rules.VMProvider$$Lambda$77/1844235204.run(Unknown > Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at >
[jira] [Commented] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[ https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719249#comment-16719249 ] Shelley Lynn Hughes-Godfrey commented on GEODE-4267: This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/229 {noformat} org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest > testCrashDuringPreparePersistentId FAILED java.lang.RuntimeException: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. Caused by: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. at org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:920) at org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1475) at org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:856) at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:796) at org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:223) at org.apache.geode.cache.RegionFactory.(RegionFactory.java:128) at org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest$1.run(PersistentRecoveryOrderOldConfigDUnitTest.java:42) java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.271/test-results/distributedTest/1544580279/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.271/test-artifacts/1544580279/distributedtestfiles-OpenJDK8-1.9.0-build.271.tgz {noformat} > PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId > fails intermittently due to DistributedSystemDisconnectedException suspect > string > -- > > Key: GEODE-4267 > URL: https://issues.apache.org/jira/browse/GEODE-4267 > Project: Geode > Issue Type: Bug > Components: persistence, tests >Reporter: Kirk Lund >Assignee: Mark Hanson >Priority: Minor > Labels: Flaky > Attachments: GEODE-4267-standard-output.txt, > lynn-findfailures-11-26-2018-15-25-48-logs.tgz > > > {noformat} > org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest > > testCrashDuringPreparePersistentId FAILED > java.lang.RuntimeException: > org.apache.geode.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > Caused by: > org.apache.geode.distributed.DistributedSystemDisconnectedException: > This connection to a distributed system has been disconnected. > 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 1443 > [error 2017/12/16 00:50:26.778 UTC > tid=0x1b] > org.apache.geode.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected. > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4267) PersistentRecoveryOrderOldConfigDUnitTest.testCrashDuringPreparePersistentId fails intermittently due to DistributedSystemDisconnectedException suspect string
[ https://issues.apache.org/jira/browse/GEODE-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719249#comment-16719249 ] Shelley Lynn Hughes-Godfrey edited comment on GEODE-4267 at 12/12/18 5:40 PM: -- This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/229 {noformat} org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest > testCrashDuringPreparePersistentId FAILED java.lang.RuntimeException: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. Caused by: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. at org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:920) at org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1475) at org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:856) at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:796) at org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:223) at org.apache.geode.cache.RegionFactory.(RegionFactory.java:128) at org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest$1.run(PersistentRecoveryOrderOldConfigDUnitTest.java:42) java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- {noformat} =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.271/test-results/distributedTest/1544580279/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.271/test-artifacts/1544580279/distributedtestfiles-OpenJDK8-1.9.0-build.271.tgz was (Author: lhughesgodfrey): This failure reproduced in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/229 {noformat} org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest > testCrashDuringPreparePersistentId FAILED java.lang.RuntimeException: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. Caused by: org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. at org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:920) at org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1475) at org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:856) at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:796) at org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:223) at org.apache.geode.cache.RegionFactory.(RegionFactory.java:128) at org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest$1.run(PersistentRecoveryOrderOldConfigDUnitTest.java:42) java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.271/test-results/distributedTest/1544580279/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at:
[jira] [Resolved] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
[ https://issues.apache.org/jira/browse/GEODE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5911. Resolution: Fixed Fix Version/s: 1.8.0 {noformat} commit de2aed4a8032fc0e0bc1f8399ce985fae7e3cb85 Author: ladyVader Date: Tue Oct 23 09:49:40 2018 -0700 GEODE-5911: Improve SSL warning to indicate specific to GEODE; reference related property * Added Apache GEODE to SSL hostname validation warning * Added ssl-endpoint-identification-enabled property to same {noformat} > Improve SSL warning to indicate specific to GEODE; reference related property > - > > Key: GEODE-5911 > URL: https://issues.apache.org/jira/browse/GEODE-5911 > Project: Geode > Issue Type: Bug > Components: security >Affects Versions: 1.8.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We currently log this warning in the system log if > ssl-endpoint-identification-enabled > {noformat} > Your SSL configuration disables hostname validation. Future releases will > mandate hostname validation. > {noformat} > This can be mis-interpreted as a JVM warning, so updating the message to show > it is Apache GEODE related ... and include the property to enable hostname > validation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
[ https://issues.apache.org/jira/browse/GEODE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-5911: -- Assignee: Shelley Lynn Hughes-Godfrey > Improve SSL warning to indicate specific to GEODE; reference related property > - > > Key: GEODE-5911 > URL: https://issues.apache.org/jira/browse/GEODE-5911 > Project: Geode > Issue Type: Bug > Components: security >Affects Versions: 1.8.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > We currently log this warning in the system log if > ssl-endpoint-identification-enabled > {noformat} > Your SSL configuration disables hostname validation. Future releases will > mandate hostname validation. > {noformat} > This can be mis-interpreted as a JVM warning, so updating the message to show > it is Apache GEODE related ... and include the property to enable hostname > validation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
[ https://issues.apache.org/jira/browse/GEODE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-5911: --- Affects Version/s: 1.8.0 > Improve SSL warning to indicate specific to GEODE; reference related property > - > > Key: GEODE-5911 > URL: https://issues.apache.org/jira/browse/GEODE-5911 > Project: Geode > Issue Type: Bug > Components: security >Affects Versions: 1.8.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > We currently log this warning in the system log if > ssl-endpoint-identification-enabled > {noformat} > Your SSL configuration disables hostname validation. Future releases will > mandate hostname validation. > {noformat} > This can be mis-interpreted as a JVM warning, so updating the message to show > it is Apache GEODE related ... and include the property to enable hostname > validation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
Shelley Lynn Hughes-Godfrey created GEODE-5911: -- Summary: Improve SSL warning to indicate specific to GEODE; reference related property Key: GEODE-5911 URL: https://issues.apache.org/jira/browse/GEODE-5911 Project: Geode Issue Type: Bug Components: security Reporter: Shelley Lynn Hughes-Godfrey We currently log this warning in the system log if ssl-endpoint-identification-enabled {noformat} Your SSL configuration disables hostname validation. Future releases will mandate hostname validation. {noformat} This can be mis-interpreted as a JVM warning, so updating the message to show it is Apache GEODE related ... and include the property to enable hostname validation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5344) race condition between Queue Removal Thread and Message Dispatcher can prevent dispatching to client
[ https://issues.apache.org/jira/browse/GEODE-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5344. Resolution: Duplicate Fix Version/s: 1.7.0 > race condition between Queue Removal Thread and Message Dispatcher can > prevent dispatching to client > > > Key: GEODE-5344 > URL: https://issues.apache.org/jira/browse/GEODE-5344 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Ryan McMahon >Priority: Major > Fix For: 1.7.0 > > > If a secondary server becomes primary while handling a Queue Removal Message > (containing a list of events already processed by the client), the Queue > Removal Message can remove that entry from the HAContainer just prior to the > Message Dispatcher attempting to dispatch the message. > Once that occurs, the Message Dispatcher (peek) gets stuck on that event and > cannot dispatch any other messages to that client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5495) Double decrement of HAEventWrapper ref count due to race between QRM and DestroyRQ
[ https://issues.apache.org/jira/browse/GEODE-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5495. Resolution: Fixed > Double decrement of HAEventWrapper ref count due to race between QRM and > DestroyRQ > -- > > Key: GEODE-5495 > URL: https://issues.apache.org/jira/browse/GEODE-5495 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When a client disconnects due to network issues e.g. SocketTimeoutExceptions > we will destroy the HARegionQueue for that client. As part of that process, > we decrement the reference count on the HAEventWrappers used by that client > in the HAContainer. > However, we may still be receiving queue removal messages for that client > which results in a decrement of those same HAEventWrappers. This double > decrementing can result in premature removal of the HAEventWrapper from the > HAContainer even though other clients still need it. > We need to prevent this double decrementing and premature removal, perhaps > through synchronization between the destroyRQ() logic and queue removal > messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5495) Double decrement of HAEventWrapper ref count due to race between QRM and DestroyRQ
[ https://issues.apache.org/jira/browse/GEODE-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568459#comment-16568459 ] Shelley Lynn Hughes-Godfrey commented on GEODE-5495: Fixed: {noformat} commit acb50f94157c25ada4163771758115a1cb108516 (HEAD -> develop, origin/develop, origin/HEAD) Author: Ryan McMahon Date: Wed Aug 1 11:33:38 2018 -0700 GEODE-5495: Destroy available ID before decrement in updateHAContainer() Co-authored-by: Ryan McMahon Co-authored-by: Lynn Hughes-Godfrey {noformat} > Double decrement of HAEventWrapper ref count due to race between QRM and > DestroyRQ > -- > > Key: GEODE-5495 > URL: https://issues.apache.org/jira/browse/GEODE-5495 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When a client disconnects due to network issues e.g. SocketTimeoutExceptions > we will destroy the HARegionQueue for that client. As part of that process, > we decrement the reference count on the HAEventWrappers used by that client > in the HAContainer. > However, we may still be receiving queue removal messages for that client > which results in a decrement of those same HAEventWrappers. This double > decrementing can result in premature removal of the HAEventWrapper from the > HAContainer even though other clients still need it. > We need to prevent this double decrementing and premature removal, perhaps > through synchronization between the destroyRQ() logic and queue removal > messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5420) Protect events in HAContainer from being removed prematurely
[ https://issues.apache.org/jira/browse/GEODE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5420. Resolution: Fixed Fix Version/s: 1.8.0 > Protect events in HAContainer from being removed prematurely > > > Key: GEODE-5420 > URL: https://issues.apache.org/jira/browse/GEODE-5420 > Project: Geode > Issue Type: Bug > Components: client queues >Affects Versions: 1.8.0 >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > This can occur when: > 1) Events are added to queuedEvents during message dispatcher initialization > 2) Events are added to giiQueue while serving initial image to peer > We have seen this issue when QRM messages are being processed after becoming > primary. This causes the event to be removed prematurely from the > HAContainer, and then the wrapper is in a bad state (null client update > message) when we try to replace the event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3820) CI failure: DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification
[ https://issues.apache.org/jira/browse/GEODE-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-3820: --- Affects Version/s: 1.7.0 > CI failure: > DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification > - > > Key: GEODE-3820 > URL: https://issues.apache.org/jira/browse/GEODE-3820 > Project: Geode > Issue Type: Bug > Components: serialization >Affects Versions: 1.7.0 >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This test contains many pauses & needs to be converted to use Awaitility. > The spelling of this class name should also be corrected. > org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest > > testDataSerializersEventIdVerificationClientsAndServers FAILED > java.lang.AssertionError: EventId found Different > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerificationClientsAndServers(DataSerializerPropogationDUnitTest.java:673) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3820) CI failure: DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification
[ https://issues.apache.org/jira/browse/GEODE-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16489779#comment-16489779 ] Shelley Lynn Hughes-Godfrey commented on GEODE-3820: Reopened as this failure reproduced on geode 1.7 branch: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.7.0/jobs/DistributedTest/builds/3 {noformat} org.apache.geode.internal.cache.tier.sockets.DataSerializerPropagationDUnitTest > testDataSerializersEventIdVerificationClientsAndServers FAILED java.lang.AssertionError: EventId found Different at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.apache.geode.internal.cache.tier.sockets.DataSerializerPropagationDUnitTest.testDataSerializersEventIdVerificationClientsAndServers(DataSerializerPropagationDUnitTest.java:408) {noformat} Comments from Barry: I know Jason and I looked at a bug awhile ago (GEODE-4144) with event ids being different. It was a timing issue with the port being set, but I'm not sure if this could affect this. If I were debugging this, I would add some logging in the afterReceivingFromServer callback if the event ids were different here: {noformat} private static void setClientServerObserver2() { PoolImpl.IS_INSTANTIATOR_CALLBACK = true; ClientServerObserverHolder.setInstance(new ClientServerObserverAdapter() { @Override public void afterReceivingFromServer(EventID eventID) { testEventIDResult = eventID.equals(eventId); } }); } {noformat} > CI failure: > DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerification > - > > Key: GEODE-3820 > URL: https://issues.apache.org/jira/browse/GEODE-3820 > Project: Geode > Issue Type: Bug > Components: serialization >Affects Versions: 1.7.0 >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This test contains many pauses & needs to be converted to use Awaitility. > The spelling of this class name should also be corrected. > org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest > > testDataSerializersEventIdVerificationClientsAndServers FAILED > java.lang.AssertionError: EventId found Different > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > org.apache.geode.internal.cache.tier.sockets.DataSerializerPropogationDUnitTest.testDataSerializersEventIdVerificationClientsAndServers(DataSerializerPropogationDUnitTest.java:673) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5187) clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl
[ https://issues.apache.org/jira/browse/GEODE-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5187. Resolution: Fixed Fix Version/s: 1.7.0 > clients can miss events when servers recycled, possibly due to null eventId > in ClientUpdateMessageImpl > -- > > Key: GEODE-5187 > URL: https://issues.apache.org/jira/browse/GEODE-5187 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > HARegionQueues may have an issue where messages are lost due to the eventId > (threadId and sequenceId) being null ... which prevents them from being > dispatched to the client. > This may be due to the ClientUpdateMessageImpl no longer including the > eventId when serialized over the wire between servers. Now the receiving > side must use eventId from the HAEventWrapper to re-populate this field in > the ClientUpdateMessage. > If the null eventId is detected by HARegionQueue.putGIIDataInRegion, the > corresponding event is silently dropped. This occurs when processing the > InitialImage of the HARegionQueue from another server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5166) NPE thrown from HARegionQueue.updateHAEventWrapper
[ https://issues.apache.org/jira/browse/GEODE-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-5166. Resolution: Fixed Fix Version/s: 1.7.0 Fixed on develop: {noformat} commit 1dfbffa71a377aa276729c80c35f0c25a2886b25 Author: Lynn Hughes-GodfreyDate: Tue May 1 16:35:28 2018 -0700 GEODE-5166: NPE thrown while processing InitialImage of subscription region * Fix NPE in updateHAEventWrapper * Clean up code (renaming variables) in putEventInHARegion * Removing old/commented out code {noformat} > NPE thrown from HARegionQueue.updateHAEventWrapper > -- > > Key: GEODE-5166 > URL: https://issues.apache.org/jira/browse/GEODE-5166 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > NPE thrown when processing the InitialImage for an HARegionQueue > {noformat} > ERROR util.TestException: > /var/vcap/data/vad/eventValidation_FullListFailOver-0430-070117/bridgegemfire4_19378/system.log > contains java.lang.NullPointerException > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.ha.HARegionQueue.updateHAEventWrapper(HARegionQueue.java:2128) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.HARegion.updateHAEventWrapper(HARegion.java:481) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.AbstractRegionMap.initialImagePut(AbstractRegionMap.java:825) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:977) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1307) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:209) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2786) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:193) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:186) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:832) > at Remote Member >
[jira] [Assigned] (GEODE-5187) clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl
[ https://issues.apache.org/jira/browse/GEODE-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-5187: -- Assignee: Shelley Lynn Hughes-Godfrey > clients can miss events when servers recycled, possibly due to null eventId > in ClientUpdateMessageImpl > -- > > Key: GEODE-5187 > URL: https://issues.apache.org/jira/browse/GEODE-5187 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > HARegionQueues may have an issue where messages are lost due to the eventId > (threadId and sequenceId) being null ... which prevents them from being > dispatched to the client. > This may be due to the ClientUpdateMessageImpl no longer including the > eventId when serialized over the wire between servers. Now the receiving > side must use eventId from the HAEventWrapper to re-populate this field in > the ClientUpdateMessage. > If the null eventId is detected by HARegionQueue.putGIIDataInRegion, the > corresponding event is silently dropped. This occurs when processing the > InitialImage of the HARegionQueue from another server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5187) clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl
Shelley Lynn Hughes-Godfrey created GEODE-5187: -- Summary: clients can miss events when servers recycled, possibly due to null eventId in ClientUpdateMessageImpl Key: GEODE-5187 URL: https://issues.apache.org/jira/browse/GEODE-5187 Project: Geode Issue Type: Bug Components: client queues Reporter: Shelley Lynn Hughes-Godfrey HARegionQueues may have an issue where messages are lost due to the eventId (threadId and sequenceId) being null ... which prevents them from being dispatched to the client. This may be due to the ClientUpdateMessageImpl no longer including the eventId when serialized over the wire between servers. Now the receiving side must use eventId from the HAEventWrapper to re-populate this field in the ClientUpdateMessage. If the null eventId is detected by HARegionQueue.putGIIDataInRegion, the corresponding event is silently dropped. This occurs when processing the InitialImage of the HARegionQueue from another server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5166) NPE thrown from HARegionQueue.updateHAEventWrapper
[ https://issues.apache.org/jira/browse/GEODE-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-5166: -- Assignee: Shelley Lynn Hughes-Godfrey > NPE thrown from HARegionQueue.updateHAEventWrapper > -- > > Key: GEODE-5166 > URL: https://issues.apache.org/jira/browse/GEODE-5166 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > NPE thrown when processing the InitialImage for an HARegionQueue > {noformat} > ERROR util.TestException: > /var/vcap/data/vad/eventValidation_FullListFailOver-0430-070117/bridgegemfire4_19378/system.log > contains java.lang.NullPointerException > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.ha.HARegionQueue.updateHAEventWrapper(HARegionQueue.java:2128) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.HARegion.updateHAEventWrapper(HARegion.java:481) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.AbstractRegionMap.initialImagePut(AbstractRegionMap.java:825) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:977) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1307) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:209) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2786) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:193) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:186) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in > org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:832) > at Remote Member > 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' > in java.lang.Thread.run(Thread.java:745) > at > org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:87) > at > org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:542) > at > org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1215) > at > org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1056) >
[jira] [Created] (GEODE-5166) NPE thrown from HARegionQueue.updateHAEventWrapper
Shelley Lynn Hughes-Godfrey created GEODE-5166: -- Summary: NPE thrown from HARegionQueue.updateHAEventWrapper Key: GEODE-5166 URL: https://issues.apache.org/jira/browse/GEODE-5166 Project: Geode Issue Type: Bug Components: client queues Reporter: Shelley Lynn Hughes-Godfrey NPE thrown when processing the InitialImage for an HARegionQueue {noformat} ERROR util.TestException: /var/vcap/data/vad/eventValidation_FullListFailOver-0430-070117/bridgegemfire4_19378/system.log contains java.lang.NullPointerException at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.ha.HARegionQueue.updateHAEventWrapper(HARegionQueue.java:2128) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.HARegion.updateHAEventWrapper(HARegion.java:481) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.AbstractRegionMap.initialImagePut(AbstractRegionMap.java:825) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.InitialImageOperation.processChunk(InitialImageOperation.java:977) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.InitialImageOperation$ImageProcessor.process(InitialImageOperation.java:1307) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:209) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.internal.cache.InitialImageOperation$ImageReplyMessage.process(InitialImageOperation.java:2786) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:193) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:186) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:832) at Remote Member 'rs-GEM-1666-scheduler(bridgegemfire4_rs-GEM-1666-scheduler_19378:19378):1028' in java.lang.Thread.run(Thread.java:745) at org.apache.geode.distributed.internal.ReplyException.handleCause(ReplyException.java:87) at org.apache.geode.internal.cache.InitialImageOperation.getFromOne(InitialImageOperation.java:542) at org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1215) at org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1056) at org.apache.geode.internal.cache.HARegion.initialize(HARegion.java:335) at org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3085) at org.apache.geode.internal.cache.HARegion.getInstance(HARegion.java:255) at org.apache.geode.internal.cache.ha.HARegionQueue.createHARegion(HARegionQueue.java:389) at org.apache.geode.internal.cache.ha.HARegionQueue.(HARegionQueue.java:373)
[jira] [Commented] (GEODE-4909) Add dunit test coverage for lucene reindex with security
[ https://issues.apache.org/jira/browse/GEODE-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459295#comment-16459295 ] Shelley Lynn Hughes-Godfrey commented on GEODE-4909: commit a9c4a0a0115e0f1462276c4cbe509b6b51cc8e41 Author: Lynn Hughes-GodfreyDate: Tue Mar 27 15:23:07 2018 -0700 GEODE-4909: Additional lucene reindex tests with security * Extended existing tests with and without gfsh to create region prior to creating lucene index. > Add dunit test coverage for lucene reindex with security > > > Key: GEODE-4909 > URL: https://issues.apache.org/jira/browse/GEODE-4909 > Project: Geode > Issue Type: Test > Components: lucene >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add new dunit tests: > - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest > - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4909) Add dunit test coverage for lucene reindex with security
[ https://issues.apache.org/jira/browse/GEODE-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey resolved GEODE-4909. Resolution: Fixed Fix Version/s: 1.6.0 > Add dunit test coverage for lucene reindex with security > > > Key: GEODE-4909 > URL: https://issues.apache.org/jira/browse/GEODE-4909 > Project: Geode > Issue Type: Test > Components: lucene >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add new dunit tests: > - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest > - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4987) Add rebalancing tests with colocated PRs and AEQ (colocated region)
[ https://issues.apache.org/jira/browse/GEODE-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-4987: -- Assignee: Shelley Lynn Hughes-Godfrey > Add rebalancing tests with colocated PRs and AEQ (colocated region) > > > Key: GEODE-4987 > URL: https://issues.apache.org/jira/browse/GEODE-4987 > Project: Geode > Issue Type: Test > Components: lucene >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > Create tests to add colocated partitioned regions during rebalance to verify > co-located region does not hang. > Create similar test with AEQ (which is a colocated region) to verify that > mutating region to add AEQ does not hang during rebalance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
Shelley Lynn Hughes-Godfrey created GEODE-5144: -- Summary: CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter Key: GEODE-5144 URL: https://issues.apache.org/jira/browse/GEODE-5144 Project: Geode Issue Type: Bug Components: wan Reporter: Shelley Lynn Hughes-Godfrey This failure occurred during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12 {noformat} org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter 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 3199 [error 2018/04/26 03:50:06.755 UTC :32774 shared ordered uid=20 port=60094> tid=309] Exception occurred in CacheListener java.util.concurrent.RejectedExecutionException: Task org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6 rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) at org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611) at org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91) at org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151) at org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468) at org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969) at org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778) at org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381) at org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170) at org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717) at org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409) at org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238) at org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149) at org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093) at org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504) at org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478) at org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56) at org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430) at org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599) at org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279) at org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186) at org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964) at org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:120) at org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1191) at org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1091) at org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378) at org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:436) at org.apache.geode.distributed.internal.ClusterDistributionManager.scheduleIncomingMessage(ClusterDistributionManager.java:3250) at
[jira] [Updated] (GEODE-5144) CI failure: org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > testReplicatedSerialPropagationWithFilter
[ https://issues.apache.org/jira/browse/GEODE-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-5144: --- Affects Version/s: 1.6.0 > CI failure: > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > > testReplicatedSerialPropagationWithFilter > > > Key: GEODE-5144 > URL: https://issues.apache.org/jira/browse/GEODE-5144 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred during CI: > > https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/12 > {noformat} > org.apache.geode.internal.cache.wan.serial.SerialWANPropagationsFeatureDUnitTest > > testReplicatedSerialPropagationWithFilter 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 3199 > [error 2018/04/26 03:50:06.755 UTC 172.17.0.5(414):32774 shared ordered uid=20 port=60094> tid=309] > Exception occurred in CacheListener > java.util.concurrent.RejectedExecutionException: Task > org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor$2@471694c6 > rejected from java.util.concurrent.ThreadPoolExecutor@c955b3b[Shutting down, > pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1778] > at > java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) > at > java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) > at > java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) > at > org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderEventProcessor.handlePrimaryDestroy(SerialGatewaySenderEventProcessor.java:611) > at > org.apache.geode.internal.cache.wan.serial.SerialSecondaryGatewayListener.afterDestroy(SerialSecondaryGatewayListener.java:91) > at > org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:151) > at > org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8468) > at > org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6969) > at > org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6778) > at > org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2381) > at > org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:170) > at > org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6717) > at > org.apache.geode.internal.cache.map.RegionMapDestroy.destroyExistingEntry(RegionMapDestroy.java:409) > at > org.apache.geode.internal.cache.map.RegionMapDestroy.handleExistingRegionEntry(RegionMapDestroy.java:238) > at > org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:149) > at > org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1093) > at > org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6504) > at > org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6478) > at > org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:56) > at > org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6430) > at > org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1599) > at > org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueue$SerialGatewaySenderQueueMetaRegion.basicDestroy(SerialGatewaySenderQueue.java:1279) > at > org.apache.geode.internal.cache.LocalRegion.localDestroy(LocalRegion.java:2186) > at > org.apache.geode.internal.cache.DistributedRegion.localDestroy(DistributedRegion.java:964) > at > org.apache.geode.internal.cache.wan.serial.BatchDestroyOperation$DestroyMessage.operateOnRegion(BatchDestroyOperation.java:120) > at > org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1191) > at > org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1091) > at >
[jira] [Updated] (GEODE-5132) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED
[ https://issues.apache.org/jira/browse/GEODE-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-5132: --- Affects Version/s: 1.7.0 > CI failure: > org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > > testParallelPropagationLoopBack3Sites FAILED > --- > > Key: GEODE-5132 > URL: https://issues.apache.org/jira/browse/GEODE-5132 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.7.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred during CI: > > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296 > {noformat} > org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > > testParallelPropagationLoopBack3Sites FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest$$Lambda$162/1703391551.run > in VM 4 running on Host 83b9797d6847 with 8 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > at > org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.testParallelPropagationLoopBack3Sites(ParallelWANPropagationLoopBackDUnitTest.java:210) > Caused by: > org.awaitility.core.ConditionTimeoutException: Condition defined as a > lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that > uses int, intorg.apache.geode.cache.Region null within 3 milliseconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648) > at > org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2721) > at > org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2706) > at > org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.lambda$testParallelPropagationLoopBack3Sites$bb17a952$21(ParallelWANPropagationLoopBackDUnitTest.java:210) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5132) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED
Shelley Lynn Hughes-Godfrey created GEODE-5132: -- Summary: CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED Key: GEODE-5132 URL: https://issues.apache.org/jira/browse/GEODE-5132 Project: Geode Issue Type: Bug Components: wan Reporter: Shelley Lynn Hughes-Godfrey This failure occurred during CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296 {noformat} org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest$$Lambda$162/1703391551.run in VM 4 running on Host 83b9797d6847 with 8 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:436) at org.apache.geode.test.dunit.VM.invoke(VM.java:405) at org.apache.geode.test.dunit.VM.invoke(VM.java:348) at org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.testParallelPropagationLoopBack3Sites(ParallelWANPropagationLoopBackDUnitTest.java:210) Caused by: org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that uses int, intorg.apache.geode.cache.Region null within 3 milliseconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117) at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648) at org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2721) at org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2706) at org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.lambda$testParallelPropagationLoopBack3Sites$bb17a952$21(ParallelWANPropagationLoopBackDUnitTest.java:210) {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5131) CI failure: org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED
[ https://issues.apache.org/jira/browse/GEODE-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-5131: --- Affects Version/s: 1.7.0 > CI failure: > org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > > testParallelPropagationSenderResume FAILED > > > Key: GEODE-5131 > URL: https://issues.apache.org/jira/browse/GEODE-5131 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.7.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > This failure occurred during CI on develop: > > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296 > {noformat} > org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > > testParallelPropagationSenderResume FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderOperationsDUnitTest$$Lambda$79/470558236.run > in VM 4 running on Host 1f5f8948cda6 with 8 VMs > Caused by: > java.lang.AssertionError: Expected events in all primary queues after > drain is 0 expected:<0> but was:<1> > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5131) CI failure: org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED
Shelley Lynn Hughes-Godfrey created GEODE-5131: -- Summary: CI failure: org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED Key: GEODE-5131 URL: https://issues.apache.org/jira/browse/GEODE-5131 Project: Geode Issue Type: Bug Components: wan Reporter: Shelley Lynn Hughes-Godfrey This failure occurred during CI on develop: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296 {noformat} org.apache.geode.internal.cache.wan.offheap.ParallelGatewaySenderOperationsOffHeapDUnitTest > testParallelPropagationSenderResume FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderOperationsDUnitTest$$Lambda$79/470558236.run in VM 4 running on Host 1f5f8948cda6 with 8 VMs Caused by: java.lang.AssertionError: Expected events in all primary queues after drain is 0 expected:<0> but was:<1> {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4915) ClusterConfigLocatorRestartDUnitTest fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4915: --- Description: This test has timing issues and needs to be more robust. Adding test name and failure details from https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/254 {noformat} org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects 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 1217 [fatal 2018/04/06 05:00:39.119 UTC :32772 shared unordered uid=10 port=37516> tid=0x65] Uncaught exception in thread Thread[P2P message reader for 172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516,10,P2P Reader Threads] org.apache.geode.distributed.DistributedSystemDisconnectedException: org.apache.geode.ForcedDisconnectException: for testing at org.apache.geode.distributed.internal.membership.gms.Services$Stopper.generateCancelledException(Services.java:402) at org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83) at org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.remove(GMSJoinLeave.java:1645) at org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.inlineCheckIfAvailable(GMSHealthMonitor.java:1328) at org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:616) at org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.verifyMember(GMSMembershipManager.java:1674) at org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.suspectMember(GMSMembershipManager.java:1657) at org.apache.geode.internal.tcp.Connection.initiateSuspicionIfSharedUnordered(Connection.java:1917) at org.apache.geode.internal.tcp.Connection.run(Connection.java:1697) at java.lang.Thread.run(Thread.java:748) {noformat} was:This test has timing issues and needs to be more robust. > ClusterConfigLocatorRestartDUnitTest fails intermittently > - > > Key: GEODE-4915 > URL: https://issues.apache.org/jira/browse/GEODE-4915 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Jens Deppe >Assignee: Kenneth Howe >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This test has timing issues and needs to be more robust. > Adding test name and failure details from > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/254 > {noformat} > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects 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 1217 > [fatal 2018/04/06 05:00:39.119 UTC 172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516> > tid=0x65] Uncaught exception in thread Thread[P2P message reader for > 172.17.0.7(server-2:182):32772 shared unordered uid=10 port=37516,10,P2P > Reader Threads] > org.apache.geode.distributed.DistributedSystemDisconnectedException: > org.apache.geode.ForcedDisconnectException: for testing > at > org.apache.geode.distributed.internal.membership.gms.Services$Stopper.generateCancelledException(Services.java:402) > at > org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83) > at > org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.remove(GMSJoinLeave.java:1645) > at > org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.inlineCheckIfAvailable(GMSHealthMonitor.java:1328) > at > org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:616) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.verifyMember(GMSMembershipManager.java:1674) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.suspectMember(GMSMembershipManager.java:1657) > at >
[jira] [Created] (GEODE-4987) Add rebalancing tests with colocated PRs and AEQ (colocated region)
Shelley Lynn Hughes-Godfrey created GEODE-4987: -- Summary: Add rebalancing tests with colocated PRs and AEQ (colocated region) Key: GEODE-4987 URL: https://issues.apache.org/jira/browse/GEODE-4987 Project: Geode Issue Type: Test Components: lucene Reporter: Shelley Lynn Hughes-Godfrey Create tests to add colocated partitioned regions during rebalance to verify co-located region does not hang. Create similar test with AEQ (which is a colocated region) to verify that mutating region to add AEQ does not hang during rebalance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4963) ConnectCommandDUnitTest is broken since GfshCommand was made 'public'
[ https://issues.apache.org/jira/browse/GEODE-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4963: --- Description: The failure looks like this: {noformat} org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest > useCurrentGfshToConnectToOlderLocator FAILED java.lang.AssertionError: Expecting: <"_ __ / _/ __/ __/ // / / / __/ /___ /_ / _ / / /__/ / / _/ / // / /__/_/ /__/_//_/1.6.0-SNAPSHOT Monitor and Manage Apache Geode Connecting to Manager at [host=localhost, port=28823] .. Could not connect to : [host=localhost, port=28823]. Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused (Connection refused)] "> to contain: <"Cannot use a"> at org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:79) at org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandDUnitTest.java:46) {noformat} > ConnectCommandDUnitTest is broken since GfshCommand was made 'public' > - > > Key: GEODE-4963 > URL: https://issues.apache.org/jira/browse/GEODE-4963 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: ci > > The failure looks like this: > {noformat} > org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <"_ __ >/ _/ __/ __/ // / > / / __/ /___ /_ / _ / > / /__/ / / _/ / // / > /__/_/ /__/_//_/1.6.0-SNAPSHOT > > Monitor and Manage Apache Geode > Connecting to Manager at [host=localhost, port=28823] .. > Could not connect to : [host=localhost, port=28823]. Failed to retrieve > RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: localhost; nested > exception is: > java.net.ConnectException: Connection refused (Connection refused)] > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:79) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandDUnitTest.java:46) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4909) Add dunit test coverage for lucene reindex with security
Shelley Lynn Hughes-Godfrey created GEODE-4909: -- Summary: Add dunit test coverage for lucene reindex with security Key: GEODE-4909 URL: https://issues.apache.org/jira/browse/GEODE-4909 Project: Geode Issue Type: Test Components: lucene Reporter: Shelley Lynn Hughes-Godfrey Add new dunit tests: - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4909) Add dunit test coverage for lucene reindex with security
[ https://issues.apache.org/jira/browse/GEODE-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey reassigned GEODE-4909: -- Assignee: Shelley Lynn Hughes-Godfrey > Add dunit test coverage for lucene reindex with security > > > Key: GEODE-4909 > URL: https://issues.apache.org/jira/browse/GEODE-4909 > Project: Geode > Issue Type: Test > Components: lucene >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey >Priority: Major > > Add new dunit tests: > - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest > - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4909) Add dunit test coverage for lucene reindex with security
[ https://issues.apache.org/jira/browse/GEODE-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4909: --- Affects Version/s: 1.6.0 > Add dunit test coverage for lucene reindex with security > > > Key: GEODE-4909 > URL: https://issues.apache.org/jira/browse/GEODE-4909 > Project: Geode > Issue Type: Test > Components: lucene >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > Add new dunit tests: > - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest > - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[ https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4892: --- Description: geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours) https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207 The progress files show this DistributedTest run starting ~4 am ... but it also shows this test completing at 9:05 ... which is only 5 hours. Are we somehow stuck in cache close for 3 hours before the hang is declared while trying to shut down the DUnit VM. dunit-hangs.txt {noformat} Started @ 2018-03-17 03:57:50.567 + Ended @ 2018-03-17 03:59:28.268 + Started @ 2018-03-17 04:00:05.872 + Ended @ 2018-03-17 04:52:41.879 + Started @ 2018-03-17 04:53:00.358 + Ended @ 2018-03-17 04:55:07.622 + Started @ 2018-03-17 04:55:33.550 + Ended @ 2018-03-17 07:34:11.639 + Started @ 2018-03-17 07:34:51.022 + Ended @ 2018-03-17 08:08:34.849 + Started @ 2018-03-17 08:09:33.853 + Ended @ 2018-03-17 08:31:43.646 + Started @ 2018-03-17 08:31:54.175 + Ended @ 2018-03-17 08:32:02.523 + Started @ 2018-03-17 08:32:13.946 + Ended @ 2018-03-17 08:32:34.626 + Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + {noformat} Last distributedTest running: {noformat} Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + {noformat} Stack dumps are taken at 5-10 second intervals and they all look the same ... so it looks like 433 is stuck in waiting during cache close => distributedLockServiceDestroys waiting for replies from 493 for ElderInit. 493 is in ClusterDistributionManager.elderChangeWait(). Dumping stack for process 433: 2018-03-17 10:55:59 {noformat} "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xe08dd870> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) at org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) at org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318) at org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872) at org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227) - locked <0xe09a8768> (a org.apache.geode.distributed.internal.locks.DLockGrantor) at org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:646) at
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[ https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4892: --- Description: geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours) https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207 The progress files show this DistributedTest run starting ~4 am ... but it also shows this test completing at 9:05 ... which is only 5 hours. Are we somehow stuck in cache close for 3 hours before the hang is declared while trying to shut down the DUnit VM. dunit-hangs.txt {noformat} Started @ 2018-03-17 03:57:50.567 + Ended @ 2018-03-17 03:59:28.268 + Started @ 2018-03-17 04:00:05.872 + Ended @ 2018-03-17 04:52:41.879 + Started @ 2018-03-17 04:53:00.358 + Ended @ 2018-03-17 04:55:07.622 + Started @ 2018-03-17 04:55:33.550 + Ended @ 2018-03-17 07:34:11.639 + Started @ 2018-03-17 07:34:51.022 + Ended @ 2018-03-17 08:08:34.849 + Started @ 2018-03-17 08:09:33.853 + Ended @ 2018-03-17 08:31:43.646 + Started @ 2018-03-17 08:31:54.175 + Ended @ 2018-03-17 08:32:02.523 + Started @ 2018-03-17 08:32:13.946 + Ended @ 2018-03-17 08:32:34.626 + Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + {noformat} Last distributedTest running: {noformat} Started @ 2018-03-17 08:33:20.100 + 2018-03-17 08:56:15.914 + org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended @ 2018-03-17 09:05:29.197 + {noformat} Stack dumps are taken at 5-10 second intervals and they all look the same ... so it looks like 433 is stuck in waiting during cache close => distributedLockServiceDestroys waiting for replies from 493 for ElderInit. 493 is in ClusterDistributionManager.elderChangeWait(). * Dumping stack for process 433: 2018-03-17 10:55:59 {noformat} "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xe08dd870> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) at org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) at org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) at org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:347) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.basicOp(GrantorRequestProcessor.java:327) at org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.clearGrantor(GrantorRequestProcessor.java:318) at org.apache.geode.distributed.internal.locks.DLockService.clearGrantor(DLockService.java:872) at org.apache.geode.distributed.internal.locks.DLockGrantor.destroy(DLockGrantor.java:1227) - locked <0xe09a8768> (a org.apache.geode.distributed.internal.locks.DLockGrantor) at org.apache.geode.distributed.internal.locks.DLockService.nullLockGrantorId(DLockService.java:646) at
[jira] [Updated] (GEODE-4892) CI failure: geode-wan distributedTest hung in org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest testGatewaySenderStatus_OnMember Ended
[ https://issues.apache.org/jira/browse/GEODE-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shelley Lynn Hughes-Godfrey updated GEODE-4892: --- Affects Version/s: 1.6.0 > CI failure: geode-wan distributedTest hung in > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember Ended > --- > > Key: GEODE-4892 > URL: https://issues.apache.org/jira/browse/GEODE-4892 > Project: Geode > Issue Type: Bug > Components: distributed lock service, gfsh >Affects Versions: 1.6.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > > geode-wan distributed tests hung after 8 hours (usually takes 5-6 hours) > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/207 > The progress files show this DistributedTest run starting ~4 am ... but it > also shows this test completing at 9:05 ... which is only 5 hours. Are we > somehow stuck in cache close for 3 hours before the hang is declared while > trying to shut down the DUnit VM. > dunit-hangs.txt > ``` > Started @ 2018-03-17 03:57:50.567 + > Ended @ 2018-03-17 03:59:28.268 + > Started @ 2018-03-17 04:00:05.872 + > Ended @ 2018-03-17 04:52:41.879 + > Started @ 2018-03-17 04:53:00.358 + > Ended @ 2018-03-17 04:55:07.622 + > Started @ 2018-03-17 04:55:33.550 + > Ended @ 2018-03-17 07:34:11.639 + > Started @ 2018-03-17 07:34:51.022 + > Ended @ 2018-03-17 08:08:34.849 + > Started @ 2018-03-17 08:09:33.853 + > Ended @ 2018-03-17 08:31:43.646 + > Started @ 2018-03-17 08:31:54.175 + > Ended @ 2018-03-17 08:32:02.523 + > Started @ 2018-03-17 08:32:13.946 + > Ended @ 2018-03-17 08:32:34.626 + > Started @ 2018-03-17 08:33:20.100 + > 2018-03-17 08:56:15.914 + > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember > Ended @ 2018-03-17 09:05:29.197 + > ``` > Last distributedTest running: > ``` > Started @ 2018-03-17 08:33:20.100 + > 2018-03-17 08:56:15.914 + > org.apache.geode.internal.cache.wan.wancommand.StatusGatewaySenderCommandDUnitTest > testGatewaySenderStatus_OnMember > Ended @ 2018-03-17 09:05:29.197 + > ``` > Stack dumps are taken at 5-10 second intervals and they all look the same ... > so it looks like 433 is stuck in waiting during cache close => > distributedLockServiceDestroys waiting for replies from 493 for ElderInit. > 493 is in ClusterDistributionManager.elderChangeWait(). > * Dumping stack for process 433: > 2018-03-17 10:55:59 > ``` > "RMI TCP Connection(1)-172.17.0.3" #30 daemon prio=5 os_prio=0 > tid=0x7f9760001800 nid=0x1ec waiting on condition [0x7f975bffb000] >java.lang.Thread.State: TIMED_WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xe08dd870> (a > java.util.concurrent.CountDownLatch$Sync) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) > at > org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) > at > org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) > at > org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) > at > org.apache.geode.distributed.internal.locks.ElderInitProcessor.init(ElderInitProcessor.java:72) > at > org.apache.geode.distributed.internal.locks.ElderState.(ElderState.java:56) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderStateWithTryLock(ClusterDistributionManager.java:3359) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.getElderState(ClusterDistributionManager.java:3309) > at > org.apache.geode.distributed.internal.locks.GrantorRequestProcessor.startElderCall(GrantorRequestProcessor.java:238) > at >