[jira] [Created] (GEODE-10213) Remove kirklund from codeowner areas of less knowledge
Kirk Lund created GEODE-10213: - Summary: Remove kirklund from codeowner areas of less knowledge Key: GEODE-10213 URL: https://issues.apache.org/jira/browse/GEODE-10213 Project: Geode Issue Type: Wish Reporter: Kirk Lund Remove kirklund from codeowner areas of less knowledge -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor
[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10211: --- Labels: GeodeOperationAPI blocks-1.15.0 pull-request-available (was: GeodeOperationAPI blocks-1.15.0) > A retried operation does not set possible duplicate in the event if retried > on an accessor > -- > > Key: GEODE-10211 > URL: https://issues.apache.org/jira/browse/GEODE-10211 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available > > In geode, or persistent region, it is possible that all persistent copies > went offline. So possible duplicate should be set in the event, even though > no members has the event in the event tracker. > Currently, the code handling this will miss the setting if the retry occurs > on an accessor (localMaxMemory set to 0) case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10212) In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the t
[
https://issues.apache.org/jira/browse/GEODE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby resolved GEODE-10212.
-
Resolution: Duplicate
> In a WAN topology with 3 sites in a star pattern, stopping a sender between
> two of the sites causes an event to be dropped even though another path
> exists between the two sites
>
>
> Key: GEODE-10212
> URL: https://issues.apache.org/jira/browse/GEODE-10212
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage
>
> A WAN topology in a star pattern means every site is connected to every other
> site like:
> {noformat}
> site-A <--> site-B <--> siteC
> ^_^
> {noformat}
> If the sender from site-A to site-B is stopped and a put is done in site-A,
> site-B doesn't receive the event even though site-A is connected to site-C
> and site-C is connected to site-B.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516170#comment-17516170 ] Geode Integration commented on GEODE-10151: --- Seen in [test-examples #298|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/298]. > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-10151. --- Resolution: Fixed > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516169#comment-17516169 ] ASF subversion and git services commented on GEODE-10151: - Commit 750e6e6e0f75913e137548ecb7618d5b04ec9de1 in geode-examples's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=750e6e6 ] GEODE-10151: Extract redis before start The redis distribution needs to be extracted *before* starting the geode servers, to ensure it's actually available to be on the classpath. Before this change, the tests would sometimes pass depending on the order of execution of these tasks. > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10212) In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the t
[
https://issues.apache.org/jira/browse/GEODE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby reassigned GEODE-10212:
---
Assignee: Barrett Oglesby
> In a WAN topology with 3 sites in a star pattern, stopping a sender between
> two of the sites causes an event to be dropped even though another path
> exists between the two sites
>
>
> Key: GEODE-10212
> URL: https://issues.apache.org/jira/browse/GEODE-10212
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barrett Oglesby
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: needsTriage
>
> A WAN topology in a star pattern means every site is connected to every other
> site like:
> {noformat}
> site-A <--> site-B <--> siteC
> ^_^
> {noformat}
> If the sender from site-A to site-B is stopped and a put is done in site-A,
> site-B doesn't receive the event even though site-A is connected to site-C
> and site-C is connected to site-B.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10212) In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the tw
[
https://issues.apache.org/jira/browse/GEODE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby updated GEODE-10212:
Description:
A WAN topology in a star pattern means every site is connected to every other
site like:
{noformat}
site-A <--> site-B <--> siteC
^_^
{noformat}
If the sender from site-A to site-B is stopped and a put is done in site-A,
site-B doesn't receive the event even though site-A is connected to site-C and
site-C is connected to site-B.
was:
A WAN topology in a star pattern means every site is connected to every other
site like:
site-A <-> site-B <-> siteC
^_^
If the sender from site-A to site-B is stopped and a put is done in site-A,
site-B doesn't receive the event even though site-A is connected to site-C and
site-C is connected to site-B.
> In a WAN topology with 3 sites in a star pattern, stopping a sender between
> two of the sites causes an event to be dropped even though another path
> exists between the two sites
>
>
> Key: GEODE-10212
> URL: https://issues.apache.org/jira/browse/GEODE-10212
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barrett Oglesby
>Priority: Major
> Labels: needsTriage
>
> A WAN topology in a star pattern means every site is connected to every other
> site like:
> {noformat}
> site-A <--> site-B <--> siteC
> ^_^
> {noformat}
> If the sender from site-A to site-B is stopped and a put is done in site-A,
> site-B doesn't receive the event even though site-A is connected to site-C
> and site-C is connected to site-B.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516167#comment-17516167 ] Geode Integration commented on GEODE-10151: --- Seen in [test-examples #297|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/297]. > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10212) In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the tw
[ https://issues.apache.org/jira/browse/GEODE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10212: -- Labels: needsTriage (was: ) > In a WAN topology with 3 sites in a star pattern, stopping a sender between > two of the sites causes an event to be dropped even though another path > exists between the two sites > > > Key: GEODE-10212 > URL: https://issues.apache.org/jira/browse/GEODE-10212 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Barrett Oglesby >Priority: Major > Labels: needsTriage > > A WAN topology in a star pattern means every site is connected to every other > site like: > site-A <-> site-B <-> siteC > ^_^ > If the sender from site-A to site-B is stopped and a put is done in site-A, > site-B doesn't receive the event even though site-A is connected to site-C > and site-C is connected to site-B. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10212) In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the tw
Barrett Oglesby created GEODE-10212: --- Summary: In a WAN topology with 3 sites in a star pattern, stopping a sender between two of the sites causes an event to be dropped even though another path exists between the two sites Key: GEODE-10212 URL: https://issues.apache.org/jira/browse/GEODE-10212 Project: Geode Issue Type: Bug Components: wan Reporter: Barrett Oglesby A WAN topology in a star pattern means every site is connected to every other site like: site-A <-> site-B <-> siteC ^_^ If the sender from site-A to site-B is stopped and a put is done in site-A, site-B doesn't receive the event even though site-A is connected to site-C and site-C is connected to site-B. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10179) bump jackson-databind to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols updated GEODE-10179: - Fix Version/s: (was: 1.12.10) (was: 1.13.9) > bump jackson-databind to recommended version > > > Key: GEODE-10179 > URL: https://issues.apache.org/jira/browse/GEODE-10179 > Project: Geode > Issue Type: Task >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0 > > > recommend getting to 2.13.2.1 for develop or 2.12.6.1 for support branches -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10179) bump jackson-databind to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516159#comment-17516159 ] ASF subversion and git services commented on GEODE-10179: - Commit f1c5efad6404ef544e43bf83c6bedd38b38bca03 in geode's branch refs/heads/support/1.13 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f1c5efa ] Revert "[1.13] GEODE-10179: Bump jackson-databind from 2.10.5.1 to 2.12.6.1 (#7503)" Fixed by mistake. We should discuss before bumping a 3rd party minor in a patch release. This reverts commit 7e18d73c478853c5d8b78c5b2c0b8124b036c493. > bump jackson-databind to recommended version > > > Key: GEODE-10179 > URL: https://issues.apache.org/jira/browse/GEODE-10179 > Project: Geode > Issue Type: Task >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > recommend getting to 2.13.2.1 for develop or 2.12.6.1 for support branches -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10179) bump jackson-databind to recommended version
[ https://issues.apache.org/jira/browse/GEODE-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516158#comment-17516158 ] ASF subversion and git services commented on GEODE-10179: - Commit f271b5335c4761b383297be4e7f858492ecd564e in geode's branch refs/heads/support/1.12 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f271b53 ] Revert "GEODE-10179: Bump jackson-databind from 2.10.5.1 to 2.12.6.1 (#7506)" Fixed by mistake. We should discuss before bumping a 3rd party minor in a patch release. This reverts commit 36d9260d8180f4a83c95f723600d556fb2dc02d8. > bump jackson-databind to recommended version > > > Key: GEODE-10179 > URL: https://issues.apache.org/jira/browse/GEODE-10179 > Project: Geode > Issue Type: Task >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.12.10, 1.13.9, 1.14.5, 1.15.0 > > > recommend getting to 2.13.2.1 for develop or 2.12.6.1 for support branches -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor
[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10211: - Labels: GeodeOperationAPI blocks-1.15.0 (was: needsTriage) > A retried operation does not set possible duplicate in the event if retried > on an accessor > -- > > Key: GEODE-10211 > URL: https://issues.apache.org/jira/browse/GEODE-10211 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Reporter: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0 > > In geode, or persistent region, it is possible that all persistent copies > went offline. So possible duplicate should be set in the event, even though > no members has the event in the event tracker. > Currently, the code handling this will miss the setting if the retry occurs > on an accessor (localMaxMemory set to 0) case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor
[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10211: Assignee: Eric Shu > A retried operation does not set possible duplicate in the event if retried > on an accessor > -- > > Key: GEODE-10211 > URL: https://issues.apache.org/jira/browse/GEODE-10211 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeOperationAPI, blocks-1.15.0 > > In geode, or persistent region, it is possible that all persistent copies > went offline. So possible duplicate should be set in the event, even though > no members has the event in the event tracker. > Currently, the code handling this will miss the setting if the retry occurs > on an accessor (localMaxMemory set to 0) case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor
[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10211: -- Labels: needsTriage (was: ) > A retried operation does not set possible duplicate in the event if retried > on an accessor > -- > > Key: GEODE-10211 > URL: https://issues.apache.org/jira/browse/GEODE-10211 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Reporter: Eric Shu >Priority: Major > Labels: needsTriage > > In geode, or persistent region, it is possible that all persistent copies > went offline. So possible duplicate should be set in the event, even though > no members has the event in the event tracker. > Currently, the code handling this will miss the setting if the retry occurs > on an accessor (localMaxMemory set to 0) case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor
Eric Shu created GEODE-10211: Summary: A retried operation does not set possible duplicate in the event if retried on an accessor Key: GEODE-10211 URL: https://issues.apache.org/jira/browse/GEODE-10211 Project: Geode Issue Type: Bug Components: persistence, regions Reporter: Eric Shu In geode, or persistent region, it is possible that all persistent copies went offline. So possible duplicate should be set in the event, even though no members has the event in the event tracker. Currently, the code handling this will miss the setting if the retry occurs on an accessor (localMaxMemory set to 0) case. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10204) Add unit test cases for SizeableByteArrayList
[
https://issues.apache.org/jira/browse/GEODE-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10204:
Description: For example, {{clearSublist()}} was added for LTRIM support
and needs unit tests. Any public method that does not just call the {{super()}}
method on {{LinkedList}} should have coverage. (was: For example,
clearSublist() was added for LTRIM support and needs tests. Any public method
without tests should have coverage.)
> Add unit test cases for SizeableByteArrayList
> -
>
> Key: GEODE-10204
> URL: https://issues.apache.org/jira/browse/GEODE-10204
> Project: Geode
> Issue Type: Test
> Components: redis
>Reporter: Ray Ingles
>Priority: Major
>
> For example, {{clearSublist()}} was added for LTRIM support and needs unit
> tests. Any public method that does not just call the {{super()}} method on
> {{LinkedList}} should have coverage.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10204) Add unit test cases for SizeableByteArrayList
[
https://issues.apache.org/jira/browse/GEODE-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-10204:
Affects Version/s: 1.15.0
> Add unit test cases for SizeableByteArrayList
> -
>
> Key: GEODE-10204
> URL: https://issues.apache.org/jira/browse/GEODE-10204
> Project: Geode
> Issue Type: Test
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> For example, {{clearSublist()}} was added for LTRIM support and needs unit
> tests. Any public method that does not just call the {{super()}} method on
> {{LinkedList}} should have coverage.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10204) Add unit test cases for SizeableByteArrayList
[ https://issues.apache.org/jira/browse/GEODE-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-10204: Summary: Add unit test cases for SizeableByteArrayList (was: Add test cases for SizeableByteArray) > Add unit test cases for SizeableByteArrayList > - > > Key: GEODE-10204 > URL: https://issues.apache.org/jira/browse/GEODE-10204 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Ray Ingles >Priority: Major > > For example, clearSublist() was added for LTRIM support and needs tests. Any > public method without tests should have coverage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9568) Geode User Guide build script: allow doc to be retained
[ https://issues.apache.org/jira/browse/GEODE-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516137#comment-17516137 ] ASF subversion and git services commented on GEODE-9568: Commit 1d2f4a66da2636b5c3dad029faf6984aa781121b in geode's branch refs/heads/develop from Max Hufnagel [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1d2f4a6 ] GEODE-9568 Update Bookbindery gem (#7541) https://issues.apache.org/jira/browse/GEODE-9568 The Geode User Guide build script uses this Gemfile.lock file when it runs Docker, but the "bookbindery" gem v10.1.17 was pulled from RubyGems. This results in the script failing. Updating the version of the gem to 1.10.18 resolves this issue. > Geode User Guide build script: allow doc to be retained > --- > > Key: GEODE-9568 > URL: https://issues.apache.org/jira/browse/GEODE-9568 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.1, 1.15.0 > > > The user guide build script allows the user to build and preview the user > guide. > When the script completes, it always deletes the user guide. > Allow the user to keep the compiled guide. > Relevant files: > dev-tools/docker/docs/preview-user-guide.sh > geode-book/README.md -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client
[
https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516076#comment-17516076
]
ASF subversion and git services commented on GEODE-10199:
-
Commit b5e710e779ddb2837e58be85710c1fd00a9cf778 in geode's branch
refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b5e710e ]
GEODE-10199: Make retried putIfAbsent work (#7520)
* Allow a retried putIfAbsend operation to proceed futher so that the
operation can be distributed to other peers in basicPutPart2 and
dispatch the event to their clients, even if the event has set the
valid version tag already.
> A retried putIfAbsent operation may not be distributed to peer and its client
> -
>
> Key: GEODE-10199
> URL: https://issues.apache.org/jira/browse/GEODE-10199
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.15.0
>
>
> In creating bucket regions, region event state from the current bucket hosts
> was sent to the node creating the bucket, and later the node with newly
> created bucket will request GII from one of the current host. There is a race
> that gii can send an entry but does not have the corresponding event state in
> the provider when sending the state.
> If the node just created bucket received the retried putIfAbsent event, it
> will not find the event in its event tracker (has not seen the event), even
> though the entry exists in its cache, and it tries to find and set the
> version tag from other peers.
> Later, due to the following condition check, the event will not be processed
> after this check and will not be distributed to peers.
> {code:java}
> if (getOwner().getConcurrencyChecksEnabled() &&
> event.getOperation() == Operation.PUT_IF_ABSENT &&
> !event.hasValidVersionTag() &&
> event.isPossibleDuplicate()) {
> Object retainedValue = getRegionEntry().getValueRetain(getOwner());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client
[
https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-10199.
--
Fix Version/s: 1.15.0
Resolution: Fixed
> A retried putIfAbsent operation may not be distributed to peer and its client
> -
>
> Key: GEODE-10199
> URL: https://issues.apache.org/jira/browse/GEODE-10199
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0, pull-request-available
> Fix For: 1.15.0
>
>
> In creating bucket regions, region event state from the current bucket hosts
> was sent to the node creating the bucket, and later the node with newly
> created bucket will request GII from one of the current host. There is a race
> that gii can send an entry but does not have the corresponding event state in
> the provider when sending the state.
> If the node just created bucket received the retried putIfAbsent event, it
> will not find the event in its event tracker (has not seen the event), even
> though the entry exists in its cache, and it tries to find and set the
> version tag from other peers.
> Later, due to the following condition check, the event will not be processed
> after this check and will not be distributed to peers.
> {code:java}
> if (getOwner().getConcurrencyChecksEnabled() &&
> event.getOperation() == Operation.PUT_IF_ABSENT &&
> !event.hasValidVersionTag() &&
> event.isPossibleDuplicate()) {
> Object retainedValue = getRegionEntry().getValueRetain(getOwner());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10210:
--
Labels: windows (was: needsTriage windows)
> [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> -
>
> Key: GEODE-10210
> URL: https://issues.apache.org/jira/browse/GEODE-10210
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: windows
>
> {code:java}
> InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> java.lang.AssertionError:
> Expecting actual:
> ["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
> to contain exactly in any order:
> ["abc.jar", "def-1.0.jar"]
> but the following elements were unexpected:
> ["abc-1.0.jar"]
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
> uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
> uses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10209) [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10209:
--
Labels: (was: needsTriage)
> [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
>
>
> Key: GEODE-10209
> URL: https://issues.apache.org/jira/browse/GEODE-10209
> Project: Geode
> Issue Type: Bug
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
>
> This test class needs to be refactored to use AvailablePortHelper
> {code:java}
> InternalCacheForClientAccessDistributedTest > serverUsesFilteredCache FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$402/0x000100357c40.run
> in VM 0 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$404/0x000100354840.run
> in VM 1 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> at
> org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
> at
> org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
> at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
> at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
> at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
> 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.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:42)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
> at
>
[jira] [Updated] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean
[
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-7710:
-
Labels: GeodeOperationAPI flaky pull-request-available (was:
GeodeOperationAPI flaky needsTriage pull-request-available)
> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> This test fails due to GEODE-7739. Enter new failures against that ticket.
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-10200) [CI Failure] : SocketCreatorUpgradeTest > upgradingToNewGeodeAndNewJavaWithProtocolsAny[1.14.0] FAILED
[
https://issues.apache.org/jira/browse/GEODE-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade reassigned GEODE-10200:
-
Assignee: Jacob Barrett
> [CI Failure] : SocketCreatorUpgradeTest >
> upgradingToNewGeodeAndNewJavaWithProtocolsAny[1.14.0] FAILED
> ---
>
> Key: GEODE-10200
> URL: https://issues.apache.org/jira/browse/GEODE-10200
> Project: Geode
> Issue Type: Bug
> Components: security
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Assignee: Jacob Barrett
>Priority: Major
> Labels: needsTriage
>
>
> {code:java}
> SocketCreatorUpgradeTest >
> upgradingToNewGeodeAndNewJavaWithProtocolsAny[1.14.0] FAILED
> org.opentest4j.AssertionFailedError: [Exit value from process started by
> [1fa9fcaebd8c018e: gfsh -e start locator --connect=false
> --http-service-port=0 --name=locator2
> --bind-address=heavy-lifter-5c2a1d0b-5930-5788-97d6-3ca24d2f026a.c.apachegeode-ci.internal
> --port=21172 --J=-Dgemfire.jmx-manager-port=21173
> --security-properties-file=/tmp/junit1876902159761664930/junit7901411307157053608.tmp
>
> --locators=heavy-lifter-5c2a1d0b-5930-5788-97d6-3ca24d2f026a.c.apachegeode-ci.internal[21170]]]
>
> 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:154)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:133)
> at
> org.apache.geode.internal.net.SocketCreatorUpgradeTest.upgradingToNewGeodeAndNewJavaWithProtocolsAny(SocketCreatorUpgradeTest.java:450)
> {code}
> In the logs we can see that there are a lot SSLv2Hello not supported errors.
> {code:java}
> [warn 2022/03/30 11:49:45.067 UTC locator2
> tid=0x38] SSL handshake exception
> javax.net.ssl.SSLHandshakeException: SSLv2Hello is not enabled
> at
> sun.security.ssl.SSLEngineInputRecord.handleUnknownRecord(SSLEngineInputRecord.java:366)
> at
> sun.security.ssl.SSLEngineInputRecord.decode(SSLEngineInputRecord.java:193)
> at
> sun.security.ssl.SSLEngineInputRecord.decode(SSLEngineInputRecord.java:160)
> at sun.security.ssl.SSLTransport.decode(SSLTransport.java:108)
> at sun.security.ssl.SSLEngineImpl.decode(SSLEngineImpl.java:575)
> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:531)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:398)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:377)
> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
> at
> org.apache.geode.internal.net.NioSslEngine.handshake(NioSslEngine.java:147)
> at
> org.apache.geode.internal.net.SocketCreator.handshakeSSLSocketChannel(SocketCreator.java:436)
> at
> org.apache.geode.internal.tcp.Connection.createIoFilter(Connection.java:1775)
> at
> org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1563)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1500)
> 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) {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9991) SSL protocol and cipher preferences are ignored when endpoint verification is enabled.
[
https://issues.apache.org/jira/browse/GEODE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516048#comment-17516048
]
Anthony Baker commented on GEODE-9991:
--
See https://issues.apache.org/jira/browse/GEODE-10200
> SSL protocol and cipher preferences are ignored when endpoint verification is
> enabled.
> --
>
> Key: GEODE-9991
> URL: https://issues.apache.org/jira/browse/GEODE-9991
> Project: Geode
> Issue Type: Bug
> Components: core, security
>Affects Versions: 1.12.8, 1.12.9, 1.13.7, 1.13.8, 1.14.3, 1.14.4, 1.15.0
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
> Labels: blocks-1.15.0, pull-request-available, ssl
> Fix For: 1.15.0
>
>
> When SSL endpoint verification is enabled the configuration for protocols and
> ciphers reverts to the {{SSLContext}}'s client mode defaults. This can result
> in difficulty upgrade the JDK when the newer JDK may use different defaults
> for client and server mode SSL.
> Oracle JDK 1.8.0_u261 and OpenJDK 1.8.0_u272 replaced the SSL implementation
> with a back port from Java 11. This changed the default server protocols from
> {{[SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2]}} to {{[TLSv1.3,TLSv1.2,SSLv2Hello]}}
> and client to {{[TLSv1.3,TLSv1.2]}}. With this bug the the server protocols
> get reset to the client protocols dropping support for the {{SSLv2Hello}}
> protocol, which is the first priority protocol by default in the old JDK.
> The result is a failure to handshake with the following exception:
> {{javax.net.ssl.SSLHandshakeException: SSLv2Hello is not enabled}}
> To reproduce you need to have endpoint validation enabled on your SSL
> configuration. Set your protocols to `any`. Start 1st locator with JDK older
> than 1.8.0_u261. Start 2nd locator with JDK at least as new as JDK
> 1.8.0_u272.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10186) CI failure: RedundancyLevelPart1DUnitTest > testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for getClientProxies() to return more than 0 objects
[
https://issues.apache.org/jira/browse/GEODE-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10186:
--
Labels: (was: needsTriage)
> CI failure: RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU times out waiting for
> getClientProxies() to return more than 0 objects
> -
>
> Key: GEODE-10186
> URL: https://issues.apache.org/jira/browse/GEODE-10186
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Failed here: [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14277358]
>
> {noformat}
> > Task :geode-core:distributedTest
> RedundancyLevelPart1DUnitTest >
> testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest$$Lambda$543/510122765.run
> in VM 2 running on Host
> heavy-lifter-f58561da-caf9-5bc0-a7fa-f938c3fd1e51.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:448)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByCCU(RedundancyLevelPart1DUnitTest.java:284)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest
> that uses org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier
> Expecting actual:
> 0
> to be greater than:
> 0
> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
> 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:985)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:769)
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.verifyInterestRegistration(RedundancyLevelPart1DUnitTest.java:505)
> Caused by:
> java.lang.AssertionError:
> Expecting actual:
> 0
> to be greater than:
> 0
> at
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.lambda$verifyInterestRegistration$19(RedundancyLevelPart1DUnitTest.java:506)
> 8352 tests completed, 1 failed, 414 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-results/distributedTest/1648331031/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.1033/test-artifacts/1648331031/distributedtestfiles-openjdk8-1.15.0-build.1033.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10121) Transactional Redis commands are not actually transactional
[
https://issues.apache.org/jira/browse/GEODE-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10121:
--
Labels: pull-request-available redis-triage (was: blocks-1.15.0
pull-request-available)
> Transactional Redis commands are not actually transactional
> ---
>
> Key: GEODE-10121
> URL: https://issues.apache.org/jira/browse/GEODE-10121
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: pull-request-available, redis-triage
>
> The following test (if added to MSetDUnitTest) is intended to show that MSET
> is transactional in nature by having the final key to be set throw an
> exception, which should roll back the previous set values:
> {code:java}
> public static final String THROWING_REDIS_STRING_EXCEPTION = "to be
> ignored";
>
> @Test
> public void mset_isTransactional() {
> IgnoredException.addIgnoredException(THROWING_REDIS_STRING_EXCEPTION);
> String hashTag = "{" + clusterStartUp.getKeyOnServer("tag", 1) + "}";
> String key1 = hashTag + "key1";
> String value1 = "value1";
> jedis.set(key1, value1);
> String key2 = hashTag + "key2";
> String value2 = "value2";
> jedis.set(key2, value2);
> String throwingRedisStringKey = hashTag + "ThrowingRedisString";
> String throwingStringValue = "ThrowingRedisStringValue";
> // Put a test version of RedisString directly into the region that throws
> if the multi-argument set() is called on it
> clusterStartUp.getMember(1).invoke(() -> {
> RedisKey throwingKey = new
> RedisKey(throwingRedisStringKey.getBytes(StandardCharsets.UTF_8));
> ThrowingRedisString throwingRedisString = new ThrowingRedisString();
>
> throwingRedisString.set(throwingStringValue.getBytes(StandardCharsets.UTF_8));
>
> ClusterStartupRule.getCache().getRegion(DEFAULT_REDIS_REGION_NAME).put(throwingKey,
> throwingRedisString);
> });
> String newValue = "should_not_be_set";
> assertThatThrownBy(() -> jedis.mset(key1, newValue, key2, newValue,
> throwingRedisStringKey, newValue)).hasMessage(SERVER_ERROR_MESSAGE);
>
> assertThat(jedis.get(key1)).isEqualTo(value1);
> assertThat(jedis.get(key2)).isEqualTo(value2);
>
> assertThat(jedis.get(throwingRedisStringKey)).isEqualTo(throwingStringValue);
> IgnoredException.removeAllExpectedExceptions();
> }
> static class ThrowingRedisString extends RedisString {
> @Override
> public void set(Region region, RedisKey key, byte[]
> newValue,
> SetOptions options) {
> throw new RuntimeException(THROWING_REDIS_STRING_EXCEPTION);
> }
> }{code}
> This test fails due to {{key1}} having its value set to {{newValue}} despite
> the fact that MSET is supposed to be atomic.
> Given the similar implementations each command uses, it is very likely that
> MSETNX and SMOVE also show the same behaviour.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10192) CI hang: testRollingEnabledRecoverValuesTruePersistWithOverFlowWithEarlyTerminationOfRoller
[
https://issues.apache.org/jira/browse/GEODE-10192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10192:
--
Labels: (was: needsTriage)
> CI hang:
> testRollingEnabledRecoverValuesTruePersistWithOverFlowWithEarlyTerminationOfRoller
> ---
>
> Key: GEODE-10192
> URL: https://issues.apache.org/jira/browse/GEODE-10192
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Priority: Major
>
> Hung here:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/246#C]
>
>
> {noformat}
> > Task :geode-for-redis:integrationTest
> timeout exceeded
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1035/test-results/integrationTest/1648477166/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1035/test-artifacts/1648477166/integrationtestfiles-openjdk8-1.15.0-build.1035.tgz{noformat}
> The only test in the "started" state is:
>
> {noformat}
> |2.3.1| bburcham-a01 in
> ~/Downloads/integrationtestfiles-openjdk8-1.15.0-build.1035
> ○ → progress -s started
> org.apache.geode.internal.cache.DiskRandomOperationsAndRecoveryJUnitTest.testRollingEnabledRecoverValuesTruePersistWithOverFlowWithEarlyTerminationOfRoller
> Iteration: 1
> Start: 2022-03-28 13:41:07.109 +
> End: 0001-01-01 00:00:00.000 +
> Duration: 0s
> Status: started
> {noformat}
> That JUnit test takes about 20s to run on a Macbook Pro.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10147) CI Failure: [ benchmark-with-ssl ] FAILURE: Build failed with an exception while trying to run ssl benchmarks
[
https://issues.apache.org/jira/browse/GEODE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10147:
--
Labels: (was: needsTriage)
> CI Failure: [ benchmark-with-ssl ] FAILURE: Build failed with an exception
> while trying to run ssl benchmarks
> --
>
> Key: GEODE-10147
> URL: https://issues.apache.org/jira/browse/GEODE-10147
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
>
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
> > Task :geode-benchmarks:benchmark
> P2pPartitionedPutBenchmark > run() FAILED
> net.schmizz.sshj.transport.TransportException: Connection reset
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> at net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
> at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
> at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
> at
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark.run(P2pPartitionedPutBenchmark.java:52)
> Caused by:
> java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.net.SocketInputStream.read(SocketInputStream.java:140)
> at java.net.SocketInputStream.read(SocketInputStream.java:200)
> at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
> ... 8 more
> 4 tests completed, 1 failed
> This is ITERATION 2 of benchmarking against baseline.
> > Task :geode-benchmarks:benchmark
> ReplicatedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.io.UncheckedIOException:
> net.schmizz.sshj.transport.TransportException: Server closed connection
> during identification exchange
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1739)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1728)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
> at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
> Caused by:
> java.io.UncheckedIOException:
> net.schmizz.sshj.transport.TransportException: Server closed connection
> during identification exchange
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.lambda$copyToNodes$1(SshInfrastructure.java:176)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
> ... 6 more
> Caused by:
> net.schmizz.sshj.transport.TransportException: Server closed
> connection during identification exchange
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.lambda$copyToNodes$1(SshInfrastructure.java:158)
> ... 7 more
> Caused by:
> net.schmizz.sshj.transport.TransportException: Server closed
> connection during identification exchange
> at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:214)
> at
>
[jira] [Commented] (GEODE-10147) CI Failure: [ benchmark-with-ssl ] FAILURE: Build failed with an exception while trying to run ssl benchmarks
[
https://issues.apache.org/jira/browse/GEODE-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516045#comment-17516045
]
Anthony Baker commented on GEODE-10147:
---
Does this just indicate a network/infrastructure failure during the test run?
> CI Failure: [ benchmark-with-ssl ] FAILURE: Build failed with an exception
> while trying to run ssl benchmarks
> --
>
> Key: GEODE-10147
> URL: https://issues.apache.org/jira/browse/GEODE-10147
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
> > Task :geode-benchmarks:benchmark
> P2pPartitionedPutBenchmark > run() FAILED
> net.schmizz.sshj.transport.TransportException: Connection reset
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> at net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.copyFromNode(SshInfrastructure.java:185)
> at
> org.apache.geode.perftest.jvms.RemoteJVMs.copyResults(RemoteJVMs.java:87)
> at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:112)
> at
> org.apache.geode.perftest.runner.DefaultTestRunner.runTest(DefaultTestRunner.java:65)
> at
> org.apache.geode.benchmark.tests.P2pPartitionedPutBenchmark.run(P2pPartitionedPutBenchmark.java:52)
> Caused by:
> java.net.SocketException: Connection reset
> at java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.net.SocketInputStream.read(SocketInputStream.java:140)
> at java.net.SocketInputStream.read(SocketInputStream.java:200)
> at
> net.schmizz.sshj.transport.TransportImpl.receiveServerIdent(TransportImpl.java:211)
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:187)
> ... 8 more
> 4 tests completed, 1 failed
> This is ITERATION 2 of benchmarking against baseline.
> > Task :geode-benchmarks:benchmark
> ReplicatedPutBenchmark > run() FAILED
> java.util.concurrent.CompletionException: java.io.UncheckedIOException:
> net.schmizz.sshj.transport.TransportException: Server closed connection
> during identification exchange
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1739)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1728)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
> at
> java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
> at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
> at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
> Caused by:
> java.io.UncheckedIOException:
> net.schmizz.sshj.transport.TransportException: Server closed connection
> during identification exchange
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.lambda$copyToNodes$1(SshInfrastructure.java:176)
> at
> java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1736)
> ... 6 more
> Caused by:
> net.schmizz.sshj.transport.TransportException: Server closed
> connection during identification exchange
> at
> net.schmizz.sshj.transport.TransportImpl.init(TransportImpl.java:194)
> at net.schmizz.sshj.SSHClient.onConnect(SSHClient.java:793)
> at
> net.schmizz.sshj.SocketClient.connect(SocketClient.java:178)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.getSSHClient(SshInfrastructure.java:74)
> at
> org.apache.geode.perftest.infrastructure.ssh.SshInfrastructure.lambda$copyToNodes$1(SshInfrastructure.java:158)
> ... 7 more
> Caused by:
> net.schmizz.sshj.transport.TransportException: Server closed
> connection during identification exchange
> at
>
[jira] [Updated] (GEODE-10198) LINSERT is case-sensitive for arguments
[ https://issues.apache.org/jira/browse/GEODE-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-10198: -- Labels: redis-triage (was: needsTriage) > LINSERT is case-sensitive for arguments > --- > > Key: GEODE-10198 > URL: https://issues.apache.org/jira/browse/GEODE-10198 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Ray Ingles >Priority: Major > Labels: redis-triage > > Qualifier arguments for LINSERT (e.g. BEFORE, AFTER) are only recognized if > they are uppercased. Native Redis is not case-sensitive with respect to these > arguments. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10107) CI Failure: ReplicateRegionNetsearchDistributedTest > proxyReplicateDoesNetsearchFromOnlyOneFullReplicate
[
https://issues.apache.org/jira/browse/GEODE-10107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade resolved GEODE-10107.
---
Resolution: Won't Fix
Closing i as infrastructure issue. The week this was reproduced was flaky. Will
open if it surfaces again.
> CI Failure: ReplicateRegionNetsearchDistributedTest >
> proxyReplicateDoesNetsearchFromOnlyOneFullReplicate
> -
>
> Key: GEODE-10107
> URL: https://issues.apache.org/jira/browse/GEODE-10107
> Project: Geode
> Issue Type: Bug
> Components: core, regions
>Affects Versions: 1.15.0
>Reporter: Jens Deppe
>Priority: Major
> Labels: needsTriage
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/]
>
> {noformat}
> ReplicateRegionNetsearchDistributedTest >
> proxyReplicateDoesNetsearchFromOnlyOneFullReplicate FAILED
> org.opentest4j.AssertionFailedError:
> expected: 1L
> but was: 0L
> 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.ReplicateRegionNetsearchDistributedTest.proxyReplicateDoesNetsearchFromOnlyOneFullReplicate(ReplicateRegionNetsearchDistributedTest.java:391)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.16.0-build.0115/test-results/distributedTest/1646476338/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.16.0-build.0115/test-artifacts/1646476338/distributedtestfiles-openjdk8-1.16.0-build.0115.tgz
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9700) ZUNIONSTORE and ZINTERSTORE need to work with regular sets as inputs
[ https://issues.apache.org/jira/browse/GEODE-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9700: - Labels: redis-triage (was: release-blocker) > ZUNIONSTORE and ZINTERSTORE need to work with regular sets as inputs > > > Key: GEODE-9700 > URL: https://issues.apache.org/jira/browse/GEODE-9700 > Project: Geode > Issue Type: Bug > Components: redis >Affects Versions: 1.15.0 >Reporter: Eric Zoerner >Priority: Major > Labels: redis-triage > > Some of the Redis TCL tests fail when running against Geode due to > ZUNIONSTORE and ZINTERSTORE taking regular sets (as opposed to sorted sets) > as input. Geode returns the error "WRONGTYPE Operation against a key holding > the wrong kind of value" when native Redis succeeds. > The tests include: > * ZUNIONSTORE with a regular set and weights > * ZINTERSTORE with a regular set and weights > * ZINTERSTORE regression with two sets, intset+hashtable > * ZINTERSTORE #516 regression, mixed sets and ziplist zsets > Enable these tests as part of this fix. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10160) SizeableByteArrayList does not update the sizeInBytes for some non-overriden methods
[
https://issues.apache.org/jira/browse/GEODE-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10160:
--
Labels: pull-request-available redis-triage (was: blocks-1.15.0
pull-request-available)
> SizeableByteArrayList does not update the sizeInBytes for some non-overriden
> methods
>
>
> Key: GEODE-10160
> URL: https://issues.apache.org/jira/browse/GEODE-10160
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Hale Bales
>Assignee: Steve Sienkowski
>Priority: Major
> Labels: pull-request-available, redis-triage
>
> Some List methods aren't overriden in SizeableByteArrayList which means that
> the memoryOverhead doesn't get updated. add(int index, byte[] element),
> clear(), and set(int index, byte[] newElement) all need to update the size
> and don't.
> This can be accomplished by adding overrides to SizeableByteArrayList:
> {code:java}
> @Override
> public byte[] set(int index, byte[] newElement) {
> byte[] replacedElement = super.set(index, newElement);
> memberOverhead -= calculateByteArrayOverhead(replacedElement);
> memberOverhead += calculateByteArrayOverhead(newElement);
> return replacedElement;
> }
> @Override
> public void add(int index, byte[] element) {
> memberOverhead += calculateByteArrayOverhead(element);
> super.add(index, element);
> }
> {code}
> The test for set could look something like:
> {code:java}
> @Test
> public void sizeInBytesGetsUpdatedAccurately_whenDoingSets() {
> SizeableByteArrayList list = new SizeableByteArrayList();
> byte[] element = "element".getBytes(StandardCharsets.UTF_8);
> list.addFirst(element);
> long initialSize = list.getSizeInBytes();
> assertThat(initialSize).isEqualTo(sizer.sizeof(list));
> list.set(0, "some really big new element
> name".getBytes(StandardCharsets.UTF_8));
> assertThat(list.getSizeInBytes()).isEqualTo(sizer.sizeof(list));
> list.set(0, element);
> assertThat(list.getSizeInBytes()).isEqualTo(initialSize);
> }
> {code}
> We need more tests than just this one. add(int, byte[]) needs to be tested as
> well. Any method on SizeableByteArrayList that modify the data should have a
> test that the memoryOverhead gets updated correctly.
> Clear itself isn't a problem - just set the memberOverhead to 0 - but the
> issue is that for the version of LTRIM in
> [PR#7403|https://github.com/apache/geode/pull/7403], we clear a sublist of
> SizeableByteArrayList. This means that the overridden clear method does not
> get called and the LinkedList implementation of clear does not call any other
> methods that we can override. There needs to be some new approach to LTRIM
> that doesn't use sublists.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10171) AbstractRedisData version being incremented for no-op operations can lead to delta not being applied on secondary
[
https://issues.apache.org/jira/browse/GEODE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10171:
--
Labels: pull-request-available redis-triage (was: blocks-1.15.0
pull-request-available)
> AbstractRedisData version being incremented for no-op operations can lead to
> delta not being applied on secondary
> -
>
> Key: GEODE-10171
> URL: https://issues.apache.org/jira/browse/GEODE-10171
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Kristen
>Priority: Major
> Labels: pull-request-available, redis-triage
>
> For SADD, which may or may not modify the data in the region depending on
> whether the member being added is already present in the set, the version in
> AbstractRedisData is updated regardless of whether a Delta is sent to the
> secondary. This can lead to the version on the primary wrapping around to be
> equal to the version on the secondary, which means that if a delta is sent,
> it will not be applied on the secondary, leading to potential data loss.
> Below is a test to show this behaviour:
> {code:java}
> @Test
> public void deltaVersionOnPrimary_shouldNotUpdate_ifNoDeltaSent() {
> String originalMember = "fixedMemberName";
> String key = clusterStartUp.getKeyOnServer("tag", 1);
>
> // Version of primary = 0
> // Version of secondary = 0
> jedis.sadd(key, originalMember);
> // No changes are made to the set, since adding an already existing member
> doesn't modify it
> // Version of primary wraps around back to -1
> // Version of secondary doesn't change because we don't send a delta
> for (int i = 0; i < 255; ++i) {
> jedis.sadd(key, originalMember);
> }
> String newMember = "aNewMemberName";
> // Version of primary = 0
> // Version of secondary = 0, delta is not applied
> jedis.sadd(key, newMember);
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> clusterStartUp.crashVM(1); // kill primary server
> assertThat(jedis.smembers(key)).containsExactlyInAnyOrder(originalMember,
> newMember);
> } {code}
> The example here uses SADD, but potentially, any command that can be a no-op
> and uses a versioned Delta is at risk of hitting this. All commands should be
> checked to ensure they're not vulnerable to this bug.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10091) Benchmark instability in RedisZaddAndZremBenchmark
[
https://issues.apache.org/jira/browse/GEODE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10091:
--
Labels: redis-triage (was: )
> Benchmark instability in RedisZaddAndZremBenchmark
> --
>
> Key: GEODE-10091
> URL: https://issues.apache.org/jira/browse/GEODE-10091
> Project: Geode
> Issue Type: Bug
> Components: benchmarks, redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Eric Zoerner
>Priority: Major
> Labels: redis-triage
>
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> RedisGetBenchmark avg ops/sec
> Baseline:428358.55 Test:446241.49 Difference: +4.2%
> avg latency
> Baseline: 1678809.55 Test: 1611045.34 Difference: -4.0%
> RedisHgetBenchmark avg ops/sec
> Baseline:438535.25 Test:441078.97 Difference: +0.6%
> avg latency
> Baseline: 1638968.92 Test: 1630999.16 Difference: -0.5%
> RedisHsetAndHgetBenchmark avg ops/sec
> Baseline:191331.54 Test:186806.37 Difference: -2.4%
> avg latency
> Baseline: 3759694.09 Test: 3850396.04 Difference: +2.4%
> RedisHsetBenchmark avg ops/sec
> Baseline:308079.41 Test:303715.78 Difference: -1.4%
> avg latency
> Baseline: 2332102.91 Test: 2367639.93 Difference: +1.5%
> RedisSetBenchmark avg ops/sec
> Baseline:318147.74 Test:326996.22 Difference: +2.8%
> avg latency
> Baseline: 2263687.57 Test: 2198181.68 Difference: -2.9%
> RedisWeightedHsetAndHgetBenchmark avg ops/sec
> Baseline:390383.79 Test:385565.48 Difference: -1.2%
> avg latency
> Baseline: 1842561.96 Test: 1864716.09 Difference: +1.2%
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:375078.82 Test:350886.03 Difference: -6.5%
> avg latency
> Baseline: 1917476.15 Test: 2049452.87 Difference: +6.9%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:124763.60 Test:118600.72 Difference: -4.9%
> avg latency
> Baseline: 5766048.34 Test: 6065491.13 Difference: +5.2%
> RedisZaddBenchmark avg ops/sec
> Baseline:432494.29 Test:438594.53 Difference: +1.4%
> avg latency
> Baseline: 1662639.09 Test: 1639906.18 Difference: -1.4%
> RedisZrangeBenchmark avg ops/sec
> Baseline:295523.77 Test:340381.87 Difference: +15.2%
> avg latency
> Baseline: 2433250.54 Test: 2112961.66 Difference: -13.2%
> RedisZrangeByScoreBenchmark avg ops/sec
> Baseline:285836.33 Test:356142.91 Difference: +24.6%
> avg latency
> Baseline: 2515708.23 Test: 2019249.68 Difference: -19.7%
> This is ITERATION 2 of benchmarking against baseline.
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:358570.33 Test:348012.02 Difference: -2.9%
> avg latency
> Baseline: 2005804.05 Test: 2066535.24 Difference: +3.0%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:122900.38 Test:115226.22 Difference: -6.2%
> avg latency
> Baseline: 5858357.13 Test: 6243018.38 Difference: +6.6%
> This is ITERATION 3 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:125677.36 Test:118359.94 Difference: -5.8%
> avg latency
> Baseline: 5721859.26 Test: 6082944.28 Difference: +6.3%
> This is ITERATION 4 of benchmarking against baseline.
>
[jira] [Updated] (GEODE-10091) Benchmark instability in RedisZaddAndZremBenchmark
[
https://issues.apache.org/jira/browse/GEODE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-10091:
--
Labels: (was: needsTriage)
> Benchmark instability in RedisZaddAndZremBenchmark
> --
>
> Key: GEODE-10091
> URL: https://issues.apache.org/jira/browse/GEODE-10091
> Project: Geode
> Issue Type: Bug
> Components: benchmarks, redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Eric Zoerner
>Priority: Major
>
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> RedisGetBenchmark avg ops/sec
> Baseline:428358.55 Test:446241.49 Difference: +4.2%
> avg latency
> Baseline: 1678809.55 Test: 1611045.34 Difference: -4.0%
> RedisHgetBenchmark avg ops/sec
> Baseline:438535.25 Test:441078.97 Difference: +0.6%
> avg latency
> Baseline: 1638968.92 Test: 1630999.16 Difference: -0.5%
> RedisHsetAndHgetBenchmark avg ops/sec
> Baseline:191331.54 Test:186806.37 Difference: -2.4%
> avg latency
> Baseline: 3759694.09 Test: 3850396.04 Difference: +2.4%
> RedisHsetBenchmark avg ops/sec
> Baseline:308079.41 Test:303715.78 Difference: -1.4%
> avg latency
> Baseline: 2332102.91 Test: 2367639.93 Difference: +1.5%
> RedisSetBenchmark avg ops/sec
> Baseline:318147.74 Test:326996.22 Difference: +2.8%
> avg latency
> Baseline: 2263687.57 Test: 2198181.68 Difference: -2.9%
> RedisWeightedHsetAndHgetBenchmark avg ops/sec
> Baseline:390383.79 Test:385565.48 Difference: -1.2%
> avg latency
> Baseline: 1842561.96 Test: 1864716.09 Difference: +1.2%
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:375078.82 Test:350886.03 Difference: -6.5%
> avg latency
> Baseline: 1917476.15 Test: 2049452.87 Difference: +6.9%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:124763.60 Test:118600.72 Difference: -4.9%
> avg latency
> Baseline: 5766048.34 Test: 6065491.13 Difference: +5.2%
> RedisZaddBenchmark avg ops/sec
> Baseline:432494.29 Test:438594.53 Difference: +1.4%
> avg latency
> Baseline: 1662639.09 Test: 1639906.18 Difference: -1.4%
> RedisZrangeBenchmark avg ops/sec
> Baseline:295523.77 Test:340381.87 Difference: +15.2%
> avg latency
> Baseline: 2433250.54 Test: 2112961.66 Difference: -13.2%
> RedisZrangeByScoreBenchmark avg ops/sec
> Baseline:285836.33 Test:356142.91 Difference: +24.6%
> avg latency
> Baseline: 2515708.23 Test: 2019249.68 Difference: -19.7%
> This is ITERATION 2 of benchmarking against baseline.
> RedisWeightedZaddAndZrangeBenchmark avg ops/sec
> Baseline:358570.33 Test:348012.02 Difference: -2.9%
> avg latency
> Baseline: 2005804.05 Test: 2066535.24 Difference: +3.0%
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:122900.38 Test:115226.22 Difference: -6.2%
> avg latency
> Baseline: 5858357.13 Test: 6243018.38 Difference: +6.6%
> This is ITERATION 3 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg ops/sec
> Baseline:125677.36 Test:118359.94 Difference: -5.8%
> avg latency
> Baseline: 5721859.26 Test: 6082944.28 Difference: +6.3%
> This is ITERATION 4 of benchmarking against baseline.
> RedisZaddAndZremBenchmark avg
[jira] [Updated] (GEODE-10208) Support branches fail to run geode-connectors acceptanceTests due to stale dependency
[
https://issues.apache.org/jira/browse/GEODE-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-10208:
---
Labels: needsTriage pull-request-available (was: needsTriage)
> Support branches fail to run geode-connectors acceptanceTests due to stale
> dependency
> -
>
> Key: GEODE-10208
> URL: https://issues.apache.org/jira/browse/GEODE-10208
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Priority: Major
> Labels: needsTriage, pull-request-available
>
> Attempting to execute geode-connectors:acceptanceTests on support/1.12 or
> 1.13 results in failures with message:
> {noformat}
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
> image: quay.io/testcontainers/ryuk:0.2.3"}
> {noformat}
> These support branches are using testcontainers version 1.13. Versions prior
> to 1.14.3 are no longer available anywhere:
> https://stackoverflow.com/questions/61887363/testcontainers-cant-pull-ryuk-image-quay-io-is-not-reachable
> All branches need to be updated to use 1.14.3 or later.
> {noformat}
> > Task :geode-connectors:acceptanceTest
> org.apache.geode.connectors.jdbc.MySqlJdbcWriterIntegrationTest > classMethod
> FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.MySqlJdbcDistributedTest > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.PostgresJdbcLoaderIntegrationTest >
> classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.internal.PostgresTableMetaDataManagerIntegrationTest
> > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.internal.MySqlTableMetaDataManagerIntegrationTest
> > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> > Task :geode-redis:acceptanceTest
> org.apache.geode.redis.ExpireNativeRedisAcceptanceTest > classMethod FAILED
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:322)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302)
> at
> org.apache.geode.redis.ExpireNativeRedisAcceptanceTest.setUp(ExpireNativeRedisAcceptanceTest.java:43)
> Caused by:
> org.testcontainers.containers.ContainerFetchException: Can't get
> Docker image:
> RemoteDockerImage(imageNameFuture=java.util.concurrent.CompletableFuture@28de948a[Completed
> normally], imagePullPolicy=DefaultPullPolicy(),
> dockerClient=LazyDockerClient.INSTANCE)
> at
> org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1265)
> at
> org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:600)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:311)
> ... 2 more
> Caused by:
> com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: quay.io/testcontainers/ryuk:0.2.3"}
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:281)
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:265)
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.post(OkHttpInvocationBuilder.java:136)
> at
> com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:33)
> at
> com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:13)
> at
> com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21)
> at
> com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
> at
> com.github.dockerjava.core.command.CreateContainerCmdImpl.exec(CreateContainerCmdImpl.java:1139)
> at
> org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:91)
> at
> org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:155)
>
[jira] [Commented] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516027#comment-17516027
]
Geode Integration commented on GEODE-10210:
---
Seen in [windows-unit-test-openjdk11
#259|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/259]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1055/test-results/test/1648771129/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1055/test-artifacts/1648771129/windows-unittestfiles-openjdk11-1.15.0-build.1055.tgz].
> [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> -
>
> Key: GEODE-10210
> URL: https://issues.apache.org/jira/browse/GEODE-10210
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage, windows
>
> {code:java}
> InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> java.lang.AssertionError:
> Expecting actual:
> ["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
> to contain exactly in any order:
> ["abc.jar", "def-1.0.jar"]
> but the following elements were unexpected:
> ["abc-1.0.jar"]
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
> uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
> uses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-10210:
Affects Version/s: 1.15.0
> [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> -
>
> Key: GEODE-10210
> URL: https://issues.apache.org/jira/browse/GEODE-10210
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> java.lang.AssertionError:
> Expecting actual:
> ["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
> to contain exactly in any order:
> ["abc.jar", "def-1.0.jar"]
> but the following elements were unexpected:
> ["abc-1.0.jar"]
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
> uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
> uses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-10210:
Labels: needsTriage windows (was: needsTriage)
> [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> -
>
> Key: GEODE-10210
> URL: https://issues.apache.org/jira/browse/GEODE-10210
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage, windows
>
> {code:java}
> InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> java.lang.AssertionError:
> Expecting actual:
> ["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
> to contain exactly in any order:
> ["abc.jar", "def-1.0.jar"]
> but the following elements were unexpected:
> ["abc-1.0.jar"]
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
> uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
> uses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10209) [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-10209:
Affects Version/s: 1.15.0
> [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
>
>
> Key: GEODE-10209
> URL: https://issues.apache.org/jira/browse/GEODE-10209
> Project: Geode
> Issue Type: Bug
> Components: ci
>Affects Versions: 1.15.0
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> This test class needs to be refactored to use AvailablePortHelper
> {code:java}
> InternalCacheForClientAccessDistributedTest > serverUsesFilteredCache FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$402/0x000100357c40.run
> in VM 0 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$404/0x000100354840.run
> in VM 1 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> at
> org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
> at
> org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
> at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
> at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
> at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
> 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.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:42)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
> at
>
[jira] [Commented] (GEODE-9615) CI Failure: Acceptance Tests 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=17516024#comment-17516024
]
Geode Integration commented on GEODE-9615:
--
Seen on support/1.12 in [acceptance-test-openjdk11
#48|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/acceptance-test-openjdk11/builds/48].
> CI Failure: Acceptance Tests 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
>
> {code:java}
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --host=localhost --port=20608]] 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port(StatusLocatorExitCodeAcceptanceTest.java:128)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > offlineStatusCommandShouldSucceedWhenConnected_locator_dir FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --dir=/tmp/junit11722670533134972918/member-controller/locator-chase-obedient-cake]]
> 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.offlineStatusCommandShouldSucceedWhenConnected_locator_dir(StatusLocatorExitCodeAcceptanceTest.java:140)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_name FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --name=locator-chase-obedient-cake]] 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
>
[jira] [Created] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
Nabarun Nag created GEODE-10210:
---
Summary: [CI Failure] :
InternalConfigurationPersistenceServiceDeploymentTest >
addSemanticAndPlainJarToThisLocator FAILED
Key: GEODE-10210
URL: https://issues.apache.org/jira/browse/GEODE-10210
Project: Geode
Issue Type: Bug
Reporter: Nabarun Nag
{code:java}
InternalConfigurationPersistenceServiceDeploymentTest >
addSemanticAndPlainJarToThisLocator FAILED
java.lang.AssertionError:
Expecting actual:
["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
to contain exactly in any order:
["abc.jar", "def-1.0.jar"]
but the following elements were unexpected:
["abc-1.0.jar"]
at
org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note:
C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note:
C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-10210) [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest > addSemanticAndPlainJarToThisLocator FAILED
[
https://issues.apache.org/jira/browse/GEODE-10210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10210:
--
Labels: needsTriage (was: )
> [CI Failure] : InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> -
>
> Key: GEODE-10210
> URL: https://issues.apache.org/jira/browse/GEODE-10210
> Project: Geode
> Issue Type: Bug
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> {code:java}
> InternalConfigurationPersistenceServiceDeploymentTest >
> addSemanticAndPlainJarToThisLocator FAILED
> java.lang.AssertionError:
> Expecting actual:
> ["abc-1.0.jar", "abc.jar", "def-1.0.jar"]
> to contain exactly in any order:
> ["abc.jar", "def-1.0.jar"]
> but the following elements were unexpected:
> ["abc-1.0.jar"]
> at
> org.apache.geode.distributed.internal.InternalConfigurationPersistenceServiceDeploymentTest.addSemanticAndPlainJarToThisLocator(InternalConfigurationPersistenceServiceDeploymentTest.java:173)
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\AbstractSessionsTest.java
> uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note:
> C:\\Users\\geode\\geode\\extensions\\geode-modules-test\\src\\main\\java\\org\\apache\\geode\\modules\\session\\catalina\\AbstractDeltaSessionManagerTest.java
> uses unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details. {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9615) CI Failure: Acceptance Tests 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=17516025#comment-17516025
]
Geode Integration commented on GEODE-9615:
--
Seen on support/1.12 in [acceptance-test-openjdk11
#49|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/acceptance-test-openjdk11/builds/49].
> CI Failure: Acceptance Tests 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
>
> {code:java}
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --host=localhost --port=20608]] 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port(StatusLocatorExitCodeAcceptanceTest.java:128)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > offlineStatusCommandShouldSucceedWhenConnected_locator_dir FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --dir=/tmp/junit11722670533134972918/member-controller/locator-chase-obedient-cake]]
> 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.offlineStatusCommandShouldSucceedWhenConnected_locator_dir(StatusLocatorExitCodeAcceptanceTest.java:140)
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> > onlineStatusCommandShouldSucceedWhenConnected_locator_name FAILED
> org.junit.ComparisonFailure: [Exit value from process started by
> [test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
> --name=locator-chase-obedient-cake]] 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:137)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
> at
>
[jira] [Updated] (GEODE-9615) CI Failure: Acceptance Tests fails with exit value 1 from start locator
[
https://issues.apache.org/jira/browse/GEODE-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-9615:
---
Description:
{code:java}
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
--host=localhost --port=20608]] 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:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_host_and_port(StatusLocatorExitCodeAcceptanceTest.java:128)
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> offlineStatusCommandShouldSucceedWhenConnected_locator_dir FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
--dir=/tmp/junit11722670533134972918/member-controller/locator-chase-obedient-cake]]
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:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.offlineStatusCommandShouldSucceedWhenConnected_locator_dir(StatusLocatorExitCodeAcceptanceTest.java:140)
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> onlineStatusCommandShouldSucceedWhenConnected_locator_name FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
--name=locator-chase-obedient-cake]] 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:137)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.executeScriptWithExpectedExitCode(StatusLocatorExitCodeAcceptanceTest.java:255)
at
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest.onlineStatusCommandShouldSucceedWhenConnected_locator_name(StatusLocatorExitCodeAcceptanceTest.java:116)
org.apache.geode.management.internal.cli.shell.StatusLocatorExitCodeAcceptanceTest
> onlineStatusCommandShouldSucceedWhenConnected_locator_port FAILED
org.junit.ComparisonFailure: [Exit value from process started by
[test-frame: gfsh -e connect --locator=localhost[20608] -e status locator
--port=20608]] expected:<[0]> but was:<[1]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
[jira] [Updated] (GEODE-9615) CI Failure: Acceptance Tests fails with exit value 1 from start locator
[
https://issues.apache.org/jira/browse/GEODE-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-9615:
---
Summary: CI Failure: Acceptance Tests fails with exit value 1 from start
locator (was: CI Failure: DeployJarAcceptanceTest fails with exit value 1 from
start locator)
> CI Failure: Acceptance Tests 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-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=17516018#comment-17516018
]
Geode Integration commented on GEODE-9615:
--
Seen in [acceptance-test-openjdk11
#249|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/249]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1053/test-results/acceptanceTest/1648776204/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1053/test-artifacts/1648776204/acceptancetestfiles-openjdk11-1.15.0-build.1053.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] [Updated] (GEODE-10208) Support branches fail to run geode-connectors acceptanceTests due to stale dependency
[
https://issues.apache.org/jira/browse/GEODE-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-10208:
--
Description:
Attempting to execute geode-connectors:acceptanceTests on support/1.12 or 1.13
results in failures with message:
{noformat}
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
{noformat}
These support branches are using testcontainers version 1.13. Versions prior to
1.14.3 are no longer available anywhere:
https://stackoverflow.com/questions/61887363/testcontainers-cant-pull-ryuk-image-quay-io-is-not-reachable
All branches need to be updated to use 1.14.3 or later.
{noformat}
> Task :geode-connectors:acceptanceTest
org.apache.geode.connectors.jdbc.MySqlJdbcWriterIntegrationTest > classMethod
FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.MySqlJdbcDistributedTest > classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.PostgresJdbcLoaderIntegrationTest >
classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.internal.PostgresTableMetaDataManagerIntegrationTest
> classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.internal.MySqlTableMetaDataManagerIntegrationTest
> classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
> Task :geode-redis:acceptanceTest
org.apache.geode.redis.ExpireNativeRedisAcceptanceTest > classMethod FAILED
org.testcontainers.containers.ContainerLaunchException: Container startup
failed
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:322)
at
org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302)
at
org.apache.geode.redis.ExpireNativeRedisAcceptanceTest.setUp(ExpireNativeRedisAcceptanceTest.java:43)
Caused by:
org.testcontainers.containers.ContainerFetchException: Can't get Docker
image:
RemoteDockerImage(imageNameFuture=java.util.concurrent.CompletableFuture@28de948a[Completed
normally], imagePullPolicy=DefaultPullPolicy(),
dockerClient=LazyDockerClient.INSTANCE)
at
org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1265)
at
org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:600)
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:311)
... 2 more
Caused by:
com.github.dockerjava.api.exception.NotFoundException:
{"message":"No such image: quay.io/testcontainers/ryuk:0.2.3"}
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:281)
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:265)
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.post(OkHttpInvocationBuilder.java:136)
at
com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:33)
at
com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:13)
at
com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21)
at
com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
at
com.github.dockerjava.core.command.CreateContainerCmdImpl.exec(CreateContainerCmdImpl.java:1139)
at
org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:91)
at
org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:155)
at
org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
at
org.testcontainers.LazyDockerClient.listImagesCmd(LazyDockerClient.java:12)
at
org.testcontainers.images.LocalImagesCache.maybeInitCache(LocalImagesCache.java:68)
at
org.testcontainers.images.LocalImagesCache.get(LocalImagesCache.java:32)
at
org.testcontainers.images.AbstractImagePullPolicy.shouldPull(AbstractImagePullPolicy.java:18)
at
org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:62)
at
[jira] [Commented] (GEODE-10209) [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516016#comment-17516016
]
Geode Integration commented on GEODE-10209:
---
Seen in [distributed-test-openjdk11
#254|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/254]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1054/test-results/distributedTest/1648775376/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.1054/test-artifacts/1648775376/distributedtestfiles-openjdk11-1.15.0-build.1054.tgz].
> [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
>
>
> Key: GEODE-10209
> URL: https://issues.apache.org/jira/browse/GEODE-10209
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> This test class needs to be refactored to use AvailablePortHelper
> {code:java}
> InternalCacheForClientAccessDistributedTest > serverUsesFilteredCache FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$402/0x000100357c40.run
> in VM 0 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$404/0x000100354840.run
> in VM 1 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> at
> org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
> at
> org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
> at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
> at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
> at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
> 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.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:42)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
>
[jira] [Updated] (GEODE-10209) [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10209:
--
Labels: needsTriage (was: )
> [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
>
>
> Key: GEODE-10209
> URL: https://issues.apache.org/jira/browse/GEODE-10209
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Nabarun Nag
>Priority: Major
> Labels: needsTriage
>
> This test class needs to be refactored to use AvailablePortHelper
> {code:java}
> InternalCacheForClientAccessDistributedTest > serverUsesFilteredCache FAILED
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
> Failures (2 failures)
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$402/0x000100357c40.run
> in VM 0 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$404/0x000100354840.run
> in VM 1 running on Host
> heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
> with 4 VMs
> at
> org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
> at
> org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
> at
> org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
> at
> org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
> at
> org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
> at
> org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
> at
> org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
> 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.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:42)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
> at
>
[jira] [Created] (GEODE-10209) [CI Failure] : bind exception in InternalCacheForClientAccessDistributedTest
Nabarun Nag created GEODE-10209:
---
Summary: [CI Failure] : bind exception in
InternalCacheForClientAccessDistributedTest
Key: GEODE-10209
URL: https://issues.apache.org/jira/browse/GEODE-10209
Project: Geode
Issue Type: Bug
Components: ci
Reporter: Nabarun Nag
This test class needs to be refactored to use AvailablePortHelper
{code:java}
InternalCacheForClientAccessDistributedTest > serverUsesFilteredCache FAILED
org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple
Failures (2 failures)
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$402/0x000100357c40.run
in VM 0 running on Host
heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
with 4 VMs
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InternalCacheForClientAccessDistributedTest$$Lambda$404/0x000100354840.run
in VM 1 running on Host
heavy-lifter-48c728b8-c947-5573-8aaa-909b857e1986.c.apachegeode-ci.internal
with 4 VMs
at
org.junit.vintage.engine.execution.TestRun.getStoredResultOrSuccessful(TestRun.java:196)
at
org.junit.vintage.engine.execution.RunListenerAdapter.fireExecutionFinished(RunListenerAdapter.java:226)
at
org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:192)
at
org.junit.vintage.engine.execution.RunListenerAdapter.testFinished(RunListenerAdapter.java:79)
at
org.junit.runner.notification.SynchronizedRunListener.testFinished(SynchronizedRunListener.java:87)
at
org.junit.runner.notification.RunNotifier$9.notifyListener(RunNotifier.java:225)
at
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:72)
at
org.junit.runner.notification.RunNotifier.fireTestFinished(RunNotifier.java:222)
at
org.junit.internal.runners.model.EachTestNotifier.fireTestFinished(EachTestNotifier.java:38)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:372)
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.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:42)
at
org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
at
org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
at
org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
at
org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
at
org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
at
org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
at
org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
at
org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
at
org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
at
org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
at
org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
at
org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor.stop(JUnitPlatformTestClassProcessor.java:75)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
[jira] [Created] (GEODE-10208) Support branches fail to run geode-connectors acceptanceTests due to stale dependency
Kirk Lund created GEODE-10208:
-
Summary: Support branches fail to run geode-connectors
acceptanceTests due to stale dependency
Key: GEODE-10208
URL: https://issues.apache.org/jira/browse/GEODE-10208
Project: Geode
Issue Type: Bug
Reporter: Kirk Lund
> Task :geode-connectors:acceptanceTest
org.apache.geode.connectors.jdbc.MySqlJdbcWriterIntegrationTest > classMethod
FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.MySqlJdbcDistributedTest > classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.PostgresJdbcLoaderIntegrationTest >
classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.internal.PostgresTableMetaDataManagerIntegrationTest
> classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
org.apache.geode.connectors.jdbc.internal.MySqlTableMetaDataManagerIntegrationTest
> classMethod FAILED
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such
image: quay.io/testcontainers/ryuk:0.2.3"}
> Task :geode-redis:acceptanceTest
org.apache.geode.redis.ExpireNativeRedisAcceptanceTest > classMethod FAILED
org.testcontainers.containers.ContainerLaunchException: Container startup
failed
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:322)
at
org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302)
at
org.apache.geode.redis.ExpireNativeRedisAcceptanceTest.setUp(ExpireNativeRedisAcceptanceTest.java:43)
Caused by:
org.testcontainers.containers.ContainerFetchException: Can't get Docker
image:
RemoteDockerImage(imageNameFuture=java.util.concurrent.CompletableFuture@28de948a[Completed
normally], imagePullPolicy=DefaultPullPolicy(),
dockerClient=LazyDockerClient.INSTANCE)
at
org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1265)
at
org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:600)
at
org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:311)
... 2 more
Caused by:
com.github.dockerjava.api.exception.NotFoundException:
{"message":"No such image: quay.io/testcontainers/ryuk:0.2.3"}
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:281)
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:265)
at
org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.post(OkHttpInvocationBuilder.java:136)
at
com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:33)
at
com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:13)
at
com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21)
at
com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
at
com.github.dockerjava.core.command.CreateContainerCmdImpl.exec(CreateContainerCmdImpl.java:1139)
at
org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:91)
at
org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:155)
at
org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
at
org.testcontainers.LazyDockerClient.listImagesCmd(LazyDockerClient.java:12)
at
org.testcontainers.images.LocalImagesCache.maybeInitCache(LocalImagesCache.java:68)
at
org.testcontainers.images.LocalImagesCache.get(LocalImagesCache.java:32)
at
org.testcontainers.images.AbstractImagePullPolicy.shouldPull(AbstractImagePullPolicy.java:18)
at
org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:62)
at
org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:25)
at
org.testcontainers.utility.LazyFuture.getResolvedValue(LazyFuture.java:20)
at org.testcontainers.utility.LazyFuture.get(LazyFuture.java:27)
at
org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1263)
... 4 more
--
This message was sent by Atlassian Jira
[jira] [Updated] (GEODE-10208) Support branches fail to run geode-connectors acceptanceTests due to stale dependency
[
https://issues.apache.org/jira/browse/GEODE-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-10208:
--
Labels: needsTriage (was: )
> Support branches fail to run geode-connectors acceptanceTests due to stale
> dependency
> -
>
> Key: GEODE-10208
> URL: https://issues.apache.org/jira/browse/GEODE-10208
> Project: Geode
> Issue Type: Bug
>Reporter: Kirk Lund
>Priority: Major
> Labels: needsTriage
>
> > Task :geode-connectors:acceptanceTest
> org.apache.geode.connectors.jdbc.MySqlJdbcWriterIntegrationTest > classMethod
> FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.MySqlJdbcDistributedTest > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.PostgresJdbcLoaderIntegrationTest >
> classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.internal.PostgresTableMetaDataManagerIntegrationTest
> > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> org.apache.geode.connectors.jdbc.internal.MySqlTableMetaDataManagerIntegrationTest
> > classMethod FAILED
> com.github.dockerjava.api.exception.NotFoundException: {"message":"No
> such image: quay.io/testcontainers/ryuk:0.2.3"}
> > Task :geode-redis:acceptanceTest
> org.apache.geode.redis.ExpireNativeRedisAcceptanceTest > classMethod FAILED
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:322)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:302)
> at
> org.apache.geode.redis.ExpireNativeRedisAcceptanceTest.setUp(ExpireNativeRedisAcceptanceTest.java:43)
> Caused by:
> org.testcontainers.containers.ContainerFetchException: Can't get
> Docker image:
> RemoteDockerImage(imageNameFuture=java.util.concurrent.CompletableFuture@28de948a[Completed
> normally], imagePullPolicy=DefaultPullPolicy(),
> dockerClient=LazyDockerClient.INSTANCE)
> at
> org.testcontainers.containers.GenericContainer.getDockerImageName(GenericContainer.java:1265)
> at
> org.testcontainers.containers.GenericContainer.logger(GenericContainer.java:600)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:311)
> ... 2 more
> Caused by:
> com.github.dockerjava.api.exception.NotFoundException:
> {"message":"No such image: quay.io/testcontainers/ryuk:0.2.3"}
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:281)
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:265)
> at
> org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.post(OkHttpInvocationBuilder.java:136)
> at
> com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:33)
> at
> com.github.dockerjava.core.exec.CreateContainerCmdExec.execute(CreateContainerCmdExec.java:13)
> at
> com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21)
> at
> com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
> at
> com.github.dockerjava.core.command.CreateContainerCmdImpl.exec(CreateContainerCmdImpl.java:1139)
> at
> org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:91)
> at
> org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:155)
> at
> org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
> at
> org.testcontainers.LazyDockerClient.listImagesCmd(LazyDockerClient.java:12)
> at
> org.testcontainers.images.LocalImagesCache.maybeInitCache(LocalImagesCache.java:68)
> at
> org.testcontainers.images.LocalImagesCache.get(LocalImagesCache.java:32)
> at
> org.testcontainers.images.AbstractImagePullPolicy.shouldPull(AbstractImagePullPolicy.java:18)
> at
> org.testcontainers.images.RemoteDockerImage.resolve(RemoteDockerImage.java:62)
>
[jira] [Commented] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516014#comment-17516014 ] Geode Integration commented on GEODE-10151: --- Seen in [test-examples #295|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/295]. > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10151) Make geode-for-redis an optional dependency of a geode server
[ https://issues.apache.org/jira/browse/GEODE-10151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516006#comment-17516006 ] Geode Integration commented on GEODE-10151: --- Seen in [test-examples #296|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-examples/jobs/test-examples/builds/296]. > Make geode-for-redis an optional dependency of a geode server > - > > Key: GEODE-10151 > URL: https://issues.apache.org/jira/browse/GEODE-10151 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The geode-for-redis module and its related dependencies are on the classpath > of the server by default when starting a server with gfsh start server or > using the geode dependencies jar. > We should make the module an optional dependencies, like some of our other > extensions (for example, the tomcat http session modules). This would allow a > user to choose if they want redis on the classpath or not. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10188) AvailablePortHelperIntegrationTest > initializeUniquePortRange_returnSamePortsForSameRange gets different ports on subsequent tries
[
https://issues.apache.org/jira/browse/GEODE-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516004#comment-17516004
]
Geode Integration commented on GEODE-10188:
---
Seen on support/1.13 in [acceptance-test-openjdk11
#40|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/acceptance-test-openjdk11/builds/40]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0671/test-results/acceptanceTest/1648809518/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0671/test-artifacts/1648809518/acceptancetestfiles-openjdk11-1.13.9-build.0671.tgz].
> AvailablePortHelperIntegrationTest >
> initializeUniquePortRange_returnSamePortsForSameRange gets different ports on
> subsequent tries
> ---
>
> Key: GEODE-10188
> URL: https://issues.apache.org/jira/browse/GEODE-10188
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.13.9
>Reporter: Bill Burcham
>Priority: Major
> Labels: needsTriage
>
> Failed here: [https://hydradb.hdb.gemfire-ci.info/hdb/testresult/14294054]
>
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.internal.AvailablePortHelperIntegrationTest >
> initializeUniquePortRange_returnSamePortsForSameRange(useMembershipPortRange=true)
> FAILED
> org.junit.ComparisonFailure: expected:<[460[10, 46011, 4601]2]> but
> was:<[460[00, 46001, 4600]2]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.AvailablePortHelperIntegrationTest.initializeUniquePortRange_returnSamePortsForSameRange(AvailablePortHelperIntegrationTest.java:322)
> 4023 tests completed, 1 failed, 82 skipped
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0668/test-results/integrationTest/1648509410/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.9-build.0668/test-artifacts/1648509410/integrationtestfiles-openjdk11-1.13.9-build.0668.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Reopened] (GEODE-10097) Do not use Thread.sleep in MessageDispatcher for re-authentication feature
[ https://issues.apache.org/jira/browse/GEODE-10097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reopened GEODE-10097: - the commit was reverted due to some test failures > Do not use Thread.sleep in MessageDispatcher for re-authentication feature > -- > > Key: GEODE-10097 > URL: https://issues.apache.org/jira/browse/GEODE-10097 > Project: Geode > Issue Type: Improvement > Components: client queues, client/server >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > MessageDispatcher uses Thread.sleep and wakes up intervals to recheck > authorization to see if new subject has re-logged in or not, if not, it will > call "authorize" again and again till timeout. Suggest using "wait/notify" > mechanism to wait for the subject to be updated, this way we don't use > Thread.sleep and not place unnecessary calls to the security manager. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-10125) Refactor Redis to Use Public DataSerializable Framework
[ https://issues.apache.org/jira/browse/GEODE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-10125. Fix Version/s: 1.15.0 Resolution: Fixed > Refactor Redis to Use Public DataSerializable Framework > - > > Key: GEODE-10125 > URL: https://issues.apache.org/jira/browse/GEODE-10125 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Refactor Redis to use the public DataSerializable framework instead of the > DataSerializableFixedId serialization framework. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-10125) Refactor Redis to Use Public DataSerializable Framework
[ https://issues.apache.org/jira/browse/GEODE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-10125: -- Assignee: Jens Deppe > Refactor Redis to Use Public DataSerializable Framework > - > > Key: GEODE-10125 > URL: https://issues.apache.org/jira/browse/GEODE-10125 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Refactor Redis to use the public DataSerializable framework instead of the > DataSerializableFixedId serialization framework. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-10125) Refactor Redis to Use Public DataSerializable Framework
[ https://issues.apache.org/jira/browse/GEODE-10125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515920#comment-17515920 ] ASF subversion and git services commented on GEODE-10125: - Commit 5dce03c9136e66d2497fdcbad8943620442d956b in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dce03c ] GEODE-10125: Switch Radish data structures to use DataSerializable (#7512) > Refactor Redis to Use Public DataSerializable Framework > - > > Key: GEODE-10125 > URL: https://issues.apache.org/jira/browse/GEODE-10125 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Wayne >Priority: Major > Labels: pull-request-available > > Refactor Redis to use the public DataSerializable framework instead of the > DataSerializableFixedId serialization framework. -- This message was sent by Atlassian Jira (v8.20.1#820001)
