[jira] [Commented] (GEODE-5619) Change scanning for XSDRootElement to consider all packages on the classpath
[ https://issues.apache.org/jira/browse/GEODE-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590463#comment-16590463 ] ASF subversion and git services commented on GEODE-5619: Commit 966852dd0f7e8f0d097c0776adcdaca9c4fa891c in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=966852d ] GEODE-5619: Change scanning for XSDRootElement to consider all packag… (#2361) > Change scanning for XSDRootElement to consider all packages on the classpath > > > Key: GEODE-5619 > URL: https://issues.apache.org/jira/browse/GEODE-5619 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > This used to be the case but switched to "org.apache.geode" with the > classpath scanner upgrade to 4.0.6 (possibly because of memory issues). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5623) SUPERFLAKY: StopLocatorCommandDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5623:
-
Labels: swat (was: )
> SUPERFLAKY: StopLocatorCommandDUnitTest
> ---
>
> Key: GEODE-5623
> URL: https://issues.apache.org/jira/browse/GEODE-5623
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed recently in CI, and it failed multiple times in the a 300
> run batch of DistributedTest
> Most recent failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/281
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest
> > testWithMemberName FAILED
>
> org.junit.ComparisonFailure: expected:<[OK]> but was:<[ERROR]>
> 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.management.internal.cli.commands.StopLocatorCommandDUnitTest.testWithMemberName(StopLocatorCommandDUnitTest.java:159)
> {noformat}
> In the 300 run batch, to two different methods in this class are failing:
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest:
> 9 failures (97.000% success rate)
> | .testWithMemberID: 2 failures (99.333% success rate)
> | | Failed build 286 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/286
> | | Failed build 146 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/146
> | .testWithMemberName: 7 failures (97.667% success rate)
> | | Failed build 260 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/260
> | | Failed build 231 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/231
> | | Failed build 178 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/178
> | | Failed build 127 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/127
> | | Failed build 87 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/87
> | | Failed build 53 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/53
> | | Failed build 27 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/27
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5623) SUPERFLAKY: StopLocatorCommandDUnitTest
Dan Smith created GEODE-5623:
Summary: SUPERFLAKY: StopLocatorCommandDUnitTest
Key: GEODE-5623
URL: https://issues.apache.org/jira/browse/GEODE-5623
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
This test failed recently in CI, and it failed multiple times in the a 300 run
batch of DistributedTest
Most recent failure:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/281
{noformat}
org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest >
testWithMemberName FAILED
org.junit.ComparisonFailure: expected:<[OK]> but was:<[ERROR]>
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.management.internal.cli.commands.StopLocatorCommandDUnitTest.testWithMemberName(StopLocatorCommandDUnitTest.java:159)
{noformat}
In the 300 run batch, to two different methods in this class are failing:
{noformat}
org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest:
9 failures (97.000% success rate)
| .testWithMemberID: 2 failures (99.333% success rate)
| | Failed build 286 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/286
| | Failed build 146 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/146
| .testWithMemberName: 7 failures (97.667% success rate)
| | Failed build 260 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/260
| | Failed build 231 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/231
| | Failed build 178 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/178
| | Failed build 127 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/127
| | Failed build 87 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/87
| | Failed build 53 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/53
| | Failed build 27 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/27
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException
Eric Shu created GEODE-5624:
---
Summary: JTA transaction does not clean up TXState due to
IllegalMonitorStateException
Key: GEODE-5624
URL: https://issues.apache.org/jira/browse/GEODE-5624
Project: Geode
Issue Type: Bug
Components: transactions
Reporter: Eric Shu
When server has different threads handling JTA beforeCompletion and
afterCompletion, IllegalMonitorStateException can be thrown when release locks
held. This causes the TXState not being cleaned up.
{noformat}
java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked
by current thread
at
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
at
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
at
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
at
org.apache.geode.internal.util.concurrent.StoppableReentrantReadWriteLock$StoppableReadLock.unlock(StoppableReentrantReadWriteLock.java:144)
at
org.apache.geode.internal.cache.locks.TXLockServiceImpl.releaseRecoveryReadLock(TXLockServiceImpl.java:275)
at
org.apache.geode.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:240)
at
org.apache.geode.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:109)
at
org.apache.geode.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:142)
at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:870)
at org.apache.geode.internal.cache.TXState.commit(TXState.java:514)
at
org.apache.geode.internal.cache.TXState.doAfterCompletion(TXState.java:1103)
at
org.apache.geode.internal.cache.TXState.afterCompletion(TXState.java:1084)
at
org.apache.geode.internal.cache.TXStateProxyImpl.afterCompletion(TXStateProxyImpl.java:452)
at
org.apache.geode.internal.cache.tier.sockets.command.TXSynchronizationCommand.cmdExecute(TXSynchronizationCommand.java:140)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:158)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:869)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:77)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1248)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:645)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5624) JTA transaction does not clean up TXState due to IllegalMonitorStateException
[
https://issues.apache.org/jira/browse/GEODE-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reassigned GEODE-5624:
---
Assignee: Eric Shu
> JTA transaction does not clean up TXState due to IllegalMonitorStateException
> -
>
> Key: GEODE-5624
> URL: https://issues.apache.org/jira/browse/GEODE-5624
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> When server has different threads handling JTA beforeCompletion and
> afterCompletion, IllegalMonitorStateException can be thrown when release
> locks held. This causes the TXState not being cleaned up.
> {noformat}
> java.lang.IllegalMonitorStateException: attempt to unlock read lock, not
> locked by current thread
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> at
> org.apache.geode.internal.util.concurrent.StoppableReentrantReadWriteLock$StoppableReadLock.unlock(StoppableReentrantReadWriteLock.java:144)
> at
> org.apache.geode.internal.cache.locks.TXLockServiceImpl.releaseRecoveryReadLock(TXLockServiceImpl.java:275)
> at
> org.apache.geode.internal.cache.locks.TXLockServiceImpl.release(TXLockServiceImpl.java:240)
> at
> org.apache.geode.internal.cache.TXLockRequest.releaseDistributed(TXLockRequest.java:109)
> at
> org.apache.geode.internal.cache.TXLockRequest.cleanup(TXLockRequest.java:142)
> at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:870)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:514)
> at
> org.apache.geode.internal.cache.TXState.doAfterCompletion(TXState.java:1103)
> at
> org.apache.geode.internal.cache.TXState.afterCompletion(TXState.java:1084)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.afterCompletion(TXStateProxyImpl.java:452)
> at
> org.apache.geode.internal.cache.tier.sockets.command.TXSynchronizationCommand.cmdExecute(TXSynchronizationCommand.java:140)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:158)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:869)
> at
> org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:77)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1248)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:645)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-3778) FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-3778:
-
Labels: Ci swat (was: Ci)
> FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail
> fails intermittently
>
>
> Key: GEODE-3778
> URL: https://issues.apache.org/jira/browse/GEODE-3778
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Priority: Major
> Labels: Ci, swat
>
> FileProcessControllerIntegrationTest tests FileProcessController which GFSH
> uses to control running Locator and Server processes.
> So far this test has failed 3 times in CI with 2 different stacks:
> {noformat}
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest >
> status_withStatusRequestFileExists_doesNotFail FAILED
> java.lang.AssertionError:
> Expecting file:
>
> to exist.
> at
> org.apache.geode.internal.process.io.StringFileWriter.writeToFile(StringFileWriter.java:40)
> at
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail(FileProcessControllerIntegrationTest.java:212)
> {noformat}
> {noformat}
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest >
> status_withStatusRequestFileExists_doesNotFail FAILED
> java.lang.InterruptedException: sleep interrupted
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:143)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest.lambda$status_withStatusRequestFileExists_doesNotFail$4(FileProcessControllerIntegrationTest.java:206)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3778) FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590486#comment-16590486
]
Dan Smith commented on GEODE-3778:
--
This test is still failing. Most recent failiure:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/280
{noformat}
org.apache.geode.internal.process.FileProcessControllerIntegrationTest >
status_withStatusRequestFileExists_doesNotFail FAILED
java.lang.AssertionError:
Expecting file:
to exist.
at
org.apache.geode.internal.process.io.StringFileWriter.writeToFile(StringFileWriter.java:40)
at
org.apache.geode.internal.process.FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail(FileProcessControllerIntegrationTest.java:202)
{noformat}
> FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail
> fails intermittently
>
>
> Key: GEODE-3778
> URL: https://issues.apache.org/jira/browse/GEODE-3778
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kirk Lund
>Priority: Major
> Labels: Ci, swat
>
> FileProcessControllerIntegrationTest tests FileProcessController which GFSH
> uses to control running Locator and Server processes.
> So far this test has failed 3 times in CI with 2 different stacks:
> {noformat}
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest >
> status_withStatusRequestFileExists_doesNotFail FAILED
> java.lang.AssertionError:
> Expecting file:
>
> to exist.
> at
> org.apache.geode.internal.process.io.StringFileWriter.writeToFile(StringFileWriter.java:40)
> at
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest.status_withStatusRequestFileExists_doesNotFail(FileProcessControllerIntegrationTest.java:212)
> {noformat}
> {noformat}
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest >
> status_withStatusRequestFileExists_doesNotFail FAILED
> java.lang.InterruptedException: sleep interrupted
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:143)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.internal.process.FileProcessControllerIntegrationTest.lambda$status_withStatusRequestFileExists_doesNotFail$4(FileProcessControllerIntegrationTest.java:206)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5601) AcceptanceTests are run in parallel without using containers, resulting in port conflicts
[
https://issues.apache.org/jira/browse/GEODE-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5601:
Assignee: Kenneth Howe
> AcceptanceTests are run in parallel without using containers, resulting in
> port conflicts
> -
>
> Key: GEODE-5601
> URL: https://issues.apache.org/jira/browse/GEODE-5601
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Jacob S. Barrett
>Assignee: Kenneth Howe
>Priority: Major
> Labels: flaky, swat
>
> {noformat}
> org.apache.geode.management.internal.cli.commands.DeployWithLargeJarTest >
> deployLargeSetOfJars FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:117)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:135)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:106)
> at
> org.apache.geode.management.internal.cli.commands.DeployWithLargeJarTest.deployLargeSetOfJars(DeployWithLargeJarTest.java:41)
> {noformat}
> Passes:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/AcceptanceTest/builds/721
> Fails:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/AcceptanceTest/builds/728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5590) CI Failure: PutCommandWithJsonTest > putWithJsonString Fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-5590.
--
Resolution: Duplicate
> CI Failure: PutCommandWithJsonTest > putWithJsonString Fails intermittently
>
>
> Key: GEODE-5590
> URL: https://issues.apache.org/jira/browse/GEODE-5590
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Kenneth Howe
>Priority: Major
> Labels: swat
>
> {code:java}
> org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest >
> putWithJsonString FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:117)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:135)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:106)
> at
> org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest.putWithJsonString(PutCommandWithJsonTest.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5625) CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
Sai Boorlagadda created GEODE-5625:
--
Summary: CI Failure:
RollingUpgradeRollServersOnPartitionedRegion_dataserializable
Key: GEODE-5625
URL: https://issues.apache.org/jira/browse/GEODE-5625
Project: Geode
Issue Type: Bug
Components: swat
Reporter: Sai Boorlagadda
https://concourse.apachegeode-ci.info/builds/19873
{code:java}
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
[fatal 2018/08/21 23:09:52.169 UTC tid=225]
Possible loss of quorum due to the loss of 1 cache processes:
[172.17.0.27(5931):32771]
---
Found suspect string in log4j at line 6222
[fatal 2018/08/21 23:09:53.171 UTC tid=225]
Membership service failure: Exiting due to possible network partition event due
to loss of 1 cache processes: [172.17.0.27(5931):32771]
org.apache.geode.ForcedDisconnectException: Exiting due to possible network
partition event due to loss of 1 cache processes: [172.17.0.27(5931):32771]
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5625) CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
[
https://issues.apache.org/jira/browse/GEODE-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5625:
---
Description:
[https://concourse.apachegeode-ci.info/builds/19873]
Build artifacts:
[http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1534894392/]
{code:java}
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
[fatal 2018/08/21 23:09:52.169 UTC tid=225]
Possible loss of quorum due to the loss of 1 cache processes:
[172.17.0.27(5931):32771]
---
Found suspect string in log4j at line 6222
[fatal 2018/08/21 23:09:53.171 UTC tid=225]
Membership service failure: Exiting due to possible network partition event due
to loss of 1 cache processes: [172.17.0.27(5931):32771]
org.apache.geode.ForcedDisconnectException: Exiting due to possible network
partition event due to loss of 1 cache processes: [172.17.0.27(5931):32771]
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
was:
https://concourse.apachegeode-ci.info/builds/19873
{code:java}
org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
[fatal 2018/08/21 23:09:52.169 UTC tid=225]
Possible loss of quorum due to the loss of 1 cache processes:
[172.17.0.27(5931):32771]
---
Found suspect string in log4j at line 6222
[fatal 2018/08/21 23:09:53.171 UTC tid=225]
Membership service failure: Exiting due to possible network partition event due
to loss of 1 cache processes: [172.17.0.27(5931):32771]
org.apache.geode.ForcedDisconnectException: Exiting due to possible network
partition event due to loss of 1 cache processes: [172.17.0.27(5931):32771]
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
> CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> -
>
> Key: GEODE-5625
> URL: https://issues.apache.org/jira/browse/GEODE-5625
> Project: Geode
> Issue Type: Bug
> Components: swat
>Reporter: Sai Boorlagadda
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/builds/19873]
> Build artifacts:
> [http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1534894392/]
>
> {code:java}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> > testRollServersOnPartitionedRe
[jira] [Updated] (GEODE-4273) org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase fails with IllegalStateException
[ https://issues.apache.org/jira/browse/GEODE-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-4273: --- Component/s: swat > org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase > fails with IllegalStateException > - > > Key: GEODE-4273 > URL: https://issues.apache.org/jira/browse/GEODE-4273 > Project: Geode > Issue Type: Bug > Components: persistence, swat >Reporter: Lynn Gallinat >Priority: Major > Labels: flaky > > org.apache.geode.internal.cache.DiskRegionJUnitTest > > testEntryDestructionInSynchPersistOnlyForIOExceptionCase FAILED > java.lang.IllegalStateException: A connection to a distributed system > already exists in this VM. It has the following configuration: > ack-severe-alert-threshold="0" > ack-wait-threshold="15" > archive-disk-space-limit="0" > archive-file-size-limit="0" > async-distribution-timeout="0" > async-max-queue-size="8" > async-queue-timeout="6" > bind-address="" > cache-xml-file="cache.xml" > cluster-configuration-dir="" > cluster-ssl-ciphers="any" > cluster-ssl-enabled="false" > cluster-ssl-keystore="" > cluster-ssl-keystore-password="" > cluster-ssl-keystore-type="" > cluster-ssl-protocols="any" > cluster-ssl-require-authentication="true" > cluster-ssl-truststore="" > cluster-ssl-truststore-password="" > conflate-events="server" > conserve-sockets="true" > delta-propagation="true" > > deploy-working-dir="/tmp/build/ae3c03f4/built-geode/test/geode-core/build/integrationTest" > disable-auto-reconnect="false" > disable-tcp="false" > distributed-system-id="-1" > distributed-transactions="false" > durable-client-id="" > durable-client-timeout="300" > enable-cluster-configuration="true" > enable-network-partition-detection="true" > enable-time-statistics="true" > enforce-unique-host="false" > gateway-ssl-ciphers="any" > gateway-ssl-enabled="false" > gateway-ssl-keystore="" > gateway-ssl-keystore-password="" > gateway-ssl-keystore-type="" > gateway-ssl-protocols="any" > gateway-ssl-require-authentication="true" > gateway-ssl-truststore="" > gateway-ssl-truststore-password="" > groups="" > http-service-bind-address="" > http-service-port="7070" > http-service-ssl-ciphers="any" > http-service-ssl-enabled="false" > http-service-ssl-keystore="" > http-service-ssl-keystore-password="" > http-service-ssl-keystore-type="" > http-service-ssl-protocols="any" > http-service-ssl-require-authentication="false" > http-service-ssl-truststore="" > http-service-ssl-truststore-password="" > jmx-manager="false" > jmx-manager-access-file="" > jmx-manager-bind-address="" > jmx-manager-hostname-for-clients="" > jmx-manager-http-port="7070" > jmx-manager-password-file="" > jmx-manager-port="1099" > jmx-manager-ssl-ciphers="any" > jmx-manager-ssl-enabled="false" > jmx-manager-ssl-keystore="" > jmx-manager-ssl-keystore-password="" > jmx-manager-ssl-keystore-type="" > jmx-manager-ssl-protocols="any" > jmx-manager-ssl-require-authentication="true" > jmx-manager-ssl-truststore="" > jmx-manager-ssl-truststore-password="" > jmx-manager-start="false" > jmx-manager-update-rate="2000" > load-cluster-configuration-from-dir="false" > locator-wait-time="0" > locators="" > lock-memory="false" > log-disk-space-limit="0" > log-file="" > log-file-size-limit="0" > log-level="config" > max-num-reconnect-tries="3" > max-wait-time-reconnect="6" > mcast-address="/239.192.81.1" > mcast-flow-control="1048576, 0.25, 5000" > mcast-port="0" > mcast-recv-buffer-size="1048576" > mcast-send-buffer-size="65535" > mcast-ttl="32" > member-timeout="5000" > membership-port-range="[1024,65535]" > memcached-bind-address="" > memcached-port="0" > memcached-protocol="ASCII" > name="" > off-heap-memory-size="" > redis-bind-address="" > redis-password="" > redis-port="0" > redundancy-zone="" > remote-locators="" > remove-unresponsive-client="false" > roles="" > security-client-accessor="" > security-client-accessor-pp="" > security-client-auth-init="" > security-client-authenticator="" > security-client-dhalgo=
[jira] [Commented] (GEODE-4273) org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase fails with IllegalStateException
[ https://issues.apache.org/jira/browse/GEODE-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590512#comment-16590512 ] Sai Boorlagadda commented on GEODE-4273: This appeared in: [https://concourse.apachegeode-ci.info/builds/19874] Build Artifact: [http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/repeatTest/1534893044/] > org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase > fails with IllegalStateException > - > > Key: GEODE-4273 > URL: https://issues.apache.org/jira/browse/GEODE-4273 > Project: Geode > Issue Type: Bug > Components: persistence, swat >Reporter: Lynn Gallinat >Priority: Major > Labels: flaky > > org.apache.geode.internal.cache.DiskRegionJUnitTest > > testEntryDestructionInSynchPersistOnlyForIOExceptionCase FAILED > java.lang.IllegalStateException: A connection to a distributed system > already exists in this VM. It has the following configuration: > ack-severe-alert-threshold="0" > ack-wait-threshold="15" > archive-disk-space-limit="0" > archive-file-size-limit="0" > async-distribution-timeout="0" > async-max-queue-size="8" > async-queue-timeout="6" > bind-address="" > cache-xml-file="cache.xml" > cluster-configuration-dir="" > cluster-ssl-ciphers="any" > cluster-ssl-enabled="false" > cluster-ssl-keystore="" > cluster-ssl-keystore-password="" > cluster-ssl-keystore-type="" > cluster-ssl-protocols="any" > cluster-ssl-require-authentication="true" > cluster-ssl-truststore="" > cluster-ssl-truststore-password="" > conflate-events="server" > conserve-sockets="true" > delta-propagation="true" > > deploy-working-dir="/tmp/build/ae3c03f4/built-geode/test/geode-core/build/integrationTest" > disable-auto-reconnect="false" > disable-tcp="false" > distributed-system-id="-1" > distributed-transactions="false" > durable-client-id="" > durable-client-timeout="300" > enable-cluster-configuration="true" > enable-network-partition-detection="true" > enable-time-statistics="true" > enforce-unique-host="false" > gateway-ssl-ciphers="any" > gateway-ssl-enabled="false" > gateway-ssl-keystore="" > gateway-ssl-keystore-password="" > gateway-ssl-keystore-type="" > gateway-ssl-protocols="any" > gateway-ssl-require-authentication="true" > gateway-ssl-truststore="" > gateway-ssl-truststore-password="" > groups="" > http-service-bind-address="" > http-service-port="7070" > http-service-ssl-ciphers="any" > http-service-ssl-enabled="false" > http-service-ssl-keystore="" > http-service-ssl-keystore-password="" > http-service-ssl-keystore-type="" > http-service-ssl-protocols="any" > http-service-ssl-require-authentication="false" > http-service-ssl-truststore="" > http-service-ssl-truststore-password="" > jmx-manager="false" > jmx-manager-access-file="" > jmx-manager-bind-address="" > jmx-manager-hostname-for-clients="" > jmx-manager-http-port="7070" > jmx-manager-password-file="" > jmx-manager-port="1099" > jmx-manager-ssl-ciphers="any" > jmx-manager-ssl-enabled="false" > jmx-manager-ssl-keystore="" > jmx-manager-ssl-keystore-password="" > jmx-manager-ssl-keystore-type="" > jmx-manager-ssl-protocols="any" > jmx-manager-ssl-require-authentication="true" > jmx-manager-ssl-truststore="" > jmx-manager-ssl-truststore-password="" > jmx-manager-start="false" > jmx-manager-update-rate="2000" > load-cluster-configuration-from-dir="false" > locator-wait-time="0" > locators="" > lock-memory="false" > log-disk-space-limit="0" > log-file="" > log-file-size-limit="0" > log-level="config" > max-num-reconnect-tries="3" > max-wait-time-reconnect="6" > mcast-address="/239.192.81.1" > mcast-flow-control="1048576, 0.25, 5000" > mcast-port="0" > mcast-recv-buffer-size="1048576" > mcast-send-buffer-size="65535" > mcast-ttl="32" > member-timeout="5000" > membership-port-range="[1024,65535]" > memcached-bind-address="" > memcached-port="0" > memcached-protocol="ASCII" > name="" > off-heap-memory-size="" > redis-bind-address="" > redis-password="" > redis-port="0" > redundancy-zone="" > remote-locators="" > remove-unrespon
[jira] [Updated] (GEODE-5625) CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
[
https://issues.apache.org/jira/browse/GEODE-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5625:
---
Labels: swat (was: )
> CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> -
>
> Key: GEODE-5625
> URL: https://issues.apache.org/jira/browse/GEODE-5625
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: swat
>
> [https://concourse.apachegeode-ci.info/builds/19873]
> Build artifacts:
> [http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1534894392/]
>
> {code:java}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> > testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
> [fatal 2018/08/21 23:09:52.169 UTC
> tid=225] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> ---
> Found suspect string in log4j at line 6222
> [fatal 2018/08/21 23:09:53.171 UTC
> tid=225] Membership service failure: Exiting due to possible network
> partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> org.apache.geode.ForcedDisconnectException: Exiting due to possible
> network partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5625) CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
[
https://issues.apache.org/jira/browse/GEODE-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5625:
---
Component/s: ci
> CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> -
>
> Key: GEODE-5625
> URL: https://issues.apache.org/jira/browse/GEODE-5625
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: swat
>
> [https://concourse.apachegeode-ci.info/builds/19873]
> Build artifacts:
> [http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1534894392/]
>
> {code:java}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> > testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
> [fatal 2018/08/21 23:09:52.169 UTC
> tid=225] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> ---
> Found suspect string in log4j at line 6222
> [fatal 2018/08/21 23:09:53.171 UTC
> tid=225] Membership service failure: Exiting due to possible network
> partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> org.apache.geode.ForcedDisconnectException: Exiting due to possible
> network partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5625) CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
[
https://issues.apache.org/jira/browse/GEODE-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5625:
---
Component/s: (was: swat)
> CI Failure: RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> -
>
> Key: GEODE-5625
> URL: https://issues.apache.org/jira/browse/GEODE-5625
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: swat
>
> [https://concourse.apachegeode-ci.info/builds/19873]
> Build artifacts:
> [http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1534894392/]
>
> {code:java}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeRollServersOnPartitionedRegion_dataserializable
> > testRollServersOnPartitionedRegion_dataserializable[from_v120] 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 6207
> [fatal 2018/08/21 23:09:52.169 UTC
> tid=225] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> ---
> Found suspect string in log4j at line 6222
> [fatal 2018/08/21 23:09:53.171 UTC
> tid=225] Membership service failure: Exiting due to possible network
> partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> org.apache.geode.ForcedDisconnectException: Exiting due to possible
> network partition event due to loss of 1 cache processes:
> [172.17.0.27(5931):32771]
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2534)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1054)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:92)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2507)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2136)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2214){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4273) org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase fails with IllegalStateException
[ https://issues.apache.org/jira/browse/GEODE-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-4273: --- Component/s: (was: swat) > org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase > fails with IllegalStateException > - > > Key: GEODE-4273 > URL: https://issues.apache.org/jira/browse/GEODE-4273 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Lynn Gallinat >Priority: Major > Labels: flaky, swat > > org.apache.geode.internal.cache.DiskRegionJUnitTest > > testEntryDestructionInSynchPersistOnlyForIOExceptionCase FAILED > java.lang.IllegalStateException: A connection to a distributed system > already exists in this VM. It has the following configuration: > ack-severe-alert-threshold="0" > ack-wait-threshold="15" > archive-disk-space-limit="0" > archive-file-size-limit="0" > async-distribution-timeout="0" > async-max-queue-size="8" > async-queue-timeout="6" > bind-address="" > cache-xml-file="cache.xml" > cluster-configuration-dir="" > cluster-ssl-ciphers="any" > cluster-ssl-enabled="false" > cluster-ssl-keystore="" > cluster-ssl-keystore-password="" > cluster-ssl-keystore-type="" > cluster-ssl-protocols="any" > cluster-ssl-require-authentication="true" > cluster-ssl-truststore="" > cluster-ssl-truststore-password="" > conflate-events="server" > conserve-sockets="true" > delta-propagation="true" > > deploy-working-dir="/tmp/build/ae3c03f4/built-geode/test/geode-core/build/integrationTest" > disable-auto-reconnect="false" > disable-tcp="false" > distributed-system-id="-1" > distributed-transactions="false" > durable-client-id="" > durable-client-timeout="300" > enable-cluster-configuration="true" > enable-network-partition-detection="true" > enable-time-statistics="true" > enforce-unique-host="false" > gateway-ssl-ciphers="any" > gateway-ssl-enabled="false" > gateway-ssl-keystore="" > gateway-ssl-keystore-password="" > gateway-ssl-keystore-type="" > gateway-ssl-protocols="any" > gateway-ssl-require-authentication="true" > gateway-ssl-truststore="" > gateway-ssl-truststore-password="" > groups="" > http-service-bind-address="" > http-service-port="7070" > http-service-ssl-ciphers="any" > http-service-ssl-enabled="false" > http-service-ssl-keystore="" > http-service-ssl-keystore-password="" > http-service-ssl-keystore-type="" > http-service-ssl-protocols="any" > http-service-ssl-require-authentication="false" > http-service-ssl-truststore="" > http-service-ssl-truststore-password="" > jmx-manager="false" > jmx-manager-access-file="" > jmx-manager-bind-address="" > jmx-manager-hostname-for-clients="" > jmx-manager-http-port="7070" > jmx-manager-password-file="" > jmx-manager-port="1099" > jmx-manager-ssl-ciphers="any" > jmx-manager-ssl-enabled="false" > jmx-manager-ssl-keystore="" > jmx-manager-ssl-keystore-password="" > jmx-manager-ssl-keystore-type="" > jmx-manager-ssl-protocols="any" > jmx-manager-ssl-require-authentication="true" > jmx-manager-ssl-truststore="" > jmx-manager-ssl-truststore-password="" > jmx-manager-start="false" > jmx-manager-update-rate="2000" > load-cluster-configuration-from-dir="false" > locator-wait-time="0" > locators="" > lock-memory="false" > log-disk-space-limit="0" > log-file="" > log-file-size-limit="0" > log-level="config" > max-num-reconnect-tries="3" > max-wait-time-reconnect="6" > mcast-address="/239.192.81.1" > mcast-flow-control="1048576, 0.25, 5000" > mcast-port="0" > mcast-recv-buffer-size="1048576" > mcast-send-buffer-size="65535" > mcast-ttl="32" > member-timeout="5000" > membership-port-range="[1024,65535]" > memcached-bind-address="" > memcached-port="0" > memcached-protocol="ASCII" > name="" > off-heap-memory-size="" > redis-bind-address="" > redis-password="" > redis-port="0" > redundancy-zone="" > remote-locators="" > remove-unresponsive-client="false" > roles="" > security-client-accessor="" > security-client-accessor-pp="" > security-client-auth-init="" > security-client-authenticator="" > security-cli
[jira] [Updated] (GEODE-4273) org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase fails with IllegalStateException
[ https://issues.apache.org/jira/browse/GEODE-4273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda updated GEODE-4273: --- Labels: flaky swat (was: flaky) > org.apache.geode.internal.cache.DiskRegionJUnitTest.testEntryDestructionInSynchPersistOnlyForIOExceptionCase > fails with IllegalStateException > - > > Key: GEODE-4273 > URL: https://issues.apache.org/jira/browse/GEODE-4273 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Lynn Gallinat >Priority: Major > Labels: flaky, swat > > org.apache.geode.internal.cache.DiskRegionJUnitTest > > testEntryDestructionInSynchPersistOnlyForIOExceptionCase FAILED > java.lang.IllegalStateException: A connection to a distributed system > already exists in this VM. It has the following configuration: > ack-severe-alert-threshold="0" > ack-wait-threshold="15" > archive-disk-space-limit="0" > archive-file-size-limit="0" > async-distribution-timeout="0" > async-max-queue-size="8" > async-queue-timeout="6" > bind-address="" > cache-xml-file="cache.xml" > cluster-configuration-dir="" > cluster-ssl-ciphers="any" > cluster-ssl-enabled="false" > cluster-ssl-keystore="" > cluster-ssl-keystore-password="" > cluster-ssl-keystore-type="" > cluster-ssl-protocols="any" > cluster-ssl-require-authentication="true" > cluster-ssl-truststore="" > cluster-ssl-truststore-password="" > conflate-events="server" > conserve-sockets="true" > delta-propagation="true" > > deploy-working-dir="/tmp/build/ae3c03f4/built-geode/test/geode-core/build/integrationTest" > disable-auto-reconnect="false" > disable-tcp="false" > distributed-system-id="-1" > distributed-transactions="false" > durable-client-id="" > durable-client-timeout="300" > enable-cluster-configuration="true" > enable-network-partition-detection="true" > enable-time-statistics="true" > enforce-unique-host="false" > gateway-ssl-ciphers="any" > gateway-ssl-enabled="false" > gateway-ssl-keystore="" > gateway-ssl-keystore-password="" > gateway-ssl-keystore-type="" > gateway-ssl-protocols="any" > gateway-ssl-require-authentication="true" > gateway-ssl-truststore="" > gateway-ssl-truststore-password="" > groups="" > http-service-bind-address="" > http-service-port="7070" > http-service-ssl-ciphers="any" > http-service-ssl-enabled="false" > http-service-ssl-keystore="" > http-service-ssl-keystore-password="" > http-service-ssl-keystore-type="" > http-service-ssl-protocols="any" > http-service-ssl-require-authentication="false" > http-service-ssl-truststore="" > http-service-ssl-truststore-password="" > jmx-manager="false" > jmx-manager-access-file="" > jmx-manager-bind-address="" > jmx-manager-hostname-for-clients="" > jmx-manager-http-port="7070" > jmx-manager-password-file="" > jmx-manager-port="1099" > jmx-manager-ssl-ciphers="any" > jmx-manager-ssl-enabled="false" > jmx-manager-ssl-keystore="" > jmx-manager-ssl-keystore-password="" > jmx-manager-ssl-keystore-type="" > jmx-manager-ssl-protocols="any" > jmx-manager-ssl-require-authentication="true" > jmx-manager-ssl-truststore="" > jmx-manager-ssl-truststore-password="" > jmx-manager-start="false" > jmx-manager-update-rate="2000" > load-cluster-configuration-from-dir="false" > locator-wait-time="0" > locators="" > lock-memory="false" > log-disk-space-limit="0" > log-file="" > log-file-size-limit="0" > log-level="config" > max-num-reconnect-tries="3" > max-wait-time-reconnect="6" > mcast-address="/239.192.81.1" > mcast-flow-control="1048576, 0.25, 5000" > mcast-port="0" > mcast-recv-buffer-size="1048576" > mcast-send-buffer-size="65535" > mcast-ttl="32" > member-timeout="5000" > membership-port-range="[1024,65535]" > memcached-bind-address="" > memcached-port="0" > memcached-protocol="ASCII" > name="" > off-heap-memory-size="" > redis-bind-address="" > redis-password="" > redis-port="0" > redundancy-zone="" > remote-locators="" > remove-unresponsive-client="false" > roles="" > security-client-accessor="" > security-client-accessor-pp="" > security-client-auth-init="" > security-client-authenticator="" > security
[jira] [Commented] (GEODE-2607) Improve release artifacts
[
https://issues.apache.org/jira/browse/GEODE-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590594#comment-16590594
]
ASF subversion and git services commented on GEODE-2607:
Commit 28cd465d3c334446d98226fa8359f7df242007a2 in geode-native's branch
refs/heads/develop from [~bbender]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=28cd465 ]
GEODE-2607: improve release artifacts
- Add packer and docker directories back into release artifacts
Geode leaves these in, so it's best to match what they do when we can.
- Generate SHA512 has along with build artifacts.
Co-authored-by: Ivan Godwin
> Improve release artifacts
> -
>
> Key: GEODE-2607
> URL: https://issues.apache.org/jira/browse/GEODE-2607
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The geode-native release artifacts for the source and binary distributions
> should include:
> - archive
> - SHA-256 hash
> - GPG signatures for archive
> In addition, the top-level directory in the archives should include the
> version (e.g. {{apache-geode-native-1.2.0-source}}.
> The process for generating the release artifacts should be documented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5616) Correct formatting within WAN geode-example
[ https://issues.apache.org/jira/browse/GEODE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5616: -- Labels: pull-request-available (was: ) > Correct formatting within WAN geode-example > --- > > Key: GEODE-5616 > URL: https://issues.apache.org/jira/browse/GEODE-5616 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > > The new Geode example demonstrating WAN distribution got merged in without my > requested change. See my comment in the PR: > https://github.com/apache/geode-examples/pull/66. This ticket exists to make > that correction: > The README.md file, steps 9 and 10 need spaces added to the beginning of > their lines in order to show in the fixed-width font. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5590) CI Failure: PutCommandWithJsonTest > putWithJsonString Fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5590:
--
Labels: pull-request-available swat (was: swat)
> CI Failure: PutCommandWithJsonTest > putWithJsonString Fails intermittently
>
>
> Key: GEODE-5590
> URL: https://issues.apache.org/jira/browse/GEODE-5590
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available, swat
>
> {code:java}
> org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest >
> putWithJsonString FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:117)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:135)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:106)
> at
> org.apache.geode.management.internal.cli.commands.PutCommandWithJsonTest.putWithJsonString(PutCommandWithJsonTest.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4978) Don't calculate revision SHA for version.h in CMake configuration
[ https://issues.apache.org/jira/browse/GEODE-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt resolved GEODE-4978. - Resolution: Fixed https://github.com/apache/geode-native/pull/334 > Don't calculate revision SHA for version.h in CMake configuration > - > > Key: GEODE-4978 > URL: https://issues.apache.org/jira/browse/GEODE-4978 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > > Pass the SHA value into CMake as parameter. Currently the version.h is > dependent on the .git/index to get the current SHA but this causes the > version.h to update on every commit and other index changing events. It slows > down builds. It doesn't allow for source based distributions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5626) Segfault in Region::registerAllKeys when getInitialValues set to true
Blake Bender created GEODE-5626: --- Summary: Segfault in Region::registerAllKeys when getInitialValues set to true Key: GEODE-5626 URL: https://issues.apache.org/jira/browse/GEODE-5626 Project: Geode Issue Type: Bug Components: native client Reporter: Blake Bender getInitialValues has a default value of false. If you attempt to set it to true, it will segfault attempting to insert a value in an internal map which is null. This may or may not be the case if the region doesn't have any initial values. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5627) ConcurrencyTestHelper fails with tests that don't use it
Galen O'Sullivan created GEODE-5627:
---
Summary: ConcurrencyTestHelper fails with tests that don't use it
Key: GEODE-5627
URL: https://issues.apache.org/jira/browse/GEODE-5627
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Galen O'Sullivan
The field {{allThreadsExecuted}} is set to {{false}} when the test runs, so if
the helper doesn't see any use at all it will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5627) ConcurrencyTestHelper fails with tests that don't use it
[
https://issues.apache.org/jira/browse/GEODE-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan reassigned GEODE-5627:
---
Assignee: Galen O'Sullivan
> ConcurrencyTestHelper fails with tests that don't use it
>
>
> Key: GEODE-5627
> URL: https://issues.apache.org/jira/browse/GEODE-5627
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>
> The field {{allThreadsExecuted}} is set to {{false}} when the test runs, so
> if the helper doesn't see any use at all it will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5626) Segfault in Region::registerAllKeys when getInitialValues set to true
[ https://issues.apache.org/jira/browse/GEODE-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-5626: Description: getInitialValues has a default value of false. If you attempt to set it to true, and the region isn't initially empty, it will segfault attempting to insert a value in an internal map which is null. (was: getInitialValues has a default value of false. If you attempt to set it to true, it will segfault attempting to insert a value in an internal map which is null. This may or may not be the case if the region doesn't have any initial values.) > Segfault in Region::registerAllKeys when getInitialValues set to true > - > > Key: GEODE-5626 > URL: https://issues.apache.org/jira/browse/GEODE-5626 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > > getInitialValues has a default value of false. If you attempt to set it to > true, and the region isn't initially empty, it will segfault attempting to > insert a value in an internal map which is null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5610) CI Failure: DiskRegionJUnitTest testAssertionErrorIfMissingOplog
[ https://issues.apache.org/jira/browse/GEODE-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590722#comment-16590722 ] ASF subversion and git services commented on GEODE-5610: Commit 9f13a5b7b2af6aa8bbf0ddf83740be1f31261073 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9f13a5b ] GEODE-5610: CI Failure: DiskRegionJUnitTest testAssertionErrorIfMissingOplog (#2357) Refactored the test to delete the oplog after closing the disk store to avoid any races. > CI Failure: DiskRegionJUnitTest testAssertionErrorIfMissingOplog > > > Key: GEODE-5610 > URL: https://issues.apache.org/jira/browse/GEODE-5610 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > Flaky DiskRegionJUnitTest on windows. > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsIntegrationTest/builds/23 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5628) CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
[
https://issues.apache.org/jira/browse/GEODE-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sai Boorlagadda updated GEODE-5628:
---
Labels: swat (was: )
> CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> --
>
> Key: GEODE-5628
> URL: https://issues.apache.org/jira/browse/GEODE-5628
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: swat
>
> CI Run: https://concourse.apachegeode-ci.info/builds/20378
> Build artifacts:
> http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1535044814/
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> > EventProcessingMixedSiteOneOldSiteTwo[from_v150] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo$$Lambda$41/436821547.run
> in VM 4 running on Host 460446c8f083 with 7 VMs with version 150
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.EventProcessingMixedSiteOneOldSiteTwo(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Failed to create server socket on
> null[25,312]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:752)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:709)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:675)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:240)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:224)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:219)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:485)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:542)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:305)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:103)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:95)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.lambda$EventProcessingMixedSiteOneOldSiteTwo$67afc7f8$1(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
> ... 13 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5628) CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
Sai Boorlagadda created GEODE-5628:
--
Summary: CI Failure:
WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
Key: GEODE-5628
URL: https://issues.apache.org/jira/browse/GEODE-5628
Project: Geode
Issue Type: Bug
Components: ci
Reporter: Sai Boorlagadda
CI Run: https://concourse.apachegeode-ci.info/builds/20378
Build artifacts:
http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1535044814/
{code:java}
org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> EventProcessingMixedSiteOneOldSiteTwo[from_v150] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo$$Lambda$41/436821547.run
in VM 4 running on Host 460446c8f083 with 7 VMs with version 150
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.EventProcessingMixedSiteOneOldSiteTwo(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
Caused by:
java.net.BindException: Failed to create server socket on null[25,312]
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:752)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:709)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:675)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:240)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:224)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:219)
at
org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:485)
at
org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:542)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:305)
at
org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
at
org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
at
org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:103)
at
org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:95)
at
org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.lambda$EventProcessingMixedSiteOneOldSiteTwo$67afc7f8$1(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
Caused by:
java.net.BindException: Address already in use (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
... 13 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5610) CI Failure: DiskRegionJUnitTest testAssertionErrorIfMissingOplog
[ https://issues.apache.org/jira/browse/GEODE-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda resolved GEODE-5610. Resolution: Fixed > CI Failure: DiskRegionJUnitTest testAssertionErrorIfMissingOplog > > > Key: GEODE-5610 > URL: https://issues.apache.org/jira/browse/GEODE-5610 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > Flaky DiskRegionJUnitTest on windows. > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsIntegrationTest/builds/23 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5627) ConcurrencyTestHelper fails with tests that don't use it
[
https://issues.apache.org/jira/browse/GEODE-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5627:
--
Labels: pull-request-available (was: )
> ConcurrencyTestHelper fails with tests that don't use it
>
>
> Key: GEODE-5627
> URL: https://issues.apache.org/jira/browse/GEODE-5627
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
> Labels: pull-request-available
>
> The field {{allThreadsExecuted}} is set to {{false}} when the test runs, so
> if the helper doesn't see any use at all it will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5460) SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
[
https://issues.apache.org/jira/browse/GEODE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5460:
--
Labels: ci flaky pull-request-available swat (was: ci flaky swat)
> SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
>
>
> Key: GEODE-5460
> URL: https://issues.apache.org/jira/browse/GEODE-5460
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Mark Hanson
>Priority: Major
> Labels: ci, flaky, pull-request-available, swat
>
> {{org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest >
> testNumOfRunningFunctions FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$29/242148781.call
> in VM 0 running on Host 57e1ae1f71ab with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:378)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:94)
> Caused by:
> java.lang.AssertionError: Event never occurred after 12 ms: wait
> for getNumOfRunningFunction to complete and get results
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:71)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:94)
> }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5460) SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
[
https://issues.apache.org/jira/browse/GEODE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590751#comment-16590751
]
ASF subversion and git services commented on GEODE-5460:
Commit c7ca13d677056b033e55891134e300dc239cc2d9 in geode's branch
refs/heads/develop from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c7ca13d ]
GEODE-5460: Fixing a race condition in TestFunctionsDUNitTest
Changing TestFunctionsDUnitTest to use a latch rather than a sleep.
> SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
>
>
> Key: GEODE-5460
> URL: https://issues.apache.org/jira/browse/GEODE-5460
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Mark Hanson
>Priority: Major
> Labels: ci, flaky, pull-request-available, swat
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest >
> testNumOfRunningFunctions FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$29/242148781.call
> in VM 0 running on Host 57e1ae1f71ab with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:378)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:94)
> Caused by:
> java.lang.AssertionError: Event never occurred after 12 ms: wait
> for getNumOfRunningFunction to complete and get results
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:71)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:94)
> }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5460) SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
[
https://issues.apache.org/jira/browse/GEODE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-5460.
--
Resolution: Fixed
Fix Version/s: 1.8.0
> SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
>
>
> Key: GEODE-5460
> URL: https://issues.apache.org/jira/browse/GEODE-5460
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Mark Hanson
>Priority: Major
> Labels: ci, flaky, pull-request-available, swat
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest >
> testNumOfRunningFunctions FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$29/242148781.call
> in VM 0 running on Host 57e1ae1f71ab with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:378)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:94)
> Caused by:
> java.lang.AssertionError: Event never occurred after 12 ms: wait
> for getNumOfRunningFunction to complete and get results
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:71)
> at
> org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:94)
> }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5616) Correct formatting within WAN geode-example
[ https://issues.apache.org/jira/browse/GEODE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590758#comment-16590758 ] ASF subversion and git services commented on GEODE-5616: Commit aee5bdbdae995a226211433705e0aa42acf5b0b1 in geode-examples's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=aee5bdb ] GEODE-5616 Correct formatting of steps 9 and 10 in WAN example > Correct formatting within WAN geode-example > --- > > Key: GEODE-5616 > URL: https://issues.apache.org/jira/browse/GEODE-5616 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The new Geode example demonstrating WAN distribution got merged in without my > requested change. See my comment in the PR: > https://github.com/apache/geode-examples/pull/66. This ticket exists to make > that correction: > The README.md file, steps 9 and 10 need spaces added to the beginning of > their lines in order to show in the fixed-width font. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5616) Correct formatting within WAN geode-example
[ https://issues.apache.org/jira/browse/GEODE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590760#comment-16590760 ] ASF subversion and git services commented on GEODE-5616: Commit 0a4449f0619bdd6e6b879ebab19f173d859f3c52 in geode-examples's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=0a4449f ] Merge pull request #67 from karensmolermiller/feature/GEODE-5616 GEODE-5616 Correct formatting of steps 9 and 10 in WAN example > Correct formatting within WAN geode-example > --- > > Key: GEODE-5616 > URL: https://issues.apache.org/jira/browse/GEODE-5616 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The new Geode example demonstrating WAN distribution got merged in without my > requested change. See my comment in the PR: > https://github.com/apache/geode-examples/pull/66. This ticket exists to make > that correction: > The README.md file, steps 9 and 10 need spaces added to the beginning of > their lines in order to show in the fixed-width font. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5616) Correct formatting within WAN geode-example
[ https://issues.apache.org/jira/browse/GEODE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590759#comment-16590759 ] ASF subversion and git services commented on GEODE-5616: Commit 0a4449f0619bdd6e6b879ebab19f173d859f3c52 in geode-examples's branch refs/heads/develop from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=0a4449f ] Merge pull request #67 from karensmolermiller/feature/GEODE-5616 GEODE-5616 Correct formatting of steps 9 and 10 in WAN example > Correct formatting within WAN geode-example > --- > > Key: GEODE-5616 > URL: https://issues.apache.org/jira/browse/GEODE-5616 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The new Geode example demonstrating WAN distribution got merged in without my > requested change. See my comment in the PR: > https://github.com/apache/geode-examples/pull/66. This ticket exists to make > that correction: > The README.md file, steps 9 and 10 need spaces added to the beginning of > their lines in order to show in the fixed-width font. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5629) GMSEncryptJUnitTest does not actually check the results of threads it starts
[
https://issues.apache.org/jira/browse/GEODE-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5629:
-
Labels: swat (was: )
> GMSEncryptJUnitTest does not actually check the results of threads it starts
>
>
> Key: GEODE-5629
> URL: https://issues.apache.org/jira/browse/GEODE-5629
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
>
> The testForClusterSecretKeyFromOtherMemberMultipleThreads method starts a
> bunch of threads, but it does not actually check to see if they ran
> successfully without an exception. It just waits for them to finish around
> line 362. This test should be refactored to use the ConcurrencyRule.
> {code}
> countDownLatch.await();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5629) GMSEncryptJUnitTest does not actually check the results of threads it starts
Dan Smith created GEODE-5629:
Summary: GMSEncryptJUnitTest does not actually check the results
of threads it starts
Key: GEODE-5629
URL: https://issues.apache.org/jira/browse/GEODE-5629
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
The testForClusterSecretKeyFromOtherMemberMultipleThreads method starts a bunch
of threads, but it does not actually check to see if they ran successfully
without an exception. It just waits for them to finish around line 362. This
test should be refactored to use the ConcurrencyRule.
{code}
countDownLatch.await();
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5629) GMSEncryptJUnitTest does not actually check the results of threads it starts
[
https://issues.apache.org/jira/browse/GEODE-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5629:
Assignee: Dan Smith
> GMSEncryptJUnitTest does not actually check the results of threads it starts
>
>
> Key: GEODE-5629
> URL: https://issues.apache.org/jira/browse/GEODE-5629
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
>
> The testForClusterSecretKeyFromOtherMemberMultipleThreads method starts a
> bunch of threads, but it does not actually check to see if they ran
> successfully without an exception. It just waits for them to finish around
> line 362. This test should be refactored to use the ConcurrencyRule.
> {code}
> countDownLatch.await();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5630) Some tests using await should use until instead of untilAsserted
Kirk Lund created GEODE-5630:
Summary: Some tests using await should use until instead of
untilAsserted
Key: GEODE-5630
URL: https://issues.apache.org/jira/browse/GEODE-5630
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Kirk Lund
Awaitility was upgraded for GEODE-5593 and most or all of the await()...until()
calls were changed to await()...untilAsserted(). One or more of these that are
now incorrect.
BucketCreationCrashCompletesRegressionTest line 173 is now:
{noformat}
await().atMost(2, MINUTES).untilAsserted(() -> {
hasBucketOwners(partitionedRegion, bucketId);
});
{noformat}
But hasBucketOwners returns a boolean and does not perform any assertions.
I'll fix this test and then review every other test that was changed to use
untilAsserted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5616) Correct formatting within WAN geode-example
[ https://issues.apache.org/jira/browse/GEODE-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-5616. Resolution: Fixed Fix Version/s: 1.7.0 > Correct formatting within WAN geode-example > --- > > Key: GEODE-5616 > URL: https://issues.apache.org/jira/browse/GEODE-5616 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The new Geode example demonstrating WAN distribution got merged in without my > requested change. See my comment in the PR: > https://github.com/apache/geode-examples/pull/66. This ticket exists to make > that correction: > The README.md file, steps 9 and 10 need spaces added to the beginning of > their lines in order to show in the fixed-width font. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5630) Some tests using await should use until instead of untilAsserted
[
https://issues.apache.org/jira/browse/GEODE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-5630:
Assignee: Kirk Lund
> Some tests using await should use until instead of untilAsserted
>
>
> Key: GEODE-5630
> URL: https://issues.apache.org/jira/browse/GEODE-5630
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> Awaitility was upgraded for GEODE-5593 and most or all of the
> await()...until() calls were changed to await()...untilAsserted(). One or
> more of these that are now incorrect.
> BucketCreationCrashCompletesRegressionTest line 173 is now:
> {noformat}
> await().atMost(2, MINUTES).untilAsserted(() -> {
> hasBucketOwners(partitionedRegion, bucketId);
> });
> {noformat}
> But hasBucketOwners returns a boolean and does not perform any assertions.
> I'll fix this test and then review every other test that was changed to use
> untilAsserted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5597) Upload geode maven snapshot artifacts from concourse
[ https://issues.apache.org/jira/browse/GEODE-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590780#comment-16590780 ] ASF subversion and git services commented on GEODE-5597: Commit 6ee86d6d3befbe721034148adc87eebc6708fb32 in geode's branch refs/heads/develop from FSOUTHERLAND [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6ee86d6 ] GEODE-5597 verify geode-dependency jar ClassPath (#2369) Co-authored-by: Finn Southerland Co-authored-by: Jacob Barrett > Upload geode maven snapshot artifacts from concourse > > > Key: GEODE-5597 > URL: https://issues.apache.org/jira/browse/GEODE-5597 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 7h > Remaining Estimate: 0h > > We would like to publish snapshots from concourse, rather than jenkins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5630) Some tests using await should use until instead of untilAsserted
[
https://issues.apache.org/jira/browse/GEODE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5630:
--
Labels: pull-request-available (was: )
> Some tests using await should use until instead of untilAsserted
>
>
> Key: GEODE-5630
> URL: https://issues.apache.org/jira/browse/GEODE-5630
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
>
> Awaitility was upgraded for GEODE-5593 and most or all of the
> await()...until() calls were changed to await()...untilAsserted(). One or
> more of these that are now incorrect.
> BucketCreationCrashCompletesRegressionTest line 173 is now:
> {noformat}
> await().atMost(2, MINUTES).untilAsserted(() -> {
> hasBucketOwners(partitionedRegion, bucketId);
> });
> {noformat}
> But hasBucketOwners returns a boolean and does not perform any assertions.
> I'll fix this test and then review every other test that was changed to use
> untilAsserted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5617) Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
[
https://issues.apache.org/jira/browse/GEODE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5617:
Assignee: Dan Smith
> Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
> --
>
> Key: GEODE-5617
> URL: https://issues.apache.org/jira/browse/GEODE-5617
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed in CI:
> {noformat}
> org.apache.geode.cache.util.AutoBalancerJUnitTest > testAuditorInvocation
> FAILED
> unexpected invocation: oobAuditor.execute()
> expectations:
> expected once, already invoked 1 time: oobAuditor.init(an instance of
> java.util.Properties)
> expected exactly 2 times, already invoked 2 times: oobAuditor.execute()
> allowed, already invoked 3 times: timeProvider.currentTimeMillis();
> returnTime
> what happened before this:
> oobAuditor.init(<{schedule=* 0/30 * * * ?}>)
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/Build/builds/356
> This test suspiciously has a 1 second timeout, which may be why it is failing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5457) Race condition in closing cache for partitioned regions
[ https://issues.apache.org/jira/browse/GEODE-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590792#comment-16590792 ] Kirk Lund commented on GEODE-5457: -- There's a TODO in PersistentPartitionedRegionDistributedTest to complete when this ticket is fixed. > Race condition in closing cache for partitioned regions > --- > > Key: GEODE-5457 > URL: https://issues.apache.org/jira/browse/GEODE-5457 > Project: Geode > Issue Type: Bug >Reporter: Helena Bales >Priority: Major > > When the cache is closed and a put is attempted on a partitioned region, a > CacheClosedException is usually thrown, but occasionally a > DistributedSystemDisconnectedException is thrown instead. (See > [GEODE-5325|https://issues.apache.org/jira/browse/GEODE-5325] and the > distributed test recoversFromCloseDuringRegionOperation in > PersistentPartitionedRegionDistributedTest). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5617) Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
[jira] [Commented] (GEODE-5597) Upload geode maven snapshot artifacts from concourse
[ https://issues.apache.org/jira/browse/GEODE-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590798#comment-16590798 ] ASF subversion and git services commented on GEODE-5597: Commit 879b2cd5878deb1129cf94094588f59d7d3dc714 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=879b2cd ] GEODE-5597: Fixes formatting. > Upload geode maven snapshot artifacts from concourse > > > Key: GEODE-5597 > URL: https://issues.apache.org/jira/browse/GEODE-5597 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 7h > Remaining Estimate: 0h > > We would like to publish snapshots from concourse, rather than jenkins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5593) Bump test dependencies
[ https://issues.apache.org/jira/browse/GEODE-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-5593. -- Resolution: Fixed Fix Version/s: 1.7.0 > Bump test dependencies > -- > > Key: GEODE-5593 > URL: https://issues.apache.org/jira/browse/GEODE-5593 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Anthony Baker >Assignee: Anthony Baker >Priority: Major > Fix For: 1.7.0 > > > Review and update test dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3853) Upgrade to Mockito 2.11.0
[ https://issues.apache.org/jira/browse/GEODE-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3853. -- Resolution: Duplicate > Upgrade to Mockito 2.11.0 > - > > Key: GEODE-3853 > URL: https://issues.apache.org/jira/browse/GEODE-3853 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: upgrades > > Geode currently uses Mockito 2.8.9. Version 2.11.0 was released on 2017-10-14 > [1]. I'd like to upgrade to 2.11.0. > [1] > https://github.com/mockito/mockito/blob/release/2.x/doc/release-notes/official.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3848) Upgrade to Awaitility 3.0.0
[ https://issues.apache.org/jira/browse/GEODE-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3848. -- Resolution: Duplicate > Upgrade to Awaitility 3.0.0 > --- > > Key: GEODE-3848 > URL: https://issues.apache.org/jira/browse/GEODE-3848 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: upgrades > > Geode currently uses Awaitility 2.0.0. Version 3.0.0 was released on > 2017-04-28[1]. I'd like to upgrade to 3.0.0. > [1] https://github.com/awaitility/awaitility/wiki/ReleaseNotes30 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3849) Upgrade to Apache HttpComponents 4.4.8
[ https://issues.apache.org/jira/browse/GEODE-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3849. -- Resolution: Duplicate > Upgrade to Apache HttpComponents 4.4.8 > -- > > Key: GEODE-3849 > URL: https://issues.apache.org/jira/browse/GEODE-3849 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: upgrades > > Geode currently uses Apache HttpComponents 4.4.6. Version 4.4.8 was released > on 2017-10-07[1]. I'd like to upgrade to 4.4.8. > [1] https://hc.apache.org/news.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3613) Jetty9CachingClientServerTest failed in jenkins, unable to shutdown container
[
https://issues.apache.org/jira/browse/GEODE-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-3613:
Assignee: (was: Dan Smith)
> Jetty9CachingClientServerTest failed in jenkins, unable to shutdown container
> -
>
> Key: GEODE-3613
> URL: https://issues.apache.org/jira/browse/GEODE-3613
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.session.tests.Jetty9ClientServerTest.html
>
>
> This test failed in jenkins build #953 due to a failure to shutdown jetty
> Jetty9CachingClientServerTest.containersShouldShareDataRemovals
> Revision: 52305a8a7679d761a084f866c1253777345fb29e
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Jetty
> 9.4.5.v20170502 container. Check the
> [/home/jenkins/jenkins-slave/workspace/Geode-nightly/geode-assembly/build/distributedTest65/cargo_logs/JETTY9_client-server_containersShouldShareDataRemovals_0_28531005061735378/container.log]
> file containing the container logs for more details.
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:303)
> at
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:210)
> at
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
> at
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
> at
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
> at
> org.apache.geode.session.tests.CargoTestBase.stop(CargoTestBase.java:71)
> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
> 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.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWo
[jira] [Resolved] (GEODE-3850) Upgrade to JMock 2.8.3
[ https://issues.apache.org/jira/browse/GEODE-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3850. -- Resolution: Duplicate > Upgrade to JMock 2.8.3 > -- > > Key: GEODE-3850 > URL: https://issues.apache.org/jira/browse/GEODE-3850 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: upgrades > > Geode currently uses JMock 2.8.2. Version 2.8.3 was released on 2017-06-15 > [1]. I'd like to upgrade to 2.8.3. > [1] https://github.com/jmock-developers/jmock-library -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5623) SUPERFLAKY: StopLocatorCommandDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5623:
Assignee: Dan Smith
> SUPERFLAKY: StopLocatorCommandDUnitTest
> ---
>
> Key: GEODE-5623
> URL: https://issues.apache.org/jira/browse/GEODE-5623
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed recently in CI, and it failed multiple times in the a 300
> run batch of DistributedTest
> Most recent failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/281
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest
> > testWithMemberName FAILED
>
> org.junit.ComparisonFailure: expected:<[OK]> but was:<[ERROR]>
> 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.management.internal.cli.commands.StopLocatorCommandDUnitTest.testWithMemberName(StopLocatorCommandDUnitTest.java:159)
> {noformat}
> In the 300 run batch, to two different methods in this class are failing:
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest:
> 9 failures (97.000% success rate)
> | .testWithMemberID: 2 failures (99.333% success rate)
> | | Failed build 286 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/286
> | | Failed build 146 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/146
> | .testWithMemberName: 7 failures (97.667% success rate)
> | | Failed build 260 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/260
> | | Failed build 231 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/231
> | | Failed build 178 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/178
> | | Failed build 127 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/127
> | | Failed build 87 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/87
> | | Failed build 53 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/53
> | | Failed build 27 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/27
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3856) Upgrade to PowerMock 1.7.3
[ https://issues.apache.org/jira/browse/GEODE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3856. -- Resolution: Duplicate > Upgrade to PowerMock 1.7.3 > -- > > Key: GEODE-3856 > URL: https://issues.apache.org/jira/browse/GEODE-3856 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: upgrades > > Geode currently uses PowerMock 1.7.1. Version 1.7.3 was released on > 2017-09-16 [1]. I'd like to upgrade to 1.7.3. > [1] https://github.com/powermock/powermock/releases/tag/powermock-1.7.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3613) Jetty9CachingClientServerTest failed in jenkins, unable to shutdown container
[
https://issues.apache.org/jira/browse/GEODE-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-3613:
Assignee: Dan Smith
> Jetty9CachingClientServerTest failed in jenkins, unable to shutdown container
> -
>
> Key: GEODE-3613
> URL: https://issues.apache.org/jira/browse/GEODE-3613
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.session.tests.Jetty9ClientServerTest.html
>
>
> This test failed in jenkins build #953 due to a failure to shutdown jetty
> Jetty9CachingClientServerTest.containersShouldShareDataRemovals
> Revision: 52305a8a7679d761a084f866c1253777345fb29e
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to stop the Jetty
> 9.4.5.v20170502 container. Check the
> [/home/jenkins/jenkins-slave/workspace/Geode-nightly/geode-assembly/build/distributedTest65/cargo_logs/JETTY9_client-server_containersShouldShareDataRemovals_0_28531005061735378/container.log]
> file containing the container logs for more details.
> at
> org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:303)
> at
> org.apache.geode.session.tests.ServerContainer.stop(ServerContainer.java:210)
> at
> org.apache.geode.session.tests.ContainerManager.stopContainer(ContainerManager.java:105)
> at
> org.apache.geode.session.tests.ContainerManager.stopContainers(ContainerManager.java:115)
> at
> org.apache.geode.session.tests.ContainerManager.stopAllActiveContainers(ContainerManager.java:122)
> at
> org.apache.geode.session.tests.CargoTestBase.stop(CargoTestBase.java:71)
> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
> 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.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks
[jira] [Commented] (GEODE-5623) SUPERFLAKY: StopLocatorCommandDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590830#comment-16590830
]
Dan Smith commented on GEODE-5623:
--
I'm seeing this test fail more consistently if I run it on a faster machine. I
think there must be a race condition between starting the locator and it being
available as something that can be stopped.
> SUPERFLAKY: StopLocatorCommandDUnitTest
> ---
>
> Key: GEODE-5623
> URL: https://issues.apache.org/jira/browse/GEODE-5623
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed recently in CI, and it failed multiple times in the a 300
> run batch of DistributedTest
> Most recent failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/281
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest
> > testWithMemberName FAILED
>
> org.junit.ComparisonFailure: expected:<[OK]> but was:<[ERROR]>
> 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.management.internal.cli.commands.StopLocatorCommandDUnitTest.testWithMemberName(StopLocatorCommandDUnitTest.java:159)
> {noformat}
> In the 300 run batch, to two different methods in this class are failing:
> {noformat}
> org.apache.geode.management.internal.cli.commands.StopLocatorCommandDUnitTest:
> 9 failures (97.000% success rate)
> | .testWithMemberID: 2 failures (99.333% success rate)
> | | Failed build 286 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/286
> | | Failed build 146 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/146
> | .testWithMemberName: 7 failures (97.667% success rate)
> | | Failed build 260 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/260
> | | Failed build 231 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/231
> | | Failed build 178 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/178
> | | Failed build 127 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/127
> | | Failed build 87 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/87
> | | Failed build 53 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/53
> | | Failed build 27 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/concourse-staging/jobs/DistributedTest/builds/27
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5631) failedBatchRemovalMessageKeys never cleared
nabarun created GEODE-5631: -- Summary: failedBatchRemovalMessageKeys never cleared Key: GEODE-5631 URL: https://issues.apache.org/jira/browse/GEODE-5631 Project: Geode Issue Type: Bug Components: wan Reporter: nabarun *+Experiment setup+*: * Region A created with async event listener attached to it * For every event processed by the async listener, a new entry is put into another region, Region B. * There is a client which does 1 million operations on 1500 keys on Region A. [to trigger conflation.] * 3 servers, 1 locator and 1 client. +*Issue:*+ It was confirmed that after upgrading to 1.6.0 , we saw an increase in the memory footprint after all operations are completed. +*Cause:*+ * We had a data structure to store all the queue removal messages that comes in when the secondary is in process of GII, called failedBatchRemovalMessageKeys. * Two removal messages were sent to the secondary for a single event, one from the processor which was processing the event and another from the conflation thread which conflated the event and hence wants the secondary to remove it. * Of the two messages whichever comes first, it removes the event from the queue. * When the second message comes in, and we try to remove it from the queue, it hits an EntryNotFoundException. This makes the message think that secondary is in GII and hence stores it in the failedBatchRemovalMessageKeys, and expects that when GII is complete, this message will be processed. * But GII was already done long before, and this data structure, failedBatchRemovalMessageKeys keeps storing messages which are never removed and hence a large memory footprint. +*Fix:*+ The data structure failedBatchRemovalMessageKeys is not used anymore if it was already processed once, as GII happens once in a server’s lifecycle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5440) SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[
https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590879#comment-16590879
]
ASF subversion and git services commented on GEODE-5440:
Commit a1f747ca126a85192ac3c36183b9bfc9ae5116f9 in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1f747c ]
GEODE-5440: when we need re-evaluate a entry in a index, we need to pass in the
outer value key in the equiJoin. (#2338)
* rewrite the flaky test with an integration test
* pass in the value key when doing the equiJoin
* code clean up.
> SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
> -
>
> Key: GEODE-5440
> URL: https://issues.apache.org/jira/browse/GEODE-5440
> Project: Geode
> Issue Type: Bug
> Components: querying
>Affects Versions: 1.8.0
>Reporter: Jacob S. Barrett
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Flaky test in CI distributedTest job.
> {noformat}
> > Task :geode-core:distributedTest
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest >
> testRRPRLocalQueryingWithHetroIndexes FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$36.run in VM 0
> running on Host 2709b168a57a with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at
> org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:873)
> Caused by:
> java.lang.AssertionError: FAILED:SelectResults size is different in
> both the cases. Size1=292 Size2 = 400; failed query=r1.ID = r2.id
> {noformat}
> Artifacts at
> http://files.apachegeode-ci.info/builds/geode-pr-2126/test-artifacts/1531783070/distributedtestcore-geode-pr-2126.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5630) Some tests using await should use until instead of untilAsserted
[
https://issues.apache.org/jira/browse/GEODE-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590883#comment-16590883
]
ASF subversion and git services commented on GEODE-5630:
Commit abb2702eb252efc2e27ba78d6dde8fc2bac13545 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=abb2702 ]
GEODE-5630: fix use of Awaitility in BucketCreationCrashCompletesRegressionTest
> Some tests using await should use until instead of untilAsserted
>
>
> Key: GEODE-5630
> URL: https://issues.apache.org/jira/browse/GEODE-5630
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Awaitility was upgraded for GEODE-5593 and most or all of the
> await()...until() calls were changed to await()...untilAsserted(). One or
> more of these that are now incorrect.
> BucketCreationCrashCompletesRegressionTest line 173 is now:
> {noformat}
> await().atMost(2, MINUTES).untilAsserted(() -> {
> hasBucketOwners(partitionedRegion, bucketId);
> });
> {noformat}
> But hasBucketOwners returns a boolean and does not perform any assertions.
> I'll fix this test and then review every other test that was changed to use
> untilAsserted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3335) CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails intermittently with ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-3335.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> CI Failure : RegionManagementDUnitTest.testNavigationAPIS fails
> intermittently with ConditionTimeoutException
> -
>
> Key: GEODE-3335
> URL: https://issues.apache.org/jira/browse/GEODE-3335
> Project: Geode
> Issue Type: Bug
> Components: management
> Environment: AWS
>Reporter: nabarun
>Assignee: Kirk Lund
>Priority: Minor
> Labels: DistributedTest, Flaky, swat
> Fix For: 1.7.0
>
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> 96fffb6d85d3 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:290)
> at
> org.apache.geode.management.RegionManagementDUnitTest.verifyNavigationApis(RegionManagementDUnitTest.java:419)
> at
> org.apache.geode.management.RegionManagementDUnitTest.testNavigationAPIS(RegionManagementDUnitTest.java:282)
> 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.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
[jira] [Resolved] (GEODE-5547) RegionManagementDUnitTest > testFixedPRRegionMBean FAILED
[
https://issues.apache.org/jira/browse/GEODE-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-5547.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> RegionManagementDUnitTest > testFixedPRRegionMBean FAILED
> -
>
> Key: GEODE-5547
> URL: https://issues.apache.org/jira/browse/GEODE-5547
> Project: Geode
> Issue Type: Bug
>Reporter: Jinmei Liao
>Assignee: Kirk Lund
>Priority: Minor
> Labels: Flaky, pull-request-available, swat
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> recent failure:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/231#L5b5be314:763
> {noformat}
> org.apache.geode.management.RegionManagementDUnitTest >
> testFixedPRRegionMBean FAILED
> {noformat}
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> 0f4308c1376f with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:343)
> at
> org.apache.geode.management.RegionManagementDUnitTest.verifyMemberNotifications(RegionManagementDUnitTest.java:565)
> at
> org.apache.geode.management.RegionManagementDUnitTest.testFixedPRRegionMBean(RegionManagementDUnitTest.java:209)
>
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda
> expression in org.apache.geode.management.RegionManagementDUnitTest that uses
> int
> Expected size:<6> but was:<4> in:
>
> <[javax.management.Notification[source=172.17.0.28(265)-32770][type=gemfire.distributedsystem.cache.region.created][message=Region
> Created With Name /MANAGEMENT_FIXED_PR],
>
> javax.management.Notification[source=172.17.0.28(276)-32771][type=gemfire.distributedsystem.cache.region.created][message=Region
> Created With Name /MANAGEMENT_FIXED_PR],
>
> javax.management.Notification[source=172.17.0.28(265)-32770][type=gemfire.distributedsystem.cache.region.closed][message=Region
> Destroyed/Closed With Name /MANAGEMENT_FIXED_PR],
>
> javax.management.Notification[source=172.17.0.28(276)-32771][type=gemfire.distributedsystem.cache.region.closed][message=Region
> Destroyed/Closed With Name /MANAGEMENT_FIXED_PR]]> within 2 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at
> org.apache.geode.management.RegionManagementDUnitTest.lambda$verifyMemberNotifications$3d0515b3$1(RegionManagementDUnitTest.java:566)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5632) Tests should prefer imporing org.assertj.core.api.Assertions instead of AssertionsForClassTypes
Kirk Lund created GEODE-5632: Summary: Tests should prefer imporing org.assertj.core.api.Assertions instead of AssertionsForClassTypes Key: GEODE-5632 URL: https://issues.apache.org/jira/browse/GEODE-5632 Project: Geode Issue Type: Bug Components: tests Reporter: Kirk Lund * JdbcWriterTest contains _import static org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5632) Tests should prefer imporing org.assertj.core.api.Assertions instead of AssertionsForClassTypes
[ https://issues.apache.org/jira/browse/GEODE-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5632: Assignee: Kirk Lund > Tests should prefer imporing org.assertj.core.api.Assertions instead of > AssertionsForClassTypes > --- > > Key: GEODE-5632 > URL: https://issues.apache.org/jira/browse/GEODE-5632 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > * JdbcWriterTest contains _import static > org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5632) Tests should prefer imporing org.assertj.core.api.Assertions instead of AssertionsForClassTypes
[ https://issues.apache.org/jira/browse/GEODE-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5632: - Description: The following tests contain _import static org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_: * JdbcWriterTest * JdbcAsyncWriterTest * QueueConnectionImplJUnitTest * GemFireBasicDataSourceJUnitTest was: * JdbcWriterTest contains _import static org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_ > Tests should prefer imporing org.assertj.core.api.Assertions instead of > AssertionsForClassTypes > --- > > Key: GEODE-5632 > URL: https://issues.apache.org/jira/browse/GEODE-5632 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > The following tests contain _import static > org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_: > * JdbcWriterTest > * JdbcAsyncWriterTest > * QueueConnectionImplJUnitTest > * GemFireBasicDataSourceJUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5632) Tests should prefer imporing org.assertj.core.api.Assertions instead of AssertionsForClassTypes
[ https://issues.apache.org/jira/browse/GEODE-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5632: -- Labels: pull-request-available (was: ) > Tests should prefer imporing org.assertj.core.api.Assertions instead of > AssertionsForClassTypes > --- > > Key: GEODE-5632 > URL: https://issues.apache.org/jira/browse/GEODE-5632 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > The following tests contain _import static > org.assertj.core.api.AssertionsForClassTypes.assertThatThrownBy;_: > * JdbcWriterTest > * JdbcAsyncWriterTest > * QueueConnectionImplJUnitTest > * GemFireBasicDataSourceJUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5633) PR pipelines deployed by meta should include fork name AND branch name
Finn Southerland created GEODE-5633: --- Summary: PR pipelines deployed by meta should include fork name AND branch name Key: GEODE-5633 URL: https://issues.apache.org/jira/browse/GEODE-5633 Project: Geode Issue Type: Task Components: ci Reporter: Finn Southerland The name for pr pipelines created on forks currently is `pr-<>`. This is inconsistent with the other pipelines and risks naming collisions. This should be easy to fix as the name is only referenced on creation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5617) Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
[
https://issues.apache.org/jira/browse/GEODE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590952#comment-16590952
]
ASF subversion and git services commented on GEODE-5617:
Commit 9be422c93f2dfcaf2ff719b760fe33881d39ba2b in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9be422c ]
GEODE-5617: FIxing a race in AutoBalancerJUnitTest
This test asserted that execute was invoked exactly twice by a
background timer task. But that task could invoke execute more times
than that if the main test thread is slow.
> Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
> --
>
> Key: GEODE-5617
> URL: https://issues.apache.org/jira/browse/GEODE-5617
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed in CI:
> {noformat}
> org.apache.geode.cache.util.AutoBalancerJUnitTest > testAuditorInvocation
> FAILED
> unexpected invocation: oobAuditor.execute()
> expectations:
> expected once, already invoked 1 time: oobAuditor.init(an instance of
> java.util.Properties)
> expected exactly 2 times, already invoked 2 times: oobAuditor.execute()
> allowed, already invoked 3 times: timeProvider.currentTimeMillis();
> returnTime
> what happened before this:
> oobAuditor.init(<{schedule=* 0/30 * * * ?}>)
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/Build/builds/356
> This test suspiciously has a 1 second timeout, which may be why it is failing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5617) Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
[
https://issues.apache.org/jira/browse/GEODE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-5617.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> Flaky Test AutoBalancerJUnitTest.testAuditorInvocation
> --
>
> Key: GEODE-5617
> URL: https://issues.apache.org/jira/browse/GEODE-5617
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed in CI:
> {noformat}
> org.apache.geode.cache.util.AutoBalancerJUnitTest > testAuditorInvocation
> FAILED
> unexpected invocation: oobAuditor.execute()
> expectations:
> expected once, already invoked 1 time: oobAuditor.init(an instance of
> java.util.Properties)
> expected exactly 2 times, already invoked 2 times: oobAuditor.execute()
> allowed, already invoked 3 times: timeProvider.currentTimeMillis();
> returnTime
> what happened before this:
> oobAuditor.init(<{schedule=* 0/30 * * * ?}>)
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> oobAuditor.execute()
> timeProvider.currentTimeMillis()
> {noformat}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/Build/builds/356
> This test suspiciously has a 1 second timeout, which may be why it is failing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5627) ConcurrencyTestHelper fails with tests that don't use it
[
https://issues.apache.org/jira/browse/GEODE-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591003#comment-16591003
]
ASF subversion and git services commented on GEODE-5627:
Commit cfa7ca5da13a07ca99562b3bfdf32efe1c1414e7 in geode's branch
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cfa7ca5 ]
GEODE-5627: ConcurrencyRule passes when not used. (#2370)
Before this, if ConcurrencyRule was used for a test it failed because
`allthreadsExecuted` was `false`.
Also delegate to the non-default constructor with the default
constructor.
> ConcurrencyTestHelper fails with tests that don't use it
>
>
> Key: GEODE-5627
> URL: https://issues.apache.org/jira/browse/GEODE-5627
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The field {{allThreadsExecuted}} is set to {{false}} when the test runs, so
> if the helper doesn't see any use at all it will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5627) ConcurrencyTestHelper fails with tests that don't use it
[
https://issues.apache.org/jira/browse/GEODE-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan resolved GEODE-5627.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> ConcurrencyTestHelper fails with tests that don't use it
>
>
> Key: GEODE-5627
> URL: https://issues.apache.org/jira/browse/GEODE-5627
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The field {{allThreadsExecuted}} is set to {{false}} when the test runs, so
> if the helper doesn't see any use at all it will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5631) failedBatchRemovalMessageKeys never cleared
[ https://issues.apache.org/jira/browse/GEODE-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5631: -- Labels: pull-request-available (was: ) > failedBatchRemovalMessageKeys never cleared > --- > > Key: GEODE-5631 > URL: https://issues.apache.org/jira/browse/GEODE-5631 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: nabarun >Priority: Major > Labels: pull-request-available > > *+Experiment setup+*: > * Region A created with async event listener attached to it > * For every event processed by the async listener, a new entry is put into > another region, Region B. > * There is a client which does 1 million operations on 1500 keys on Region A. > [to trigger conflation.] > * 3 servers, 1 locator and 1 client. > +*Issue:*+ > It was confirmed that after upgrading to 1.6.0 , we saw an increase in the > memory footprint after all operations are completed. > +*Cause:*+ > * We had a data structure to store all the queue removal messages that comes > in when the secondary is in process of GII, called > failedBatchRemovalMessageKeys. > * Two removal messages were sent to the secondary for a single event, one > from the processor which was processing the event and another from the > conflation thread which conflated the event and hence wants the secondary to > remove it. > * Of the two messages whichever comes first, it removes the event from the > queue. > * When the second message comes in, and we try to remove it from the queue, > it hits an EntryNotFoundException. This makes the message think that > secondary is in GII and hence stores it in the failedBatchRemovalMessageKeys, > and expects that when GII is complete, this message will be processed. > * But GII was already done long before, and this data structure, > failedBatchRemovalMessageKeys keeps storing messages which are never removed > and hence a large memory footprint. > +*Fix:*+ > The data structure failedBatchRemovalMessageKeys is not used anymore if it > was already processed once, as GII happens once in a server’s lifecycle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
