[jira] [Resolved] (GEODE-9327) Remove all remaining references to ACE networking
[ https://issues.apache.org/jira/browse/GEODE-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-9327. - Resolution: Fixed > Remove all remaining references to ACE networking > - > > Key: GEODE-9327 > URL: https://issues.apache.org/jira/browse/GEODE-9327 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* native client contributor > *I WANT TO* remove all remaining references to ACE networking > *SO THAT* eventually we can get rid of ACE library > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (GEODE-9327) Remove all remaining references to ACE networking
[ https://issues.apache.org/jira/browse/GEODE-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-9327. --- > Remove all remaining references to ACE networking > - > > Key: GEODE-9327 > URL: https://issues.apache.org/jira/browse/GEODE-9327 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* native client contributor > *I WANT TO* remove all remaining references to ACE networking > *SO THAT* eventually we can get rid of ACE library > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9327) Remove all remaining references to ACE networking
[ https://issues.apache.org/jira/browse/GEODE-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494724#comment-17494724 ] ASF subversion and git services commented on GEODE-9327: Commit c9a893d3dbd9e43762193a780f48ef0c12192d78 in geode-native's branch refs/heads/develop from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c9a893d ] GEODE-9327: Remove ACE networking code references (#815) - Replaced method implementation to get a random port in old ITs framework. - Replaced convertHostToCanonicalForm implementation. - Changed ClientProxyMembershipID address serialization. - Removed unused PoolFactory::addCheck method. - Modified QueueConnectionRequestTest test to pass after the changes. - Fixed min/max macros windows compilcation - Changed ClientProxyMembershipID member attribute names to match style guidelines. - Changed HostStatSampler member attribute names to match style guidelines. - Changed Utils::convertHostToCanonicalForm to make the method more readable. > Remove all remaining references to ACE networking > - > > Key: GEODE-9327 > URL: https://issues.apache.org/jira/browse/GEODE-9327 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* native client contributor > *I WANT TO* remove all remaining references to ACE networking > *SO THAT* eventually we can get rid of ACE library > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9327) Remove all remaining references to ACE networking
[ https://issues.apache.org/jira/browse/GEODE-9327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494723#comment-17494723 ] ASF GitHub Bot commented on GEODE-9327: --- pdxcodemonkey merged pull request #815: URL: https://github.com/apache/geode-native/pull/815 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove all remaining references to ACE networking > - > > Key: GEODE-9327 > URL: https://issues.apache.org/jira/browse/GEODE-9327 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: obliterate-ace, pull-request-available > > *AS A* native client contributor > *I WANT TO* remove all remaining references to ACE networking > *SO THAT* eventually we can get rid of ACE library > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10065) Fix regexp in gnmsg for handshake messages
[ https://issues.apache.org/jira/browse/GEODE-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10065: -- Labels: needsTriage (was: ) > Fix regexp in gnmsg for handshake messages > -- > > Key: GEODE-10065 > URL: https://issues.apache.org/jira/browse/GEODE-10065 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Labels: needsTriage > > gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10065) Fix regexp in gnmsg for handshake messages
Michael Martell created GEODE-10065: --- Summary: Fix regexp in gnmsg for handshake messages Key: GEODE-10065 URL: https://issues.apache.org/jira/browse/GEODE-10065 Project: Geode Issue Type: Bug Reporter: Michael Martell gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10065) Fix regexp in gnmsg for handshake messages
[ https://issues.apache.org/jira/browse/GEODE-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494774#comment-17494774 ] ASF GitHub Bot commented on GEODE-10065: mmartell opened a new pull request #926: URL: https://github.com/apache/geode-native/pull/926 This fixes the regexp for handling handshake messages. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix regexp in gnmsg for handshake messages > -- > > Key: GEODE-10065 > URL: https://issues.apache.org/jira/browse/GEODE-10065 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Labels: needsTriage > > gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager
[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10063: --- Labels: GeodeOperationAPI blocks-1.15.0 pull-request-available (was: GeodeOperationAPI blocks-1.15.0) > A closed/destroyed connection can be set as a primary queueConnection in > QueueManager > - > > Key: GEODE-10063 > URL: https://issues.apache.org/jira/browse/GEODE-10063 > Project: Geode > Issue Type: Bug > Components: client queues, security >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available > > In certain race cases, a destroyed connection is set to be the primary queue > connection connected to servers. If re-auth is enabled, and server pauses the > primary queue waiting for the re-auth token, there will be no client to > server connection available to send the valid re-auth token for server to > unpause the queue. And the said client can not receive any events afterwards. > The situation should be detected during RedundancySatisfierTask, but it could > not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10065) Fix regexp in gnmsg for handshake messages
[ https://issues.apache.org/jira/browse/GEODE-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10065: --- Labels: needsTriage pull-request-available (was: needsTriage) > Fix regexp in gnmsg for handshake messages > -- > > Key: GEODE-10065 > URL: https://issues.apache.org/jira/browse/GEODE-10065 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Labels: needsTriage, pull-request-available > > gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10065) Fix regexp in gnmsg for handshake messages
[ https://issues.apache.org/jira/browse/GEODE-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494776#comment-17494776 ] ASF subversion and git services commented on GEODE-10065: - Commit 06413ef0cfb07e27f55007770496aba0ed418802 in geode-native's branch refs/heads/develop from Michael Martell [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=06413ef ] GEODE-10065: Add missing colon in regexp (#926) > Fix regexp in gnmsg for handshake messages > -- > > Key: GEODE-10065 > URL: https://issues.apache.org/jira/browse/GEODE-10065 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Labels: needsTriage, pull-request-available > > gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10065) Fix regexp in gnmsg for handshake messages
[ https://issues.apache.org/jira/browse/GEODE-10065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494775#comment-17494775 ] ASF GitHub Bot commented on GEODE-10065: mmartell merged pull request #926: URL: https://github.com/apache/geode-native/pull/926 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix regexp in gnmsg for handshake messages > -- > > Key: GEODE-10065 > URL: https://issues.apache.org/jira/browse/GEODE-10065 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Labels: needsTriage, pull-request-available > > gnmsg tool has a bug in the regexp for handshake messages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException
[
https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494786#comment-17494786
]
Geode Integration commented on GEODE-8760:
--
Seen in [benchmark-base
#160|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/160].
> P2pPartitionedPutBenchmark fails with UnmarshalException
>
>
> Key: GEODE-8760
> URL: https://issues.apache.org/jira/browse/GEODE-8760
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.14.0
>Reporter: Bill Burcham
>Priority: Major
>
> {code:java}
> > Task :geode-benchmarks:benchmark
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:89)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
> ... 3 more
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:254)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:235)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:180)
> at com.sun.proxy.$Proxy13.execute(Unknown Source)
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:87)
> ... 4 more
> Caused by:
> java.io.EOFException
> at
> java.io.DataInputStream.readByte(DataInputStream.java:267)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:240)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException
[
https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494787#comment-17494787
]
Geode Integration commented on GEODE-8760:
--
Seen in [benchmark-base
#153|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/153].
> P2pPartitionedPutBenchmark fails with UnmarshalException
>
>
> Key: GEODE-8760
> URL: https://issues.apache.org/jira/browse/GEODE-8760
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.14.0
>Reporter: Bill Burcham
>Priority: Major
>
> {code:java}
> > Task :geode-benchmarks:benchmark
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:89)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
> ... 3 more
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:254)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:235)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:180)
> at com.sun.proxy.$Proxy13.execute(Unknown Source)
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:87)
> ... 4 more
> Caused by:
> java.io.EOFException
> at
> java.io.DataInputStream.readByte(DataInputStream.java:267)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:240)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException
[
https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494788#comment-17494788
]
Geode Integration commented on GEODE-8760:
--
Seen on support/1.14 in [benchmark-with-security-manager
#29|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/benchmark-with-security-manager/builds/29].
> P2pPartitionedPutBenchmark fails with UnmarshalException
>
>
> Key: GEODE-8760
> URL: https://issues.apache.org/jira/browse/GEODE-8760
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.14.0
>Reporter: Bill Burcham
>Priority: Major
>
> {code:java}
> > Task :geode-benchmarks:benchmark
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:89)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
> ... 3 more
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:254)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:235)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:180)
> at com.sun.proxy.$Proxy13.execute(Unknown Source)
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:87)
> ... 4 more
> Caused by:
> java.io.EOFException
> at
> java.io.DataInputStream.readByte(DataInputStream.java:267)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:240)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8760) P2pPartitionedPutBenchmark fails with UnmarshalException
[
https://issues.apache.org/jira/browse/GEODE-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494789#comment-17494789
]
Geode Integration commented on GEODE-8760:
--
Seen in [benchmark-with-ssl
#162|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-with-ssl/builds/162].
> P2pPartitionedPutBenchmark fails with UnmarshalException
>
>
> Key: GEODE-8760
> URL: https://issues.apache.org/jira/browse/GEODE-8760
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.14.0
>Reporter: Bill Burcham
>Priority: Major
>
> {code:java}
> > Task :geode-benchmarks:benchmark
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.lang.RuntimeException:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1643)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by:
> java.lang.RuntimeException: java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.io.EOFException
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:89)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640)
> ... 3 more
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header;
> nested exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:254)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:235)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:180)
> at com.sun.proxy.$Proxy13.execute(Unknown Source)
> at
> org.apache.geode.perftest.jvms.rmi.Controller.lambda$onWorker$0(Controller.java:87)
> ... 4 more
> Caused by:
> java.io.EOFException
> at
> java.io.DataInputStream.readByte(DataInputStream.java:267)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:240)
> ... 9 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494794#comment-17494794 ] Geode Integration commented on GEODE-9998: -- Seen in [benchmark-radish #167|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/167]. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494795#comment-17494795 ] Steve Sienkowski commented on GEODE-9998: - I assigned the above benchmark failure to this issue. It looks like it could become resolved in build #168, which includes the changes to geode-benchmarks. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8554) CI Failure: JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
[
https://issues.apache.org/jira/browse/GEODE-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494797#comment-17494797
]
Geode Integration commented on GEODE-8554:
--
Seen in [distributed-test-openjdk8
#171|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/171]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-results/distributedTest/1645144255/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-artifacts/1645144255/distributedtestfiles-openjdk8-1.16.0-build.0087.tgz].
> CI Failure:
> JMXMBeanReconnectDUnitTest.locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns
>
>
> Key: GEODE-8554
> URL: https://issues.apache.org/jira/browse/GEODE-8554
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Jianxia Chen
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.management.JMXMBeanReconnectDUnitTest >
> locatorMXBeansOnOtherLocatorAreRestoredAfterCrashedLocatorReturns FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$355/858468979.call
> in VM -1 running on Host 7a5c340f5c23 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:472)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:191)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest [GemFire mbeans on
> locator2]
> Expecting HashSet:
> <[GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:type=Member,member=server1,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:service=Region,name=/region1,type=Member,member=server1,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region1,type=Distributed]>
> to contain:
> <[GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> but could not find the following element(s):
>
> <[GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.lambda$setUp$515fd116$3(JMXMBeanReconnectDUnitTest.java:192)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
>
[jira] [Commented] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494798#comment-17494798 ] Geode Integration commented on GEODE-9998: -- Seen in [benchmark-with-security-manager #165|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-with-security-manager/builds/165]. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494795#comment-17494795 ] Steve Sienkowski edited comment on GEODE-9998 at 2/18/22, 7:37 PM: --- I assigned two benchmark failures to this issue. It looks like it could become resolved after a recent commit to geode-benchmarks. (Awaiting results of benchmark-radish build [#168|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/168] ) was (Author: ssienkowski): I assigned two benchmark failures to this issue. It looks like it could become resolved from a recent commit to geode-benchmarks. (Awaiting results of benchmarks [#168|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/168] ) > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (GEODE-9998) Update jedis library to the current latest (>= 4.1.0)
[ https://issues.apache.org/jira/browse/GEODE-9998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494795#comment-17494795 ] Steve Sienkowski edited comment on GEODE-9998 at 2/18/22, 7:37 PM: --- I assigned two benchmark failures to this issue. It looks like it could become resolved from a recent commit to geode-benchmarks. (Awaiting results of benchmarks [#168|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-radish/builds/168] ) was (Author: ssienkowski): I assigned the above benchmark failure to this issue. It looks like it could become resolved in build #168, which includes the changes to geode-benchmarks. > Update jedis library to the current latest (>= 4.1.0) > - > > Key: GEODE-9998 > URL: https://issues.apache.org/jira/browse/GEODE-9998 > Project: Geode > Issue Type: Test > Components: redis >Affects Versions: 1.16.0 >Reporter: Jens Deppe >Assignee: Eric Zoerner >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > The 4.x version has been out for a while and we're still on 3.6.x (3.8 is the > last in the 3.x line). > This is not a trivial change as various APIs have changed which will affect a > lot of test code. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9615) CI Failure: DeployJarAcceptanceTest fails with exit value 1 from start locator
[
https://issues.apache.org/jira/browse/GEODE-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494802#comment-17494802
]
Geode Integration commented on GEODE-9615:
--
Seen in [acceptance-test-openjdk8
#163|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/163]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-results/acceptanceTest/1645148995/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-artifacts/1645148995/acceptancetestfiles-openjdk8-1.16.0-build.0087.tgz].
> CI Failure: DeployJarAcceptanceTest fails with exit value 1 from start locator
> --
>
> Key: GEODE-9615
> URL: https://issues.apache.org/jira/browse/GEODE-9615
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Priority: Major
>
> {noformat}
> org.apache.geode.modules.DeployJarAcceptanceTest > classMethod FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [41497e8cf7689a63: gfsh -e start locator --name=locator -e configure pdx
> --read-serialized=true -e start server --name=server
> --locators=localhost[10334]]] 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:103)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153)
> at
> org.apache.geode.modules.DeployJarAcceptanceTest.setup(DeployJarAcceptanceTest.java:62)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7017) CI failure: org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored
[
https://issues.apache.org/jira/browse/GEODE-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494803#comment-17494803
]
Geode Integration commented on GEODE-7017:
--
Seen in [acceptance-test-openjdk8
#163|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/163]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-results/acceptanceTest/1645148995/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0087/test-artifacts/1645148995/acceptancetestfiles-openjdk8-1.16.0-build.0087.tgz].
> CI failure:
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored
> ---
>
> Key: GEODE-7017
> URL: https://issues.apache.org/jira/browse/GEODE-7017
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Mark Hanson
>Priority: Major
> Attachments: acceptancetestfiles-OpenJDK11-1.14.0-build.0628.tgz
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> 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.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.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupValueRecoveryNotificationTest.persistentRegionThatRequiresValueRecovery(ServerStartupValueRecoveryNotificationTest.java:120)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9871) CI failure: InfoStatsIntegrationTest > networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
[
https://issues.apache.org/jira/browse/GEODE-9871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9871:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI failure: InfoStatsIntegrationTest >
> networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
>
>
> Key: GEODE-9871
> URL: https://issues.apache.org/jira/browse/GEODE-9871
> Project: Geode
> Issue Type: Bug
> Components: redis, statistics
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> link:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/38]
> stack trace:
> {code:java}
> InfoStatsIntegrationTest >
> networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond
> FAILED
> org.opentest4j.AssertionFailedError:
> expected: 0.0
> but was: 0.01
> 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.redis.internal.commands.executor.server.AbstractRedisInfoStatsIntegrationTest.networkKiloBytesReadOverLastSecond_shouldBeCloseToBytesReadOverLastSecond(AbstractRedisInfoStatsIntegrationTest.java:228)
> 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:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.util.str
[jira] [Updated] (GEODE-9810) CI: NativeRedisClusterTest testEachProxyReturnsExposedPorts failed
[
https://issues.apache.org/jira/browse/GEODE-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9810:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI: NativeRedisClusterTest testEachProxyReturnsExposedPorts failed
> --
>
> Key: GEODE-9810
> URL: https://issues.apache.org/jira/browse/GEODE-9810
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Xiaojian Zhou
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
>
> {code:java}
> > Task :geode-for-redis:acceptanceTest
> NativeRedisClusterTest > testEachProxyReturnsExposedPorts FAILED
> java.lang.AssertionError:
> Expecting actual:
> [44073, 45679, 36065, 40077, 42137]
> to contain exactly in any order:
> [40077, 45679, 33425, 36065, 42137, 44073]
> but could not find the following elements:
> [33425]
> at
> org.apache.geode.redis.NativeRedisClusterTest.testEachProxyReturnsExposedPorts(NativeRedisClusterTest.java:48)
> 1385 tests completed, 1 failed, 2 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0662/test-results/acceptanceTest/1637046056/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0662/test-artifacts/1637046056/acceptancetestfiles-openjdk8-1.15.0-build.0662.tgz
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED
[ https://issues.apache.org/jira/browse/GEODE-9729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9729: - Component/s: tests > CI Failure: > PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED > - > > Key: GEODE-9729 > URL: https://issues.apache.org/jira/browse/GEODE-9729 > Project: Geode > Issue Type: Bug > Components: client/server, tests >Affects Versions: 1.15.0 >Reporter: Eric Shu >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > org.apache.geode.cache.client.AllConnectionsInUseException > at > org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:304) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:137) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:120) > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:805) > at > org.apache.geode.cache.client.internal.GetClientPRMetaDataOp.execute(GetClientPRMetaDataOp.java:53) > at > org.apache.geode.cache.client.internal.ClientMetadataService.getClientPRMetadata(ClientMetadataService.java:574) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:972) > at > org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:234) > at > org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:221) > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:829) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9675) CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
[
https://issues.apache.org/jira/browse/GEODE-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9675:
-
Component/s: tests
> CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> -
>
> Key: GEODE-9675
> URL: https://issues.apache.org/jira/browse/GEODE-9675
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Bill Burcham
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
> Attachments: screenshot-1.png
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1983
> {code:java}
> ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> org.apache.geode.SystemConnectException: Problem starting up membership
> services
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:466)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:499)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:328)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:757)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:133)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3013)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:283)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:209)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:180)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:256)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManagerDUnitTest.testConnectAfterBeingShunned(ClusterDistributionManagerDUnitTest.java:170)
> Caused by:
>
> org.apache.geode.distributed.internal.membership.api.MemberStartupException:
> unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:401)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:203)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.start(GMSMembership.java:1642)
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:171)
> ... 13 more
> Caused by:
> java.lang.Exception: failed to open a port in range 41003-41003
> at
> org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:503)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:348)
> at org.jgroups.protocols.UDP.start(UDP.java:266)
> at
> org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:553)
> at org.jgroups.JChannel.connect(JChannel.java:288)
> at org.jgroups.JChannel.connect(JChannel.java:279)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:397)
> ... 16 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9675) CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
[
https://issues.apache.org/jira/browse/GEODE-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9675:
-
Labels: flaky-test pull-request-available (was: pull-request-available)
> CI: ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> -
>
> Key: GEODE-9675
> URL: https://issues.apache.org/jira/browse/GEODE-9675
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.15.0
>Reporter: Xiaojian Zhou
>Assignee: Bill Burcham
>Priority: Major
> Labels: flaky-test, pull-request-available
> Fix For: 1.15.0
>
> Attachments: screenshot-1.png
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1983
> {code:java}
> ClusterDistributionManagerDUnitTest > testConnectAfterBeingShunned FAILED
> org.apache.geode.SystemConnectException: Problem starting up membership
> services
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:466)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:499)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:328)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:757)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:133)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3013)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:283)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:209)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:180)
> at
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:256)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManagerDUnitTest.testConnectAfterBeingShunned(ClusterDistributionManagerDUnitTest.java:170)
> Caused by:
>
> org.apache.geode.distributed.internal.membership.api.MemberStartupException:
> unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:401)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:203)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership.start(GMSMembership.java:1642)
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:171)
> ... 13 more
> Caused by:
> java.lang.Exception: failed to open a port in range 41003-41003
> at
> org.jgroups.protocols.UDP.createMulticastSocketWithBindPort(UDP.java:503)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:348)
> at org.jgroups.protocols.UDP.start(UDP.java:266)
> at
> org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:553)
> at org.jgroups.JChannel.connect(JChannel.java:288)
> at org.jgroups.JChannel.connect(JChannel.java:279)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.start(JGroupsMessenger.java:397)
> ... 16 more
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9606) CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9606: - Component/s: tests > CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with > AssertionError > --- > > Key: GEODE-9606 > URL: https://issues.apache.org/jira/browse/GEODE-9606 > Project: Geode > Issue Type: Bug > Components: redis, tests >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The following failure occurred in a CI run: > org.apache.geode.redis.internal.executor.pubsub.PubSubIntegrationTest > > testPatternWithoutAGlob FAILED > java.lang.AssertionError: > Expecting actual: > [] > to contain exactly (and in same order): > ["hello"] > but could not find the following elements: > ["hello"] > at > org.apache.geode.redis.internal.executor.pubsub.AbstractPubSubIntegrationTest.testPatternWithoutAGlob(AbstractPubSubIntegrationTest.java:774) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > 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:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapte
[jira] [Updated] (GEODE-9606) CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with AssertionError
[ https://issues.apache.org/jira/browse/GEODE-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9606: - Labels: flaky-test pull-request-available unreleased (was: pull-request-available) > CI Failure: PubSubIntegrationTest.testPatternWithoutAGlob fails with > AssertionError > --- > > Key: GEODE-9606 > URL: https://issues.apache.org/jira/browse/GEODE-9606 > Project: Geode > Issue Type: Bug > Components: redis, tests >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Priority: Major > Labels: flaky-test, pull-request-available, unreleased > Fix For: 1.15.0 > > > The following failure occurred in a CI run: > org.apache.geode.redis.internal.executor.pubsub.PubSubIntegrationTest > > testPatternWithoutAGlob FAILED > java.lang.AssertionError: > Expecting actual: > [] > to contain exactly (and in same order): > ["hello"] > but could not find the following elements: > ["hello"] > at > org.apache.geode.redis.internal.executor.pubsub.AbstractPubSubIntegrationTest.testPatternWithoutAGlob(AbstractPubSubIntegrationTest.java:774) > 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:59) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) > 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.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) > at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) > at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at > org.apache.geode.test.junit.rules.serializable.SerializableExternalResource$1.evaluate(SerializableExternalResource.java:38) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) > at org.junit.runners.ParentRunner.run(ParentRunner.java:413) > 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:36) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) > at > org.gradle.inte
[jira] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9528:
-
Component/s: tests
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership, tests
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.9, 1.13.8, 1.14.4, 1.15.0
>
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> 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.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9506:
-
Labels: flaky-test pull-request-available unreleased (was: flaky-test
pull-request-available)
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: flaky-test, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> 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
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9506:
-
Component/s: tests
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Donal Evans
>Priority: Major
> Labels: flaky-test, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> 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
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9442: - Labels: pull-request-available unreleased (was: pull-request-available) > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis, tests >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redis container wit
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9442: - Component/s: tests > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis, tests >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redis container with exposed port 6379 -> 33290 > Someone has more knowledge of redis
[jira] [Updated] (GEODE-9299) CI Failure: WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
[
https://issues.apache.org/jira/browse/GEODE-9299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9299:
-
Component/s: tests
> CI Failure:
> WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover >
> testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> --
>
> Key: GEODE-9299
> URL: https://issues.apache.org/jira/browse/GEODE-9299
> Project: Geode
> Issue Type: Bug
> Components: tests, wan
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover
> > testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover[from_v1.12.2]
> FAILED
> java.lang.AssertionError: expected:<100> but was:<101>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.stopSenderAndVerifyEvents(WANRollingUpgradeDUnitTest.java:227)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover(WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover.java:98)
> {code}
> CI Failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/229#B
> Artifacts Available here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0253/test-results/upgradeTest/1621635640/
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Component/s: tests
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9252:
-
Labels: flaky-test pull-request-available unreleased (was:
pull-request-available unreleased)
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: flaky-test, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9069:
-
Component/s: tests
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161436/distributedtestfiles-OpenJDK11-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-8719:
-
Component/s: tests
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test
> Fix For: 1.15.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9069) CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest > testConcurrentHExists_whileAddingValues FAILED
[
https://issues.apache.org/jira/browse/GEODE-9069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-9069:
-
Labels: pull-request-available unreleased (was: pull-request-available)
> CI Failure: org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> ---
>
> Key: GEODE-9069
> URL: https://issues.apache.org/jira/browse/GEODE-9069
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Reporter: Jens Deppe
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available, unreleased
> Fix For: 1.14.0, 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest >
> testConcurrentHExists_whileAddingValues FAILED
> 00:56:20java.lang.RuntimeException:
> java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:77)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.runInLockstep(ConcurrentLoopingThreads.java:96)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.testConcurrentHExists_whileAddingValues(HExistsDUnitTest.java:121)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.ExecutionException:
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> java.util.concurrent.FutureTask.report(FutureTask.java:122)
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:205)
> 00:56:20at
> org.apache.geode.redis.ConcurrentLoopingThreads.await(ConcurrentLoopingThreads.java:73)
> 00:56:20... 2 more
> 00:56:20
> 00:56:20Caused by:
> 00:56:20org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest that uses
> java.lang.String, java.lang.Stringjava.lang.Integer null within 1 seconds.
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:56:20at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:56:20at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:56:20at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:56:20at
> org.apache.geode.redis.internal.executor.hash.HExistsDUnitTest.lambda$testConcurrentHExists_whileAddingValues$5(HExistsDUnitTest.java:120)
> 00:56:20
> 00:56:20Caused by:
> 00:56:20java.util.concurrent.TimeoutException
> 00:56:20at
> java.util.concurrent.FutureTask.get(FutureTask.java:204)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:101)
> 00:56:20at
> org.awaitility.core.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:81)
> 00:56:20at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:101)
> 00:56:20... 5 more {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161436/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161436/distributedtestfiles-OpenJDK11-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne updated GEODE-8719:
-
Labels: flaky-test unreleased (was: flaky-test)
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis, tests
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test, unreleased
> Fix For: 1.15.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-6751: - Component/s: tests > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management, tests >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Assignee: Nabarun Nag >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.16.0 > > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10066) SSL handshake failures on 1 locator prevents connection pool from trying other locators
Jacob Barrett created GEODE-10066:
-
Summary: SSL handshake failures on 1 locator prevents connection
pool from trying other locators
Key: GEODE-10066
URL: https://issues.apache.org/jira/browse/GEODE-10066
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: Jacob Barrett
If an {{SSLException}} is thrown when handshaking with a locator the exception
is wrapped in an {{IllegalStateException}} that is not caught by the connection
pool, the stack is blown, and no connections can be established. If not wrapped
the connection pool will properly try the next locator.
The {{SSLExceptions}} are wrapped in at least {{TcpClient.getServerVersion()}}
but other locations may exist in this path. This method throws {{IOException}}
and the {{SSLExceptions}} extend {{IOExceptions}} so they should not be
wrapped. It probably makes sense to split the concern of socket connection from
determining the server version in {{TcpClient.getServerVersion()}}.
{noformat}
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
No subject alternative names matching IP address 10.2.8.12 found
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310)
at
sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639)
at
sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
at
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
at
org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:594)
at
org.apache.geode.internal.net.SCAdvancedSocketCreator.connect(SCAdvancedSocketCreator.java:83)
at
org.apache.geode.distributed.internal.tcpserver.ClusterSocketCreatorImpl.connect(ClusterSocketCreatorImpl.java:96)
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.getServerVersion(TcpClient.java:246)
at
org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:151)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:227)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:217)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:264)
at
org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:176)
at
org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:211)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:282)
at
org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:940)
at
org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:464)
at
org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:105)
at
org.apache.geode.cache.wan.internal.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:66)
at
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1107)
at
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1081)
Caused by: java.security.cert.CertificateException: No subject alternative
names matching IP address 10.2.8.12 found
at sun.security.util.HostnameChecker.matchIP(HostnameChecker.java:168)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:94)
at
sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java
[jira] [Updated] (GEODE-10066) SSL handshake failures on 1 locator prevents connection pool from trying other locators
[
https://issues.apache.org/jira/browse/GEODE-10066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10066:
--
Labels: needsTriage (was: )
> SSL handshake failures on 1 locator prevents connection pool from trying
> other locators
> ---
>
> Key: GEODE-10066
> URL: https://issues.apache.org/jira/browse/GEODE-10066
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Jacob Barrett
>Priority: Major
> Labels: needsTriage
>
> If an {{SSLException}} is thrown when handshaking with a locator the
> exception is wrapped in an {{IllegalStateException}} that is not caught by
> the connection pool, the stack is blown, and no connections can be
> established. If not wrapped the connection pool will properly try the next
> locator.
> The {{SSLExceptions}} are wrapped in at least
> {{TcpClient.getServerVersion()}} but other locations may exist in this path.
> This method throws {{IOException}} and the {{SSLExceptions}} extend
> {{IOExceptions}} so they should not be wrapped. It probably makes sense to
> split the concern of socket connection from determining the server version in
> {{TcpClient.getServerVersion()}}.
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative names matching IP address 10.2.8.12 found
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639)
> at
> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:594)
> at
> org.apache.geode.internal.net.SCAdvancedSocketCreator.connect(SCAdvancedSocketCreator.java:83)
> at
> org.apache.geode.distributed.internal.tcpserver.ClusterSocketCreatorImpl.connect(ClusterSocketCreatorImpl.java:96)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.getServerVersion(TcpClient.java:246)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:151)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:227)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:217)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:264)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:176)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:211)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:282)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:940)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:464)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:105)
> at
> org.apache.geode.cache.wan.internal.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:66)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1107)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySender
[jira] [Updated] (GEODE-9984) Mass-Test-Run: WanCopyRegionCommandDUnitTest > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED
[ https://issues.apache.org/jira/browse/GEODE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-9984: - Labels: flaky-test pull-request-available (was: needsTriage pull-request-available) > Mass-Test-Run: WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted FAILED > - > > Key: GEODE-9984 > URL: https://issues.apache.org/jira/browse/GEODE-9984 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Kristen >Assignee: Alberto Gomez >Priority: Major > Labels: flaky-test, pull-request-available > > WanCopyRegionCommandDUnitTest > > testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(true, true) [0] FAILED > org.opentest4j.AssertionFailedError: > expected: 5 > but was: 50001 > 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.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testCommandDoesNotCopyEntriesUpdatedAfterCommandStarted(WanCopyRegionCommandDUnitTest.java:884) > 948 tests completed, 1 failed, 59 skipped > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0806/test-artifacts/1642850654/distributedtestfiles-openjdk8-1.15.0-build.0806.tgz*] > > > > May be an issue similar or related to > https://issues.apache.org/jira/browse/GEODE-9859. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9859) Mass-Test-Run: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer updated GEODE-9859:
-
Labels: pull-request-available (was: needsTriage pull-request-available)
> Mass-Test-Run:
> WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false,
> false) [0] FAILED
>
>
> Key: GEODE-9859
> URL: https://issues.apache.org/jira/browse/GEODE-9859
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Mark Hanson
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Looks like this might be failing from the original PR. I have linked to
> GEODE-9369 as the most likely origination.
>
> {noformat}
> WanCopyRegionCommandDUnitTest > testRegionDestroyedDuringExecution(false,
> false) [0] FAILED
> java.lang.AssertionError:
> Expecting elements:
> ["Execution failed. Error:
> org.apache.geode.cache.EntryDestroyedException: 937"]
> to have exactly 1 times execution error
> at
> org.apache.geode.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(WanCopyRegionCommandDUnitTest.java:450)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[
https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494855#comment-17494855
]
Barrett Oglesby commented on GEODE-9910:
Here is some analysis of this issue.
h3. Server Addresses
node 1:
membership: 10.196.55.141(15661):42000
locator: 10.196.55.141:10335
node 2:
membership: 10.196.55.142(19002):42000
locator: 10.196.55.142:10335
h3. Node2 Initial Disconnect
node2 lost connectivity with node1 and removed it:
{noformat}
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Availability check failed for member
10.196.55.141(15661):42000
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Requesting removal of suspect member
10.196.55.141(15661):42000
2021-11-28 04:03:45,085 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] This member is becoming the membership coordinator with
address 10.196.55.142(19002):42000
{noformat}
It then realized that quorum had been lost (node1 was coordinator with
weight=15; node2 was not coordinator with weight=10):
{noformat}
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] View Creator thread is starting
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] 10.196.55.141(15661):42000 had a weight
of 15
2021-11-28 04:03:45,092 WARN
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] total weight lost in this view change is 15 of 25.
Quorum has been lost!
2021-11-28 04:03:45,092 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Possible loss of quorum due to the loss of 1 cache
processes: [10.196.55.141(15661):42000]
{noformat}
And disconnected itself from the distributed system:
{noformat}
2021-11-28 04:03:46,093 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Membership service failure: Exiting due to possible
network partition event due to loss of 1 cache processes:
[10.196.55.141(15661):42000]
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Exiting due to possible network partition event due to loss of 1 cache
processes: [10.196.55.141(15661):42000]
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2588)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2204)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2286)
[geode-membership-1.14.0.jar:?]
{noformat}
It stopped its locator:
{noformat}
2021-11-28 04:03:46,794 INFO
[org.apache.geode.distributed.internal.InternalLocator]-[ReconnectThread] []
Distribution Locator on
vmw-hcs-248e71fd-dd76-4111-ba82-379151aabbb7-3000-1-node-2/10.196.55.142 is
stopped{noformat}
h3. Node2 Reconnect Attempt 1
{noformat}
2021-11-28 04:04:46,800 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] Attempting to reconnect to the distributed system. This is attempt #1.
{noformat}
The first retry attempt failed to get quorum (it needed a weight of 13 but is
10):
{noformat}
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] performing a quorum check to see if location services can be started early
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] beginning quorum check with GMSQuorumChecker on view
View[10.196.55.141(15661):42000|1] members:
[10.196.55.141(15661):42000{lead}, 10.196.55.142(19002):42000]
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] quorum check: sending request to 10.196.55.141(15661):42000
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distr
[jira] [Comment Edited] (GEODE-9910) Failure to auto-reconnect upon network partition
[
https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494855#comment-17494855
]
Barrett Oglesby edited comment on GEODE-9910 at 2/19/22, 12:41 AM:
---
Here is some analysis of this issue.
h3. Server Addresses
node 1:
membership: 10.196.55.141(15661):42000
locator: 10.196.55.141:10335
node 2:
membership: 10.196.55.142(19002):42000
locator: 10.196.55.142:10335
h3. Node2 Initial Disconnect
node2 lost connectivity with node1 and removed it:
{noformat}
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Availability check failed for member
10.196.55.141(15661):42000
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Requesting removal of suspect member
10.196.55.141(15661):42000
2021-11-28 04:03:45,085 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] This member is becoming the membership coordinator with
address 10.196.55.142(19002):42000
{noformat}
It then realized that quorum had been lost (node1 was coordinator with
weight=15; node2 was not coordinator with weight=10):
{noformat}
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] View Creator thread is starting
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] 10.196.55.141(15661):42000 had a weight
of 15
2021-11-28 04:03:45,092 WARN
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] total weight lost in this view change is 15 of 25.
Quorum has been lost!
2021-11-28 04:03:45,092 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Possible loss of quorum due to the loss of 1 cache
processes: [10.196.55.141(15661):42000]
{noformat}
And disconnected itself from the distributed system:
{noformat}
2021-11-28 04:03:46,093 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Membership service failure: Exiting due to possible
network partition event due to loss of 1 cache processes:
[10.196.55.141(15661):42000]
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Exiting due to possible network partition event due to loss of 1 cache
processes: [10.196.55.141(15661):42000]
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2588)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2204)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2286)
[geode-membership-1.14.0.jar:?]
{noformat}
It stopped its locator:
{noformat}
2021-11-28 04:03:46,794 INFO
[org.apache.geode.distributed.internal.InternalLocator]-[ReconnectThread] []
Distribution Locator on
vmw-hcs-248e71fd-dd76-4111-ba82-379151aabbb7-3000-1-node-2/10.196.55.142 is
stopped{noformat}
h3. Node2 Reconnect Attempt 1
{noformat}
2021-11-28 04:04:46,800 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] Attempting to reconnect to the distributed system. This is attempt #1.
{noformat}
The first reconnect attempt failed to get quorum (it needed a weight of 13 but
is 10):
{noformat}
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] performing a quorum check to see if location services can be started early
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] beginning quorum check with GMSQuorumChecker on view
View[10.196.55.141(15661):42000|1] members:
[10.196.55.141(15661):42000{lead}, 10.196.55.142(19002):42000]
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] quorum check: sending request to 10.196.55.141(15661):420
[jira] [Comment Edited] (GEODE-9910) Failure to auto-reconnect upon network partition
[
https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494855#comment-17494855
]
Barrett Oglesby edited comment on GEODE-9910 at 2/19/22, 12:42 AM:
---
Here is some analysis of this issue.
h3. Server Addresses
node 1:
membership: 10.196.55.141(15661):42000
locator: 10.196.55.141:10335
node 2:
membership: 10.196.55.142(19002):42000
locator: 10.196.55.142:10335
h3. Node2 Initial Disconnect
node2 lost connectivity with node1 and removed it:
{noformat}
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Availability check failed for member
10.196.55.141(15661):42000
2021-11-28 04:03:45,084 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] Requesting removal of suspect member
10.196.55.141(15661):42000
2021-11-28 04:03:45,085 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode Failure
Detection thread 9] [] This member is becoming the membership coordinator with
address 10.196.55.142(19002):42000
{noformat}
It then realized that quorum had been lost (node1 was coordinator with
weight=15; node2 was not coordinator with weight=10):
{noformat}
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] View Creator thread is starting
2021-11-28 04:03:45,091 INFO
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] 10.196.55.141(15661):42000 had a weight
of 15
2021-11-28 04:03:45,092 WARN
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] total weight lost in this view change is 15 of 25.
Quorum has been lost!
2021-11-28 04:03:45,092 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Possible loss of quorum due to the loss of 1 cache
processes: [10.196.55.141(15661):42000]
{noformat}
And disconnected itself from the distributed system:
{noformat}
2021-11-28 04:03:46,093 FATAL
[org.apache.geode.distributed.internal.membership.gms.Services]-[Geode
Membership View Creator] [] Membership service failure: Exiting due to possible
network partition event due to loss of 1 cache processes:
[10.196.55.141(15661):42000]
org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
Exiting due to possible network partition event due to loss of 1 cache
processes: [10.196.55.141(15661):42000]
at
org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1787)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1300(GMSJoinLeave.java:80)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2588)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2204)
[geode-membership-1.14.0.jar:?]
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2286)
[geode-membership-1.14.0.jar:?]
{noformat}
It stopped its locator:
{noformat}
2021-11-28 04:03:46,794 INFO
[org.apache.geode.distributed.internal.InternalLocator]-[ReconnectThread] []
Distribution Locator on
vmw-hcs-248e71fd-dd76-4111-ba82-379151aabbb7-3000-1-node-2/10.196.55.142 is
stopped{noformat}
h3. Node2 Reconnect Attempt 1
{noformat}
2021-11-28 04:04:46,800 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] Attempting to reconnect to the distributed system. This is attempt #1.
{noformat}
The first reconnect attempt failed to get quorum (it needed a weight of 13 but
is 10):
{noformat}
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread]
[] performing a quorum check to see if location services can be started early
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] beginning quorum check with GMSQuorumChecker on view
View[10.196.55.141(15661):42000|1] members:
[10.196.55.141(15661):42000{lead}, 10.196.55.142(19002):42000]
2021-11-28 04:04:46,810 INFO
[org.apache.geode.distributed.internal.membership.gms.messenger.GMSQuorumChecker]-[ReconnectThread]
[] quorum check: sending request to 10.196.55.141(15661):420
[jira] [Created] (GEODE-10067) WANCopyRegionFunctionDelegate needs to be optimized to handle large regions
Udo Kohlmeyer created GEODE-10067: - Summary: WANCopyRegionFunctionDelegate needs to be optimized to handle large regions Key: GEODE-10067 URL: https://issues.apache.org/jira/browse/GEODE-10067 Project: Geode Issue Type: Improvement Components: wan Affects Versions: 1.15.0, 1.16.0 Reporter: Udo Kohlmeyer The current WanCopyRegionFunctionDelegate may cause significant memory issues in with really large regions. The [getEntries|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L102] method returns both primary and redundant Region Entries for local server. The invocation of getEntries from the PartitionedRegionDataStore will cause all entries to be deserialized https://github.com/apache/geode/blob/develop/geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegionDataStore.java#L2501-L2515 The [createBatch|https://github.com/apache/geode/blob/develop/geode-wan/src/main/java/org/apache/geode/management/internal/cli/functions/WanCopyRegionFunctionDelegate.java#L107-L108] method creates a List equally that of the local Region size. Essentially ... In a system with VERY large regions this might cause significant memory issues -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494856#comment-17494856 ] Barrett Oglesby commented on GEODE-9910: With a modification to the product to simulate a failed JoinRequestMessage, I can reproduce this issue. h3. Test # Start server 1 (becomes coordinator) # Start server 2 # Play dead server 2 # The servers disconnect from each other # Server 2 disconnects from the distributed system since it doesn't have quorum When server 2 reconnects, it: - establishes quorum - starts the locator - is unable to join the distributed system (due to the modification I made) - attempts to reconnect again - fails because the locator is already started > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, needsTriage > Attachments: geode-logs.zip > > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2326) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1187) > ~[geode-membership-1.14.0.jar:?] > at
[jira] [Created] (GEODE-10068) Make WanCopyRegionFunctionService thread pool configurable through configuration or property
Udo Kohlmeyer created GEODE-10068: - Summary: Make WanCopyRegionFunctionService thread pool configurable through configuration or property Key: GEODE-10068 URL: https://issues.apache.org/jira/browse/GEODE-10068 Project: Geode Issue Type: Improvement Components: wan Affects Versions: 1.15.0, 1.16.0 Reporter: Udo Kohlmeyer The current implementation of `WanCopyRegionFunctionService` creates a fixed thread pool of size 10. This is possibly something that one would like to be able to configure. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10069) WanCopyRegionCommand currently targets all members in cluster
Udo Kohlmeyer created GEODE-10069: - Summary: WanCopyRegionCommand currently targets all members in cluster Key: GEODE-10069 URL: https://issues.apache.org/jira/browse/GEODE-10069 Project: Geode Issue Type: Improvement Components: wan Affects Versions: 1.15.0, 1.16.0 Reporter: Udo Kohlmeyer The current implementation of `WanCopyRegionCommand` will execute on all members. This could possibly be improved by targeting a single member, which then has the ability to determine if the wan copy functionality needs to run on a single member (in the case of Replicate regions) or across multiple members (in the case of Partitioned Regions). In addition, initiating function also has the ability to invoke the function using `onRegion` which then allows for the targeting of primary data only vs the current implementation which (perceivably) targets primary and redundant bucket data -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10070) Add method onto InternalGatewaySender to send batch
Udo Kohlmeyer created GEODE-10070: - Summary: Add method onto InternalGatewaySender to send batch Key: GEODE-10070 URL: https://issues.apache.org/jira/browse/GEODE-10070 Project: Geode Issue Type: Improvement Components: wan Affects Versions: 1.15.0, 1.16.0 Reporter: Udo Kohlmeyer In the current Wan Copy feature, the `WanCopyRegionFunctionDelegate` has to: # Create a ConnectionState # retrieve the GatewaySenderEventDispatcher off the AbstractGatewaySender # Send batch and handle all exception handling related to the sending of a batch This functionality is really something that needs to be consolidated into a single location for reuse. Having the ability to get into guts of the system to send batches and possibly affect how errors are handled in an inconsistent manner (in comparison to the normal GatewaySender flow) can lead to many problems. Not exposing the sendBatch logic and complexity would be much simpler and more consistent in behavior. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10071) Remove the dependency that WanCopyRegionFunction has on WanCopyRegionCommand
Udo Kohlmeyer created GEODE-10071: - Summary: Remove the dependency that WanCopyRegionFunction has on WanCopyRegionCommand Key: GEODE-10071 URL: https://issues.apache.org/jira/browse/GEODE-10071 Project: Geode Issue Type: Improvement Components: wan Affects Versions: 1.15.0, 1.16.0 Reporter: Udo Kohlmeyer There is a cyclical dependency between the Command and the implementing function for the Wan copy feature. Logically, the command needs to have a dependency on the function. The error messages currently defined in the Command class need to be moved to the function class where they are used. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10066) SSL handshake failures on 1 locator prevents connection pool from trying other locators
[
https://issues.apache.org/jira/browse/GEODE-10066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-10066:
--
Affects Version/s: 1.15.0
1.16.0
> SSL handshake failures on 1 locator prevents connection pool from trying
> other locators
> ---
>
> Key: GEODE-10066
> URL: https://issues.apache.org/jira/browse/GEODE-10066
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.15.0, 1.16.0
>Reporter: Jacob Barrett
>Priority: Major
> Labels: needsTriage
>
> If an {{SSLException}} is thrown when handshaking with a locator the
> exception is wrapped in an {{IllegalStateException}} that is not caught by
> the connection pool, the stack is blown, and no connections can be
> established. If not wrapped the connection pool will properly try the next
> locator.
> The {{SSLExceptions}} are wrapped in at least
> {{TcpClient.getServerVersion()}} but other locations may exist in this path.
> This method throws {{IOException}} and the {{SSLExceptions}} extend
> {{IOExceptions}} so they should not be wrapped. It probably makes sense to
> split the concern of socket connection from determining the server version in
> {{TcpClient.getServerVersion()}}.
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative names matching IP address 10.2.8.12 found
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310)
> at
> sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639)
> at
> sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:594)
> at
> org.apache.geode.internal.net.SCAdvancedSocketCreator.connect(SCAdvancedSocketCreator.java:83)
> at
> org.apache.geode.distributed.internal.tcpserver.ClusterSocketCreatorImpl.connect(ClusterSocketCreatorImpl.java:96)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.getServerVersion(TcpClient.java:246)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpClient.requestToServer(TcpClient.java:151)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocatorUsingConnection(AutoConnectionSourceImpl.java:227)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryOneLocator(AutoConnectionSourceImpl.java:217)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.queryLocators(AutoConnectionSourceImpl.java:264)
> at
> org.apache.geode.cache.client.internal.AutoConnectionSourceImpl.findServer(AutoConnectionSourceImpl.java:176)
> at
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:211)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:196)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.createPooledConnection(ConnectionManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:282)
> at
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:940)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:464)
> at
> org.apache.geode.cache.wan.internal.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:105)
> at
> org.apache.geode.cache.wan.internal.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:66)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1107)
> at
> org.apache.geode.internal.cache.wan.Abst
