[jira] [Created] (GEODE-9590) distributed test run timed out when running on 1.13 support branch.

Eric Shu created GEODE-9590: --- Summary: distributed test run timed out when running on 1.13 support branch. Key: GEODE-9590 URL: https://issues.apache.org/jira/browse/GEODE-9590 Project: Geode Issu

[jira] [Resolved] (GEODE-5103) During rebalance, a client node may miss a transactional event

[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5103. - Resolution: Fixed Fix Version/s: 1.7.0 > During rebalance, a client node may miss a transactional e

[jira] [Updated] (GEODE-5103) During rebalance, a client node may miss a transactional event

[ https://issues.apache.org/jira/browse/GEODE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5103: Affects Version/s: 1.6.0 1.1.0 1.2.0 1.3

[jira] [Created] (GEODE-5148) CI Failure: InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown

Eric Shu created GEODE-5148: --- Summary: CI Failure: InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown Key: GEODE-5148 URL: https://issues.apache.org/jira/browse/GEODE-5148

[jira] [Assigned] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException

[ https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5173: --- Assignee: Eric Shu > Transactional get from a client on a REPLICATE_HEAP_LRU region throws > NotSeri

[jira] [Created] (GEODE-5181) A get operation in a transaction on a persistent region on a restarted server could fail

Eric Shu created GEODE-5181: --- Summary: A get operation in a transaction on a persistent region on a restarted server could fail Key: GEODE-5181 URL: https://issues.apache.org/jira/browse/GEODE-5181 Project:

[jira] [Updated] (GEODE-5181) A get operation in a transaction on a persistent region on a restarted server could fail

[ https://issues.apache.org/jira/browse/GEODE-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5181: Affects Version/s: 1.1.0 1.1.1 1.2.0 1.3

[jira] [Updated] (GEODE-5181) A get operation in a transaction on a persistent region on a restarted server could fail

[ https://issues.apache.org/jira/browse/GEODE-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5181: Description: When trying to fix GEODE-5173, we find out that transaction could fail on persistent region as

[jira] [Updated] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException

[ https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5173: Affects Version/s: 1.1.0 1.1.1 1.2.0 1.3

[jira] [Assigned] (GEODE-5181) A get operation in a transaction on a persistent region on a restarted server could fail

[ https://issues.apache.org/jira/browse/GEODE-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5181: --- Assignee: Eric Shu > A get operation in a transaction on a persistent region on a restarted server >

[jira] [Created] (GEODE-5186) set operation in a client transaction could cause the transaction to hang

Eric Shu created GEODE-5186: --- Summary: set operation in a client transaction could cause the transaction to hang Key: GEODE-5186 URL: https://issues.apache.org/jira/browse/GEODE-5186 Project: Geode

[jira] [Updated] (GEODE-5186) set operation in a client transaction could cause the transaction to hang

[ https://issues.apache.org/jira/browse/GEODE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5186: Affects Version/s: 1.1.0 1.1.1 1.2.0 1.3

[jira] [Resolved] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException

[ https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5173. - Resolution: Fixed Fix Version/s: 1.7.0 > Transactional get from a client on a REPLICATE_HEAP_LRU re

[jira] [Resolved] (GEODE-5181) A get operation in a transaction on a persistent region on a restarted server could fail

[ https://issues.apache.org/jira/browse/GEODE-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5181. - Resolution: Fixed Fix Version/s: 1.7.0 Fix for GEODE-5173 fixes this one as well. > A get operatio

[jira] [Reopened] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException

[ https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-5173: - > Transactional get from a client on a REPLICATE_HEAP_LRU region throws > NotSerializableException >

[jira] [Resolved] (GEODE-5173) Transactional get from a client on a REPLICATE_HEAP_LRU region throws NotSerializableException

[ https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5173. - Resolution: Fixed > Transactional get from a client on a REPLICATE_HEAP_LRU region throws > NotSerializab

[jira] [Updated] (GEODE-5233) Eliminate the TxManagerImpl singleton

[ https://issues.apache.org/jira/browse/GEODE-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5233: Component/s: (was: regions) transactions > Eliminate the TxManagerImpl singleton >

[jira] [Updated] (GEODE-5186) set operation in a client transaction could cause the transaction to hang

[ https://issues.apache.org/jira/browse/GEODE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5186: Affects Version/s: 1.7.0 > set operation in a client transaction could cause the transaction to hang > -

[jira] [Resolved] (GEODE-5186) set operation in a client transaction could cause the transaction to hang

[ https://issues.apache.org/jira/browse/GEODE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5186. - Resolution: Fixed Fix Version/s: 1.8.0 > set operation in a client transaction could cause the tran

[jira] [Created] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

Eric Shu created GEODE-5255: --- Summary: In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted Key: GEODE-5255 URL: https://issues.apache.org/jira/browse/GEODE-5255

[jira] [Updated] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

[ https://issues.apache.org/jira/browse/GEODE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5255: Fix Version/s: 1.8.0 > In a race condition, a colocated bucket may not be created during rebalance > when m

[jira] [Assigned] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

[ https://issues.apache.org/jira/browse/GEODE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5255: --- Assignee: Eric Shu > In a race condition, a colocated bucket may not be created during rebalance > w

[jira] [Updated] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

[ https://issues.apache.org/jira/browse/GEODE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5255: Affects Version/s: 1.1.0 1.2.0 1.3.0 1.4

[jira] [Updated] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

[ https://issues.apache.org/jira/browse/GEODE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5255: Affects Version/s: 1.7.0 > In a race condition, a colocated bucket may not be created during rebalance > wh

[jira] [Resolved] (GEODE-5255) In a race condition, a colocated bucket may not be created during rebalance when member nodes are restarted

[ https://issues.apache.org/jira/browse/GEODE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5255. - Resolution: Fixed > In a race condition, a colocated bucket may not be created during rebalance > when m

[jira] [Created] (GEODE-5271) Transaction should throw TransactionDataRebalancedException if primary bucket is moved to another node during commit

Eric Shu created GEODE-5271: --- Summary: Transaction should throw TransactionDataRebalancedException if primary bucket is moved to another node during commit Key: GEODE-5271 URL: https://issues.apache.org/jira/browse/GEO

[jira] [Updated] (GEODE-5271) Transaction should throw TransactionDataRebalancedException if primary bucket is moved to another node during commit

[ https://issues.apache.org/jira/browse/GEODE-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5271: Affects Version/s: 1.6.0 > Transaction should throw TransactionDataRebalancedException if primary bucket >

[jira] [Assigned] (GEODE-5271) Transaction should throw TransactionDataRebalancedException if primary bucket is moved to another node during commit

[ https://issues.apache.org/jira/browse/GEODE-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5271: --- Assignee: Eric Shu > Transaction should throw TransactionDataRebalancedException if primary bucket

[jira] [Commented] (GEODE-5271) Transaction should throw TransactionDataRebalancedException if primary bucket is moved to another node during commit

[ https://issues.apache.org/jira/browse/GEODE-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497142#comment-16497142 ] Eric Shu commented on GEODE-5271: - This should be prevented by lockBucketRegions call in

[jira] [Created] (GEODE-5286) ClientServerTransactionDUnitTest.testBug42942 failed due to StackOverflowError

Eric Shu created GEODE-5286: --- Summary: ClientServerTransactionDUnitTest.testBug42942 failed due to StackOverflowError Key: GEODE-5286 URL: https://issues.apache.org/jira/browse/GEODE-5286 Project: Geode

[jira] [Commented] (GEODE-5286) ClientServerTransactionDUnitTest.testBug42942 failed due to StackOverflowError

[ https://issues.apache.org/jira/browse/GEODE-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500850#comment-16500850 ] Eric Shu commented on GEODE-5286: - The stack dump {noformat} org.apache.geode.test.dunit

[jira] [Created] (GEODE-5302) the totalLiveCount should be set to 0 after oplog is compacted (all live data has been copied forward to new oplog)

Eric Shu created GEODE-5302: --- Summary: the totalLiveCount should be set to 0 after oplog is compacted (all live data has been copied forward to new oplog) Key: GEODE-5302 URL: https://issues.apache.org/jira/browse/GEOD

[jira] [Assigned] (GEODE-5302) the totalLiveCount should be set to 0 after oplog is compacted (all live data has been copied forward to new oplog)

[ https://issues.apache.org/jira/browse/GEODE-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5302: --- Assignee: Eric Shu > the totalLiveCount should be set to 0 after oplog is compacted (all live data

[jira] [Updated] (GEODE-5302) the totalLiveCount should be set to 0 after oplog is compacted (all live data has been copied forward to new oplog)

[ https://issues.apache.org/jira/browse/GEODE-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5302: Affects Version/s: 1.7.0 1.1.0 1.2.0 1.

[jira] [Created] (GEODE-5303) CI Failure: ConcurrentRegionOperationIntegrationTest.replaceWithClearAndDestroy FAILED

Eric Shu created GEODE-5303: --- Summary: CI Failure: ConcurrentRegionOperationIntegrationTest.replaceWithClearAndDestroy FAILED Key: GEODE-5303 URL: https://issues.apache.org/jira/browse/GEODE-5303 Project: G

[jira] [Updated] (GEODE-5303) CI Failure: ConcurrentRegionOperationIntegrationTest.replaceWithClearAndDestroy FAILED

[ https://issues.apache.org/jira/browse/GEODE-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5303: Affects Version/s: 1.8.0 > CI Failure: > ConcurrentRegionOperationIntegrationTest.replaceWithClearAndDestr

[jira] [Created] (GEODE-5304) RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED

Eric Shu created GEODE-5304: --- Summary: RemoteTransactionCCEDUnitTest.testValuesIteratorOnDestroy FAILED Key: GEODE-5304 URL: https://issues.apache.org/jira/browse/GEODE-5304 Project: Geode Issue T

[jira] [Resolved] (GEODE-5302) the totalLiveCount should be set to 0 after oplog is compacted (all live data has been copied forward to new oplog)

[ https://issues.apache.org/jira/browse/GEODE-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5302. - Resolution: Fixed Fix Version/s: 1.8.0 > the totalLiveCount should be set to 0 after oplog is comp

[jira] [Created] (GEODE-5312) A client transaction may be removed by FindRemoteTXMessage during transaction failover

Eric Shu created GEODE-5312: --- Summary: A client transaction may be removed by FindRemoteTXMessage during transaction failover Key: GEODE-5312 URL: https://issues.apache.org/jira/browse/GEODE-5312 Project: G

[jira] [Assigned] (GEODE-5312) A client transaction may be removed by FindRemoteTXMessage during transaction failover

[ https://issues.apache.org/jira/browse/GEODE-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5312: --- Assignee: Eric Shu > A client transaction may be removed by FindRemoteTXMessage during transaction

[jira] [Resolved] (GEODE-5312) A client transaction may be removed by FindRemoteTXMessage during transaction failover

[ https://issues.apache.org/jira/browse/GEODE-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5312. - Resolution: Fixed Fix Version/s: 1.8.0 > A client transaction may be removed by FindRemoteTXMessag

[jira] [Created] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

Eric Shu created GEODE-5376: --- Summary: In JTA, Geode afterCompletion may fail even though the JTA host still available Key: GEODE-5376 URL: https://issues.apache.org/jira/browse/GEODE-5376 Project: Geode

[jira] [Assigned] (GEODE-5379) affinityRetryCount should not be reseted after executeOnServer successfully

[ https://issues.apache.org/jira/browse/GEODE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5379: --- Assignee: Eric Shu > affinityRetryCount should not be reseted after executeOnServer successfully >

[jira] [Created] (GEODE-5379) affinityRetryCount should not be reseted after executeOnServer successfully

Eric Shu created GEODE-5379: --- Summary: affinityRetryCount should not be reseted after executeOnServer successfully Key: GEODE-5379 URL: https://issues.apache.org/jira/browse/GEODE-5379 Project: Geode

[jira] [Created] (GEODE-5382) Geode TransactionManagerImpl.commit() does not throw Exception when notifyAfterCompletion failed

Eric Shu created GEODE-5382: --- Summary: Geode TransactionManagerImpl.commit() does not throw Exception when notifyAfterCompletion failed Key: GEODE-5382 URL: https://issues.apache.org/jira/browse/GEODE-5382

[jira] [Commented] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531928#comment-16531928 ] Eric Shu commented on GEODE-5376: - Currently the client could not failover. The JTA would

[jira] [Created] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed

Eric Shu created GEODE-5400: --- Summary: JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed Key: GEODE-5400 URL: https://issues.apache.org/jira/browse/GEODE-5400

[jira] [Updated] (GEODE-5401) Client transaction should not be expired once it is failed over

[ https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5401: Affects Version/s: 1.7.0 1.1.0 1.2.0 1.

[jira] [Created] (GEODE-5401) Client transaction should not be expired once it is failed over

Eric Shu created GEODE-5401: --- Summary: Client transaction should not be expired once it is failed over Key: GEODE-5401 URL: https://issues.apache.org/jira/browse/GEODE-5401 Project: Geode Issue Ty

[jira] [Assigned] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5376: --- Assignee: Eric Shu > In JTA, Geode afterCompletion may fail even though the JTA host still > availa

[jira] [Assigned] (GEODE-5382) Geode TransactionManagerImpl.commit() does not throw Exception when notifyAfterCompletion failed

[ https://issues.apache.org/jira/browse/GEODE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5382: --- Assignee: Eric Shu > Geode TransactionManagerImpl.commit() does not throw Exception when > notifyAf

[jira] [Commented] (GEODE-5382) Geode TransactionManagerImpl.commit() does not throw Exception when notifyAfterCompletion failed

[ https://issues.apache.org/jira/browse/GEODE-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539347#comment-16539347 ] Eric Shu commented on GEODE-5382: - The Geode TransactionManagerImpl was deprecated and wi

[jira] [Assigned] (GEODE-5401) Client transaction should not be expired once it is failed over

[ https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5401: --- Assignee: Eric Shu > Client transaction should not be expired once it is failed over > -

[jira] [Updated] (GEODE-5401) Client transaction should not be expired once it is failed over

[ https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5401: Labels: swat (was: ) > Client transaction should not be expired once it is failed over > -

[jira] [Updated] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5376: Fix Version/s: 1.8.0 > In JTA, Geode afterCompletion may fail even though the JTA host still > available >

[jira] [Resolved] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5376. - Resolution: Fixed > In JTA, Geode afterCompletion may fail even though the JTA host still > available >

[jira] [Updated] (GEODE-5376) In JTA, Geode afterCompletion may fail even though the JTA host still available

[ https://issues.apache.org/jira/browse/GEODE-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5376: Affects Version/s: 1.7.0 1.1.0 1.2.0 1.

[jira] [Assigned] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed

[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5400: --- Assignee: Eric Shu > JTA transaction locks are not released if the jta originator is crashed after

[jira] [Updated] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed

[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5400: Affects Version/s: 1.6.0 > JTA transaction locks are not released if the jta originator is crashed after >

[jira] [Resolved] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed

[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5400. - Resolution: Fixed Fix Version/s: 1.7.0 > JTA transaction locks are not released if the jta origina

[jira] [Updated] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed

[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5400: Affects Version/s: 1.1.0 1.2.0 1.3.0 1.

[jira] [Created] (GEODE-5515) Transaction originated from peer sets the onBehalfOfClientMember on remote transaction host

Eric Shu created GEODE-5515: --- Summary: Transaction originated from peer sets the onBehalfOfClientMember on remote transaction host Key: GEODE-5515 URL: https://issues.apache.org/jira/browse/GEODE-5515 Proje

[jira] [Updated] (GEODE-5515) Transaction originated from peer sets the onBehalfOfClientMember on remote transaction host

[ https://issues.apache.org/jira/browse/GEODE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5515: Affects Version/s: 1.4.0 1.5.0 1.6.0 > Transaction originated

[jira] [Assigned] (GEODE-5515) Transaction originated from peer sets the onBehalfOfClientMember on remote transaction host

[ https://issues.apache.org/jira/browse/GEODE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5515: --- Assignee: Eric Shu > Transaction originated from peer sets the onBehalfOfClientMember on remote > t

[jira] [Resolved] (GEODE-5515) Transaction originated from peer sets the onBehalfOfClientMember on remote transaction host

[ https://issues.apache.org/jira/browse/GEODE-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5515. - Resolution: Fixed Fix Version/s: 1.7.0 > Transaction originated from peer sets the onBehalfOfClien

[jira] [Assigned] (GEODE-5524) Verify transaction results can fail in clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer DUnit test

[ https://issues.apache.org/jira/browse/GEODE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5524: --- Assignee: Eric Shu > Verify transaction results can fail in > clientTransactionOperationsAreNotLost

[jira] [Updated] (GEODE-5524) Verify transaction results can fail in clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer DUnit test

[ https://issues.apache.org/jira/browse/GEODE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5524: Labels: swat (was: ) > Verify transaction results can fail in > clientTransactionOperationsAreNotLostIfTr

[jira] [Resolved] (GEODE-5524) Verify transaction results can fail in clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer DUnit test

[ https://issues.apache.org/jira/browse/GEODE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5524. - Resolution: Fixed Fix Version/s: 1.7.0 > Verify transaction results can fail in > clientTransacti

[jira] [Updated] (GEODE-5524) Verify transaction results can fail in clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer DUnit test

[ https://issues.apache.org/jira/browse/GEODE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5524: Affects Version/s: 1.7.0 > Verify transaction results can fail in > clientTransactionOperationsAreNotLostI

[jira] [Assigned] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node

[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5541: --- Assignee: Eric Shu > A create followed by a destroy of the same key in a transaction invokes cache

[jira] [Created] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node

Eric Shu created GEODE-5541: --- Summary: A create followed by a destroy of the same key in a transaction invokes cache listener on remote node Key: GEODE-5541 URL: https://issues.apache.org/jira/browse/GEODE-5541

[jira] [Created] (GEODE-5542) Transaction should not distribute a no op destroy to remote nodes

Eric Shu created GEODE-5542: --- Summary: Transaction should not distribute a no op destroy to remote nodes Key: GEODE-5542 URL: https://issues.apache.org/jira/browse/GEODE-5542 Project: Geode Issue

[jira] [Updated] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node

[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5541: Affects Version/s: 1.1.0 1.2.0 1.3.0 1.

[jira] [Resolved] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node

[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5541. - Resolution: Fixed Fix Version/s: 1.7.0 > A create followed by a destroy of the same key in a trans

[jira] [Reopened] (GEODE-5541) A create followed by a destroy of the same key in a transaction invokes cache listener on remote node

[ https://issues.apache.org/jira/browse/GEODE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-5541: - revert this checkin as it does not handle rebalance case. > A create followed by a destroy of the same key i

[jira] [Created] (GEODE-5592) During commit, cleanupTransactionIfNoLongerHost could fail with DistributedSystemDisconnectedException

Eric Shu created GEODE-5592: --- Summary: During commit, cleanupTransactionIfNoLongerHost could fail with DistributedSystemDisconnectedException Key: GEODE-5592 URL: https://issues.apache.org/jira/browse/GEODE-5592

[jira] [Assigned] (GEODE-5592) During commit, cleanupTransactionIfNoLongerHost could fail with DistributedSystemDisconnectedException

[ https://issues.apache.org/jira/browse/GEODE-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5592: --- Assignee: Eric Shu > During commit, cleanupTransactionIfNoLongerHost could fail with > DistributedS

[jira] [Resolved] (GEODE-5592) During commit, cleanupTransactionIfNoLongerHost could fail with DistributedSystemDisconnectedException

[ https://issues.apache.org/jira/browse/GEODE-5592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5592. - Resolution: Fixed Fix Version/s: 1.7.0 > During commit, cleanupTransactionIfNoLongerHost could fai

[jira] [Created] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException

Eric Shu created GEODE-5624: --- Summary: JTA transaction does not clean up TXState due to IllegalMonitorStateException Key: GEODE-5624 URL: https://issues.apache.org/jira/browse/GEODE-5624 Project: Geode

[jira] [Assigned] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException

[ https://issues.apache.org/jira/browse/GEODE-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5624: --- Assignee: Eric Shu > JTA transaction does not clean up TXState due to IllegalMonitorStateException >

[jira] [Updated] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException

[ https://issues.apache.org/jira/browse/GEODE-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5624: Affects Version/s: 1.7.0 > JTA transaction does not clean up TXState due to IllegalMonitorStateException >

[jira] [Resolved] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException

[ https://issues.apache.org/jira/browse/GEODE-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5624. - Resolution: Fixed Fix Version/s: 1.7.0 > JTA transaction does not clean up TXState due to IllegalM

[jira] [Created] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close

Eric Shu created GEODE-5697: --- Summary: SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close Key: GEODE-5697 URL: https://issues.apache.org/jira/browse/GEODE-5697 Project:

[jira] [Assigned] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close

[ https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5697: --- Assignee: Eric Shu > SingleThreadJTAExecutor.cleanup method should ignore exception thrown during >

[jira] [Created] (GEODE-5702) AbstractPeerTXRegionStub does not need to wrap a specific TransactionException

Eric Shu created GEODE-5702: --- Summary: AbstractPeerTXRegionStub does not need to wrap a specific TransactionException Key: GEODE-5702 URL: https://issues.apache.org/jira/browse/GEODE-5702 Project: Geode

[jira] [Assigned] (GEODE-5702) AbstractPeerTXRegionStub does not need to wrap a specific TransactionException

[ https://issues.apache.org/jira/browse/GEODE-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5702: --- Assignee: Eric Shu > AbstractPeerTXRegionStub does not need to wrap a specific TransactionException

[jira] [Updated] (GEODE-5702) AbstractPeerTXRegionStub does not need to wrap a specific TransactionException

[ https://issues.apache.org/jira/browse/GEODE-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5702: Affects Version/s: 1.7.0 > AbstractPeerTXRegionStub does not need to wrap a specific TransactionException >

[jira] [Resolved] (GEODE-5702) AbstractPeerTXRegionStub does not need to wrap a specific TransactionException

[ https://issues.apache.org/jira/browse/GEODE-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5702. - Resolution: Fixed Fix Version/s: 1.8.0 > AbstractPeerTXRegionStub does not need to wrap a specific

[jira] [Commented] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close

[ https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607700#comment-16607700 ] Eric Shu commented on GEODE-5697: - See another issue that BeforeCompletion.doOp could fai

[jira] [Updated] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close

[ https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5697: Affects Version/s: 1.7.0 > SingleThreadJTAExecutor.cleanup method should ignore exception thrown during >

[jira] [Resolved] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close

[ https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5697. - Resolution: Fixed Fix Version/s: 1.8.0 > SingleThreadJTAExecutor.cleanup method should ignore exce

[jira] [Assigned] (GEODE-5748) When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation

[ https://issues.apache.org/jira/browse/GEODE-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5748: --- Assignee: Eric Shu > When gii failed and needs to cleanup it should clearRegion write lock to > avo

[jira] [Created] (GEODE-5748) When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation

Eric Shu created GEODE-5748: --- Summary: When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation Key: GEODE-5748 URL: https://issues.apache.org/jira/br

[jira] [Commented] (GEODE-5748) When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation

[ https://issues.apache.org/jira/browse/GEODE-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622272#comment-16622272 ] Eric Shu commented on GEODE-5748: - Apparently that cache operation on secondary buckets o

[jira] [Resolved] (GEODE-5748) When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation

[ https://issues.apache.org/jira/browse/GEODE-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5748. - Resolution: Fixed Fix Version/s: 1.8.0 > When gii failed and needs to cleanup it should clearRegio

[jira] [Updated] (GEODE-5748) When gii failed and needs to cleanup it should clearRegion write lock to avoid race condition with concurrent cache operation

[ https://issues.apache.org/jira/browse/GEODE-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5748: Affects Version/s: 1.7.0 1.1.0 1.2.0 1.

[jira] [Assigned] (GEODE-5828) A replicate does not apply transaction commit even if another replicate applied commit after tx host departed

[ https://issues.apache.org/jira/browse/GEODE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5828: --- Assignee: Eric Shu > A replicate does not apply transaction commit even if another replicate > appl

[jira] [Updated] (GEODE-5828) A replicate does not apply transaction commit even if another replicate applied commit after tx host departed

[ https://issues.apache.org/jira/browse/GEODE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5828: Affects Version/s: 1.1.0 > A replicate does not apply transaction commit even if another replicate > appli

[jira] [Created] (GEODE-5828) A replicate does not apply transaction commit even if another replicate applied commit after tx host departed

Eric Shu created GEODE-5828: --- Summary: A replicate does not apply transaction commit even if another replicate applied commit after tx host departed Key: GEODE-5828 URL: https://issues.apache.org/jira/browse/GEODE-5828

[jira] [Resolved] (GEODE-5828) A replicate does not apply transaction commit even if another replicate applied commit after tx host departed

[ https://issues.apache.org/jira/browse/GEODE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5828. - Resolution: Fixed Fix Version/s: 1.8.0 > A replicate does not apply transaction commit even if ano

<    1   2   3   4   5   6   7   8   9   >