[jira] [Resolved] (GEODE-4573) Query execution within a transaction (JTA) produces a ClassCastException in version 1.4.0
[
https://issues.apache.org/jira/browse/GEODE-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-4573.
-
Resolution: Fixed
Fix Version/s: 1.5.0
> Query execution within a transaction (JTA) produces a ClassCastException in
> version 1.4.0
> -
>
> Key: GEODE-4573
> URL: https://issues.apache.org/jira/browse/GEODE-4573
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.4.0
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The stack trace is like that:
> {code:java}
> Caused by: java.lang.ClassCastException:
> org.apache.geode.internal.cache.TXEntry cannot be cast to
> org.apache.geode.internal.cache.LocalRegion$NonTXEntry
> at
> org.apache.geode.internal.cache.EntriesSet$EntriesIterator.moveNext(EntriesSet.java:179)
> at
> org.apache.geode.internal.cache.EntriesSet$EntriesIterator.(EntriesSet.java:118)
> at org.apache.geode.internal.cache.EntriesSet.iterator(EntriesSet.java:83)
> at
> org.apache.geode.cache.query.internal.ResultsCollectionWrapper.iterator(ResultsCollectionWrapper.java:184)
> at org.apache.geode.cache.query.internal.QRegion.iterator(QRegion.java:244)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.doNestedIterations(CompiledSelect.java:834)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.doIterationEvaluate(CompiledSelect.java:701)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:545)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:55)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:557)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:384)
> {code}
> When property {{-Dgemfire.restoreSetOperationTransactionBehavior=true}} is
> set than everything works without errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4641) CI Failure: PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild
Eric Shu created GEODE-4641:
---
Summary: CI Failure:
PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild
Key: GEODE-4641
URL: https://issues.apache.org/jira/browse/GEODE-4641
Project: Geode
Issue Type: Bug
Reporter: Eric Shu
{noformat}
org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> testHierarchyOfColocatedChildPRsMissingGrandchild FAILED
java.lang.AssertionError: An exception occurred during asynchronous
invocation.
at
org.apache.geode.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:150)
at
org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:424)
at
org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild(PersistentColocatedPartitionedRegionDUnitTest.java:1143)
Caused by:
org.mockito.exceptions.verification.NoInteractionsWanted:
No interactions wanted here:
-> at
org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest$10.call(PersistentColocatedPartitionedRegionDUnitTest.java:521)
But found this interaction on mock 'appender':
-> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
***
For your reference, here is the list of all invocations ([?] - means
unverified).
1. -> at
org.apache.logging.log4j.core.config.AbstractConfiguration.addLoggerAppender(AbstractConfiguration.java:704)
2. -> at
org.apache.logging.log4j.core.config.AppenderControl.(AppenderControl.java:51)
3. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
4. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
5. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
6. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
7. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
8. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
9. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
10. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
11. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
12. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
13. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
14. -> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
15. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
16. [?]-> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
17. -> at
org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
18. [?]-> at
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4641) CI Failure: PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild
[
https://issues.apache.org/jira/browse/GEODE-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4641:
Component/s: regions
> CI Failure:
> PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild
> ---
>
> Key: GEODE-4641
> URL: https://issues.apache.org/jira/browse/GEODE-4641
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Eric Shu
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest
> > testHierarchyOfColocatedChildPRsMissingGrandchild FAILED
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at
> org.apache.geode.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:150)
> at
> org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:424)
> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testHierarchyOfColocatedChildPRsMissingGrandchild(PersistentColocatedPartitionedRegionDUnitTest.java:1143)
> Caused by:
> org.mockito.exceptions.verification.NoInteractionsWanted:
> No interactions wanted here:
> -> at
> org.apache.geode.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest$10.call(PersistentColocatedPartitionedRegionDUnitTest.java:521)
> But found this interaction on mock 'appender':
> -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> ***
> For your reference, here is the list of all invocations ([?] - means
> unverified).
> 1. -> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.addLoggerAppender(AbstractConfiguration.java:704)
> 2. -> at
> org.apache.logging.log4j.core.config.AppenderControl.(AppenderControl.java:51)
> 3. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 4. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 5. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 6. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 7. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 8. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 9. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 10. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 11. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 12. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 13. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 14. -> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 15. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 16. [?]-> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> 17. -> at
> org.apache.logging.log4j.core.config.AppenderControl.ensureAppenderStarted(AppenderControl.java:134)
> 18. [?]-> at
> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4634) CI Failure: OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
[
https://issues.apache.org/jira/browse/GEODE-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-4634.
-
Resolution: Duplicate
Fix Version/s: 1.5.0
duplicate of GEODE-4621
> CI Failure: OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
> --
>
> Key: GEODE-4634
> URL: https://issues.apache.org/jira/browse/GEODE-4634
> Project: Geode
> Issue Type: Bug
> Components: eviction
>Reporter: Eric Shu
>Priority: Major
> Fix For: 1.5.0
>
>
> {noformat}
> org.apache.geode.internal.cache.OplogJUnitTest >
> testHelperAPIsForOverflowOnlyRegion FAILED
> java.lang.AssertionError: expected null, but was: Oplog = 0; Value Length = 1000; UserBits is = 0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotNull(Assert.java:755)
> at org.junit.Assert.assertNull(Assert.java:737)
> at org.junit.Assert.assertNull(Assert.java:747)
> at
> org.apache.geode.internal.cache.OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion(OplogJUnitTest.java:1240)
> {noformat}
> Possibly this has the same cause as GEODE-4621
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4634) CI Failure: OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
[
https://issues.apache.org/jira/browse/GEODE-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4634:
Affects Version/s: 1.5.0
> CI Failure: OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion
> --
>
> Key: GEODE-4634
> URL: https://issues.apache.org/jira/browse/GEODE-4634
> Project: Geode
> Issue Type: Bug
> Components: eviction
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Priority: Major
> Fix For: 1.5.0
>
>
> {noformat}
> org.apache.geode.internal.cache.OplogJUnitTest >
> testHelperAPIsForOverflowOnlyRegion FAILED
> java.lang.AssertionError: expected null, but was: Oplog = 0; Value Length = 1000; UserBits is = 0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotNull(Assert.java:755)
> at org.junit.Assert.assertNull(Assert.java:737)
> at org.junit.Assert.assertNull(Assert.java:747)
> at
> org.apache.geode.internal.cache.OplogJUnitTest.testHelperAPIsForOverflowOnlyRegion(OplogJUnitTest.java:1240)
> {noformat}
> Possibly this has the same cause as GEODE-4621
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4655) CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow
Eric Shu created GEODE-4655: --- Summary: CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow Key: GEODE-4655 URL: https://issues.apache.org/jira/browse/GEODE-4655 Project: Geode Issue Type: Bug Components: eviction Reporter: Eric Shu org.apache.geode.internal.cache.DiskRegionJUnitTest > testDiskRegionOverflow FAILED java.lang.AssertionError: expected:<2> but was:<1> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.internal.cache.DiskRegionJUnitTest.testDiskRegionOverflow(DiskRegionJUnitTest.java:219) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4655) CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow
[ https://issues.apache.org/jira/browse/GEODE-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-4655: --- Assignee: Eric Shu > CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow > -- > > Key: GEODE-4655 > URL: https://issues.apache.org/jira/browse/GEODE-4655 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > org.apache.geode.internal.cache.DiskRegionJUnitTest > testDiskRegionOverflow > FAILED > java.lang.AssertionError: expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.internal.cache.DiskRegionJUnitTest.testDiskRegionOverflow(DiskRegionJUnitTest.java:219) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4655) CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow
[ https://issues.apache.org/jira/browse/GEODE-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-4655. - Resolution: Fixed Fix Version/s: 1.5.0 > CI Failure: DiskRegionJUnitTest.testDiskRegionOverflow > -- > > Key: GEODE-4655 > URL: https://issues.apache.org/jira/browse/GEODE-4655 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.internal.cache.DiskRegionJUnitTest > testDiskRegionOverflow > FAILED > java.lang.AssertionError: expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.internal.cache.DiskRegionJUnitTest.testDiskRegionOverflow(DiskRegionJUnitTest.java:219) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4712) CI Failure: EvictionDUnitTest.testDummyInlineNCentralizedEviction
Eric Shu created GEODE-4712: --- Summary: CI Failure: EvictionDUnitTest.testDummyInlineNCentralizedEviction Key: GEODE-4712 URL: https://issues.apache.org/jira/browse/GEODE-4712 Project: Geode Issue Type: Bug Components: eviction Reporter: Eric Shu org.apache.geode.internal.cache.eviction.EvictionDUnitTest > testDummyInlineNCentralizedEviction FAILED java.lang.AssertionError: expected:<4> but was:<3> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.apache.geode.internal.cache.eviction.EvictionTestBase.validateNoOfEvictions(EvictionTestBase.java:403) at org.apache.geode.internal.cache.eviction.EvictionDUnitTest.testDummyInlineNCentralizedEviction(EvictionDUnitTest.java:49) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4712) CI Failure: EvictionDUnitTest.testDummyInlineNCentralizedEviction
[ https://issues.apache.org/jira/browse/GEODE-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371743#comment-16371743 ] Eric Shu commented on GEODE-4712: - Similar to offheap version of the test failure which was marked as flaky. (https://issues.apache.org/jira/browse/GEODE-1770) > CI Failure: EvictionDUnitTest.testDummyInlineNCentralizedEviction > - > > Key: GEODE-4712 > URL: https://issues.apache.org/jira/browse/GEODE-4712 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Eric Shu >Priority: Major > > org.apache.geode.internal.cache.eviction.EvictionDUnitTest > > testDummyInlineNCentralizedEviction FAILED > java.lang.AssertionError: expected:<4> but was:<3> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.internal.cache.eviction.EvictionTestBase.validateNoOfEvictions(EvictionTestBase.java:403) > at > org.apache.geode.internal.cache.eviction.EvictionDUnitTest.testDummyInlineNCentralizedEviction(EvictionDUnitTest.java:49) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
Eric Shu created GEODE-4738:
---
Summary: EventSeqNum and versionVector in a region are accessed
when they are not yet initialized
Key: GEODE-4738
URL: https://issues.apache.org/jira/browse/GEODE-4738
Project: Geode
Issue Type: Bug
Components: regions
Reporter: Eric Shu
It is possible that eventSeqNum and versionVector are accessed when they are
not initialized yet. This could cause transaction to fail on the node just
start up.
{noformat}
Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
Incomplete commit of transaction TXId:
rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
Caused by the following exceptions: From member:
rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
java.lang.NullPointerException
at
org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
at
org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
at
org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
at
org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
at
org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
at
org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
at
org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
at
org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
at
org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
at
org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
at
org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
at
org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
at java.lang.Thread.run(Thread.java:748).
at
org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
at
org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
at
org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
at
org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
at
org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
at
org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
at
org.apache.geode.distributed.internal.ClusterDistributionManager$6$1.run(ClusterDistributionManager.java:862)
at java.lang.Thread.run(Thread.java:748)
{noformat}
And
{noformat}
Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
Incomplete commit of transaction TXId:
r02-s02(edgegemfire2_r02-s02_10305:10305:loner):36970:e226a1a8:edgegemfire2_r02-s02_10305:11669.
Caused by the following exceptions: From member:
r02-s02(bridgegem
[jira] [Updated] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
[
https://issues.apache.org/jira/browse/GEODE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4738:
Affects Version/s: 1.4.0
> EventSeqNum and versionVector in a region are accessed when they are not yet
> initialized
>
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Priority: Major
>
> It is possible that eventSeqNum and versionVector are accessed when they are
> not initialized yet. This could cause transaction to fail on the node just
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
> Incomplete commit of transaction TXId:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
> Caused by the following exceptions: From member:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
> java.lang.NullPointerException
> at
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
> at
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
> at
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
> at java.lang.Thread.run(Thread.java:748).
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
> at
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
> at
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
> at
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
> at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$6$1.run(ClusterDistributionMana
[jira] [Assigned] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
[
https://issues.apache.org/jira/browse/GEODE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reassigned GEODE-4738:
---
Assignee: Eric Shu
> EventSeqNum and versionVector in a region are accessed when they are not yet
> initialized
>
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> It is possible that eventSeqNum and versionVector are accessed when they are
> not initialized yet. This could cause transaction to fail on the node just
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
> Incomplete commit of transaction TXId:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
> Caused by the following exceptions: From member:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
> java.lang.NullPointerException
> at
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
> at
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
> at
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
> at java.lang.Thread.run(Thread.java:748).
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
> at
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
> at
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
> at
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
> at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManage
[jira] [Resolved] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
[
https://issues.apache.org/jira/browse/GEODE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-4738.
-
Resolution: Fixed
Fix Version/s: 1.5.0
> EventSeqNum and versionVector in a region are accessed when they are not yet
> initialized
>
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is possible that eventSeqNum and versionVector are accessed when they are
> not initialized yet. This could cause transaction to fail on the node just
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
> Incomplete commit of transaction TXId:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
> Caused by the following exceptions: From member:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
> java.lang.NullPointerException
> at
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
> at
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
> at
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
> at java.lang.Thread.run(Thread.java:748).
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
> at
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
> at
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
> at
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
> at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal
[jira] [Assigned] (GEODE-4721) Being invoked within JTA Region.values() does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reassigned GEODE-4721:
---
Assignee: Eric Shu
> Being invoked within JTA Region.values() does return empty collection
> -
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Major
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379082#comment-16379082
]
Eric Shu commented on GEODE-4721:
-
Does your failed case use client proxy region to perform JTA? If so, there is a
workaround by performing a region.get() on a existing/non existing key before
accessing the values.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381171#comment-16381171
]
Eric Shu commented on GEODE-4721:
-
So far I could not reproduce the issue mentioned unless JTA and set operation
is on a client proxy region.
Can you share your function body, and how it was invoked -- using onMember or
onRegion?
Please note, if you set gemfire.restoreSetOperationTransactionBehavior=true,
and then in the function you perform some entry operations. If you then access
the set (values, entrySet), JTA/transaction will fail with
IllegalStateException of "The Region collection is not transactional but is
being used in a transaction".
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382828#comment-16382828
]
Eric Shu commented on GEODE-4721:
-
[~vlotarev] I will look into getEntry() call. Seems you are correct.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
[
https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4887:
Affects Version/s: 1.5.0
> ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
> ---
>
> Key: GEODE-4887
> URL: https://issues.apache.org/jira/browse/GEODE-4887
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Priority: Major
>
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
> testDistributedUpdate FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
> running on Host 34d5b30e2f93 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
> at
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
> Caused by:
> java.lang.AssertionError:
> Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
> State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
> isSerialized=true, isCompressed=false, DataType=java.lang.String,
> DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
[
https://issues.apache.org/jira/browse/GEODE-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-4887:
Component/s: offheap
> ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
> ---
>
> Key: GEODE-4887
> URL: https://issues.apache.org/jira/browse/GEODE-4887
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Priority: Major
>
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
> testDistributedUpdate FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
> running on Host 34d5b30e2f93 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
> at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
> at
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
> Caused by:
> java.lang.AssertionError:
> Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
> State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
> isSerialized=true, isCompressed=false, DataType=java.lang.String,
> DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4887) ci Failure: PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
Eric Shu created GEODE-4887:
---
Summary: ci Failure:
PartitionedRegionOffHeapDUnitTest.testDistributedUpdate
Key: GEODE-4887
URL: https://issues.apache.org/jira/browse/GEODE-4887
Project: Geode
Issue Type: Bug
Reporter: Eric Shu
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest >
testDistributedUpdate FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest$1.run in VM 1
running on Host 34d5b30e2f93 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
at
org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.preTearDownAssertions(PartitionedRegionOffHeapDUnitTest.java:49)
Caused by:
java.lang.AssertionError:
Expecting empty but was:<[MemoryBlock{MemoryAddress=139834149486752,
State=ALLOCATED, BlockSize=24, SlabId=0, FreeListId=NONE, RefCount=1,
isSerialized=true, isCompressed=false, DataType=java.lang.String,
DataValue=NEW_VALUE}]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (GEODE-3205) CI failure: org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles
[
https://issues.apache.org/jira/browse/GEODE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reopened GEODE-3205:
-
Reproduced with different stack.
org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest >
aboveZeroDeletesPreviousFiles FAILED
java.lang.AssertionError:
Expecting file:
to exist.
at
org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:205)
> CI failure:
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles
>
>
> Key: GEODE-3205
> URL: https://issues.apache.org/jira/browse/GEODE-3205
> Project: Geode
> Issue Type: Bug
> Components: statistics, tests
>Reporter: Lynn Gallinat
>Assignee: Kirk Lund
>Priority: Major
> Labels: Flaky, pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest >
> aboveZeroDeletesPreviousFiles FAILED
> org.junit.ComparisonFailure: [Unexpected files:
> [/tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-01.gfs,
> /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles-02-02.gfs,
> /tmp/junit7694480016466771827/aboveZeroDeletesPreviousFiles.gfs]]
> expected:<[2]> but was:<[3]>
> 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.statistics.DiskSpaceLimitIntegrationTest.validateNumberFiles(DiskSpaceLimitIntegrationTest.java:263)
> at
> org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:202)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (GEODE-2275) CI Failure: ClearTXLockingDUnitTest.testPutWithClearDifferentVM
[ https://issues.apache.org/jira/browse/GEODE-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reopened GEODE-2275: - This reproduced in geode-1.5 release branch. https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/8 org.apache.geode.internal.cache.ClearTXLockingDUnitTest > testPutWithClearDifferentVM FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.ClearTXLockingDUnitTest$$Lambda$31/1790143529.run in VM 0 running on Host 09baa480fa1f with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:401) at org.apache.geode.test.dunit.VM.invoke(VM.java:370) at org.apache.geode.test.dunit.VM.invoke(VM.java:313) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.performTestAndCheckResults(ClearTXLockingDUnitTest.java:159) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.testPutWithClearDifferentVM(ClearTXLockingDUnitTest.java:109) Caused by: org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.ClearTXLockingDUnitTest$$Lambda$54/238328752.run in VM 0 running on Host 09baa480fa1f with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:401) at org.apache.geode.test.dunit.VM.invoke(VM.java:370) at org.apache.geode.test.dunit.VM.invoke(VM.java:313) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.putOperationsTest(ClearTXLockingDUnitTest.java:181) Caused by: org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.ClearTXLockingDUnitTest$$Lambda$57/1737276174.run in VM 1 running on Host 09baa480fa1f with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:401) at org.apache.geode.test.dunit.VM.invoke(VM.java:370) at org.apache.geode.test.dunit.VM.invoke(VM.java:313) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.releaseRegionOperation(ClearTXLockingDUnitTest.java:294) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.access$000(ClearTXLockingDUnitTest.java:62) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest$CommitTestCallback.run(ClearTXLockingDUnitTest.java:374) at org.apache.geode.internal.cache.TXState.applyChanges(TXState.java:792) at org.apache.geode.internal.cache.TXState.commit(TXState.java:460) at org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228) at org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.doPuts(ClearTXLockingDUnitTest.java:286) at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.lambda$putOperationsTest$bb17a952$1(ClearTXLockingDUnitTest.java:181) Caused by: java.lang.NullPointerException at org.apache.geode.internal.cache.ClearTXLockingDUnitTest.lambda$releaseRegionOperation$b6506259$1(ClearTXLockingDUnitTest.java:294) > CI Failure: ClearTXLockingDUnitTest.testPutWithClearDifferentVM > --- > > Key: GEODE-2275 > URL: https://issues.apache.org/jira/browse/GEODE-2275 > Project: Geode > Issue Type: Bug > Components: regions, transactions >Reporter: Eric Shu >Assignee: Nick Reich >Priority: Major > Labels: ci, flaky, pull-request-available > Fix For: 1.5.0 > > > org.apache.geode.internal.cache.ClearTXLockingDUnitTest > > testPutWithClearDifferentVM FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$1.run in VM 0 running > on Host d7fcb695b430 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:344) > at org.apache.geode.test.dunit.VM.invoke(VM.java:314) > at org.apache.geode.test.dunit.VM.invoke(VM.java:259) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.runLockingTest(ClearTXLockingDUnitTest.java:206) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.performTestAndCheckResults(ClearTXLockingDUnitTest.java:170) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.testPutWithClearDifferentVM(ClearTXLockingDUnitTest.java:115) > Caused by: > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$1$$Lambda$21/402256214.run > in VM 0 running on Host d7fcb695b430 with 4 VMs > Caused by: > org.apache.geode.test.dunit.RMIException: While invo
[jira] [Updated] (GEODE-2275) CI Failure: ClearTXLockingDUnitTest.testPutWithClearDifferentVM
[ https://issues.apache.org/jira/browse/GEODE-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-2275: Fix Version/s: (was: 1.5.0) > CI Failure: ClearTXLockingDUnitTest.testPutWithClearDifferentVM > --- > > Key: GEODE-2275 > URL: https://issues.apache.org/jira/browse/GEODE-2275 > Project: Geode > Issue Type: Bug > Components: regions, transactions >Reporter: Eric Shu >Assignee: Nick Reich >Priority: Major > Labels: ci, flaky, pull-request-available > > org.apache.geode.internal.cache.ClearTXLockingDUnitTest > > testPutWithClearDifferentVM FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$1.run in VM 0 running > on Host d7fcb695b430 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:344) > at org.apache.geode.test.dunit.VM.invoke(VM.java:314) > at org.apache.geode.test.dunit.VM.invoke(VM.java:259) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.runLockingTest(ClearTXLockingDUnitTest.java:206) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.performTestAndCheckResults(ClearTXLockingDUnitTest.java:170) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.testPutWithClearDifferentVM(ClearTXLockingDUnitTest.java:115) > Caused by: > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$1$$Lambda$21/402256214.run > in VM 0 running on Host d7fcb695b430 with 4 VMs > Caused by: > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$$Lambda$24/1595591059.run > in VM 1 running on Host d7fcb695b430 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:344) > at org.apache.geode.test.dunit.VM.invoke(VM.java:314) > at org.apache.geode.test.dunit.VM.invoke(VM.java:259) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.releaseRegionOperation(ClearTXLockingDUnitTest.java:324) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.access$100(ClearTXLockingDUnitTest.java:67) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest$CommitTestCallback.run(ClearTXLockingDUnitTest.java:408) > at > org.apache.geode.internal.cache.TXState.applyChanges(TXState.java:796) > at > org.apache.geode.internal.cache.TXState.commit(TXState.java:468) > at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:254) > at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:375) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.doPuts(ClearTXLockingDUnitTest.java:316) > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.access$000(ClearTXLockingDUnitTest.java:67) > Caused by: > java.lang.NullPointerException > at > org.apache.geode.internal.cache.ClearTXLockingDUnitTest.lambda$releaseRegionOperation$b6506259$1(ClearTXLockingDUnitTest.java:324) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work
[ https://issues.apache.org/jira/browse/GEODE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5039: Affects Version/s: 1.5.0 > EvictionAttributesMutator.setMaximum does not work > -- > > Key: GEODE-5039 > URL: https://issues.apache.org/jira/browse/GEODE-5039 > Project: Geode > Issue Type: Bug > Components: eviction >Affects Versions: 1.5.0 >Reporter: Eric Shu >Priority: Major > > EvictionAttributesMutator.setMaximum does not change the lru count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work
Eric Shu created GEODE-5039: --- Summary: EvictionAttributesMutator.setMaximum does not work Key: GEODE-5039 URL: https://issues.apache.org/jira/browse/GEODE-5039 Project: Geode Issue Type: Bug Components: eviction Reporter: Eric Shu EvictionAttributesMutator.setMaximum does not change the lru count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work
[ https://issues.apache.org/jira/browse/GEODE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5039: --- Assignee: Eric Shu > EvictionAttributesMutator.setMaximum does not work > -- > > Key: GEODE-5039 > URL: https://issues.apache.org/jira/browse/GEODE-5039 > Project: Geode > Issue Type: Bug > Components: eviction >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > EvictionAttributesMutator.setMaximum does not change the lru count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-5046: --- Assignee: Eric Shu > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
Eric Shu created GEODE-5046: --- Summary: RemotePutMessage.distribute should handle RegionDestoryedException Key: GEODE-5046 URL: https://issues.apache.org/jira/browse/GEODE-5046 Project: Geode Issue Type: Bug Components: regions Reporter: Eric Shu RemotePutMessage.distribute() tries to get a version tag from a remote member in a loop. It tries another member if one member failed. It is possible that a region is destroyed on a member, and the method should handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5046: Affects Version/s: 1.5.0 > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5046. - Resolution: Fixed Fix Version/s: 1.6.0 > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work
[ https://issues.apache.org/jira/browse/GEODE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-5039. - Resolution: Fixed Fix Version/s: 1.6.0 > EvictionAttributesMutator.setMaximum does not work > -- > > Key: GEODE-5039 > URL: https://issues.apache.org/jira/browse/GEODE-5039 > Project: Geode > Issue Type: Bug > Components: eviction >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > EvictionAttributesMutator.setMaximum does not change the lru count. > Â > Given I am configuring eviction > When setting EvictionAttributesMutator.setMaximum > Then the lru count should update accordingly -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5022) Transactions are not propagating deltas
[ https://issues.apache.org/jira/browse/GEODE-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5022: Issue Type: New Feature (was: Bug) > Transactions are not propagating deltas > --- > > Key: GEODE-5022 > URL: https://issues.apache.org/jira/browse/GEODE-5022 > Project: Geode > Issue Type: New Feature > Components: transactions >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0 >Reporter: Bruce Schuchardt >Priority: Major > Attachments: TransactionsWithDeltaDUnitTest.java > > > Client to server transactions propagate a delta from the client to the > server. The server then applies the delta to its cache and forgets about it. > It transmits the full object to other servers and to clients. > Server-initiated transactions also ignore delta values. > I'm attaching a client/server test that demonstrates the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5022) Transactions are not propagating deltas
[ https://issues.apache.org/jira/browse/GEODE-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435953#comment-16435953 ] Eric Shu commented on GEODE-5022: - Currently transaction implementation does not support delta propagation. We should document this behavior and then prioritize implementing if needed. > Transactions are not propagating deltas > --- > > Key: GEODE-5022 > URL: https://issues.apache.org/jira/browse/GEODE-5022 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0 >Reporter: Bruce Schuchardt >Priority: Major > Attachments: TransactionsWithDeltaDUnitTest.java > > > Client to server transactions propagate a delta from the client to the > server. The server then applies the delta to its cache and forgets about it. > It transmits the full object to other servers and to clients. > Server-initiated transactions also ignore delta values. > I'm attaching a client/server test that demonstrates the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5022) Transactions are not propagating deltas
[ https://issues.apache.org/jira/browse/GEODE-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5022: Priority: Minor (was: Major) > Transactions are not propagating deltas > --- > > Key: GEODE-5022 > URL: https://issues.apache.org/jira/browse/GEODE-5022 > Project: Geode > Issue Type: New Feature > Components: transactions >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0 >Reporter: Bruce Schuchardt >Priority: Minor > Attachments: TransactionsWithDeltaDUnitTest.java > > > Client to server transactions propagate a delta from the client to the > server. The server then applies the delta to its cache and forgets about it. > It transmits the full object to other servers and to clients. > Server-initiated transactions also ignore delta values. > I'm attaching a client/server test that demonstrates the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5022) Transactions do not support propagating deltas
[ https://issues.apache.org/jira/browse/GEODE-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5022: Summary: Transactions do not support propagating deltas (was: Transactions are not propagating deltas) > Transactions do not support propagating deltas > -- > > Key: GEODE-5022 > URL: https://issues.apache.org/jira/browse/GEODE-5022 > Project: Geode > Issue Type: New Feature > Components: transactions >Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0 >Reporter: Bruce Schuchardt >Priority: Minor > Attachments: TransactionsWithDeltaDUnitTest.java > > > Client to server transactions propagate a delta from the client to the > server. The server then applies the delta to its cache and forgets about it. > It transmits the full object to other servers and to clients. > Server-initiated transactions also ignore delta values. > I'm attaching a client/server test that demonstrates the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5046: Affects Version/s: 1.6.0 > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0, 1.6.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5046: Fix Version/s: (was: 1.6.0) 1.7.0 > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0, 1.6.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5046: Fix Version/s: (was: 1.7.0) 1.6.0 > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException
[ https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5046: Affects Version/s: (was: 1.6.0) > RemotePutMessage.distribute should handle RegionDestoryedException > -- > > Key: GEODE-5046 > URL: https://issues.apache.org/jira/browse/GEODE-5046 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.5.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > RemotePutMessage.distribute() tries to get a version tag from a remote member > in a loop. It tries another member if one member failed. > It is possible that a region is destroyed on a member, and the method should > handle it and retry to another member instead of failing the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5103) During rebalance, a client node may miss a transactional event
Eric Shu created GEODE-5103: --- Summary: During rebalance, a client node may miss a transactional event Key: GEODE-5103 URL: https://issues.apache.org/jira/browse/GEODE-5103 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu During rebalance, a new primary bucket could be created on another node while the original primary bucket become secondary in a short period of time. If a transaction occurs on the primary bucket node, TXCommitMessage will be sent to the secondary primary bucket node. There is a race that a event could be missed to be added to the subscription queue when the now secondary bucket is being removed to satisfy the redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 reassigned GEODE-5103: --- Assignee: Eric Shu > During rebalance, a client node may miss a transactional event > -- > > Key: GEODE-5103 > URL: https://issues.apache.org/jira/browse/GEODE-5103 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > During rebalance, a new primary bucket could be created on another node while > the original primary bucket become secondary in a short period of time. If a > transaction occurs on the primary bucket node, TXCommitMessage will be sent > to the secondary primary bucket node. > There is a race that a event could be missed to be added to the subscription > queue when the now secondary bucket is being removed to satisfy the > redundancy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6715) Possible NPE if member is becoming elder while shutting down
[ https://issues.apache.org/jira/browse/GEODE-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-6715. - Resolution: Duplicate This is duplicate of GEODE-6812 > Possible NPE if member is becoming elder while shutting down > > > Key: GEODE-6715 > URL: https://issues.apache.org/jira/browse/GEODE-6715 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Ryan McMahon >Priority: Major > Fix For: 1.10.0 > > > There is a race which can occur if a member is shutting down and becoming > elder simultaneously that results in an NPE. The logic for becoming elder > assumes we always successfully become the elder, but that might not be the > case if the member is shutting down. See the "close in progress" case in > ClusterElderManager.waitForElder() method to see when we would return false. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6886) Region Sync should not be invoked when lost member is an empty accessor of persistent replicate region
[ https://issues.apache.org/jira/browse/GEODE-6886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-6886: --- Assignee: Eric Shu > Region Sync should not be invoked when lost member is an empty accessor of > persistent replicate region > -- > > Key: GEODE-6886 > URL: https://issues.apache.org/jira/browse/GEODE-6886 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > The following ClassCastException would be thrown: > [warn 2019/06/17 13:51:57.025 PDT tid=0x39] Timer task > encountered > exception > org.apache.geode.ToDataException: class > org.apache.geode.internal.cache.versions.DiskRegionVersionVector > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2331) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2067) > at > org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2943) > at > org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.toData(InitialImageOperation.java:2138) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.tcp.MsgStreamer.writeMessage(MsgStreamer.java:242) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:385) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241) > at > org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1711) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1892) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2852) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:2779) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2816) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1526) > at > org.apache.geode.internal.cache.InitialImageOperation.synchronizeWith(InitialImageOperation.java:649) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeWith(DistributedRegion.java:1338) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeForLostMember(DistributedRegion.java:1327) > at > org.apache.geode.internal.cache.DistributedRegion.performSynchronizeForLostMemberTask(DistributedRegion.java:1309) > at > org.apache.geode.internal.cache.DistributedRegion$1.run2(DistributedRegion.java:1283) > at > org.apache.geode.internal.SystemTimer$SystemTimerTask.run(SystemTimer.java:445) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.ClassCastException: > org.apache.geode.distributed.internal.membership.InternalDistributedMember > cannot be cast to org.apache.geode.internal.cache.persistence.DiskStoreID > at > org.apache.geode.internal.cache.versions.DiskRegionVersionVector.writeMember(DiskRegionVersionVector.java:30) > at > org.apache.geode.internal.cache.versions.RegionVersionVector.toData(RegionVersionVector.java:1205) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > ... 24 more > The reason there is no need to sync with empty accessor is that it forwards > the writes to actual region hosts, and only a host could generate a region > version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6886) Region Sync should not be invoked when lost member is an empty accessor of persistent replicate region
Eric Shu created GEODE-6886: --- Summary: Region Sync should not be invoked when lost member is an empty accessor of persistent replicate region Key: GEODE-6886 URL: https://issues.apache.org/jira/browse/GEODE-6886 Project: Geode Issue Type: Bug Components: regions Reporter: Eric Shu The following ClassCastException would be thrown: [warn 2019/06/17 13:51:57.025 PDT tid=0x39] Timer task encountered exception org.apache.geode.ToDataException: class org.apache.geode.internal.cache.versions.DiskRegionVersionVector at org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2331) at org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) at org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2067) at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2943) at org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.toData(InitialImageOperation.java:2138) at org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) at org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) at org.apache.geode.internal.tcp.MsgStreamer.writeMessage(MsgStreamer.java:242) at org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:385) at org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241) at org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596) at org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1711) at org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1892) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2852) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:2779) at org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2816) at org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1526) at org.apache.geode.internal.cache.InitialImageOperation.synchronizeWith(InitialImageOperation.java:649) at org.apache.geode.internal.cache.DistributedRegion.synchronizeWith(DistributedRegion.java:1338) at org.apache.geode.internal.cache.DistributedRegion.synchronizeForLostMember(DistributedRegion.java:1327) at org.apache.geode.internal.cache.DistributedRegion.performSynchronizeForLostMemberTask(DistributedRegion.java:1309) at org.apache.geode.internal.cache.DistributedRegion$1.run2(DistributedRegion.java:1283) at org.apache.geode.internal.SystemTimer$SystemTimerTask.run(SystemTimer.java:445) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Caused by: java.lang.ClassCastException: org.apache.geode.distributed.internal.membership.InternalDistributedMember cannot be cast to org.apache.geode.internal.cache.persistence.DiskStoreID at org.apache.geode.internal.cache.versions.DiskRegionVersionVector.writeMember(DiskRegionVersionVector.java:30) at org.apache.geode.internal.cache.versions.RegionVersionVector.toData(RegionVersionVector.java:1205) at org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) ... 24 more The reason there is no need to sync with empty accessor is that it forwards the writes to actual region hosts, and only a host could generate a region version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6886) Region Sync should not be invoked when lost member is an empty accessor of persistent replicate region
[ https://issues.apache.org/jira/browse/GEODE-6886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6886: Affects Version/s: 1.10.0 > Region Sync should not be invoked when lost member is an empty accessor of > persistent replicate region > -- > > Key: GEODE-6886 > URL: https://issues.apache.org/jira/browse/GEODE-6886 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.10.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The following ClassCastException would be thrown: > [warn 2019/06/17 13:51:57.025 PDT tid=0x39] Timer task > encountered > exception > org.apache.geode.ToDataException: class > org.apache.geode.internal.cache.versions.DiskRegionVersionVector > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2331) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2067) > at > org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2943) > at > org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.toData(InitialImageOperation.java:2138) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.tcp.MsgStreamer.writeMessage(MsgStreamer.java:242) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:385) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241) > at > org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1711) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1892) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2852) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:2779) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2816) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1526) > at > org.apache.geode.internal.cache.InitialImageOperation.synchronizeWith(InitialImageOperation.java:649) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeWith(DistributedRegion.java:1338) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeForLostMember(DistributedRegion.java:1327) > at > org.apache.geode.internal.cache.DistributedRegion.performSynchronizeForLostMemberTask(DistributedRegion.java:1309) > at > org.apache.geode.internal.cache.DistributedRegion$1.run2(DistributedRegion.java:1283) > at > org.apache.geode.internal.SystemTimer$SystemTimerTask.run(SystemTimer.java:445) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.ClassCastException: > org.apache.geode.distributed.internal.membership.InternalDistributedMember > cannot be cast to org.apache.geode.internal.cache.persistence.DiskStoreID > at > org.apache.geode.internal.cache.versions.DiskRegionVersionVector.writeMember(DiskRegionVersionVector.java:30) > at > org.apache.geode.internal.cache.versions.RegionVersionVector.toData(RegionVersionVector.java:1205) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > ... 24 more > The reason there is no need to sync with empty accessor is that it forwards > the writes to actual region hosts, and only a host could generate a region > version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6886) Region Sync should not be invoked when lost member is an empty accessor of persistent replicate region
[ https://issues.apache.org/jira/browse/GEODE-6886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-6886. - Resolution: Fixed Fix Version/s: 1.10.0 > Region Sync should not be invoked when lost member is an empty accessor of > persistent replicate region > -- > > Key: GEODE-6886 > URL: https://issues.apache.org/jira/browse/GEODE-6886 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.10.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The following ClassCastException would be thrown: > [warn 2019/06/17 13:51:57.025 PDT tid=0x39] Timer task > encountered > exception > org.apache.geode.ToDataException: class > org.apache.geode.internal.cache.versions.DiskRegionVersionVector > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2331) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2067) > at > org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2943) > at > org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.toData(InitialImageOperation.java:2138) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > at > org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1492) > at > org.apache.geode.internal.tcp.MsgStreamer.writeMessage(MsgStreamer.java:242) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:385) > at > org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241) > at > org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1711) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1892) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2852) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:2779) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2816) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1526) > at > org.apache.geode.internal.cache.InitialImageOperation.synchronizeWith(InitialImageOperation.java:649) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeWith(DistributedRegion.java:1338) > at > org.apache.geode.internal.cache.DistributedRegion.synchronizeForLostMember(DistributedRegion.java:1327) > at > org.apache.geode.internal.cache.DistributedRegion.performSynchronizeForLostMemberTask(DistributedRegion.java:1309) > at > org.apache.geode.internal.cache.DistributedRegion$1.run2(DistributedRegion.java:1283) > at > org.apache.geode.internal.SystemTimer$SystemTimerTask.run(SystemTimer.java:445) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.ClassCastException: > org.apache.geode.distributed.internal.membership.InternalDistributedMember > cannot be cast to org.apache.geode.internal.cache.persistence.DiskStoreID > at > org.apache.geode.internal.cache.versions.DiskRegionVersionVector.writeMember(DiskRegionVersionVector.java:30) > at > org.apache.geode.internal.cache.versions.RegionVersionVector.toData(RegionVersionVector.java:1205) > at > org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2300) > ... 24 more > The reason there is no need to sync with empty accessor is that it forwards > the writes to actual region hosts, and only a host could generate a region > version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6900) Add a unit test that transaction1 commit failed if it writes on a key was read in transaction2 and transaction2 has hold the lock when read conflict detection is on
[ https://issues.apache.org/jira/browse/GEODE-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-6900: --- Assignee: Eric Shu > Add a unit test that transaction1 commit failed if it writes on a key was > read in transaction2 and transaction2 has hold the lock when read conflict > detection is on > - > > Key: GEODE-6900 > URL: https://issues.apache.org/jira/browse/GEODE-6900 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > Need to add a unit test with read conflict detection is on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6900) Add a unit test that transaction1 commit failed if it writes on a key was read in transaction2 and transaction2 has hold the lock when read conflict detection is on
Eric Shu created GEODE-6900: --- Summary: Add a unit test that transaction1 commit failed if it writes on a key was read in transaction2 and transaction2 has hold the lock when read conflict detection is on Key: GEODE-6900 URL: https://issues.apache.org/jira/browse/GEODE-6900 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu Need to add a unit test with read conflict detection is on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6903) CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion
Eric Shu created GEODE-6903: --- Summary: CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion Key: GEODE-6903 URL: https://issues.apache.org/jira/browse/GEODE-6903 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest > testExceptionHandlingGetConnection FAILED org.junit.ComparisonFailure: expected:<[0]> but was:<[2]> at sun.reflect.GeneratedConstructorAccessor26.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection(GemFireTransactionDataSourceIntegrationTest.java:141) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-results/integrationTest/1561170841/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-artifacts/1561170841/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0399.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6337) Rolling upgrade test fails on JDK11 in CI (sometimes)
[
https://issues.apache.org/jira/browse/GEODE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871556#comment-16871556
]
Eric Shu commented on GEODE-6337:
-
Failed again in another CI run.
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions
> testHARegionNameOnDifferentServerVersions[from_v170] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.VM$$Lambda$158/0x000840246c40.run in VM 1
running on Host 97cb14f26e62 with 4 VMs with version 160
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583)
at org.apache.geode.test.dunit.VM.bounce(VM.java:540)
at org.apache.geode.test.dunit.VM.bounce(VM.java:517)
at
org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87)
at
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions.testHARegionNameOnDifferentServerVersions(RollingUpgradeHARegionNameOnDifferentServerVersions.java:38)
Caused by:
java.rmi.UnmarshalException: Error unmarshaling return header; nested
exception is:
java.io.EOFException
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161)
at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source)
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576)
... 4 more
Caused by:
java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:272)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222)
... 9 more
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host
97cb14f26e62 with 4 VMs with version 160
Caused by:
java.lang.IllegalStateException: VM not available: VM 1 running on Host
97cb14f26e62 with 4 VMs with version 160
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0400/test-results/upgradeTest/1561397510/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0400/test-artifacts/1561397510/upgradetestfiles-OpenJDK11-1.10.0-SNAPSHOT.0400.tgz
> Rolling upgrade test fails on JDK11 in CI (sometimes)
> -
>
> Key: GEODE-6337
> URL: https://issues.apache.org/jira/browse/GEODE-6337
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.9.0
>Reporter: Bill Burcham
>Priority: Major
> Labels: jdk11
>
> In this build:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/333
> {{RollingUpgradeRollLocatorsWithOldServer.testRollLocatorsWithOldServer()}}
> fails, apparently trying to start up Geode version 1.3.0.
> Have a look at the first two errors in the test output:
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollLocatorsWithOldServer
> > testRollLocatorsWithOldServer[from_v130] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.VM$$Lambda$157/0x000840246c40.run in VM 1
> running on Host f634ce7e984c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:537)
> at org.apache.geode.test.dunit.VM.bounce(VM.java:497)
> at org.apache.geode.test.dunit.VM.bounce(VM.java:476)
> at
> org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:85)
> at
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollLocatorsWithOldServer.testRollLocatorsWithOldServer(RollingUpgradeRollLocatorsWithOldServer.java:39)
> Caused by:
> java.rmi.UnmarshalException: Error unmarshaling return header; nested
> exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209)
> at
> java.rmi.server.RemoteObjectInv
[jira] [Comment Edited] (GEODE-6337) Rolling upgrade test fails on JDK11 in CI (sometimes)
[ https://issues.apache.org/jira/browse/GEODE-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871556#comment-16871556 ] Eric Shu edited comment on GEODE-6337 at 6/24/19 6:00 PM: -- Failed again in another CI run. org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions > testHARegionNameOnDifferentServerVersions[from_v170] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.VM$$Lambda$158/0x000840246c40.run in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:583) at org.apache.geode.test.dunit.VM.bounce(VM.java:540) at org.apache.geode.test.dunit.VM.bounce(VM.java:517) at org.apache.geode.test.dunit.internal.DUnitHost.getVM(DUnitHost.java:87) at org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions.testHARegionNameOnDifferentServerVersions(RollingUpgradeHARegionNameOnDifferentServerVersions.java:38) Caused by: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.io.EOFException at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:236) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161) at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:209) at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:161) at com.sun.proxy.$Proxy40.executeMethodOnObject(Unknown Source) at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:576) ... 4 more Caused by: java.io.EOFException at java.io.DataInputStream.readByte(DataInputStream.java:272) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:222) ... 9 more org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 Caused by: java.lang.IllegalStateException: VM not available: VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions > testHARegionNameOnDifferentServerVersions[from_v180] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.VM$$Lambda$157/0x000840247040.call in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.21; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.21; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeHARegionNameOnDifferentServerVersions > testHARegionNameOnDifferentServerVersions[from_v190] FAILED org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.21; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 97cb14f26e62 with 4 VMs with version 160 Caused by: java.rmi.ConnectException: Connection refused to host: 172.17.0.21; nested exception is: java.net.ConnectException: Connection refused (Connection refused) Caused by: java.net.ConnectException: Connection refused (Connection refused) =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0400/test-results/upgradeTest/1561397510/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[jira] [Created] (GEODE-6905) Do not need to wait for initialization of distributed region before schedule region sync timed task
Eric Shu created GEODE-6905: --- Summary: Do not need to wait for initialization of distributed region before schedule region sync timed task Key: GEODE-6905 URL: https://issues.apache.org/jira/browse/GEODE-6905 Project: Geode Issue Type: Bug Components: regions Reporter: Eric Shu The wait for initialization is only needed before the actual region sync operation. There is no need to wait for initialization just to schedule the region sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6905) Do not need to wait for initialization of distributed region before schedule region sync timed task
[ https://issues.apache.org/jira/browse/GEODE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-6905: --- Assignee: Eric Shu > Do not need to wait for initialization of distributed region before schedule > region sync timed task > --- > > Key: GEODE-6905 > URL: https://issues.apache.org/jira/browse/GEODE-6905 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > The wait for initialization is only needed before the actual region sync > operation. There is no need to wait for initialization just to schedule the > region sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6905) Do not need to wait for initialization of distributed region before schedule region sync timed task
[ https://issues.apache.org/jira/browse/GEODE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6905: Affects Version/s: 1.10.0 > Do not need to wait for initialization of distributed region before schedule > region sync timed task > --- > > Key: GEODE-6905 > URL: https://issues.apache.org/jira/browse/GEODE-6905 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.10.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The wait for initialization is only needed before the actual region sync > operation. There is no need to wait for initialization just to schedule the > region sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6905) Do not need to wait for initialization of distributed region before schedule region sync timed task
[ https://issues.apache.org/jira/browse/GEODE-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-6905. - Resolution: Fixed Fix Version/s: 1.10.0 > Do not need to wait for initialization of distributed region before schedule > region sync timed task > --- > > Key: GEODE-6905 > URL: https://issues.apache.org/jira/browse/GEODE-6905 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The wait for initialization is only needed before the actual region sync > operation. There is no need to wait for initialization just to schedule the > region sync. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6955) Client transaction commits failed with NPE in detectReadConflicts
Eric Shu created GEODE-6955: --- Summary: Client transaction commits failed with NPE in detectReadConflicts Key: GEODE-6955 URL: https://issues.apache.org/jira/browse/GEODE-6955 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu This is shown when I add a dunit test for changes in detectReadConflicts implementation. It occurs when client registers interest and a key is read locked. The issue is that a read locked key op in transaction is null. [vm0] [info 2019/07/10 14:21:05.412 PDT tid=0x51] event is TXEntryState$TxEntryEventImpl[op=null;region=/TempdunitTest_readTransactionCanBlockWriteTransaction_region;key=1;callbackArg=null;originRemote=true;originMember=10.118.20.78(7291):41001] [vm0] [info 2019/07/10 14:21:05.412 PDT tid=0x51] event.getOperation is null [vm2] [info 2019/07/10 14:21:05.428 PDT tid=0x13] Got result: EXCEPTION_OCCURRED [vm2] org.apache.geode.cache.client.ServerOperationException: remote server on 10.118.20.78(7293:loner):54498:f4dcc2dd: While performing a remote commit [vm2] at org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:286) [vm2] at org.apache.geode.cache.client.internal.CommitOp$CommitOpImpl.processResponse(CommitOp.java:68) [vm2] at org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222) [vm2] at org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207) [vm2] at org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382) [vm2] at org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263) [vm2] at org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353) [vm2] at org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750) [vm2] at org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329) [vm2] at org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:183) [vm2] at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:122) [vm2] at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) [vm2] at org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) [vm2] at org.apache.geode.cache.client.internal.CommitOp.execute(CommitOp.java:34) [vm2] at org.apache.geode.cache.client.internal.ServerRegionProxy.commit(ServerRegionProxy.java:246) [vm2] at org.apache.geode.internal.cache.tx.ClientTXStateStub.commit(ClientTXStateStub.java:115) [vm2] at org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:211) [vm2] at org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:426) [vm2] at org.apache.geode.internal.cache.TempdunitTest.commitReadTransaction(TempdunitTest.java:221) [vm2] at org.apache.geode.internal.cache.TempdunitTest.lambda$readTransactionCanBlockWriteTransaction$632092bf$1(TempdunitTest.java:105) [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm2] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm2] at java.lang.reflect.Method.invoke(Method.java:498) [vm2] at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) [vm2] at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm2] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm2] at java.lang.reflect.Method.invoke(Method.java:498) [vm2] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:200) [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:197) [vm2] at java.security.AccessController.doPrivileged(Native Method) [vm2] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [vm2] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [vm2] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [vm2] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [vm2] at java.security.AccessController.doPrivileged(Native Method) [vm2] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [vm2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [vm2] at java.util.concurrent.Thread
[jira] [Updated] (GEODE-6955) Client transaction commits failed with NPE in detectReadConflicts
[ https://issues.apache.org/jira/browse/GEODE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6955: Affects Version/s: 1.1.0 > Client transaction commits failed with NPE in detectReadConflicts > - > > Key: GEODE-6955 > URL: https://issues.apache.org/jira/browse/GEODE-6955 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Priority: Major > > This is shown when I add a dunit test for changes in detectReadConflicts > implementation. > It occurs when client registers interest and a key is read locked. The issue > is that a read locked key op in transaction is null. > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event is > TXEntryState$TxEntryEventImpl[op=null;region=/TempdunitTest_readTransactionCanBlockWriteTransaction_region;key=1;callbackArg=null;originRemote=true;originMember=10.118.20.78(7291):41001] > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event.getOperation is null > [vm2] [info 2019/07/10 14:21:05.428 PDT > tid=0x13] Got result: EXCEPTION_OCCURRED > [vm2] org.apache.geode.cache.client.ServerOperationException: remote server > on 10.118.20.78(7293:loner):54498:f4dcc2dd: While performing a remote commit > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:286) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp$CommitOpImpl.processResponse(CommitOp.java:68) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382) > [vm2] at > org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263) > [vm2] at > org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:183) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:122) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) > [vm2] at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp.execute(CommitOp.java:34) > [vm2] at > org.apache.geode.cache.client.internal.ServerRegionProxy.commit(ServerRegionProxy.java:246) > [vm2] at > org.apache.geode.internal.cache.tx.ClientTXStateStub.commit(ClientTXStateStub.java:115) > [vm2] at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:211) > [vm2] at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:426) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.commitReadTransaction(TempdunitTest.java:221) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.lambda$readTransactionCanBlockWriteTransaction$632092bf$1(TempdunitTest.java:105) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm2] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm2] at java.security.AccessController.doPrivileged(Native Method) > [vm2]
[jira] [Assigned] (GEODE-6955) Client transaction commits failed with NPE in detectReadConflicts
[ https://issues.apache.org/jira/browse/GEODE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-6955: --- Assignee: Eric Shu > Client transaction commits failed with NPE in detectReadConflicts > - > > Key: GEODE-6955 > URL: https://issues.apache.org/jira/browse/GEODE-6955 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > This is shown when I add a dunit test for changes in detectReadConflicts > implementation. > It occurs when client registers interest and a key is read locked. The issue > is that a read locked key op in transaction is null. > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event is > TXEntryState$TxEntryEventImpl[op=null;region=/TempdunitTest_readTransactionCanBlockWriteTransaction_region;key=1;callbackArg=null;originRemote=true;originMember=10.118.20.78(7291):41001] > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event.getOperation is null > [vm2] [info 2019/07/10 14:21:05.428 PDT > tid=0x13] Got result: EXCEPTION_OCCURRED > [vm2] org.apache.geode.cache.client.ServerOperationException: remote server > on 10.118.20.78(7293:loner):54498:f4dcc2dd: While performing a remote commit > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:286) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp$CommitOpImpl.processResponse(CommitOp.java:68) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382) > [vm2] at > org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263) > [vm2] at > org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:183) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:122) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) > [vm2] at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp.execute(CommitOp.java:34) > [vm2] at > org.apache.geode.cache.client.internal.ServerRegionProxy.commit(ServerRegionProxy.java:246) > [vm2] at > org.apache.geode.internal.cache.tx.ClientTXStateStub.commit(ClientTXStateStub.java:115) > [vm2] at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:211) > [vm2] at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:426) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.commitReadTransaction(TempdunitTest.java:221) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.lambda$readTransactionCanBlockWriteTransaction$632092bf$1(TempdunitTest.java:105) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm2] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm2] at java.security.AccessController.doPr
[jira] [Updated] (GEODE-6955) Client transaction commits failed with NPE in detectReadConflicts
[ https://issues.apache.org/jira/browse/GEODE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6955: Labels: GeodeCommons (was: ) > Client transaction commits failed with NPE in detectReadConflicts > - > > Key: GEODE-6955 > URL: https://issues.apache.org/jira/browse/GEODE-6955 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > This is shown when I add a dunit test for changes in detectReadConflicts > implementation. > It occurs when client registers interest and a key is read locked. The issue > is that a read locked key op in transaction is null. > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event is > TXEntryState$TxEntryEventImpl[op=null;region=/TempdunitTest_readTransactionCanBlockWriteTransaction_region;key=1;callbackArg=null;originRemote=true;originMember=10.118.20.78(7291):41001] > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event.getOperation is null > [vm2] [info 2019/07/10 14:21:05.428 PDT > tid=0x13] Got result: EXCEPTION_OCCURRED > [vm2] org.apache.geode.cache.client.ServerOperationException: remote server > on 10.118.20.78(7293:loner):54498:f4dcc2dd: While performing a remote commit > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:286) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp$CommitOpImpl.processResponse(CommitOp.java:68) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382) > [vm2] at > org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263) > [vm2] at > org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:183) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:122) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) > [vm2] at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp.execute(CommitOp.java:34) > [vm2] at > org.apache.geode.cache.client.internal.ServerRegionProxy.commit(ServerRegionProxy.java:246) > [vm2] at > org.apache.geode.internal.cache.tx.ClientTXStateStub.commit(ClientTXStateStub.java:115) > [vm2] at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:211) > [vm2] at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:426) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.commitReadTransaction(TempdunitTest.java:221) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.lambda$readTransactionCanBlockWriteTransaction$632092bf$1(TempdunitTest.java:105) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm2] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm2] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm2]
[jira] [Created] (GEODE-6975) When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what hap
Eric Shu created GEODE-6975: --- Summary: When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what happened Key: GEODE-6975 URL: https://issues.apache.org/jira/browse/GEODE-6975 Project: Geode Issue Type: Bug Components: persistence, regions Reporter: Eric Shu Currently, when a persistent bucket or distributed region is created on member A, member A will send its new PersistentMemberID to other hosts (e.g member B), so that member B will know and persist A's new ID for the region. However, when member B is being shut down during processing the PrepareNewPersistentMemberMessage (did not persist A's id), it just send a reply message indicate it had persisted. This will cause Member A removes its old member id and only persists its new member id. This is wrong as the member A could also been shut down at the same time. There is a race that member B could be recognized as hosting the last copy for the region. This will lead to member B to recover first, and member B can only recover member A's old persistent id. This will lead to Member A not able to restart, as B does not recognize A's new persistent id. [error 2018/09/19 01:18:00.972 PDT dataStoregemfire6_host1_6131 tid=0x77] A DiskAccessException has occurred while writing to the disk for region /__PR/_B__partitionedRegion_0. The cache will be closed. org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region /__PR/_B__partitionedRegion_0 remote member rs-FullRegression19041704a3i3large-hydra-client-62(dataStoregemfire1_host1_5862:5862):1025 with persistent data /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_1_dataStore1_disk_1 created at timestamp 1537345060760 version 0 diskStoreId a35a937a082b4066-af019365b6a5114b name null was not part of the same distributed system as the local data from /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_6_dataStore6_disk_1 created at timestamp 1537344996470 version 0 diskStoreId 108be5a03966418f-980c1d88e9b26d1d name null at org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:521) at org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.removeReplicatesIfWeAreEqualToAnyOrElseClearEqualMembers(PersistenceInitialImageAdvisor.java:181) at org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.getAdvice(PersistenceInitialImageAdvisor.java:69) at org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:831) at org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52) at org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1200) at org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1081) at org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:258) at org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:1014) at org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:779) at org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:454) at org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2895) at org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:447) at org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:390) at org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1756) at org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58) at org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1748) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-6975) When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what hap
[ https://issues.apache.org/jira/browse/GEODE-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6975: Affects Version/s: 1.1.0 > When a redundant copy or replica of a distributed region failed to persistent > remote member's new persistence id, it should send reply exception back to > indicate what happened > --- > > Key: GEODE-6975 > URL: https://issues.apache.org/jira/browse/GEODE-6975 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > Currently, when a persistent bucket or distributed region is created on > member A, member A will send its new PersistentMemberID to other hosts (e.g > member B), so that member B will know and persist A's new ID for the region. > However, when member B is being shut down during processing the > PrepareNewPersistentMemberMessage (did not persist A's id), it just send a > reply message indicate it had persisted. This will cause Member A removes its > old member id and only persists its new member id. This is wrong as the > member A could also been shut down at the same time. There is a race that > member B could be recognized as hosting the last copy for the region. This > will lead to member B to recover first, and member B can only recover member > A's old persistent id. This will lead to Member A not able to restart, as B > does not recognize A's new persistent id. > [error 2018/09/19 01:18:00.972 PDT dataStoregemfire6_host1_6131 thread for bucket _B__partitionedRegion_0> tid=0x77] A DiskAccessException > has occurred while writing to the disk for region > /__PR/_B__partitionedRegion_0. The cache will be closed. > org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region > /__PR/_B__partitionedRegion_0 remote member > rs-FullRegression19041704a3i3large-hydra-client-62(dataStoregemfire1_host1_5862:5862):1025 > with persistent data > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_1_dataStore1_disk_1 > created at timestamp 1537345060760 version 0 diskStoreId > a35a937a082b4066-af019365b6a5114b name null was not part of the same > distributed system as the local data from > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_6_dataStore6_disk_1 > created at timestamp 1537344996470 version 0 diskStoreId > 108be5a03966418f-980c1d88e9b26d1d name null > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:521) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.removeReplicatesIfWeAreEqualToAnyOrElseClearEqualMembers(PersistenceInitialImageAdvisor.java:181) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.getAdvice(PersistenceInitialImageAdvisor.java:69) > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:831) > at > org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52) > at > org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1200) > at > org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1081) > at > org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:258) > at > org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:1014) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:779) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:454) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2895) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:447) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:390) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1756) > at > org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1748) > at java.lang.Thread.run
[jira] [Assigned] (GEODE-6975) When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what ha
[ https://issues.apache.org/jira/browse/GEODE-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-6975: --- Assignee: Eric Shu > When a redundant copy or replica of a distributed region failed to persistent > remote member's new persistence id, it should send reply exception back to > indicate what happened > --- > > Key: GEODE-6975 > URL: https://issues.apache.org/jira/browse/GEODE-6975 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > Currently, when a persistent bucket or distributed region is created on > member A, member A will send its new PersistentMemberID to other hosts (e.g > member B), so that member B will know and persist A's new ID for the region. > However, when member B is being shut down during processing the > PrepareNewPersistentMemberMessage (did not persist A's id), it just send a > reply message indicate it had persisted. This will cause Member A removes its > old member id and only persists its new member id. This is wrong as the > member A could also been shut down at the same time. There is a race that > member B could be recognized as hosting the last copy for the region. This > will lead to member B to recover first, and member B can only recover member > A's old persistent id. This will lead to Member A not able to restart, as B > does not recognize A's new persistent id. > [error 2018/09/19 01:18:00.972 PDT dataStoregemfire6_host1_6131 thread for bucket _B__partitionedRegion_0> tid=0x77] A DiskAccessException > has occurred while writing to the disk for region > /__PR/_B__partitionedRegion_0. The cache will be closed. > org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region > /__PR/_B__partitionedRegion_0 remote member > rs-FullRegression19041704a3i3large-hydra-client-62(dataStoregemfire1_host1_5862:5862):1025 > with persistent data > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_1_dataStore1_disk_1 > created at timestamp 1537345060760 version 0 diskStoreId > a35a937a082b4066-af019365b6a5114b name null was not part of the same > distributed system as the local data from > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_6_dataStore6_disk_1 > created at timestamp 1537344996470 version 0 diskStoreId > 108be5a03966418f-980c1d88e9b26d1d name null > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:521) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.removeReplicatesIfWeAreEqualToAnyOrElseClearEqualMembers(PersistenceInitialImageAdvisor.java:181) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.getAdvice(PersistenceInitialImageAdvisor.java:69) > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:831) > at > org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52) > at > org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1200) > at > org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1081) > at > org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:258) > at > org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:1014) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:779) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:454) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2895) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:447) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:390) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1756) > at > org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.java:1748) > at java.lang.Thread.run(Thread.java:748) -- This
[jira] [Updated] (GEODE-6975) When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what hap
[ https://issues.apache.org/jira/browse/GEODE-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-6975: Labels: GeodeCommons (was: ) > When a redundant copy or replica of a distributed region failed to persistent > remote member's new persistence id, it should send reply exception back to > indicate what happened > --- > > Key: GEODE-6975 > URL: https://issues.apache.org/jira/browse/GEODE-6975 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > Currently, when a persistent bucket or distributed region is created on > member A, member A will send its new PersistentMemberID to other hosts (e.g > member B), so that member B will know and persist A's new ID for the region. > However, when member B is being shut down during processing the > PrepareNewPersistentMemberMessage (did not persist A's id), it just send a > reply message indicate it had persisted. This will cause Member A removes its > old member id and only persists its new member id. This is wrong as the > member A could also been shut down at the same time. There is a race that > member B could be recognized as hosting the last copy for the region. This > will lead to member B to recover first, and member B can only recover member > A's old persistent id. This will lead to Member A not able to restart, as B > does not recognize A's new persistent id. > [error 2018/09/19 01:18:00.972 PDT dataStoregemfire6_host1_6131 thread for bucket _B__partitionedRegion_0> tid=0x77] A DiskAccessException > has occurred while writing to the disk for region > /__PR/_B__partitionedRegion_0. The cache will be closed. > org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region > /__PR/_B__partitionedRegion_0 remote member > rs-FullRegression19041704a3i3large-hydra-client-62(dataStoregemfire1_host1_5862:5862):1025 > with persistent data > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_1_dataStore1_disk_1 > created at timestamp 1537345060760 version 0 diskStoreId > a35a937a082b4066-af019365b6a5114b name null was not part of the same > distributed system as the local data from > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_6_dataStore6_disk_1 > created at timestamp 1537344996470 version 0 diskStoreId > 108be5a03966418f-980c1d88e9b26d1d name null > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:521) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.removeReplicatesIfWeAreEqualToAnyOrElseClearEqualMembers(PersistenceInitialImageAdvisor.java:181) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.getAdvice(PersistenceInitialImageAdvisor.java:69) > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:831) > at > org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52) > at > org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1200) > at > org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1081) > at > org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:258) > at > org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:1014) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:779) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:454) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2895) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:447) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:390) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1756) > at > org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run(PRHARedundancyProvider.jav
[jira] [Resolved] (GEODE-6955) Client transaction commits failed with NPE in detectReadConflicts
[ https://issues.apache.org/jira/browse/GEODE-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-6955. - Resolution: Fixed Fix Version/s: 1.10.0 > Client transaction commits failed with NPE in detectReadConflicts > - > > Key: GEODE-6955 > URL: https://issues.apache.org/jira/browse/GEODE-6955 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This is shown when I add a dunit test for changes in detectReadConflicts > implementation. > It occurs when client registers interest and a key is read locked. The issue > is that a read locked key op in transaction is null. > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event is > TXEntryState$TxEntryEventImpl[op=null;region=/TempdunitTest_readTransactionCanBlockWriteTransaction_region;key=1;callbackArg=null;originRemote=true;originMember=10.118.20.78(7291):41001] > [vm0] [info 2019/07/10 14:21:05.412 PDT Thread 1> tid=0x51] event.getOperation is null > [vm2] [info 2019/07/10 14:21:05.428 PDT > tid=0x13] Got result: EXCEPTION_OCCURRED > [vm2] org.apache.geode.cache.client.ServerOperationException: remote server > on 10.118.20.78(7293:loner):54498:f4dcc2dd: While performing a remote commit > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processObjResponse(AbstractOp.java:286) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp$CommitOpImpl.processResponse(CommitOp.java:68) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:207) > [vm2] at > org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382) > [vm2] at > org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263) > [vm2] at > org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:183) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:122) > [vm2] at > org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108) > [vm2] at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:770) > [vm2] at > org.apache.geode.cache.client.internal.CommitOp.execute(CommitOp.java:34) > [vm2] at > org.apache.geode.cache.client.internal.ServerRegionProxy.commit(ServerRegionProxy.java:246) > [vm2] at > org.apache.geode.internal.cache.tx.ClientTXStateStub.commit(ClientTXStateStub.java:115) > [vm2] at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:211) > [vm2] at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:426) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.commitReadTransaction(TempdunitTest.java:221) > [vm2] at > org.apache.geode.internal.cache.TempdunitTest.lambda$readTransactionCanBlockWriteTransaction$632092bf$1(TempdunitTest.java:105) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm2] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm2] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm2] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm2] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm2] at java.lang.reflect.Method.invoke(Method.java:498) > [vm2] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm2] at sun.rmi.transport.Transport$1.run(Tra
[jira] [Commented] (GEODE-6586) ClientServerTransactionFailoverDistributedTest txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted failed
[
https://issues.apache.org/jira/browse/GEODE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887456#comment-16887456
]
Eric Shu commented on GEODE-6586:
-
This is reproduced again in ci.
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
>
txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$167/1387407484.run
in VM 1 running on Host 591d851cdcf8 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted(ClientServerTransactionFailoverDistributedTest.java:437)
Caused by:
org.junit.ComparisonFailure: expected:<"TxValue-2"> but was:
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.ClientServerTransactionFailoverDistributedTest.lambda$txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted$bb17a952$7(ClientServerTransactionFailoverDistributedTest.java:440)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-results/distributedTest/1563400137/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-artifacts/1563400137/distributedtestfiles-OpenJDK8-9.9.0-build.0239.tgz
> ClientServerTransactionFailoverDistributedTest
> txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
> failed
> -
>
> Key: GEODE-6586
> URL: https://issues.apache.org/jira/browse/GEODE-6586
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: xiaojian zhou
>Assignee: Eric Shu
>Priority: Major
>
> {noformat}
> It's found in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/559
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> >
> txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$177/577249945.run
> in VM 1 running on Host 09628b632eb3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted(ClientServerTransactionFailoverDistributedTest.java:437)
> Caused by:
> org.junit.ComparisonFailure: expected:<"TxValue-1"> but was:
> 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.ClientServerTransactionFailoverDistributedTest.lambda$txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted$bb17a952$7(ClientServerTransactionFailoverDistributedTest.java:439)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (GEODE-6586) ClientServerTransactionFailoverDistributedTest txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted failed
[
https://issues.apache.org/jira/browse/GEODE-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887456#comment-16887456
]
Eric Shu edited comment on GEODE-6586 at 7/17/19 10:07 PM:
---
This is reproduced again in ci:
https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK8/builds/781
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
>
txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$167/1387407484.run
in VM 1 running on Host 591d851cdcf8 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted(ClientServerTransactionFailoverDistributedTest.java:437)
Caused by:
org.junit.ComparisonFailure: expected:<"TxValue-2"> but was:
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.ClientServerTransactionFailoverDistributedTest.lambda$txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted$bb17a952$7(ClientServerTransactionFailoverDistributedTest.java:440)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-results/distributedTest/1563400137/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-artifacts/1563400137/distributedtestfiles-OpenJDK8-9.9.0-build.0239.tgz
was (Author: eshu):
This is reproduced again in ci.
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
>
txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$167/1387407484.run
in VM 1 running on Host 591d851cdcf8 with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
at
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted(ClientServerTransactionFailoverDistributedTest.java:437)
Caused by:
org.junit.ComparisonFailure: expected:<"TxValue-2"> but was:
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.ClientServerTransactionFailoverDistributedTest.lambda$txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted$bb17a952$7(ClientServerTransactionFailoverDistributedTest.java:440)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-results/distributedTest/1563400137/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0239/test-artifacts/1563400137/distributedtestfiles-OpenJDK8-9.9.0-build.0239.tgz
> ClientServerTransactionFailoverDistributedTest
> txCommitGetsAppliedOnAllTheReplicasAfterHostIsShutDownAndIfOneOfTheNodeHasCommitted
> failed
> -
>
> Key: GEODE-6586
> URL: https://issues.apache.org/jira/browse/GEODE-6586
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: xiaojian zhou
>Assignee: Eric Shu
>Priority: Major
>
> {noformat}
> It's found in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-devel
[jira] [Commented] (GEODE-6298) CI Failure: LRUListWithAsyncSortingTest.scanMovesRecentlyUsedNodeToTail
[
https://issues.apache.org/jira/browse/GEODE-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888152#comment-16888152
]
Eric Shu commented on GEODE-6298:
-
Failed again in ci runs:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/669
> CI Failure: LRUListWithAsyncSortingTest.scanMovesRecentlyUsedNodeToTail
>
>
> Key: GEODE-6298
> URL: https://issues.apache.org/jira/browse/GEODE-6298
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Bruce Schuchardt
>Assignee: Anilkumar Gingade
>Priority: Major
> Labels: CI
>
> Failed in Windows JDK 11 run
> [234|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/234]
> {noformat}
> org.apache.geode.internal.cache.eviction.LRUListWithAsyncSortingTest >
> scanMovesRecentlyUsedNodeToTail FAILED
> org.junit.ComparisonFailure: expected:<[first]> but was:<[third]>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.eviction.LRUListWithAsyncSortingTest.scanMovesRecentlyUsedNodeToTail(LRUListWithAsyncSortingTest.java:231)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (GEODE-6975) When a redundant copy or replica of a distributed region failed to persistent remote member's new persistence id, it should send reply exception back to indicate what ha
[ https://issues.apache.org/jira/browse/GEODE-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-6975. - Resolution: Fixed Fix Version/s: 1.10.0 > When a redundant copy or replica of a distributed region failed to persistent > remote member's new persistence id, it should send reply exception back to > indicate what happened > --- > > Key: GEODE-6975 > URL: https://issues.apache.org/jira/browse/GEODE-6975 > Project: Geode > Issue Type: Bug > Components: persistence, regions >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.10.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Currently, when a persistent bucket or distributed region is created on > member A, member A will send its new PersistentMemberID to other hosts (e.g > member B), so that member B will know and persist A's new ID for the region. > However, when member B is being shut down during processing the > PrepareNewPersistentMemberMessage (did not persist A's id), it just send a > reply message indicate it had persisted. This will cause Member A removes its > old member id and only persists its new member id. This is wrong as the > member A could also been shut down at the same time. There is a race that > member B could be recognized as hosting the last copy for the region. This > will lead to member B to recover first, and member B can only recover member > A's old persistent id. This will lead to Member A not able to restart, as B > does not recognize A's new persistent id. > [error 2018/09/19 01:18:00.972 PDT dataStoregemfire6_host1_6131 thread for bucket _B__partitionedRegion_0> tid=0x77] A DiskAccessException > has occurred while writing to the disk for region > /__PR/_B__partitionedRegion_0. The cache will be closed. > org.apache.geode.cache.persistence.ConflictingPersistentDataException: Region > /__PR/_B__partitionedRegion_0 remote member > rs-FullRegression19041704a3i3large-hydra-client-62(dataStoregemfire1_host1_5862:5862):1025 > with persistent data > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_1_dataStore1_disk_1 > created at timestamp 1537345060760 version 0 diskStoreId > a35a937a082b4066-af019365b6a5114b name null was not part of the same > distributed system as the local data from > /10.32.109.230:/var/vcap/data/rundir/concParRegHAPersistPdxVA57H/concParRegHAPersistPdx-0919-011540/vm_6_dataStore6_disk_1 > created at timestamp 1537344996470 version 0 diskStoreId > 108be5a03966418f-980c1d88e9b26d1d name null > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.checkMyStateOnMembers(PersistenceAdvisorImpl.java:521) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.removeReplicatesIfWeAreEqualToAnyOrElseClearEqualMembers(PersistenceInitialImageAdvisor.java:181) > at > org.apache.geode.internal.cache.persistence.PersistenceInitialImageAdvisor.getAdvice(PersistenceInitialImageAdvisor.java:69) > at > org.apache.geode.internal.cache.persistence.PersistenceAdvisorImpl.getInitialImageAdvice(PersistenceAdvisorImpl.java:831) > at > org.apache.geode.internal.cache.persistence.CreatePersistentRegionProcessor.getInitialImageAdvice(CreatePersistentRegionProcessor.java:52) > at > org.apache.geode.internal.cache.DistributedRegion.getInitialImageAndRecovery(DistributedRegion.java:1200) > at > org.apache.geode.internal.cache.DistributedRegion.initialize(DistributedRegion.java:1081) > at > org.apache.geode.internal.cache.BucketRegion.initialize(BucketRegion.java:258) > at > org.apache.geode.internal.cache.LocalRegion.createSubregion(LocalRegion.java:1014) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.createBucketRegion(PartitionedRegionDataStore.java:779) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabFreeBucket(PartitionedRegionDataStore.java:454) > at > org.apache.geode.internal.cache.PartitionedRegionDataStore.grabBucket(PartitionedRegionDataStore.java:2895) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDisk(ProxyBucketRegion.java:447) > at > org.apache.geode.internal.cache.ProxyBucketRegion.recoverFromDiskRecursively(ProxyBucketRegion.java:390) > at > org.apache.geode.internal.cache.PRHARedundancyProvider$4.run2(PRHARedundancyProvider.java:1756) > at > org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
[jira] [Created] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
Eric Shu created GEODE-7080: --- Summary: EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed Key: GEODE-7080 URL: https://issues.apache.org/jira/browse/GEODE-7080 Project: Geode Issue Type: Bug Components: snapshot Reporter: Eric Shu ExportOfflineSnapshot is aborted if the exception is thrown. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
[ https://issues.apache.org/jira/browse/GEODE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7080: --- Assignee: Eric Shu > EntryDestroyedException can be thrown during exportOfflineSnapshot if a key > was destroyed > - > > Key: GEODE-7080 > URL: https://issues.apache.org/jira/browse/GEODE-7080 > Project: Geode > Issue Type: Bug > Components: snapshot >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > ExportOfflineSnapshot is aborted if the exception is thrown. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
[ https://issues.apache.org/jira/browse/GEODE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7080: Description: ExportOfflineSnapshot is aborted if the exception is thrown. org.apache.geode.cache.EntryDestroyedException at org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.convertToBytes(SnapshotPacket.java:161) at org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.(SnapshotPacket.java:62) at org.apache.geode.internal.cache.DiskStoreImpl$2.writeBatch(DiskStoreImpl.java:3849) at org.apache.geode.internal.cache.ExportDiskRegion.oplogRecovered(ExportDiskRegion.java:67) at org.apache.geode.internal.cache.PersistentOplogSet.recoverOplogs(PersistentOplogSet.java:468) at org.apache.geode.internal.cache.PersistentOplogSet.recoverRegionsThatAreReady(PersistentOplogSet.java:367) at org.apache.geode.internal.cache.DiskStoreImpl.recoverRegionsThatAreReady(DiskStoreImpl.java:2043) at org.apache.geode.internal.cache.DiskStoreImpl.exportSnapshot(DiskStoreImpl.java:3855) at org.apache.geode.internal.cache.DiskStoreImpl.exportOfflineSnapshot(DiskStoreImpl.java:4147) at org.apache.geode.management.internal.cli.commands.ExportOfflineDiskStoreCommand.exportOfflineDiskStore(ExportOfflineDiskStoreCommand.java:53) was:ExportOfflineSnapshot is aborted if the exception is thrown. > EntryDestroyedException can be thrown during exportOfflineSnapshot if a key > was destroyed > - > > Key: GEODE-7080 > URL: https://issues.apache.org/jira/browse/GEODE-7080 > Project: Geode > Issue Type: Bug > Components: snapshot >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > ExportOfflineSnapshot is aborted if the exception is thrown. > org.apache.geode.cache.EntryDestroyedException > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.convertToBytes(SnapshotPacket.java:161) > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.(SnapshotPacket.java:62) > at > org.apache.geode.internal.cache.DiskStoreImpl$2.writeBatch(DiskStoreImpl.java:3849) > at > org.apache.geode.internal.cache.ExportDiskRegion.oplogRecovered(ExportDiskRegion.java:67) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverOplogs(PersistentOplogSet.java:468) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverRegionsThatAreReady(PersistentOplogSet.java:367) > at > org.apache.geode.internal.cache.DiskStoreImpl.recoverRegionsThatAreReady(DiskStoreImpl.java:2043) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportSnapshot(DiskStoreImpl.java:3855) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportOfflineSnapshot(DiskStoreImpl.java:4147) > at > org.apache.geode.management.internal.cli.commands.ExportOfflineDiskStoreCommand.exportOfflineDiskStore(ExportOfflineDiskStoreCommand.java:53) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
[ https://issues.apache.org/jira/browse/GEODE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7080: Affects Version/s: 1.1.0 > EntryDestroyedException can be thrown during exportOfflineSnapshot if a key > was destroyed > - > > Key: GEODE-7080 > URL: https://issues.apache.org/jira/browse/GEODE-7080 > Project: Geode > Issue Type: Bug > Components: snapshot >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > ExportOfflineSnapshot is aborted if the exception is thrown. > org.apache.geode.cache.EntryDestroyedException > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.convertToBytes(SnapshotPacket.java:161) > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.(SnapshotPacket.java:62) > at > org.apache.geode.internal.cache.DiskStoreImpl$2.writeBatch(DiskStoreImpl.java:3849) > at > org.apache.geode.internal.cache.ExportDiskRegion.oplogRecovered(ExportDiskRegion.java:67) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverOplogs(PersistentOplogSet.java:468) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverRegionsThatAreReady(PersistentOplogSet.java:367) > at > org.apache.geode.internal.cache.DiskStoreImpl.recoverRegionsThatAreReady(DiskStoreImpl.java:2043) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportSnapshot(DiskStoreImpl.java:3855) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportOfflineSnapshot(DiskStoreImpl.java:4147) > at > org.apache.geode.management.internal.cli.commands.ExportOfflineDiskStoreCommand.exportOfflineDiskStore(ExportOfflineDiskStoreCommand.java:53) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
[ https://issues.apache.org/jira/browse/GEODE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-7080. - Resolution: Fixed Fix Version/s: 1.11.0 > EntryDestroyedException can be thrown during exportOfflineSnapshot if a key > was destroyed > - > > Key: GEODE-7080 > URL: https://issues.apache.org/jira/browse/GEODE-7080 > Project: Geode > Issue Type: Bug > Components: snapshot >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.11.0 > > Time Spent: 1h > Remaining Estimate: 0h > > ExportOfflineSnapshot is aborted if the exception is thrown. > org.apache.geode.cache.EntryDestroyedException > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.convertToBytes(SnapshotPacket.java:161) > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.(SnapshotPacket.java:62) > at > org.apache.geode.internal.cache.DiskStoreImpl$2.writeBatch(DiskStoreImpl.java:3849) > at > org.apache.geode.internal.cache.ExportDiskRegion.oplogRecovered(ExportDiskRegion.java:67) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverOplogs(PersistentOplogSet.java:468) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverRegionsThatAreReady(PersistentOplogSet.java:367) > at > org.apache.geode.internal.cache.DiskStoreImpl.recoverRegionsThatAreReady(DiskStoreImpl.java:2043) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportSnapshot(DiskStoreImpl.java:3855) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportOfflineSnapshot(DiskStoreImpl.java:4147) > at > org.apache.geode.management.internal.cli.commands.ExportOfflineDiskStoreCommand.exportOfflineDiskStore(ExportOfflineDiskStoreCommand.java:53) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (GEODE-7084) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects has suspect string
Eric Shu created GEODE-7084: --- Summary: CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects has suspect string Key: GEODE-7084 URL: https://issues.apache.org/jira/browse/GEODE-7084 Project: Geode Issue Type: Bug Reporter: Eric Shu org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > serverRestartsAfterLocatorReconnects 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 log4j at line 3039 [error 2019/08/13 22:16:12.668 GMT tid=308] Received invalid result from 172.17.0.5(locator-0:1808:locator):41001: null =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0028/test-results/distributedTest/1565735940/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0028/test-artifacts/1565735940/distributedtestfiles-OpenJDK8-9.10.0-build.0028.tgz -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (GEODE-7084) CI Failure: ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects has suspect string
[ https://issues.apache.org/jira/browse/GEODE-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7084: --- Assignee: Jinmei Liao > CI Failure: > ClusterConfigLocatorRestartDUnitTest.serverRestartsAfterLocatorReconnects has > suspect string > > > Key: GEODE-7084 > URL: https://issues.apache.org/jira/browse/GEODE-7084 > Project: Geode > Issue Type: Bug >Reporter: Eric Shu >Assignee: Jinmei Liao >Priority: Major > > org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest > > serverRestartsAfterLocatorReconnects 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 log4j at line 3039 > [error 2019/08/13 22:16:12.668 GMT tid=308] Received > invalid result from 172.17.0.5(locator-0:1808:locator):41001: null > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0028/test-results/distributedTest/1565735940/ > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0028/test-artifacts/1565735940/distributedtestfiles-OpenJDK8-9.10.0-build.0028.tgz -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-6613:
Labels: GeodeCommons flaky (was: flaky)
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> is flaky
> -
>
> Key: GEODE-6613
> URL: https://issues.apache.org/jira/browse/GEODE-6613
> Project: Geode
> Issue Type: Bug
> Components: client/server, transactions
>Reporter: Darrel Schneider
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
>
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> has recently started failing once in a while.
> This may have been caused by: GEODE-6515
> When it fails it us because at least one of the transactions changes do not
> happen. Here is an example of how it fails:
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> Â >Â
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperationsÂ
> FAILED
> org.apache.geode.test.dunit.RMIException: While invokingÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$144/1667766308.run
>  in VM 3 running on Host 671fd56a424e with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations(ClientServerTransactionFailoverDistributedTest.java:294)
> Caused by:
> org.junit.ComparisonFailure:Â expected:<[value1]>Â butÂ
> was:<[originalValue]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverDistributedTest.java:222)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.lambda$multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations$2967fbd$1(ClientServerTransactionFailoverDistributedTest.java:294){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (GEODE-7087) IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging
[ https://issues.apache.org/jira/browse/GEODE-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7087: --- Assignee: Eric Shu > IllegalMonitorStateException: attempt to unlock read lock, not locked by > current thread is shown in debug logging > - > > Key: GEODE-7087 > URL: https://issues.apache.org/jira/browse/GEODE-7087 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > GotBucketLocks flag is never being reset after lock is released cause the > following debug logging. However. it does not affect the correctness of the > transaction layer. > [vm3] [debug 2019/08/14 05:14:37.163 PDT Thread 13> tid=0x5464] Exception while unlocking bucket region > /_PR/_BClientServerTransactionFailoverDistributedTestmultipleClientLongTransactionsCanFailoverWithoutLosingOperations_region_0 > this is probably because the bucket was destroyed and never locked initially. > [vm3] java.lang.IllegalMonitorStateException: attempt to unlock read lock, > not locked by current thread > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428) > [vm3] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881) > [vm3] at > org.apache.geode.internal.cache.BucketRegion.doUnlockForPrimary(BucketRegion.java:862) > [vm3] at org.apache.geode.internal.cache.TXState.doCleanup(TXState.java:913) > [vm3] at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:880) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.cleanupTransactionIfNoLongerHost(TXManagerImpl.java:1069) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.unmasquerade(TXManagerImpl.java:1055) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:180) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212) > [vm3] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm3] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:673) > [vm3] at > org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121) > [vm3] at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (GEODE-7087) IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging
Eric Shu created GEODE-7087: --- Summary: IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging Key: GEODE-7087 URL: https://issues.apache.org/jira/browse/GEODE-7087 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu GotBucketLocks flag is never being reset after lock is released cause the following debug logging. However. it does not affect the correctness of the transaction layer. [vm3] [debug 2019/08/14 05:14:37.163 PDT tid=0x5464] Exception while unlocking bucket region /_PR/_BClientServerTransactionFailoverDistributedTestmultipleClientLongTransactionsCanFailoverWithoutLosingOperations_region_0 this is probably because the bucket was destroyed and never locked initially. [vm3] java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444) [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428) [vm3] at java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341) [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881) [vm3] at org.apache.geode.internal.cache.BucketRegion.doUnlockForPrimary(BucketRegion.java:862) [vm3] at org.apache.geode.internal.cache.TXState.doCleanup(TXState.java:913) [vm3] at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:880) [vm3] at org.apache.geode.internal.cache.TXManagerImpl.cleanupTransactionIfNoLongerHost(TXManagerImpl.java:1069) [vm3] at org.apache.geode.internal.cache.TXManagerImpl.unmasquerade(TXManagerImpl.java:1055) [vm3] at org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:180) [vm3] at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848) [vm3] at org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72) [vm3] at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212) [vm3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [vm3] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [vm3] at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:673) [vm3] at org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121) [vm3] at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908460#comment-16908460
]
Eric Shu commented on GEODE-6613:
-
This is caused by transaction expired due to resource issue -- (in-between op
is longer than the 4 seconds set in the test).
[vm0] [info 2019/08/08 18:40:54.053 GMT
tid=0x20] Received method:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877.run
with 0 args on object:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877@6f4ed7f2
[vm0] [warn 2019/08/08 18:40:54.055 GMT
tid=0x20] ClientHealthMonitor: Unregistering client with member id
identity(172.17.0.5(1:loner):40276:5da48872,connection=1 due to: Unknown reason
[vm0] [info 2019/08/08 18:40:54.057 GMT
tid=0x20] Got result: null
[vm0] from
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877.run
with 0 args on object:
org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$208/2063800877@6f4ed7f2
(took 2 ms)
[warn 2019/08/08 18:40:59.398 GMT tid=0x48] Statistics sampling
thread detected a wakeup delay of 3375 ms, indicating a possible resource
issue. Check the GC, memory, and CPU statistics.
[vm1] [warn 2019/08/08 18:40:59.412 GMT tid=0x45] Statistics
sampling thread detected a wakeup delay of 3679 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm3] [warn 2019/08/08 18:40:59.031 GMT tid=0x40] Statistics
sampling thread detected a wakeup delay of 3318 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm2] [warn 2019/08/08 18:40:59.556 GMT tid=0x49] Statistics
sampling thread detected a wakeup delay of 3819 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[locator] [warn 2019/08/08 18:40:59.267 GMT tid=0x3a] Statistics
sampling thread detected a wakeup delay of 3713 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[vm0] [warn 2019/08/08 18:40:59.636 GMT tid=0x42] Statistics
sampling thread detected a wakeup delay of 4003 ms, indicating a possible
resource issue. Check the GC, memory, and CPU statistics.
[warn 2019/08/08 18:40:59.978 GMT tid=0x64] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
[warn 2019/08/08 18:40:59.984 GMT tid=0x69] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
[warn 2019/08/08 18:40:59.988 GMT tid=0x62] Pool unexpected closed
socket on server connection=Pooled Connection to 8227e70436f0:41843:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> is flaky
> -
>
> Key: GEODE-6613
> URL: https://issues.apache.org/jira/browse/GEODE-6613
> Project: Geode
> Issue Type: Bug
> Components: client/server, transactions
>Reporter: Darrel Schneider
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
>
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> has recently started failing once in a while.
> This may have been caused by: GEODE-6515
> When it fails it us because at least one of the transactions changes do not
> happen. Here is an example of how it fails:
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> Â >Â
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperationsÂ
> FAILED
> org.apache.geode.test.dunit.RMIException: While invokingÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$144/1667766308.run
>  in VM 3 running on Host 671fd56a424e with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations(ClientServerTransactionFailoverDistributedTest.java:294)
> Caused by:
> org.junit.ComparisonFailure:Â expected:<[value1]>Â butÂ
> was:<[originalValue]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> Â
[jira] [Updated] (GEODE-7087) IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging
[ https://issues.apache.org/jira/browse/GEODE-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7087: Labels: GeodeCommons (was: ) > IllegalMonitorStateException: attempt to unlock read lock, not locked by > current thread is shown in debug logging > - > > Key: GEODE-7087 > URL: https://issues.apache.org/jira/browse/GEODE-7087 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Time Spent: 10m > Remaining Estimate: 0h > > GotBucketLocks flag is never being reset after lock is released cause the > following debug logging. However. it does not affect the correctness of the > transaction layer. > [vm3] [debug 2019/08/14 05:14:37.163 PDT Thread 13> tid=0x5464] Exception while unlocking bucket region > /_PR/_BClientServerTransactionFailoverDistributedTestmultipleClientLongTransactionsCanFailoverWithoutLosingOperations_region_0 > this is probably because the bucket was destroyed and never locked initially. > [vm3] java.lang.IllegalMonitorStateException: attempt to unlock read lock, > not locked by current thread > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428) > [vm3] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881) > [vm3] at > org.apache.geode.internal.cache.BucketRegion.doUnlockForPrimary(BucketRegion.java:862) > [vm3] at org.apache.geode.internal.cache.TXState.doCleanup(TXState.java:913) > [vm3] at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:880) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.cleanupTransactionIfNoLongerHost(TXManagerImpl.java:1069) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.unmasquerade(TXManagerImpl.java:1055) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:180) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212) > [vm3] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm3] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:673) > [vm3] at > org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121) > [vm3] at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-6613) ClientServerTransactionFailoverDistributedTest multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations is flaky
[
https://issues.apache.org/jira/browse/GEODE-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-6613.
-
Resolution: Fixed
Fix Version/s: 1.11.0
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> is flaky
> -
>
> Key: GEODE-6613
> URL: https://issues.apache.org/jira/browse/GEODE-6613
> Project: Geode
> Issue Type: Bug
> Components: client/server, transactions
>Reporter: Darrel Schneider
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeCommons, flaky
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ClientServerTransactionFailoverDistributedTest
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations
> has recently started failing once in a while.
> This may have been caused by: GEODE-6515
> When it fails it us because at least one of the transactions changes do not
> happen. Here is an example of how it fails:
> {noformat}
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest
> Â >Â
> multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperationsÂ
> FAILED
> org.apache.geode.test.dunit.RMIException: While invokingÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest$$Lambda$144/1667766308.run
>  in VM 3 running on Host 671fd56a424e with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations(ClientServerTransactionFailoverDistributedTest.java:294)
> Caused by:
> org.junit.ComparisonFailure:Â expected:<[value1]>Â butÂ
> was:<[originalValue]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverDistributedTest.java:222)
> atÂ
> org.apache.geode.internal.cache.ClientServerTransactionFailoverDistributedTest.lambda$multipleClientLongTransactionsCanFailoverMultipleTimesWithoutLosingOperations$2967fbd$1(ClientServerTransactionFailoverDistributedTest.java:294){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (GEODE-7080) EntryDestroyedException can be thrown during exportOfflineSnapshot if a key was destroyed
[ https://issues.apache.org/jira/browse/GEODE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7080: Fix Version/s: (was: 1.11.0) 1.10.0 > EntryDestroyedException can be thrown during exportOfflineSnapshot if a key > was destroyed > - > > Key: GEODE-7080 > URL: https://issues.apache.org/jira/browse/GEODE-7080 > Project: Geode > Issue Type: Bug > Components: snapshot >Affects Versions: 1.1.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h > Remaining Estimate: 0h > > ExportOfflineSnapshot is aborted if the exception is thrown. > org.apache.geode.cache.EntryDestroyedException > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.convertToBytes(SnapshotPacket.java:161) > at > org.apache.geode.internal.cache.snapshot.SnapshotPacket$SnapshotRecord.(SnapshotPacket.java:62) > at > org.apache.geode.internal.cache.DiskStoreImpl$2.writeBatch(DiskStoreImpl.java:3849) > at > org.apache.geode.internal.cache.ExportDiskRegion.oplogRecovered(ExportDiskRegion.java:67) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverOplogs(PersistentOplogSet.java:468) > at > org.apache.geode.internal.cache.PersistentOplogSet.recoverRegionsThatAreReady(PersistentOplogSet.java:367) > at > org.apache.geode.internal.cache.DiskStoreImpl.recoverRegionsThatAreReady(DiskStoreImpl.java:2043) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportSnapshot(DiskStoreImpl.java:3855) > at > org.apache.geode.internal.cache.DiskStoreImpl.exportOfflineSnapshot(DiskStoreImpl.java:4147) > at > org.apache.geode.management.internal.cli.commands.ExportOfflineDiskStoreCommand.exportOfflineDiskStore(ExportOfflineDiskStoreCommand.java:53) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (GEODE-7087) IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging
[ https://issues.apache.org/jira/browse/GEODE-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-7087. - Fix Version/s: 1.11.0 Resolution: Fixed > IllegalMonitorStateException: attempt to unlock read lock, not locked by > current thread is shown in debug logging > - > > Key: GEODE-7087 > URL: https://issues.apache.org/jira/browse/GEODE-7087 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > GotBucketLocks flag is never being reset after lock is released cause the > following debug logging. However. it does not affect the correctness of the > transaction layer. > [vm3] [debug 2019/08/14 05:14:37.163 PDT Thread 13> tid=0x5464] Exception while unlocking bucket region > /_PR/_BClientServerTransactionFailoverDistributedTestmultipleClientLongTransactionsCanFailoverWithoutLosingOperations_region_0 > this is probably because the bucket was destroyed and never locked initially. > [vm3] java.lang.IllegalMonitorStateException: attempt to unlock read lock, > not locked by current thread > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428) > [vm3] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341) > [vm3] at > java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881) > [vm3] at > org.apache.geode.internal.cache.BucketRegion.doUnlockForPrimary(BucketRegion.java:862) > [vm3] at org.apache.geode.internal.cache.TXState.doCleanup(TXState.java:913) > [vm3] at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:880) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.cleanupTransactionIfNoLongerHost(TXManagerImpl.java:1069) > [vm3] at > org.apache.geode.internal.cache.TXManagerImpl.unmasquerade(TXManagerImpl.java:1055) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:180) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212) > [vm3] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm3] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm3] at > org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:673) > [vm3] at > org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121) > [vm3] at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7112) CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky
Eric Shu created GEODE-7112: --- Summary: CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky Key: GEODE-7112 URL: https://issues.apache.org/jira/browse/GEODE-7112 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu This test is flaky, as test may be timed out later than expected due to resources constraints during the test run. [vm0] [info 2019/08/21 00:11:05.805 GMT tid=0x4f] Received method: org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run with 0 args on object: org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 [vm0] [warn 2019/08/21 00:11:11.536 GMT tid=0x3d] Statistics sampling thread detected a wakeup delay of 3487 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. [vm0] [info 2019/08/21 00:11:11.677 GMT tid=0x3e] Transaction org.apache.geode.internal.jta.GlobalTransaction@5c6195b9 has timed out. [locator] [warn 2019/08/21 00:11:11.851 GMT tid=0x3c] Statistics sampling thread detected a wakeup delay of 3293 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. [vm0] [info 2019/08/21 00:11:12.134 GMT tid=0x22] Got result: null [vm0] from org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440.run with 0 args on object: org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440@36607038 (took 6330 ms) [info 2019/08/21 00:11:12.354 GMT tid=0x1b] Thread Thread[run invoked on an instance of org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$157/0x00084023ac40,5,] took 6404 ms to exit. [vm0] [info 2019/08/21 00:11:12.464 GMT tid=0x4f] Got result: EXCEPTION_OCCURRED [vm0] java.lang.AssertionError: Exception did not occur although was supposed to occur [vm0] at org.junit.Assert.fail(Assert.java:88) [vm0] at org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.runTest1(TxnTimeOutDUnitTest.java:216) [vm0] at org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.lambda$testLoginTimeOut$61fe3738$1(TxnTimeOutDUnitTest.java:186) [vm0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm0] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) [vm0] at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) [vm0] at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) [vm0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm0] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm0] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) [vm0] at java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) [vm0] at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) [vm0] at java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) [vm0] at java.base/java.security.AccessController.doPrivileged(Native Method) [vm0] at java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) [vm0] at java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) [vm0] at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) [vm0] at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) [vm0] at java.base/java.security.AccessController.doPrivileged(Native Method) [vm0] at java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) [vm0] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [vm0] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [vm0] at java.base/java.lang.Thread.run(Thread.java:834) [vm0] from org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run with 0 args on object: org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 (took 6657 ms) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (GEODE-7112) CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky
[ https://issues.apache.org/jira/browse/GEODE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7112: --- Assignee: Eric Shu > CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky > - > > Key: GEODE-7112 > URL: https://issues.apache.org/jira/browse/GEODE-7112 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:11:05.805 GMT > tid=0x4f] Received method: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 > [vm0] [warn 2019/08/21 00:11:11.536 GMT tid=0x3d] Statistics > sampling thread detected a wakeup delay of 3487 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:11.677 GMT tid=0x3e] > Transaction org.apache.geode.internal.jta.GlobalTransaction@5c6195b9 has > timed out. > [locator] [warn 2019/08/21 00:11:11.851 GMT tid=0x3c] > Statistics sampling thread detected a wakeup delay of 3293 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:12.134 GMT > tid=0x22] Got result: null > [vm0] from > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440@36607038 > (took 6330 ms) > [info 2019/08/21 00:11:12.354 GMT tid=0x1b] Thread Thread[run > invoked on an instance of > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$157/0x00084023ac40,5,] > took 6404 ms to exit. > [vm0] [info 2019/08/21 00:11:12.464 GMT > tid=0x4f] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: Exception did not occur although was supposed > to occur > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.runTest1(TxnTimeOutDUnitTest.java:216) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.lambda$testLoginTimeOut$61fe3738$1(TxnTimeOutDUnitTest.java:186) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > [vm0] at java.base/java.lang.Thread.run(Thread.java:834) > [vm0] fr
[jira] [Updated] (GEODE-7112) CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky
[ https://issues.apache.org/jira/browse/GEODE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7112: Affects Version/s: 1.11.0 > CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky > - > > Key: GEODE-7112 > URL: https://issues.apache.org/jira/browse/GEODE-7112 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:11:05.805 GMT > tid=0x4f] Received method: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 > [vm0] [warn 2019/08/21 00:11:11.536 GMT tid=0x3d] Statistics > sampling thread detected a wakeup delay of 3487 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:11.677 GMT tid=0x3e] > Transaction org.apache.geode.internal.jta.GlobalTransaction@5c6195b9 has > timed out. > [locator] [warn 2019/08/21 00:11:11.851 GMT tid=0x3c] > Statistics sampling thread detected a wakeup delay of 3293 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:12.134 GMT > tid=0x22] Got result: null > [vm0] from > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440@36607038 > (took 6330 ms) > [info 2019/08/21 00:11:12.354 GMT tid=0x1b] Thread Thread[run > invoked on an instance of > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$157/0x00084023ac40,5,] > took 6404 ms to exit. > [vm0] [info 2019/08/21 00:11:12.464 GMT > tid=0x4f] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: Exception did not occur although was supposed > to occur > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.runTest1(TxnTimeOutDUnitTest.java:216) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.lambda$testLoginTimeOut$61fe3738$1(TxnTimeOutDUnitTest.java:186) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > [vm0]
[jira] [Updated] (GEODE-7112) CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky
[ https://issues.apache.org/jira/browse/GEODE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7112: Labels: GeodeCommons (was: ) > CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky > - > > Key: GEODE-7112 > URL: https://issues.apache.org/jira/browse/GEODE-7112 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:11:05.805 GMT > tid=0x4f] Received method: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 > [vm0] [warn 2019/08/21 00:11:11.536 GMT tid=0x3d] Statistics > sampling thread detected a wakeup delay of 3487 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:11.677 GMT tid=0x3e] > Transaction org.apache.geode.internal.jta.GlobalTransaction@5c6195b9 has > timed out. > [locator] [warn 2019/08/21 00:11:11.851 GMT tid=0x3c] > Statistics sampling thread detected a wakeup delay of 3293 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:12.134 GMT > tid=0x22] Got result: null > [vm0] from > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440@36607038 > (took 6330 ms) > [info 2019/08/21 00:11:12.354 GMT tid=0x1b] Thread Thread[run > invoked on an instance of > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$157/0x00084023ac40,5,] > took 6404 ms to exit. > [vm0] [info 2019/08/21 00:11:12.464 GMT > tid=0x4f] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: Exception did not occur although was supposed > to occur > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.runTest1(TxnTimeOutDUnitTest.java:216) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.lambda$testLoginTimeOut$61fe3738$1(TxnTimeOutDUnitTest.java:186) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > [vm0] at java.base/java.lang
[jira] [Assigned] (GEODE-7114) CI failure: TransactionTimeOutDUnitTest.test4 is flaky
[ https://issues.apache.org/jira/browse/GEODE-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7114: --- Assignee: Eric Shu > CI failure: TransactionTimeOutDUnitTest.test4 is flaky > -- > > Key: GEODE-7114 > URL: https://issues.apache.org/jira/browse/GEODE-7114 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:24:49.917 GMT tid=0xcc] > Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has > timed out. > [vm0] [warn 2019/08/21 00:24:49.752 GMT tid=0xca] Statistics > sampling thread detected a wakeup delay of 3895 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:24:50.818 GMT > tid=0x20] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166) > [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) > [vm0] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm0] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm0] at java.lang.Thread.run(Thread.java:748) > [vm0] from > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee > (took 7958 ms) > [locator] [warn 2019/08/21 00:24:50.140 GMT tid=0x3a] > Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7114) CI failure: TransactionTimeOutDUnitTest.test4 is flaky
Eric Shu created GEODE-7114: --- Summary: CI failure: TransactionTimeOutDUnitTest.test4 is flaky Key: GEODE-7114 URL: https://issues.apache.org/jira/browse/GEODE-7114 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu This test is flaky, as test may be timed out later than expected due to resources constraints during the test run. [vm0] [info 2019/08/21 00:24:49.917 GMT tid=0xcc] Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has timed out. [vm0] [warn 2019/08/21 00:24:49.752 GMT tid=0xca] Statistics sampling thread detected a wakeup delay of 3895 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. [vm0] [info 2019/08/21 00:24:50.818 GMT tid=0x20] Got result: EXCEPTION_OCCURRED [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction [vm0] at org.junit.Assert.fail(Assert.java:88) [vm0] at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312) [vm0] at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.lang.reflect.Method.invoke(Method.java:498) [vm0] at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) [vm0] at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [vm0] at java.lang.reflect.Method.invoke(Method.java:498) [vm0] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) [vm0] at java.security.AccessController.doPrivileged(Native Method) [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) [vm0] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) [vm0] at java.security.AccessController.doPrivileged(Native Method) [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) [vm0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [vm0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [vm0] at java.lang.Thread.run(Thread.java:748) [vm0] from org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run with 0 args on object: org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee (took 7958 ms) [locator] [warn 2019/08/21 00:24:50.140 GMT tid=0x3a] Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7114) CI failure: TransactionTimeOutDUnitTest.test4 is flaky
[ https://issues.apache.org/jira/browse/GEODE-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7114: Affects Version/s: 1.11.0 > CI failure: TransactionTimeOutDUnitTest.test4 is flaky > -- > > Key: GEODE-7114 > URL: https://issues.apache.org/jira/browse/GEODE-7114 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:24:49.917 GMT tid=0xcc] > Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has > timed out. > [vm0] [warn 2019/08/21 00:24:49.752 GMT tid=0xca] Statistics > sampling thread detected a wakeup delay of 3895 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:24:50.818 GMT > tid=0x20] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166) > [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) > [vm0] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm0] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm0] at java.lang.Thread.run(Thread.java:748) > [vm0] from > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee > (took 7958 ms) > [locator] [warn 2019/08/21 00:24:50.140 GMT tid=0x3a] > Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GEODE-7112) CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky
[ https://issues.apache.org/jira/browse/GEODE-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-7112. - Fix Version/s: 1.11.0 Resolution: Fixed > CI failure: TxnTimeOutDUnitTest.testLoginTimeOut is flaky > - > > Key: GEODE-7112 > URL: https://issues.apache.org/jira/browse/GEODE-7112 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.11.0 > > Time Spent: 50m > Remaining Estimate: 0h > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:11:05.805 GMT > tid=0x4f] Received method: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$329/0x000840585840@53dab2f9 > [vm0] [warn 2019/08/21 00:11:11.536 GMT tid=0x3d] Statistics > sampling thread detected a wakeup delay of 3487 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:11.677 GMT tid=0x3e] > Transaction org.apache.geode.internal.jta.GlobalTransaction@5c6195b9 has > timed out. > [locator] [warn 2019/08/21 00:11:11.851 GMT tid=0x3c] > Statistics sampling thread detected a wakeup delay of 3293 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:11:12.134 GMT > tid=0x22] Got result: null > [vm0] from > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$328/0x000840586440@36607038 > (took 6330 ms) > [info 2019/08/21 00:11:12.354 GMT tid=0x1b] Thread Thread[run > invoked on an instance of > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest$$Lambda$157/0x00084023ac40,5,] > took 6404 ms to exit. > [vm0] [info 2019/08/21 00:11:12.464 GMT > tid=0x4f] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: Exception did not occur although was supposed > to occur > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.runTest1(TxnTimeOutDUnitTest.java:216) > [vm0] at > org.apache.geode.internal.jta.dunit.TxnTimeOutDUnitTest.lambda$testLoginTimeOut$61fe3738$1(TxnTimeOutDUnitTest.java:186) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.base/java.lang.reflect.Method.invoke(Method.java:566) > [vm0] at > java.rmi/sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at > java.rmi/sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677) > [vm0] at java.base/java.security.AccessController.doPrivileged(Native > Method) > [vm0] at > java.rmi/sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:676) > [vm0] at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > [vm0]
[jira] [Created] (GEODE-7130) Expired global transaction was not correctly cleaned up
Eric Shu created GEODE-7130: --- Summary: Expired global transaction was not correctly cleaned up Key: GEODE-7130 URL: https://issues.apache.org/jira/browse/GEODE-7130 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu When trying to fix GEODE-7114, I discovered that the global transaction timed out was not correctly cleaned up and leave the transaction in an uncommitted state state and could block other transactions. org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run in VM 0 running on Host localhost with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) 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.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.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) Caused by: java.lang.AssertionError: Exception occurred in test Commit due to at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) 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:69) 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 su
[jira] [Assigned] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7130: --- Assignee: Eric Shu > Expired global transaction was not correctly cleaned up > --- > > Key: GEODE-7130 > URL: https://issues.apache.org/jira/browse/GEODE-7130 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > When trying to fix GEODE-7114, I discovered that the global transaction timed > out was not correctly cleaned up and leave the transaction in an uncommitted > state state and could block other transactions. > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run > in VM 0 running on Host localhost with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) > 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.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.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.AssertionError: Exception occurred in test Commit due to > at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) > 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:69) > 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(Tr
[jira] [Updated] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7130: Labels: GeodeCommons (was: ) > Expired global transaction was not correctly cleaned up > --- > > Key: GEODE-7130 > URL: https://issues.apache.org/jira/browse/GEODE-7130 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > When trying to fix GEODE-7114, I discovered that the global transaction timed > out was not correctly cleaned up and leave the transaction in an uncommitted > state state and could block other transactions. > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run > in VM 0 running on Host localhost with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) > 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.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.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.AssertionError: Exception occurred in test Commit due to > at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) > 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:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) >
[jira] [Updated] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7130: Description: When trying to fix GEODE-7114, I discovered that the global transaction timed out was not correctly cleaned up and leave the transaction in an uncommitted state state and could block other transactions. The following exception is thrown if you repeatedly running the same test (test7()) -- this is because the first transaction not rolled back when timed out. org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run in VM 0 running on Host localhost with 4 VMs at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) at org.apache.geode.test.dunit.VM.invoke(VM.java:406) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) 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.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.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) Caused by: java.lang.AssertionError: Exception occurred in test Commit due to at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) 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:69) 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.
[jira] [Resolved] (GEODE-7130) Expired global transaction was not correctly cleaned up
[ https://issues.apache.org/jira/browse/GEODE-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu resolved GEODE-7130. - Fix Version/s: 1.11.0 Resolution: Fixed > Expired global transaction was not correctly cleaned up > --- > > Key: GEODE-7130 > URL: https://issues.apache.org/jira/browse/GEODE-7130 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When trying to fix GEODE-7114, I discovered that the global transaction timed > out was not correctly cleaned up and leave the transaction in an uncommitted > state state and could block other transactions. > The following exception is thrown if you repeatedly running the same test > (test7()) -- this is because the first transaction not rolled back when timed > out. > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$28/199449817.run > in VM 0 running on Host localhost with 4 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.test7(TransactionTimeOutDUnitTest.java:187) > 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.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.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:54) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.AssertionError: Exception occurred in test Commit due to > at org.apache.geode.test.dunit.Assert.fail(Assert.java:66) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest9(TransactionTimeOutDUnitTest.java:406) > at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test7$bb17a952$1(TransactionTimeOutDUnitTest.java:187) > 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:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMetho
[jira] [Assigned] (GEODE-7138) CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer
[ https://issues.apache.org/jira/browse/GEODE-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-7138: --- Assignee: Eric Shu > CI failure: > ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer > -- > > Key: GEODE-7138 > URL: https://issues.apache.org/jira/browse/GEODE-7138 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Assignee: Eric Shu >Priority: Major > > DistributedTestOpenJDK8 #1035 > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest$$Lambda$47/1742885319.run > in VM 0 running on Host 13889d5ebaf9 with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > that uses org.apache.geode.cache.Region, org.apache.geode.cache.Regionint > expected:<[144]> but was:<[37]> within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer$2967fbd$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.junit.ComparisonFailure: expected:<[144]> but was:<[37]> > at > sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$verifyTransactionResult$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7138) CI failure: ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer
[ https://issues.apache.org/jira/browse/GEODE-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7138: Labels: GeodeCommons (was: ) > CI failure: > ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer > -- > > Key: GEODE-7138 > URL: https://issues.apache.org/jira/browse/GEODE-7138 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Anilkumar Gingade >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > > DistributedTestOpenJDK8 #1035 > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > > clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest$$Lambda$47/1742885319.run > in VM 0 running on Host 13889d5ebaf9 with 6 VMs > at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579) > at org.apache.geode.test.dunit.VM.invoke(VM.java:406) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest > that uses org.apache.geode.cache.Region, org.apache.geode.cache.Regionint > expected:<[144]> but was:<[37]> within 300 seconds. > at > org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122) > at > org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32) > at > org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902) > at > org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.verifyTransactionResult(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$clientTransactionOperationsAreNotLostIfTransactionIsOnRolledServer$2967fbd$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:137) > Caused by: > org.junit.ComparisonFailure: expected:<[144]> but was:<[37]> > at > sun.reflect.GeneratedConstructorAccessor38.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.internal.cache.ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.lambda$verifyTransactionResult$2(ClientServerTransactionFailoverWithMixedVersionServersDistributedTest.java:361) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (GEODE-7114) CI failure: TransactionTimeOutDUnitTest.test4 is flaky
[ https://issues.apache.org/jira/browse/GEODE-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-7114: Labels: GeodeCommons (was: ) > CI failure: TransactionTimeOutDUnitTest.test4 is flaky > -- > > Key: GEODE-7114 > URL: https://issues.apache.org/jira/browse/GEODE-7114 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.11.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: GeodeCommons > Time Spent: 20m > Remaining Estimate: 0h > > This test is flaky, as test may be timed out later than expected due to > resources constraints during the test run. > [vm0] [info 2019/08/21 00:24:49.917 GMT tid=0xcc] > Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has > timed out. > [vm0] [warn 2019/08/21 00:24:49.752 GMT tid=0xca] Statistics > sampling thread detected a wakeup delay of 3895 ms, indicating a possible > resource issue. Check the GC, memory, and CPU statistics. > [vm0] [info 2019/08/21 00:24:50.818 GMT > tid=0x20] Got result: EXCEPTION_OCCURRED > [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction > [vm0] at org.junit.Assert.fail(Assert.java:88) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312) > [vm0] at > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166) > [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [vm0] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123) > [vm0] at > org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69) > [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) > [vm0] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [vm0] at java.lang.reflect.Method.invoke(Method.java:498) > [vm0] at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200) > [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196) > [vm0] at > sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688) > [vm0] at java.security.AccessController.doPrivileged(Native Method) > [vm0] at > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687) > [vm0] at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [vm0] at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [vm0] at java.lang.Thread.run(Thread.java:748) > [vm0] from > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run > with 0 args on object: > org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee > (took 7958 ms) > [locator] [warn 2019/08/21 00:24:50.140 GMT tid=0x3a] > Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a > possible resource issue. Check the GC, memory, and CPU statistics. -- This message was sent by Atlassian Jira (v8.3.2#803003)
