[jira] [Created] (GEODE-10381) CI Failure: SocketCreatorUpgradeTest.upgradingToNewGeodeAndNewJavaWithProtocolsTLSv1_2WithNewProperties[1.13.1] FAILED

Eric Shu created GEODE-10381: Summary: CI Failure: SocketCreatorUpgradeTest.upgradingToNewGeodeAndNewJavaWithProtocolsTLSv1_2WithNewProperties[1.13.1] FAILED Key: GEODE-10381 URL:

[jira] [Assigned] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

[ https://issues.apache.org/jira/browse/GEODE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10373: Assignee: Robert Houghton > CI Failures: Windows geode-lucene:integrationTest hitting OOM cause

[jira] [Created] (GEODE-10373) CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout

Eric Shu created GEODE-10373: Summary: CI Failures: Windows geode-lucene:integrationTest hitting OOM cause CI test run to timeout Key: GEODE-10373 URL: https://issues.apache.org/jira/browse/GEODE-10373

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552368#comment-17552368 ] Eric Shu commented on GEODE-10372: -- Remove needs to triage label as this seems has the same cause of

[jira] [Updated] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10372: - Labels: (was: needsTriage) > CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED >

[jira] [Commented] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

[ https://issues.apache.org/jira/browse/GEODE-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552354#comment-17552354 ] Eric Shu commented on GEODE-10372: -- Possibly has the same cause of GEODE-10195. > CI Failures:

[jira] [Created] (GEODE-10372) CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED

Eric Shu created GEODE-10372: Summary: CI Failures: MicrometerBinderTest.uptimeMetricsBinderExists FAILED Key: GEODE-10372 URL: https://issues.apache.org/jira/browse/GEODE-10372 Project: Geode

[jira] [Resolved] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10294. -- Fix Version/s: 1.15.0 Resolution: Fixed > Need to consider invalid token when comparing value

[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10294: - Fix Version/s: 1.16.0 > Need to consider invalid token when comparing value during putIfAbsent >

[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10294: - Fix Version/s: (was: 1.15.0) (was: 1.16.0) > Need to consider invalid token

[jira] [Reopened] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-10294: -- > Need to consider invalid token when comparing value during putIfAbsent >

[jira] [Updated] (GEODE-10298) [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > testBridgeServerAndGatewayReceiverClientAndServerWithGroup FAILED

[ https://issues.apache.org/jira/browse/GEODE-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10298: - Fix Version/s: (was: 1.16.0) > [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > >

[jira] [Commented] (GEODE-10298) [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > testBridgeServerAndGatewayReceiverClientAndServerWithGroup FAILED

[ https://issues.apache.org/jira/browse/GEODE-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536946#comment-17536946 ] Eric Shu commented on GEODE-10298: -- >From the test code and failed test run logs, this exception thrown

[jira] [Commented] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536943#comment-17536943 ] Eric Shu commented on GEODE-10294: -- This is a safe fix. I think this can be back-ported to 1.15 support

[jira] [Resolved] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10294. -- Fix Version/s: 1.16.0 Resolution: Fixed > Need to consider invalid token when comparing value

[jira] [Resolved] (GEODE-10298) [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > testBridgeServerAndGatewayReceiverClientAndServerWithGroup FAILED

[ https://issues.apache.org/jira/browse/GEODE-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10298. -- Fix Version/s: 1.16.0 Resolution: Fixed > [CI Failure]

[jira] [Reopened] (GEODE-10298) [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > testBridgeServerAndGatewayReceiverClientAndServerWithGroup FAILED

[ https://issues.apache.org/jira/browse/GEODE-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-10298: -- > [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > >

[jira] [Created] (GEODE-10308) CI Failure: Tomcat8SessionsClientServerDUnitTest.testSessionExpiration1 failed

Eric Shu created GEODE-10308: Summary: CI Failure: Tomcat8SessionsClientServerDUnitTest.testSessionExpiration1 failed Key: GEODE-10308 URL: https://issues.apache.org/jira/browse/GEODE-10308 Project:

[jira] [Assigned] (GEODE-10303) CI Failure: MemberMXBeanDistributedTest.testBucketCount failed due to insufficient memory

[ https://issues.apache.org/jira/browse/GEODE-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10303: Assignee: Robert Houghton > CI Failure: MemberMXBeanDistributedTest.testBucketCount failed due

[jira] [Created] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed

Eric Shu created GEODE-10305: Summary: CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed Key: GEODE-10305 URL:

[jira] [Created] (GEODE-10304) CI Failure: ReconnectDUnitTest.testReconnectALocator

Eric Shu created GEODE-10304: Summary: CI Failure: ReconnectDUnitTest.testReconnectALocator Key: GEODE-10304 URL: https://issues.apache.org/jira/browse/GEODE-10304 Project: Geode Issue Type: Bug

[jira] [Created] (GEODE-10303) CI Failure: MemberMXBeanDistributedTest.testBucketCount failed due to insufficient memory

Eric Shu created GEODE-10303: Summary: CI Failure: MemberMXBeanDistributedTest.testBucketCount failed due to insufficient memory Key: GEODE-10303 URL: https://issues.apache.org/jira/browse/GEODE-10303

[jira] [Assigned] (GEODE-10298) [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > testBridgeServerAndGatewayReceiverClientAndServerWithGroup FAILED

[ https://issues.apache.org/jira/browse/GEODE-10298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10298: Assignee: Eric Shu > [CI Failure] GatewayReceiverAutoConnectionSourceDUnitTest > >

[jira] [Assigned] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10294: Assignee: Eric Shu > Need to consider invalid token when comparing value during putIfAbsent >

[jira] [Created] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

Eric Shu created GEODE-10294: Summary: Need to consider invalid token when comparing value during putIfAbsent Key: GEODE-10294 URL: https://issues.apache.org/jira/browse/GEODE-10294 Project: Geode

[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10294: - Labels: blocks-1.15.0 (was: needsTriage) > Need to consider invalid token when comparing value during

[jira] [Resolved] (GEODE-10272) CI failure: SerialGatewaySenderEventProcessor throws RejectedExecutionException in handlePrimaryDestroy

[ https://issues.apache.org/jira/browse/GEODE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10272. -- Fix Version/s: 1.15.0 Resolution: Fixed > CI failure: SerialGatewaySenderEventProcessor throws

[jira] [Resolved] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

[ https://issues.apache.org/jira/browse/GEODE-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10242. -- Fix Version/s: 1.15.0 Resolution: Fixed > Same tail key can be generated for different events

[jira] [Assigned] (GEODE-10272) CI failure: SerialGatewaySenderEventProcessor throws RejectedExecutionException in handlePrimaryDestroy

[ https://issues.apache.org/jira/browse/GEODE-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10272: Assignee: Eric Shu > CI failure: SerialGatewaySenderEventProcessor throws >

[jira] [Updated] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

[ https://issues.apache.org/jira/browse/GEODE-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10242: - Labels: GeodeOperationAPI blocks-1.15.0 needsTriage (was: blocks-1.15.0 needsTriage) > Same tail key

[jira] [Assigned] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

[ https://issues.apache.org/jira/browse/GEODE-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10242: Assignee: Eric Shu > Same tail key can be generated for different events on (different colocated

[jira] [Updated] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

[ https://issues.apache.org/jira/browse/GEODE-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10242: - Labels: blocks-1.15.0 needsTriage (was: needsTriage) > Same tail key can be generated for different

[jira] [Created] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

Eric Shu created GEODE-10242: Summary: Same tail key can be generated for different events on (different colocated regions) from different servers Key: GEODE-10242 URL:

[jira] [Updated] (GEODE-10242) Same tail key can be generated for different events on (different colocated regions) from different servers

[ https://issues.apache.org/jira/browse/GEODE-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10242: - Affects Version/s: 1.12.0 > Same tail key can be generated for different events on (different colocated

[jira] [Updated] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

[ https://issues.apache.org/jira/browse/GEODE-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10234: - Labels: blocks-1.15.0 pull-request-available (was: pull-request-available) > No need to generate

[jira] [Resolved] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

[ https://issues.apache.org/jira/browse/GEODE-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10234. -- Fix Version/s: 1.15.0 Resolution: Fixed > No need to generate tailKey for transaction if there

[jira] [Updated] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

[ https://issues.apache.org/jira/browse/GEODE-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10234: - Affects Version/s: 1.12.0 > No need to generate tailKey for transaction if there is no parallel wan >

[jira] [Updated] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

[ https://issues.apache.org/jira/browse/GEODE-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10234: - Labels: (was: needsTriage) > No need to generate tailKey for transaction if there is no parallel wan

[jira] [Assigned] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

[ https://issues.apache.org/jira/browse/GEODE-10234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10234: Assignee: Eric Shu > No need to generate tailKey for transaction if there is no parallel wan >

[jira] [Created] (GEODE-10234) No need to generate tailKey for transaction if there is no parallel wan enabled

Eric Shu created GEODE-10234: Summary: No need to generate tailKey for transaction if there is no parallel wan enabled Key: GEODE-10234 URL: https://issues.apache.org/jira/browse/GEODE-10234 Project:

[jira] [Resolved] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor

[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10211. -- Fix Version/s: 1.15.0 Resolution: Fixed > A retried operation does not set possible duplicate

[jira] [Updated] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor

[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10211: - Labels: GeodeOperationAPI blocks-1.15.0​ (was: needsTriage) > A retried operation does not set

[jira] [Assigned] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor

[ https://issues.apache.org/jira/browse/GEODE-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10211: Assignee: Eric Shu > A retried operation does not set possible duplicate in the event if retried

[jira] [Created] (GEODE-10211) A retried operation does not set possible duplicate in the event if retried on an accessor

Eric Shu created GEODE-10211: Summary: A retried operation does not set possible duplicate in the event if retried on an accessor Key: GEODE-10211 URL: https://issues.apache.org/jira/browse/GEODE-10211

[jira] [Resolved] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client

[ https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10199. -- Fix Version/s: 1.15.0 Resolution: Fixed > A retried putIfAbsent operation may not be

[jira] [Updated] (GEODE-10162) A retried operation may sometimes not set valid tag

[ https://issues.apache.org/jira/browse/GEODE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10162: - Labels: GeodeOperationAPI blocks-1.15.0 pull-request-available (was: GeodeOperationAPI

[jira] [Updated] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client

[ https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10199: - Labels: GeodeOperationAPI blocks-1.15.0 (was: GeodeOperationAPI) > A retried putIfAbsent operation may

[jira] [Updated] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client

[ https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10199: - Labels: GeodeOperationAPI (was: needsTriage) > A retried putIfAbsent operation may not be distributed

[jira] [Resolved] (GEODE-10162) A retried operation may sometimes not set valid tag

[ https://issues.apache.org/jira/browse/GEODE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10162. -- Fix Version/s: 1.15.0 Resolution: Fixed > A retried operation may sometimes not set valid tag

[jira] [Assigned] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client

[ https://issues.apache.org/jira/browse/GEODE-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10199: Assignee: Eric Shu > A retried putIfAbsent operation may not be distributed to peer and its

[jira] [Created] (GEODE-10199) A retried putIfAbsent operation may not be distributed to peer and its client

Eric Shu created GEODE-10199: Summary: A retried putIfAbsent operation may not be distributed to peer and its client Key: GEODE-10199 URL: https://issues.apache.org/jira/browse/GEODE-10199 Project: Geode

[jira] [Resolved] (GEODE-10182) A null check due to detecting read conflict is no longer necessary

[ https://issues.apache.org/jira/browse/GEODE-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10182. -- Fix Version/s: 1.15.0 Resolution: Fixed > A null check due to detecting read conflict is no

[jira] [Updated] (GEODE-10182) A null check due to detecting read conflict is no longer necessary

[ https://issues.apache.org/jira/browse/GEODE-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10182: - Labels: GeodeOperationAPI (was: needsTriage) > A null check due to detecting read conflict is no

[jira] [Updated] (GEODE-10182) A null check due to detecting read conflict is no longer necessary

[ https://issues.apache.org/jira/browse/GEODE-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10182: - Affects Version/s: 1.12.2 > A null check due to detecting read conflict is no longer necessary >

[jira] [Assigned] (GEODE-10182) A null check due to detecting read conflict is no longer necessary

[ https://issues.apache.org/jira/browse/GEODE-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10182: Assignee: Eric Shu > A null check due to detecting read conflict is no longer necessary >

[jira] [Created] (GEODE-10182) A null check due to detecting read conflict is no longer necessary

Eric Shu created GEODE-10182: Summary: A null check due to detecting read conflict is no longer necessary Key: GEODE-10182 URL: https://issues.apache.org/jira/browse/GEODE-10182 Project: Geode

[jira] [Updated] (GEODE-10162) A retried operation may sometimes not set valid tag

[ https://issues.apache.org/jira/browse/GEODE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10162: - Labels: GeodeOperationAPI (was: needsTriage) > A retried operation may sometimes not set valid tag >

[jira] [Assigned] (GEODE-10162) A retried operation may sometimes not set valid tag

[ https://issues.apache.org/jira/browse/GEODE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10162: Assignee: Eric Shu > A retried operation may sometimes not set valid tag >

[jira] [Created] (GEODE-10162) A retried operation may sometimes not set valid tag

Eric Shu created GEODE-10162: Summary: A retried operation may sometimes not set valid tag Key: GEODE-10162 URL: https://issues.apache.org/jira/browse/GEODE-10162 Project: Geode Issue Type: Bug

[jira] [Created] (GEODE-10156) RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.12.0] FAILED

Eric Shu created GEODE-10156: Summary: RollingUpgradeWithGfshDUnitTest > testRollingUpgradeWithDeployment[1.12.0] FAILED Key: GEODE-10156 URL: https://issues.apache.org/jira/browse/GEODE-10156 Project:

[jira] [Updated] (GEODE-10130) cq destroy event in replicate region can be missing

[ https://issues.apache.org/jira/browse/GEODE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10130: - Affects Version/s: 1.14.0 (was: 1.15.0) (was:

[jira] [Resolved] (GEODE-10130) cq destroy event in replicate region can be missing

[ https://issues.apache.org/jira/browse/GEODE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10130. -- Fix Version/s: 1.15.0 Resolution: Fixed > cq destroy event in replicate region can be missing

[jira] [Commented] (GEODE-10132) org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest Failed

[ https://issues.apache.org/jira/browse/GEODE-10132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508364#comment-17508364 ] Eric Shu commented on GEODE-10132: -- GEODE-5603 was closed as duplicate of

[jira] [Created] (GEODE-10132) org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest Failed

Eric Shu created GEODE-10132: Summary: org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest Failed Key: GEODE-10132 URL: https://issues.apache.org/jira/browse/GEODE-10132 Project:

[jira] [Updated] (GEODE-10130) cq destroy event in replicate region can be missing

[ https://issues.apache.org/jira/browse/GEODE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10130: - Labels: GeodeOperationAPI (was: needsTriage) > cq destroy event in replicate region can be missing >

[jira] [Assigned] (GEODE-10130) cq destroy event in replicate region can be missing

[ https://issues.apache.org/jira/browse/GEODE-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10130: Assignee: Eric Shu > cq destroy event in replicate region can be missing >

[jira] [Created] (GEODE-10130) cq destroy event in replicate region can be missing

Eric Shu created GEODE-10130: Summary: cq destroy event in replicate region can be missing Key: GEODE-10130 URL: https://issues.apache.org/jira/browse/GEODE-10130 Project: Geode Issue Type: Bug

[jira] [Resolved] (GEODE-10114) NullPointerException is logged if create index when cache is closing.

[ https://issues.apache.org/jira/browse/GEODE-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10114. -- Fix Version/s: 1.16.0 Resolution: Fixed > NullPointerException is logged if create index when

[jira] [Updated] (GEODE-10114) NullPointerException is logged if create index when cache is closing.

[ https://issues.apache.org/jira/browse/GEODE-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10114: - Labels: GeodeOperationAPI (was: needsTriage) > NullPointerException is logged if create index when

[jira] [Created] (GEODE-10114) NullPointerException is logged if create index when cache is closing.

Eric Shu created GEODE-10114: Summary: NullPointerException is logged if create index when cache is closing. Key: GEODE-10114 URL: https://issues.apache.org/jira/browse/GEODE-10114 Project: Geode

[jira] [Assigned] (GEODE-10114) NullPointerException is logged if create index when cache is closing.

[ https://issues.apache.org/jira/browse/GEODE-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10114: Assignee: Eric Shu > NullPointerException is logged if create index when cache is closing. >

[jira] [Resolved] (GEODE-10110) When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException

[ https://issues.apache.org/jira/browse/GEODE-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10110. -- Fix Version/s: 1.16.0 Resolution: Fixed > When creating index in geode,

[jira] [Assigned] (GEODE-10110) When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException

[ https://issues.apache.org/jira/browse/GEODE-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10110: Assignee: Eric Shu > When creating index in geode, InternalGemFireException should not be thrown

[jira] [Updated] (GEODE-10110) When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException

[ https://issues.apache.org/jira/browse/GEODE-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10110: - Description: Here is the exception thrown to the user: org.apache.geode.InternalGemFireException:

[jira] [Updated] (GEODE-10110) When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException

[ https://issues.apache.org/jira/browse/GEODE-10110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10110: - Labels: GeodeOperationAPI (was: needsTriage) > When creating index in geode, InternalGemFireException

[jira] [Created] (GEODE-10110) When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException

Eric Shu created GEODE-10110: Summary: When creating index in geode, InternalGemFireException should not be thrown to user if hitting CacheClosedException Key: GEODE-10110 URL:

[jira] [Resolved] (GEODE-10094) NPE could be encountered when accessing index manager if cache is closing

[ https://issues.apache.org/jira/browse/GEODE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10094. -- Fix Version/s: 1.16.0 Resolution: Fixed > NPE could be encountered when accessing index

[jira] [Updated] (GEODE-10094) NPE could be encountered when accessing index manager if cache is closing

[ https://issues.apache.org/jira/browse/GEODE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10094: - Labels: GeodeOperationAPI (was: needsTriage) > NPE could be encountered when accessing index manager

[jira] [Assigned] (GEODE-10094) NPE could be encountered when accessing index manager if cache is closing

[ https://issues.apache.org/jira/browse/GEODE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10094: Assignee: Eric Shu > NPE could be encountered when accessing index manager if cache is closing >

[jira] [Created] (GEODE-10094) NPE could be encountered when accessing index manager if cache is closing

Eric Shu created GEODE-10094: Summary: NPE could be encountered when accessing index manager if cache is closing Key: GEODE-10094 URL: https://issues.apache.org/jira/browse/GEODE-10094 Project: Geode

[jira] [Resolved] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-10063. -- Fix Version/s: 1.15.0 1.16.0 Resolution: Fixed > A closed/destroyed

[jira] [Updated] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10063: - Labels: GeodeOperationAPI blocks-1.15.0​ (was: blocks-1.15.0​) > A closed/destroyed connection can be

[jira] [Updated] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10063: - Description: In certain race cases, a destroyed connection is set to be the primary queue connection

[jira] [Updated] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10063: - Labels: blocks-1.15.0​ (was: needsTriage) > A closed/destroyed connection can be set as a primary

[jira] [Assigned] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-10063: Assignee: Eric Shu > A closed/destroyed connection can be set as a primary queueConnection in >

[jira] [Created] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

Eric Shu created GEODE-10063: Summary: A closed/destroyed connection can be set as a primary queueConnection in QueueManager Key: GEODE-10063 URL: https://issues.apache.org/jira/browse/GEODE-10063

[jira] [Updated] (GEODE-10063) A closed/destroyed connection can be set as a primary queueConnection in QueueManager

[ https://issues.apache.org/jira/browse/GEODE-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-10063: - Component/s: security > A closed/destroyed connection can be set as a primary queueConnection in >

[jira] [Updated] (GEODE-9990) Geode should handle certain DiskAccessException due to CacheClosedException when creating bucket

[ https://issues.apache.org/jira/browse/GEODE-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9990: Affects Version/s: 1.15.0 > Geode should handle certain DiskAccessException due to CacheClosedException >

[jira] [Created] (GEODE-9990) Geode should handle certain DiskAccessException due to CacheClosedException when creating bucket

Eric Shu created GEODE-9990: --- Summary: Geode should handle certain DiskAccessException due to CacheClosedException when creating bucket Key: GEODE-9990 URL: https://issues.apache.org/jira/browse/GEODE-9990

[jira] [Resolved] (GEODE-9944) NPE could occur if HARegion is being created again but not fully initialized

[ https://issues.apache.org/jira/browse/GEODE-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-9944. - Fix Version/s: 1.15.0 Resolution: Fixed > NPE could occur if HARegion is being created again but

[jira] [Updated] (GEODE-9944) NPE could occur if HARegion is being created again but not fully initialized

[ https://issues.apache.org/jira/browse/GEODE-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9944: Labels: GeodeOperationAPI needsTriage (was: needsTriage) > NPE could occur if HARegion is being created

[jira] [Assigned] (GEODE-9944) NPE could occur if HARegion is being created again but not fully initialized

[ https://issues.apache.org/jira/browse/GEODE-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-9944: --- Assignee: Eric Shu > NPE could occur if HARegion is being created again but not fully initialized

[jira] [Updated] (GEODE-9944) NPE could occur if HARegion is being created again but not fully initialized

[ https://issues.apache.org/jira/browse/GEODE-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9944: Affects Version/s: 1.15.0 > NPE could occur if HARegion is being created again but not fully initialized

[jira] [Created] (GEODE-9944) NPE could occur if HARegion is being created again but not fully initialized

Eric Shu created GEODE-9944: --- Summary: NPE could occur if HARegion is being created again but not fully initialized Key: GEODE-9944 URL: https://issues.apache.org/jira/browse/GEODE-9944 Project: Geode

[jira] [Created] (GEODE-9918) Distributed transaction is not a supported feature in geode

Eric Shu created GEODE-9918: --- Summary: Distributed transaction is not a supported feature in geode Key: GEODE-9918 URL: https://issues.apache.org/jira/browse/GEODE-9918 Project: Geode Issue Type:

[jira] [Updated] (GEODE-9918) Distributed transaction is not a supported feature in geode

[ https://issues.apache.org/jira/browse/GEODE-9918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9918: Labels: GeodeOperationAPI (was: ) > Distributed transaction is not a supported feature in geode >

[jira] [Created] (GEODE-9785) CI Failure: RedundancyLevelPart2DUnitTest.testRedundancySpecifiedEPFails FAILED

Eric Shu created GEODE-9785: --- Summary: CI Failure: RedundancyLevelPart2DUnitTest.testRedundancySpecifiedEPFails FAILED Key: GEODE-9785 URL: https://issues.apache.org/jira/browse/GEODE-9785 Project: Geode

[jira] [Created] (GEODE-9729) CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED

Eric Shu created GEODE-9729: --- Summary: CI Failure: PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs FAILED Key: GEODE-9729 URL: https://issues.apache.org/jira/browse/GEODE-9729

[jira] [Created] (GEODE-9724) CI Failure: RollingUpgradeRollServersOnReplicatedRegion_dataserializable.testRollServersOnReplicatedRegion_dataserializable[from_v1.4.0] FAILED

Eric Shu created GEODE-9724: --- Summary: CI Failure: RollingUpgradeRollServersOnReplicatedRegion_dataserializable.testRollServersOnReplicatedRegion_dataserializable[from_v1.4.0] FAILED Key: GEODE-9724 URL:

[jira] [Resolved] (GEODE-9640) When cluster shut down completely and restarted, new operations may be lost on client

[ https://issues.apache.org/jira/browse/GEODE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-9640. - Fix Version/s: 1.15.0 1.14.1 1.13.5 1.12.5

  1   2   3   4   5   6   7   8   >