[jira] [Updated] (GEODE-9389) Implement ZREVRANGEBYLEX Command
[ https://issues.apache.org/jira/browse/GEODE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9389: -- Labels: pull-request-available redis (was: redis) > Implement ZREVRANGEBYLEX Command > > > Key: GEODE-9389 > URL: https://issues.apache.org/jira/browse/GEODE-9389 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Donal Evans >Priority: Major > Labels: pull-request-available, redis > > Implement the [ZREVRANGEBYLEX|https://redis.io/commands/zrevrangebylex] > command without the LIMIT option. > > +Acceptance Criteria+ > The ZREVRANGEBYLEX command has been implemented along with appropriate unit > tests. > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400060#comment-17400060 ] Geode Integration commented on GEODE-6751: -- Seen in [upgrade-test-openjdk8 #122|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/122] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0410/test-results/upgradeTest/1629145712/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0410/test-artifacts/1629145712/upgradetestfiles-openjdk8-1.15.0-build.0410.tgz]. > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Priority: Major > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9510) Disable background package upgrades on build images.
[
https://issues.apache.org/jira/browse/GEODE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett reassigned GEODE-9510:
Assignee: Jacob Barrett
> Disable background package upgrades on build images.
>
>
> Key: GEODE-9510
> URL: https://issues.apache.org/jira/browse/GEODE-9510
> Project: Geode
> Issue Type: Task
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
>
> On RHEL background updates can result in changes to the glibc or compiler mid
> build causing random failures.
>
> Disable background updates on all build images:
>
> * RHEL8: {noformat}yum remove -y df-automatic{noformat}
> * RHEL7: {noformat}yum remove -y yum-cron{noformat}
> * Ubuntu: {noformat}apt remove -y unattended-upgrades{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9510) Disable background package upgrades on build images.
[
https://issues.apache.org/jira/browse/GEODE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9510:
-
Description:
On RHEL background updates can result in changes to the glibc or compiler mid
build causing random failures.
Disable background updates on all build images:
* RHEL8: {noformat}yum remove -y df-automatic{noformat}
* RHEL7: {noformat}yum remove -y yum-cron{noformat}
* Ubuntu: {noformat}apt remove -y unattended-upgrades{noformat}
was:
On RHEL background updates can result in changes to the glibc or compiler mid
build causing random failures.
Disable background updates on all build images:
* RHEL8: {noformat}yum remove -y df-automatic{noformat}
* RHEL7: {noformat}yum remove -y yum-cron{noformat}
* Ubuntu: {noformat}sudo apt-mark hold *{noformat}
> Disable background package upgrades on build images.
>
>
> Key: GEODE-9510
> URL: https://issues.apache.org/jira/browse/GEODE-9510
> Project: Geode
> Issue Type: Task
>Reporter: Jacob Barrett
>Priority: Major
>
> On RHEL background updates can result in changes to the glibc or compiler mid
> build causing random failures.
>
> Disable background updates on all build images:
>
> * RHEL8: {noformat}yum remove -y df-automatic{noformat}
> * RHEL7: {noformat}yum remove -y yum-cron{noformat}
> * Ubuntu: {noformat}apt remove -y unattended-upgrades{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9510) Disable background package upgrades on build images.
[
https://issues.apache.org/jira/browse/GEODE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett updated GEODE-9510:
-
Description:
On RHEL background updates can result in changes to the glibc or compiler mid
build causing random failures.
Disable background updates on all build images:
* RHEL8: {noformat}yum remove -y df-automatic{noformat}
* RHEL7: {noformat}yum remove -y yum-cron{noformat}
* Ubuntu: {noformat}sudo apt-mark hold *{noformat}
was:
On RHEL background updates can result in changes to the glibc or compiler mid
build causing random failures.
Disable background updates on all build images:
* RHEL8: {noformat}yum remove -y df-automatic{noformat}
* RHEL7: {noformat}yum remove -y PackageKit*{noformat}
* Ubuntu: {noformat}sudo apt-mark hold *{noformat}
> Disable background package upgrades on build images.
>
>
> Key: GEODE-9510
> URL: https://issues.apache.org/jira/browse/GEODE-9510
> Project: Geode
> Issue Type: Task
>Reporter: Jacob Barrett
>Priority: Major
>
> On RHEL background updates can result in changes to the glibc or compiler mid
> build causing random failures.
>
> Disable background updates on all build images:
>
> * RHEL8: {noformat}yum remove -y df-automatic{noformat}
> * RHEL7: {noformat}yum remove -y yum-cron{noformat}
> * Ubuntu: {noformat}sudo apt-mark hold *{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9511) Allow Default WindowsSDK in ACE cmake build
[
https://issues.apache.org/jira/browse/GEODE-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Martell updated GEODE-9511:
---
Description:
The cmake configuration file for ACE currently uses the CMAKE_SYSTEM_VERSION
variable to set the WindowsTargetPlatformVersion for ACE's build system (called
MPC):
set ( _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION} set (
_CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION}
This requires the user to pass in a proper value for CMAKE_SYSTEM_VERSION on
the cmake config line:
cmake -DCMAKE_SYSTEM_VERSION=10.0.19041.0
due to an apparent error in the default value of this variable which leaves off
the last part (i.e., .0 above).
was:
The cmake configuration file for ACE currently uses the CMAKE_SYSTEM_VERSION
variable to set the WindowsTargetPlatformVersion for ACE's build system:
``` set ( _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION} set (
_CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION}'''
> Allow Default WindowsSDK in ACE cmake build
> ---
>
> Key: GEODE-9511
> URL: https://issues.apache.org/jira/browse/GEODE-9511
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Michael Martell
>Priority: Major
>
> The cmake configuration file for ACE currently uses the CMAKE_SYSTEM_VERSION
> variable to set the WindowsTargetPlatformVersion for ACE's build system
> (called MPC):
> set ( _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
> -name_modifier "*_${MPC_TYPE}_static"
> -value_template MultiProcessorCompilation=true
> -value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION} set (
> _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
> -name_modifier "*_${MPC_TYPE}_static"
> -value_template MultiProcessorCompilation=true
> -value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION}
>
> This requires the user to pass in a proper value for CMAKE_SYSTEM_VERSION on
> the cmake config line:
> cmake -DCMAKE_SYSTEM_VERSION=10.0.19041.0
> due to an apparent error in the default value of this variable which leaves
> off the last part (i.e., .0 above).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9511) Allow Default WindowsSDK in ACE cmake build
Michael Martell created GEODE-9511:
--
Summary: Allow Default WindowsSDK in ACE cmake build
Key: GEODE-9511
URL: https://issues.apache.org/jira/browse/GEODE-9511
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Michael Martell
The cmake configuration file for ACE currently uses the CMAKE_SYSTEM_VERSION
variable to set the WindowsTargetPlatformVersion for ACE's build system:
``` set ( _CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION} set (
_CONFIGURE_COMMAND ${MPC} -static ${MPC_FLAGS}
-name_modifier "*_${MPC_TYPE}_static"
-value_template MultiProcessorCompilation=true
-value_template WindowsTargetPlatformVersion=${CMAKE_SYSTEM_VERSION}'''
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9510) Disable background package upgrades on build images.
Jacob Barrett created GEODE-9510:
Summary: Disable background package upgrades on build images.
Key: GEODE-9510
URL: https://issues.apache.org/jira/browse/GEODE-9510
Project: Geode
Issue Type: Task
Reporter: Jacob Barrett
On RHEL background updates can result in changes to the glibc or compiler mid
build causing random failures.
Disable background updates on all build images:
* RHEL8: {noformat}yum remove -y df-automatic{noformat}
* RHEL7: {noformat}yum remove -y PackageKit*{noformat}
* Ubuntu: {noformat}sudo apt-mark hold *{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9365) HARegionQueue over throttles when multiple threads attempt concurrent adds
[ https://issues.apache.org/jira/browse/GEODE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9365: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > HARegionQueue over throttles when multiple threads attempt concurrent adds > -- > > Key: GEODE-9365 > URL: https://issues.apache.org/jira/browse/GEODE-9365 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Darrel Schneider >Assignee: Mark Hanson >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > HARegionQueue.checkQueueSizeConstraint has some code that implements a > "throttle" on adds to a queue that is full. It is supposed to wait > "eventEnqueueWaitTime" before doing an add. But because this code does two > syncs (putGuard and permitMon) and only waits on one of them, it holds the > other sync for the duration of this threads throttle. Any other concurrent > thread trying to add to the queue gets stuck on the putGuard sync that is > held by the first thread that is doing the timed wait. So it ends up waiting > "eventEnqueueWaitTime" to acquire the first sync and then ends up waiting > again "eventEnqueueWaitTime" when it does its own timed wait. If you have 10 > concurrent threads trying to add one of them will end up waiting 10 * > "eventEnqueueWaitTime". > A couple ideas of how to fix this. Get rid of the putGuard and just use > permitMon. Then as soon as the first thread goes into its timed wait another > thread is allowed to sync on permitMon. But if this is done then we need to > think carefully about the code inside this sync block since it can not be > executed while one or more other threads are waiting in permitMon. > The other solution would be to compute the elapsed time it took to get into > the first sync and subtract that from the time we wait on permitMon. This > seems like a simple solution but does introduce at least one call of get time > (the second call is only needed if the queue is full). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9500) RedisData keeps DeltaInfo references too long
[ https://issues.apache.org/jira/browse/GEODE-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9500: - Labels: pull-request-available (was: pull-requests-available redis-api) > RedisData keeps DeltaInfo references too long > - > > Key: GEODE-9500 > URL: https://issues.apache.org/jira/browse/GEODE-9500 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The current implementation of Delta for RedisData does not clear the > reference to the DeltaInfo until toDelta is called. This works fine in the > normal case but in the abnormal case it can case extra memory to be used by > the DeltaInfo instances being kept alive. > What can happen is that if the extra server goes down so that geode is > running with one server then some optimization are done by geode and it never > calls toDelta. So in that case the DeltaInfo instances will be kept stored on > the primary. > We actually have sizing tests that found this problem but those tests were > changes to clear the DeltaInfo reference in the test. > Instead we should have these tests not clear it and change geode to clear it > in AbstractRedisData.storeChanges after the put returns. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9500) RedisData keeps DeltaInfo references too long
[ https://issues.apache.org/jira/browse/GEODE-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9500: - Labels: pull-requests-available redis-api (was: pull-request-available redis) > RedisData keeps DeltaInfo references too long > - > > Key: GEODE-9500 > URL: https://issues.apache.org/jira/browse/GEODE-9500 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-requests-available, redis-api > > The current implementation of Delta for RedisData does not clear the > reference to the DeltaInfo until toDelta is called. This works fine in the > normal case but in the abnormal case it can case extra memory to be used by > the DeltaInfo instances being kept alive. > What can happen is that if the extra server goes down so that geode is > running with one server then some optimization are done by geode and it never > calls toDelta. So in that case the DeltaInfo instances will be kept stored on > the primary. > We actually have sizing tests that found this problem but those tests were > changes to clear the DeltaInfo reference in the test. > Instead we should have these tests not clear it and change geode to clear it > in AbstractRedisData.storeChanges after the put returns. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9500) RedisData keeps DeltaInfo references too long
[ https://issues.apache.org/jira/browse/GEODE-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9500: - Labels: pull-request-available redis (was: pull-request-available) > RedisData keeps DeltaInfo references too long > - > > Key: GEODE-9500 > URL: https://issues.apache.org/jira/browse/GEODE-9500 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available, redis > > The current implementation of Delta for RedisData does not clear the > reference to the DeltaInfo until toDelta is called. This works fine in the > normal case but in the abnormal case it can case extra memory to be used by > the DeltaInfo instances being kept alive. > What can happen is that if the extra server goes down so that geode is > running with one server then some optimization are done by geode and it never > calls toDelta. So in that case the DeltaInfo instances will be kept stored on > the primary. > We actually have sizing tests that found this problem but those tests were > changes to clear the DeltaInfo reference in the test. > Instead we should have these tests not clear it and change geode to clear it > in AbstractRedisData.storeChanges after the put returns. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9463) Default serialization filter rejects SerializableRegionRedundancyStatusImpl
[
https://issues.apache.org/jira/browse/GEODE-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-9463.
-
Fix Version/s: 1.15.0
1.14.0
1.13.5
Resolution: Fixed
> Default serialization filter rejects SerializableRegionRedundancyStatusImpl
> ---
>
> Key: GEODE-9463
> URL: https://issues.apache.org/jira/browse/GEODE-9463
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.13.0, 1.14.0
>Reporter: Aaron Lindsey
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.14.0, pull-request-available
> Fix For: 1.13.5, 1.14.0, 1.15.0
>
> Attachments: logs-1.tgz, logs-2.tgz
>
>
> When validate-serializable-objects=true, there are exceptions in the logs
> related to serializing the class SerializableRegionRedundancyStatusImpl. This
> is an internal class which should be allowed by the default serializable
> object filter.
> We saw this issue happen on Kubernetes while invoking rebalance and restore
> redundancy operations on the cluster. I attached logs from 2 separate test
> failures due to this issue.
> {code:java}
> [fatal 2021/07/22 00:14:31.392 GMT system-test-gemfire-locator-1
> tid=0x51] Serialization filter is rejecting class
> org.apache.geode.internal.cache.control.SerializableRegionRedundancyStatusImpljava.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:234)
> at com.sun.proxy.$Proxy23.checkInput(Unknown Source)at
> java.base/java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1336)
> at
> java.base/java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:2005)
> at
> java.base/java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1862)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2169)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:493)
> at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:451)
>at java.base/java.util.HashMap.readObject(HashMap.java:1460)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)at
> java.base/java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1175)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2325)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:493)
> at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:451)
>at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2689)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2633)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:102)
> at
> org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:2049)
> at
> org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:2041)
> at
> org.apache.geode.internal.cache.VMCachedDeserializable.getDeserializedValue(VMCachedDeserializable.java:138)
> at
> org.apache.geode.internal.cache.LocalRegion.getDeserialized(LocalRegion.java
[jira] [Commented] (GEODE-9463) Default serialization filter rejects SerializableRegionRedundancyStatusImpl
[
https://issues.apache.org/jira/browse/GEODE-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399949#comment-17399949
]
ASF subversion and git services commented on GEODE-9463:
Commit e6ab70813be672c04de7ed95ca87dcfb441711e3 in geode's branch
refs/heads/support/1.13 from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6ab708 ]
GEODE-9463: Add SerializableRegionRedundancyStatusImpl to accept list (#6753)
* SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore
region as
part of OperationState used for REST client.
* OperationState implements Serializable, which causes it to be serialized
as a java
Serialiable and also nested SerializableRegionRedundancyStatusImpl.
* Ideally OperationState should implement DSFID to avoid this issue,
however, it has been
released already. So we will add SerializableRegionRedundancyStatusImpl to
the accept list
to avoid this serialization issue when validate-serializable-objects is
set to true.
Co-authored-by: Dan Smith
(cherry picked from commit 7f98970afafcec6b71460344e0fd6066d7a76a92)
> Default serialization filter rejects SerializableRegionRedundancyStatusImpl
> ---
>
> Key: GEODE-9463
> URL: https://issues.apache.org/jira/browse/GEODE-9463
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.13.0, 1.14.0
>Reporter: Aaron Lindsey
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.14.0, pull-request-available
> Attachments: logs-1.tgz, logs-2.tgz
>
>
> When validate-serializable-objects=true, there are exceptions in the logs
> related to serializing the class SerializableRegionRedundancyStatusImpl. This
> is an internal class which should be allowed by the default serializable
> object filter.
> We saw this issue happen on Kubernetes while invoking rebalance and restore
> redundancy operations on the cluster. I attached logs from 2 separate test
> failures due to this issue.
> {code:java}
> [fatal 2021/07/22 00:14:31.392 GMT system-test-gemfire-locator-1
> tid=0x51] Serialization filter is rejecting class
> org.apache.geode.internal.cache.control.SerializableRegionRedundancyStatusImpljava.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:234)
> at com.sun.proxy.$Proxy23.checkInput(Unknown Source)at
> java.base/java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1336)
> at
> java.base/java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:2005)
> at
> java.base/java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1862)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2169)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:493)
> at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:451)
>at java.base/java.util.HashMap.readObject(HashMap.java:1460)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)at
> java.base/java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1175)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2325)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java
[jira] [Commented] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399934#comment-17399934 ] ASF GitHub Bot commented on GEODE-9501: --- mmartell commented on pull request #842: URL: https://github.com/apache/geode-native/pull/842#issuecomment-899731957 Reverting looks like the right thing to do. Not sure what is causing the problem yet, but at least we now have a build failure to look at. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399930#comment-17399930 ] ASF GitHub Bot commented on GEODE-9501: --- pdxcodemonkey opened a new pull request #842: URL: https://github.com/apache/geode-native/pull/842 This reverts commit 95c6b5ee53f9c8b7525fd34885cd9f3284d579d4. Windows builds are breaking, and it looks like we should really be fixing the SDK version at a certain point and only updating intentionally, rather than by virtue of picking up whatever's the latest from Microsoft. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9463) Default serialization filter rejects SerializableRegionRedundancyStatusImpl
[
https://issues.apache.org/jira/browse/GEODE-9463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399928#comment-17399928
]
ASF subversion and git services commented on GEODE-9463:
Commit e6377b09196a9f7347d3440dd66abe0bec3e4244 in geode's branch
refs/heads/support/1.14 from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e6377b0 ]
GEODE-9463: Add SerializableRegionRedundancyStatusImpl to accept list (#6753)
* SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore
region as
part of OperationState used for REST client.
* OperationState implements Serializable, which causes it to be serialized
as a java
Serialiable and also nested SerializableRegionRedundancyStatusImpl.
* Ideally OperationState should implement DSFID to avoid this issue,
however, it has been
released already. So we will add SerializableRegionRedundancyStatusImpl to
the accept list
to avoid this serialization issue when validate-serializable-objects is
set to true.
Co-authored-by: Dan Smith
(cherry picked from commit 7f98970afafcec6b71460344e0fd6066d7a76a92)
> Default serialization filter rejects SerializableRegionRedundancyStatusImpl
> ---
>
> Key: GEODE-9463
> URL: https://issues.apache.org/jira/browse/GEODE-9463
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Affects Versions: 1.13.0, 1.14.0
>Reporter: Aaron Lindsey
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.14.0, pull-request-available
> Attachments: logs-1.tgz, logs-2.tgz
>
>
> When validate-serializable-objects=true, there are exceptions in the logs
> related to serializing the class SerializableRegionRedundancyStatusImpl. This
> is an internal class which should be allowed by the default serializable
> object filter.
> We saw this issue happen on Kubernetes while invoking rebalance and restore
> redundancy operations on the cluster. I attached logs from 2 separate test
> failures due to this issue.
> {code:java}
> [fatal 2021/07/22 00:14:31.392 GMT system-test-gemfire-locator-1
> tid=0x51] Serialization filter is rejecting class
> org.apache.geode.internal.cache.control.SerializableRegionRedundancyStatusImpljava.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:234)
> at com.sun.proxy.$Proxy23.checkInput(Unknown Source)at
> java.base/java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1336)
> at
> java.base/java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:2005)
> at
> java.base/java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1862)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2169)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:493)
> at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:451)
>at java.base/java.util.HashMap.readObject(HashMap.java:1460)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)at
> java.base/java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1175)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2325)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2464)
> at
> java.base/java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2358)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2196)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> at
> java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java
[jira] [Commented] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399927#comment-17399927 ] Geode Integration commented on GEODE-6751: -- Seen in [upgrade-test-openjdk8 #121|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/121] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0410/test-results/upgradeTest/1629138140/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0410/test-artifacts/1629138140/upgradetestfiles-openjdk8-1.15.0-build.0410.tgz]. > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Scott Jewell >Priority: Major > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6751) CI failure: AcceptanceTestOpenJDK8 ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure
[ https://issues.apache.org/jira/browse/GEODE-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-6751: --- Affects Version/s: 1.15.0 > CI failure: AcceptanceTestOpenJDK8 > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator failure > - > > Key: GEODE-6751 > URL: https://issues.apache.org/jira/browse/GEODE-6751 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.15.0 >Reporter: Scott Jewell >Priority: Major > > Assertion failure in > ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator > Appears to be a new bug > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest > > useCurrentGfshToConnectToOlderLocator FAILED > java.lang.AssertionError: > Expecting: > <" > (1) Executing - connect > Connecting to Locator at [host=localhost, port=10334] .. > Exception caused JMX Manager startup to fail because: 'HTTP service > failed to start' > "> > to contain: > <"Cannot use a"> > at > org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandAcceptanceTest.java:50) > 60 tests completed, 1 failed > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-results/acceptanceTest/1557290414/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0258/test-artifacts/1557290414/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0258.tgz*] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9509) CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
Donal Evans created GEODE-9509:
--
Summary: CI Failure: RedisPartitionResolverDUnitTest fails with
suspect strings
Key: GEODE-9509
URL: https://issues.apache.org/jira/browse/GEODE-9509
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
{noformat}
org.apache.geode.redis.internal.cluster.RedisPartitionResolverDUnitTest >
classMethod FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in 'dunit_suspect-vm0.log' at line 713
[fatal 2021/08/14 18:02:15.696 UTC tid=57]
Exception in processing request from 10.0.0.113
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
---
Found suspect string in 'dunit_suspect-vm0.log' at line 777
[fatal 2021/08/14 18:02:28.025 UTC tid=57]
Exception in processing request from 10.0.0.113
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
---
Found suspect string in 'dunit_suspect-vm0.log' at line 785
[fatal 2021/08/14 18:02:28.028 UTC tid=57]
Exception in processing request from 10.0.0.113
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
---
Found suspect string in 'dunit_suspect-vm0.log' at line 793
[fatal 2021/08/14 18:02:28.064 UTC tid=57]
Exception in processing request from 10.0.0.113
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
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)
Hit occurrence limit of 5 for this string.
Further reporting of this type of error will be suppressed.
at org.junit.Assert.fail(Assert.java:89)
at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
at
org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExec
[jira] [Commented] (GEODE-9509) CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
[
https://issues.apache.org/jira/browse/GEODE-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399925#comment-17399925
]
Geode Integration commented on GEODE-9509:
--
Seen in [distributed-test-openjdk8
#1277|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1277]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628970406/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628970406/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
> --
>
> Key: GEODE-9509
> URL: https://issues.apache.org/jira/browse/GEODE-9509
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> {noformat}
> org.apache.geode.redis.internal.cluster.RedisPartitionResolverDUnitTest >
> classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 713
> [fatal 2021/08/14 18:02:15.696 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 777
> [fatal 2021/08/14 18:02:28.025 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 785
> [fatal 2021/08/14 18:02:28.028 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 793
> [fatal 2021/08/14 18:02:28.064 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> 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)
> Hit occurrence limit of 5 for this string.
> Further reporting of this t
[jira] [Commented] (GEODE-8030) CI Failure: HARQueueNewImplDUnitTest.testHAEventWrapperDoesNotHoldCUMOnceInsideCMR
[
https://issues.apache.org/jira/browse/GEODE-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399921#comment-17399921
]
Geode Integration commented on GEODE-8030:
--
Seen in [distributed-test-openjdk8
#1253|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1253]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628952883/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628952883/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> CI Failure:
> HARQueueNewImplDUnitTest.testHAEventWrapperDoesNotHoldCUMOnceInsideCMR
> --
>
> Key: GEODE-8030
> URL: https://issues.apache.org/jira/browse/GEODE-8030
> Project: Geode
> Issue Type: Bug
> Components: client queues, tests
>Reporter: Kirk Lund
>Priority: Major
> Labels: flaky
>
> Link:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0220/test-results/distributedTest/1587763613/classes/org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.html#testHAEventWrapperDoesNotHoldCUMOnceInsideCMR
> Partial stack:
> {noformat}
> Caused by: org.junit.ComparisonFailure: expected: but
> was: bytes;threadID=3;sequenceID=14];shouldConflate=false;versionTag={v1; rv6;
> time=1587758285078; remote};hasCqs=false]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.verifyNullCUMReference(HARQueueNewImplDUnitTest.java:855)
> at
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.lambda$testHAEventWrapperDoesNotHoldCUMOnceInsideCMR$bb17a952$4(HARQueueNewImplDUnitTest.java:683)
> {noformat}
> Full stack:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest$$Lambda$260/1730948285.run
> in VM 1 running on Host c8674217ee1c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> at
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.testHAEventWrapperDoesNotHoldCUMOnceInsideCMR(HARQueueNewImplDUnitTest.java:683)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:59)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnit
[jira] [Commented] (GEODE-9508) CI Failure: PartitionedRegionSingleHopWithServerGroupDUnitTest tests fail when verifying metadata
[
https://issues.apache.org/jira/browse/GEODE-9508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399920#comment-17399920
]
Geode Integration commented on GEODE-9508:
--
Seen in [distributed-test-openjdk8
#1218|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1218]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628920271/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628920271/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> CI Failure: PartitionedRegionSingleHopWithServerGroupDUnitTest tests fail
> when verifying metadata
> -
>
> Key: GEODE-9508
> URL: https://issues.apache.org/jira/browse/GEODE-9508
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> Creating this ticket to consolidate other similar failures in the
> PartitionedRegionSingleHopWithServerGroupDUnitTest class.
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest
> > test_SingleHopWithServerGroupTwoClientOneWithOneWithoutServerGroup FAILED
> org.junit.ComparisonFailure: expected:<[2]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest.verifyMetadata(PartitionedRegionSingleHopWithServerGroupDUnitTest.java:612)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientOneWithOneWithoutServerGroup(PartitionedRegionSingleHopWithServerGroupDUnitTest.java:504)
> 8294 tests completed, 1 failed, 413 skipped
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628920271/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628920271/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9508) CI Failure: PartitionedRegionSingleHopWithServerGroupDUnitTest tests fail when verifying metadata
Donal Evans created GEODE-9508:
--
Summary: CI Failure:
PartitionedRegionSingleHopWithServerGroupDUnitTest tests fail when verifying
metadata
Key: GEODE-9508
URL: https://issues.apache.org/jira/browse/GEODE-9508
Project: Geode
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Donal Evans
Creating this ticket to consolidate other similar failures in the
PartitionedRegionSingleHopWithServerGroupDUnitTest class.
{noformat}
org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest
> test_SingleHopWithServerGroupTwoClientOneWithOneWithoutServerGroup FAILED
org.junit.ComparisonFailure: expected:<[2]> but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest.verifyMetadata(PartitionedRegionSingleHopWithServerGroupDUnitTest.java:612)
at
org.apache.geode.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientOneWithOneWithoutServerGroup(PartitionedRegionSingleHopWithServerGroupDUnitTest.java:504)
8294 tests completed, 1 failed, 413 skipped
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628920271/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628920271/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399911#comment-17399911
]
Donal Evans commented on GEODE-9071:
Seen in mass test run on develop, artifacts below:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628946920/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628946920/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz
> CI Failure: PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy
> ---
>
> Key: GEODE-9071
> URL: https://issues.apache.org/jira/browse/GEODE-9071
> Project: Geode
> Issue Type: Bug
> Components: cq
>Affects Versions: 1.12.3, 1.13.3, 1.14.0, 1.15.0
>Reporter: Jens Deppe
>Priority: Major
> Labels: caching-applications
>
> {noformat}
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy FAILED
> 10:10:22org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$87/434016892.run
> in VM 2 running on Host bb8c1d338b8b with 4 VMs
> 10:10:22at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 10:10:22at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testRemoveAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:243)
> 10:10:22
> 10:10:22Caused by:
> 10:10:22org.junit.ComparisonFailure: expected:<[999]> but was:<[645]>
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 10:10:22at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testRemoveAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:251)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-results/distributedTest/1616696789/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-artifacts/1616696789/distributedtestfiles-OpenJDK8-1.15.0-build.0082.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399907#comment-17399907 ] ASF subversion and git services commented on GEODE-9501: Commit 95c6b5ee53f9c8b7525fd34885cd9f3284d579d4 in geode-native's branch refs/heads/develop from Michael Martell [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=95c6b5e ] GEODE-9501: Works with toolset Microsoft v142 (#841) * Use default WindowsSDK for ACE * Cleaner Windows tools configuration > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399904#comment-17399904 ] ASF GitHub Bot commented on GEODE-9501: --- mmartell merged pull request #841: URL: https://github.com/apache/geode-native/pull/841 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to destroy"
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-706:
--
Description:
git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
{noformat}
Error Message
com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
Stacktrace
com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
at
com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
at
com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
at
com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Standard Output
Previously run tests: [IndexCommandsDUnitTest, ConfigCommandsDUnitTest,
FunctionCommandsDUnitTest, ListAndDescribeDiskStoreCommandsDUnitTest,
MiscellaneousCommandsExportLogsPart4DUnitTest,
MiscellaneousCommandsExportLogsPart2DUnitTest,
GetCommandOnRegionWithCacheLoaderDuringCacheMissDUnitTest,
ListAndDescribeRegionDUnitTest, MiscellaneousCommandsExportLogsPart3DUnitTest,
UserCommandsDUnitTest, SharedConfigurationDUnitTest, TestLocatorsDUnitTest,
TestFunctionsDUnitTest, TestClientIdsDUnitTest, TestHeapDUnitTest,
TestSubscriptionsDUnitTest, DynamicRegionDUnitTest, PutAllMultiVmDUnitTest,
RolePerformanceDUnitTest, PutAllCallBkRemoteVMDUnitTest, CacheXml41DUnitTest,
ClearMultiVmDUnitTest, DiskDistributedNoAckAsyncRegionDUnitTest]
{noformat}
Stack trace from the most recent failure on 08/14/21:
{noformat}
org.apache.geode.cache30.DiskDist
[jira] [Commented] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to destroy"
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399903#comment-17399903
]
Donal Evans commented on GEODE-706:
---
Reopening and editing the ticket name as this failure was seen again recently
in a mass test run. The artifacts in the above comment also include an
unrelated failure in PartitionedRegionCqQueryDUnitTest.
> CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to
> destroy"
>
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating, 1.15.0
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
> Fix For: 1.1.0
>
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
> at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(
[jira] [Updated] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to destroy"
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-706:
--
Summary: CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry
failed to destroy" (was: CI failure: RegionTestCase.testEntryIdleDestroy fails
with )
> CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to
> destroy"
>
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating, 1.15.0
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
> Fix For: 1.1.0
>
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
> at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Standard Output
> Previously run tests: [IndexCommandsDUnitTest, ConfigCommand
[jira] [Commented] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to destroy"
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399901#comment-17399901
]
Geode Integration commented on GEODE-706:
-
Seen in [distributed-test-openjdk8
#1247|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1247]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628946920/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628946920/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> CI failure: RegionTestCase.testEntryIdleDestroy fails with "Entry failed to
> destroy"
>
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating, 1.15.0
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
> Fix For: 1.1.0
>
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
> at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
[jira] [Updated] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-706:
--
Affects Version/s: 1.15.0
Summary: CI failure: RegionTestCase.testEntryIdleDestroy (was:
CI failure: DiskDistributedNoAckAsyncRegionDUnitTest.testEntryIdleDestroy)
> CI failure: RegionTestCase.testEntryIdleDestroy
> ---
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating, 1.15.0
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
> Fix For: 1.1.0
>
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
> at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Standard Output
> Previously run tests: [IndexCommandsDUnitTest, ConfigCommandsDUnitTest,
> FunctionCommandsDUnitTest, ListAndDescribeDisk
[jira] [Updated] (GEODE-706) CI failure: RegionTestCase.testEntryIdleDestroy fails with
[
https://issues.apache.org/jira/browse/GEODE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-706:
--
Summary: CI failure: RegionTestCase.testEntryIdleDestroy fails with (was:
CI failure: RegionTestCase.testEntryIdleDestroy)
> CI failure: RegionTestCase.testEntryIdleDestroy fails with
> ---
>
> Key: GEODE-706
> URL: https://issues.apache.org/jira/browse/GEODE-706
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating, 1.15.0
>Reporter: Jens Deppe
>Assignee: Hitesh Khamesra
>Priority: Major
> Labels: CI, Flaky
> Fix For: 1.1.0
>
>
> git rev e3d24d77150382f363f334b3e2d6622c6e02e8bc build #948
> {noformat}
> Error Message
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> Stacktrace
> com.gemstone.gemfire.InternalGemFireError: Entry failed to destroy
> at com.gemstone.gemfire.internal.Assert.throwError(Assert.java:91)
> at com.gemstone.gemfire.internal.Assert.assertTrue(Assert.java:115)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2074)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.waitForDestroy(RegionTestCase.java:2034)
> at
> com.gemstone.gemfire.cache30.RegionTestCase.testEntryIdleDestroy(RegionTestCase.java:3569)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Standard Output
> Previously run tests: [IndexCommandsDUnitTest, ConfigCommandsDUnitTest,
> FunctionCommandsDUnitTest, ListAndDescribeDiskStoreCommandsDUnitTest,
> Mis
[jira] [Assigned] (GEODE-9507) AssertJ Assertions should be used instead of Java6Assertions
[
https://issues.apache.org/jira/browse/GEODE-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-9507:
Assignee: Kirk Lund
> AssertJ Assertions should be used instead of Java6Assertions
>
>
> Key: GEODE-9507
> URL: https://issues.apache.org/jira/browse/GEODE-9507
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> AssertJ Java6Assertions is deprecated, but it's easy to accidentally import
> it for use in a new test instead of Assertions because of the way IntelliJ
> adds the imports:
> {noformat}
> import static org.assertj.core.api.Java6Assertions.assertThat;
> {noformat}
> Should change to:
> {noformat}
> import static org.assertj.core.api.Assertions.assertThat;
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9507) AssertJ Assertions should be used instead of Java6Assertions
Kirk Lund created GEODE-9507:
Summary: AssertJ Assertions should be used instead of
Java6Assertions
Key: GEODE-9507
URL: https://issues.apache.org/jira/browse/GEODE-9507
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Kirk Lund
AssertJ Java6Assertions is deprecated, but it's easy to accidentally import it
for use in a new test instead of Assertions because of the way IntelliJ adds
the imports:
{noformat}
import static org.assertj.core.api.Java6Assertions.assertThat;
{noformat}
Should change to:
{noformat}
import static org.assertj.core.api.Assertions.assertThat;
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9507) AssertJ Assertions should be used instead of Java6Assertions
[
https://issues.apache.org/jira/browse/GEODE-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9507:
-
Labels: GeodeOperationAPI (was: )
> AssertJ Assertions should be used instead of Java6Assertions
>
>
> Key: GEODE-9507
> URL: https://issues.apache.org/jira/browse/GEODE-9507
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
>
> AssertJ Java6Assertions is deprecated, but it's easy to accidentally import
> it for use in a new test instead of Assertions because of the way IntelliJ
> adds the imports:
> {noformat}
> import static org.assertj.core.api.Java6Assertions.assertThat;
> {noformat}
> Should change to:
> {noformat}
> import static org.assertj.core.api.Assertions.assertThat;
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9501: -- Labels: pull-request-available (was: ) > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9501) Support Latest Microsoft Platform Toolset and Compilers for C++
[ https://issues.apache.org/jira/browse/GEODE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399893#comment-17399893 ] ASF GitHub Bot commented on GEODE-9501: --- pdxcodemonkey commented on a change in pull request #841: URL: https://github.com/apache/geode-native/pull/841#discussion_r689741407 ## File path: ci/base/base.yml ## @@ -61,7 +61,7 @@ builds: with_dot_net: #@ True #@yaml/map-key-override params: - CMAKE_CONFIGURE_FLAGS: "-A x64 -Tv141,version=14.16,host=x64 -DCMAKE_SYSTEM_VERSION=10.0.16299.0" Review comment: Okay, so some Googling tells me that for cmake 3.13 or newer, we need to ditch "Win64" in the -G parameter and use "-A x64" to configure 64-bit builds: https://stackoverflow.com/questions/28350214/how-to-build-x86-and-or-x64-on-windows-from-command-line-with-cmake And "-T host=x64" is used only to specifically force 64-bit toolset, so I don't suppose this is anything other than maybe a small performance hit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support Latest Microsoft Platform Toolset and Compilers for C++ > --- > > Key: GEODE-9501 > URL: https://issues.apache.org/jira/browse/GEODE-9501 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > > Currently, the Windows build of geode-native uses Platform Toolset v141. This > ticket is to build using the default Platform Toolset and compiler which is > v142. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9506:
---
Description:
{noformat}
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
sessionOperationsDoNotFail_whileServersAreRestarted FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3 running
on Host
heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
at
org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
Caused by:
org.apache.geode.management.ManagementException: Could not start server
compatible with Redis using bind address: /127.0.0.1 and port: 35275. Please
make sure nothing else is running on this address/port combination.
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
at
org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
at
org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
at
org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
at
org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
at
org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
at
org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
at
org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
at
org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.rmi.tran
[jira] [Commented] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399890#comment-17399890
]
Geode Integration commented on GEODE-9506:
--
Seen in [distributed-test-openjdk8
#1210|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1210]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628912682/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628912682/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnit
[jira] [Created] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
Donal Evans created GEODE-9506:
--
Summary: CI Failure: BindException in SessionsAndCrashesDUnitTest
Key: GEODE-9506
URL: https://issues.apache.org/jira/browse/GEODE-9506
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
{noformat}
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
sessionOperationsDoNotFail_whileServersAreRestarted FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3 running
on Host
heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
at
org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
Caused by:
org.apache.geode.management.ManagementException: Could not start server
compatible with Redis using bind address: /127.0.0.1 and port: 35275. Please
make sure nothing else is running on this address/port combination.
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
at
org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
at
org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
at
org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
at
org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
at
org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
at
org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
at
org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
at
org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at
sun.
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399887#comment-17399887 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399886#comment-17399886 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399881#comment-17399881 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399883#comment-17399883 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399882#comment-17399882 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399885#comment-17399885 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399884#comment-17399884 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399880#comment-17399880 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399874#comment-17399874 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399876#comment-17399876 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399878#comment-17399878 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399872#comment-17399872 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399875#comment-17399875 ] ASF GitHub Bot commented on GEODE-9356: --- mreddington merged pull request #839: URL: https://github.com/apache/geode-native/pull/839 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399879#comment-17399879 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9365) HARegionQueue over throttles when multiple threads attempt concurrent adds
[ https://issues.apache.org/jira/browse/GEODE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399873#comment-17399873 ] ASF subversion and git services commented on GEODE-9365: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > HARegionQueue over throttles when multiple threads attempt concurrent adds > -- > > Key: GEODE-9365 > URL: https://issues.apache.org/jira/browse/GEODE-9365 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Darrel Schneider >Assignee: Mark Hanson >Priority: Major > Labels: GeodeOperationAPI > > HARegionQueue.checkQueueSizeConstraint has some code that implements a > "throttle" on adds to a queue that is full. It is supposed to wait > "eventEnqueueWaitTime" before doing an add. But because this code does two > syncs (putGuard and permitMon) and only waits on one of them, it holds the > other sync for the duration of this threads throttle. Any other concurrent > thread trying to add to the queue gets stuck on the putGuard sync that is > held by the first thread that is doing the timed wait. So it ends up waiting > "eventEnqueueWaitTime" to acquire the first sync and then ends up waiting > again "eventEnqueueWaitTime" when it does its own timed wait. If you have 10 > concurrent threads trying to add one of them will end up waiting 10 * > "eventEnqueueWaitTime". > A couple ideas of how to fix this. Get rid of the putGuard and just use > permitMon. Then as soon as the first thread goes into its timed wait another > thread is allowed to sync on permitMon. But if this is done then we need to > think carefully about the code inside this sync block since it can not be > executed while one or more other threads are waiting in permitMon. > The other solution would be to compute the elapsed time it took to get into > the first sync and subtract that from the time we wait on permitMon. This > seems like a simple solution but does introduce at least one call of get time > (the second call is only needed if the queue is full). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399877#comment-17399877 ] ASF subversion and git services commented on GEODE-9356: Commit 53941d0e3e9091680bd9f24c20c9e53a9e66a1df in geode-native's branch refs/heads/develop from Matthew Reddington [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=53941d0 ] GEODE-9356: Adding NetCore and testing to the CI. (#839) * GEODE-9365: Building netcore as part of ALL. * GEODE-9356: Added missing newline. * GEODE-9356: Finding the dotnet program and added a compile option. * GEODE-9356: Adding .Net 5 to Windows builds. * GEODE-9356: Changed .Net SDK to 3.1, installing NetCore dll. * GEODE-9356: Code review changes. * GEODE-9356: Installing .Net toolchain to Linux platforms. * GEODE-9356: Changed a variable name. * GEODE-9356: Moved .NET install to its own script. * GEODE-9356: Added netcore unit tests. * GEODE-9356: Added missing endif. * GEODE-9356: Shooting in the dark because... YAML... * GEODE-9356: .Net tasks can fail the pipeline. * GEODE-9356: Code review changes. > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9486) Serialized classes in geode-serializable fail to deserialize when validate-serializable-objects is enabled
[
https://issues.apache.org/jira/browse/GEODE-9486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399866#comment-17399866
]
Geode Integration commented on GEODE-9486:
--
Seen in [distributed-test-openjdk8
#1204|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1204]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628912577/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628912577/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> Serialized classes in geode-serializable fail to deserialize when
> validate-serializable-objects is enabled
> --
>
> Key: GEODE-9486
> URL: https://issues.apache.org/jira/browse/GEODE-9486
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
>
> Serialized classes in geode-serializable fail to deserialize when
> {{validate-serializable-objects}} is enabled. This bug was caught by
> {{SessionsAndCrashesDUnitTest}} in geode-apis-compatible-with-redis
> (GEODE-9485):
> {noformat}
> [fatal 2021/08/04 13:50:57.548 UTC tid=114]
> Serialization filter is rejecting class
> org.apache.geode.internal.serialization.DSFIDNotFoundException
> java.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:234)
> at com.sun.proxy.$Proxy26.checkInput(Unknown Source)
> at
> java.base/java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1336)
> at
> java.base/java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:2005)
> at
> java.base/java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1862)
> at
> java.base/java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2169)
> at
> java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1679)
> {noformat}
> Any module with a class that may be serialized must implement
> {{DistributedSystemService}} to provide the list of sanctioned serializables
> as defined in {{sanctionedDataSerializables.txt}} and a concrete test
> subclassing {{AnalyzeSerializablesJUnitTestBase}}.
> {{org.apache.geode.internal.serialization.DSFIDNotFoundException}} is in
> geode-serialization which cannot depend on geode-core which owns
> {{DistributedSystemService}}. Even if we remove the unused {{void
> init(InternalDistributedSystem internalDistributedSystem)}} and move it to
> geode-serialization, {{SerializationDistributedSystemService}} would need to
> implement {{getSerializationAcceptlist()}} as:
> {noformat}
> @Override
> public Collection getSerializationAcceptlist() throws IOException {
> URL sanctionedSerializables =
> ClassPathLoader.getLatest().getResource(getClass(),
> "sanctioned-geode-gfsh-serializables.txt");
> return InternalDataSerializer.loadClassNames(sanctionedSerializables);
> }
> {noformat}
> ... which uses {{ClassPathLoader}} and {{InternalDataSerializer}} which live
> in geode-core.
> This requires moving the classes {{ClassPathLoader}} and
> {{InternalDataSerializer}} that need to be used within
> {{getSerializationAcceptlist()}}.
> {{ClassPathLoader}} depends on geode deployment:
> {noformat}
> import org.apache.geode.internal.deployment.DeploymentServiceFactory;
> import org.apache.geode.internal.deployment.JarDeploymentService;
> {noformat}
> {{InternalDataSerializer}} gets even more complicated with many dependencies.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17399864#comment-17399864
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#1220|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1220]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628921671/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628921671/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> 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
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17399862#comment-17399862
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#1207|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1207]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628911721/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628911721/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> 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
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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.3.4#803005)
[jira] [Resolved] (GEODE-9332) CI Failure: JmxServerReconnectDistributedTest > serverMXBeansOnServerAreUnaffectedByLocatorCrash
[
https://issues.apache.org/jira/browse/GEODE-9332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-9332.
Resolution: Duplicate
> CI Failure: JmxServerReconnectDistributedTest >
> serverMXBeansOnServerAreUnaffectedByLocatorCrash
>
>
> Key: GEODE-9332
> URL: https://issues.apache.org/jira/browse/GEODE-9332
> Project: Geode
> Issue Type: Test
> Components: jmx, tests
>Reporter: Owen Nichols
>Priority: Major
>
> {noformat}
> java.lang.AssertionError: [GemFire mxbeans on locator2]
> Expecting HashSet:
> [GemFire:type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator2,
> GemFire:service=Region,name=/region,type=Member,member=server,
> GemFire:service=Manager,type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator2,
> GemFire:type=Member,member=locator2,
> GemFire:type=Member,member=server,
> GemFire:service=FileUploader,type=Distributed,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator2,
> GemFire:service=Manager,type=Member,member=locator2,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=System,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=Region,name=/region,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]
> to contain:
> [GemFire:type=Member,member=locator1,
> GemFire:service=Locator,type=Member,member=locator1,
> GemFire:service=Manager,type=Member,member=locator1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]
> but could not find the following element(s):
>
> [GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator1]
> at
> org.apache.geode.management.JmxServerReconnectDistributedTest.lambda$null$7(JmxServerReconnectDistributedTest.java:203)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17399861#comment-17399861
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#1251|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1251]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628953139/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628953139/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> 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
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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.3.4#803005)
[jira] [Updated] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans updated GEODE-8644: --- Affects Version/s: 1.15.0 > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[
https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399847#comment-17399847
]
Donal Evans commented on GEODE-8644:
Seen in a mass test run on 1.15, artifacts below:
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628970863/}}
{{=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=}}
{{Test report artifacts from this job are available at:}}
{{http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628970863/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz}}
> SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely()
> intermittently fails when queues drain too slowly
> ---
>
> Key: GEODE-8644
> URL: https://issues.apache.org/jira/browse/GEODE-8644
> Project: Geode
> Issue Type: Bug
>Reporter: Benjamin P Ross
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Currently the test
> SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely()
> relies on a 2 second delay to allow for queues to finish draining after
> finishing the put operation. If queues take longer than 2 seconds to drain
> the test will fail. We should change the test to wait for the queues to be
> empty with a long timeout in case the queues never fully drain.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17399846#comment-17399846
]
Geode Integration commented on GEODE-7710:
--
Seen in [distributed-test-openjdk8
#1275|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1275]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-results/distributedTest/1628970863/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0406/test-artifacts/1628970863/distributedtestfiles-openjdk8-1.15.0-build.0406.tgz].
> 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
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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.3.4#803005)
[jira] [Created] (GEODE-9505) enhance geode to support zgc
Darrel Schneider created GEODE-9505: --- Summary: enhance geode to support zgc Key: GEODE-9505 URL: https://issues.apache.org/jira/browse/GEODE-9505 Project: Geode Issue Type: Improvement Components: core Reporter: Darrel Schneider Geode has a ResourceManger that interacts with the jvm garbage collector. It wants to know how much "tenured" memory the jvm currently has allocated. To do this it needs to know which of the jvm's memory pools represents tenured memory. In the case of ZGC, it currently (as of java 17) does not support generations so it has just one memory pool. It is named "ZHeap". For geode to support zgc the method org.apache.geode.internal.cache.control.HeapMemoryMonitor#isTenured needs to be enhanced to recognize the pool named "ZHeap" as the tenured pool. A work around currently exists in geode. By setting the system property "gemfire.ResourceManager.HEAP_POOL" to "ZHeap" geode should work with ZGC. Note that ZGC is available as of java 11 so we don't need to use java 16. ZGC became production ready in java 15. Before java 15 it required that a command line option to enable experimental features. java 16 ZGC has been optimized compared to java 15. java 16 requires --illegal-access=permit so that our calls to setAccessible will not blow up and we could just make this one of our ZGC command line options. As far as I can tell java 17 has no new ZGC features but it does drop support for --illegal-access=permit and instead --add-opens will need to be used. Look for geode tickets with the "java16" label to see all the product features that currently have illegal-access issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9504) geode-web-api needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9504: - Description: There are 20+ classes not counting Exceptions and Enums in geode-web-api, but there are only 3 unit tests and 1 integration test. Unit tests should be written with Mockito to verify that each class is interacting properly with its collaborators and validate as much logic or behavior as possible. was: There are 20+ classes not counting Exceptions and Enums in geode-web-api, but there are only 3 unit tests. Unit tests should be written with Mockito to verify that each class is interacting properly with its collaborators and validate as much logic or behavior as possible. > geode-web-api needs unit tests > -- > > Key: GEODE-9504 > URL: https://issues.apache.org/jira/browse/GEODE-9504 > Project: Geode > Issue Type: Test > Components: rest (dev) >Reporter: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI > > There are 20+ classes not counting Exceptions and Enums in geode-web-api, but > there are only 3 unit tests and 1 integration test. > Unit tests should be written with Mockito to verify that each class is > interacting properly with its collaborators and validate as much logic or > behavior as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9504) geode-web-api needs unit tests
[ https://issues.apache.org/jira/browse/GEODE-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9504: - Labels: GeodeOperationAPI (was: ) > geode-web-api needs unit tests > -- > > Key: GEODE-9504 > URL: https://issues.apache.org/jira/browse/GEODE-9504 > Project: Geode > Issue Type: Test > Components: rest (dev) >Reporter: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI > > There are 20+ classes not counting Exceptions and Enums in geode-web-api, but > there are only 3 unit tests. > Unit tests should be written with Mockito to verify that each class is > interacting properly with its collaborators and validate as much logic or > behavior as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9504) geode-web-api needs unit tests
Kirk Lund created GEODE-9504: Summary: geode-web-api needs unit tests Key: GEODE-9504 URL: https://issues.apache.org/jira/browse/GEODE-9504 Project: Geode Issue Type: Test Components: rest (dev) Reporter: Kirk Lund There are 20+ classes not counting Exceptions and Enums in geode-web-api, but there are only 3 unit tests. Unit tests should be written with Mockito to verify that each class is interacting properly with its collaborators and validate as much logic or behavior as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9503) Improve BUILDING.md
Michael Martell created GEODE-9503: -- Summary: Improve BUILDING.md Key: GEODE-9503 URL: https://issues.apache.org/jira/browse/GEODE-9503 Project: Geode Issue Type: Improvement Components: native client Reporter: Michael Martell The BUILDING.md is missing a few items that may help developers who wish to build/test/debug geode-native. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9493) redis data structure sizing is hard coded for compressed oops
[ https://issues.apache.org/jira/browse/GEODE-9493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399818#comment-17399818 ] ASF subversion and git services commented on GEODE-9493: Commit 1210cbc48c80df9d4f87a94cd417e424b85cbccf in geode's branch refs/heads/develop from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1210cbc ] GEODE-9493: rework sizing of RedisString, RedisHash, RedisSet, and RedisSortedSet (#6727) Removed SizeableObjectSizer and made the Sizeable redis classes abstract. They now require subclasses that implement sizeKey, sizeValue, or sizeElement. Instead of having hard coded constants stating what the size of a redis base class is, the code now uses JvmSizeUtils.memoryOverhead(Class) to statically compute the class size overhead. This allows the size to be correct for different jvm configs. Also simplified the sizing logic to use int and if needed use casts instead of narrow. Narrow was more expensive and would still cause problems as the size goes back down toward zero. The sizing of OrderStatisticsTree was simplified some more since it did not need an extra int field since we do not keep track of its element sizes. Also the size of the hashing strategy object is no longer accounted for since it is a singleton. OrderStatisticsTree has been simplified to not size the elements it contains. It is currently only used by RedisSortedSet and it does not need the element size to be computed (it already is done in the hash map it also uses). If in the future we need to also size the elements of an OrderStatisticsTree we can figure out the best way to do that then in that new context. > redis data structure sizing is hard coded for compressed oops > - > > Key: GEODE-9493 > URL: https://issues.apache.org/jira/browse/GEODE-9493 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The sizing of the redis data structures (string, hash, set, sorted set) has > some constants that were precomputed by tests. Because the tests are run with > smaller heaps that use compressed oops the size estimates end up being too > small for large heaps or if compressed oops are disabled. > Also a "strategy" object is currently part of the size and should not be > since it is a single canonical instance shared by all hash and set instances. > Also the way sizing is currently done does not take advantage of us knowing > the element type. By optimizing the code for "byte[]" for example we can > compute the size faster and use less memory by storing less "sizing" state in > our objects. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9493) redis data structure sizing is hard coded for compressed oops
[ https://issues.apache.org/jira/browse/GEODE-9493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-9493. - Fix Version/s: 1.15.0 Resolution: Fixed > redis data structure sizing is hard coded for compressed oops > - > > Key: GEODE-9493 > URL: https://issues.apache.org/jira/browse/GEODE-9493 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The sizing of the redis data structures (string, hash, set, sorted set) has > some constants that were precomputed by tests. Because the tests are run with > smaller heaps that use compressed oops the size estimates end up being too > small for large heaps or if compressed oops are disabled. > Also a "strategy" object is currently part of the size and should not be > since it is a single canonical instance shared by all hash and set instances. > Also the way sizing is currently done does not take advantage of us knowing > the element type. By optimizing the code for "byte[]" for example we can > compute the size faster and use less memory by storing less "sizing" state in > our objects. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9356) Create CI pipeline for net-core
[ https://issues.apache.org/jira/browse/GEODE-9356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399771#comment-17399771 ] ASF GitHub Bot commented on GEODE-9356: --- mreddington commented on a change in pull request #839: URL: https://github.com/apache/geode-native/pull/839#discussion_r688096228 ## File path: packer/build-windows-2016-vs-2017.json ## @@ -92,7 +92,8 @@ "choco install doxygen.install -confirm", "choco install openssl -confirm", "choco install strawberryperl -confirm", -"choco install nuget.commandline -confirm" +"choco install nuget.commandline -confirm", +"choco install dotnetcore-sdk -confirm" Review comment: We build against 3.1. Choco documentation says this package is 3.1. The bash install script specifies 3.1 explicitly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Create CI pipeline for net-core > --- > > Key: GEODE-9356 > URL: https://issues.apache.org/jira/browse/GEODE-9356 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > > This pipeline will be hosted on the Apache publicly available Concourse and > publish to NuGet -- This message was sent by Atlassian Jira (v8.3.4#803005)
