[jira] [Reopened] (GEODE-5292) Replace with concurrent clear and destroy leaks off heap memory
[ https://issues.apache.org/jira/browse/GEODE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reopened GEODE-5292: -- > Replace with concurrent clear and destroy leaks off heap memory > --- > > Key: GEODE-5292 > URL: https://issues.apache.org/jira/browse/GEODE-5292 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > For a region that has been configured with off-heap storage and overflow to > disk, memory can be leaked if > * region clear > * region destroy > * region replace > all happen concurrently. The root cause appears to be region clear modifying > entries for values stored on disk without synchronizing the entries. This > prevents replace from freeing the off-heap memory for the new value when the > replace fails because the region is being destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5292) Replace with concurrent clear and destroy leaks off heap memory
[ https://issues.apache.org/jira/browse/GEODE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5292: Assignee: Dan Smith > Replace with concurrent clear and destroy leaks off heap memory > --- > > Key: GEODE-5292 > URL: https://issues.apache.org/jira/browse/GEODE-5292 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > For a region that has been configured with off-heap storage and overflow to > disk, memory can be leaked if > * region clear > * region destroy > * region replace > all happen concurrently. The root cause appears to be region clear modifying > entries for values stored on disk without synchronizing the entries. This > prevents replace from freeing the off-heap memory for the new value when the > replace fails because the region is being destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5292) Replace with concurrent clear and destroy leaks off heap memory
[ https://issues.apache.org/jira/browse/GEODE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5292: - Labels: pull-request-available swat (was: pull-request-available) > Replace with concurrent clear and destroy leaks off heap memory > --- > > Key: GEODE-5292 > URL: https://issues.apache.org/jira/browse/GEODE-5292 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > For a region that has been configured with off-heap storage and overflow to > disk, memory can be leaked if > * region clear > * region destroy > * region replace > all happen concurrently. The root cause appears to be region clear modifying > entries for values stored on disk without synchronizing the entries. This > prevents replace from freeing the off-heap memory for the new value when the > replace fails because the region is being destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5378. -- Resolution: Fixed Fixed by 2c3a7b120b7727e3e5a46aaa8bad1fbb7510b92c > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5383) DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5383:
Assignee: Helena Bales (was: Dan Smith)
> DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
>
>
> Key: GEODE-5383
> URL: https://issues.apache.org/jira/browse/GEODE-5383
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Helena Bales
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This test failed in a recent CI run on 4ec28788d7.
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest$$Lambda$43/701247168.run
> in VM 4 running on Host 747efeba1777 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.testPartitionedRegionParallelPropagation(DistTXWANDUnitTest.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.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.$Proxy1.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
[jira] [Updated] (GEODE-5389) Add a job to generate a code coverage report
[
https://issues.apache.org/jira/browse/GEODE-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5389:
-
Description:
Add a job to the concourse pipeline that generates two code coverage reports
* A code coverage report just from the unit tests (The test task)
* A code coverage report from all of the tests (test, integrationTest,
distributedTest, acceptanceTest, ...?)
There should be support in the gradle build already to run tests with code
coverage enabled and generate the report. However, this code may not have been
tested recently so it's possible it no longer works. This is how it used to work
{code}
#Run the tests with code coverage enabled
./gradlew -PcodeCoverage test distributedTest integrationTest
#Generate a report of the coverage from all tests
./gradlew -PcodeCoverage jacocoOverallTestReport
#Generate a report of the coverage from just the unit tests
./gradlew -PcodeCoverage jacocoTestReport
{code}
was:
We want to add to jobs
Add a task to the develop pipeline to generate a code coverage report from all
of the test jobs.
Q
> Add a job to generate a code coverage report
>
>
> Key: GEODE-5389
> URL: https://issues.apache.org/jira/browse/GEODE-5389
> Project: Geode
> Issue Type: Task
> Components: tests
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> Add a job to the concourse pipeline that generates two code coverage reports
> * A code coverage report just from the unit tests (The test task)
> * A code coverage report from all of the tests (test, integrationTest,
> distributedTest, acceptanceTest, ...?)
> There should be support in the gradle build already to run tests with code
> coverage enabled and generate the report. However, this code may not have
> been tested recently so it's possible it no longer works. This is how it used
> to work
> {code}
> #Run the tests with code coverage enabled
> ./gradlew -PcodeCoverage test distributedTest integrationTest
> #Generate a report of the coverage from all tests
> ./gradlew -PcodeCoverage jacocoOverallTestReport
> #Generate a report of the coverage from just the unit tests
> ./gradlew -PcodeCoverage jacocoTestReport
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5389) Add a task to generate a code coverage report
[ https://issues.apache.org/jira/browse/GEODE-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5389: - Description: We want to add to jobs Add a task to the develop pipeline to generate a code coverage report from all of the test jobs. Q was:Add a task to the develop pipeline to generate a code coverage report from all of the test jobs. > Add a task to generate a code coverage report > - > > Key: GEODE-5389 > URL: https://issues.apache.org/jira/browse/GEODE-5389 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > We want to add to jobs > Add a task to the develop pipeline to generate a code coverage report from > all of the test jobs. > Q -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5389) Add a job to generate a code coverage report
[ https://issues.apache.org/jira/browse/GEODE-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5389: - Summary: Add a job to generate a code coverage report (was: Add a task to generate a code coverage report) > Add a job to generate a code coverage report > > > Key: GEODE-5389 > URL: https://issues.apache.org/jira/browse/GEODE-5389 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > We want to add to jobs > Add a task to the develop pipeline to generate a code coverage report from > all of the test jobs. > Q -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5401) Client transaction should not be expired once it is failed over
Eric Shu created GEODE-5401: --- Summary: Client transaction should not be expired once it is failed over Key: GEODE-5401 URL: https://issues.apache.org/jira/browse/GEODE-5401 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu When a client is disconnected from the server, the client's originated transactions are scheduled to be expired. However, when the client transaction failed over, the expire transaction task is not cancelled. If transaction is not finished/committed within the timeout period (transactionTimeToLive default to 180 seconds), the transaction will be expired. The consequence is that only part of the transaction gets committed. The expire transaction task will close the transaction and remove it from the hosted txstates map removing the existing operations. The subsequent operations will starts a new transaction -- only the operations afterwards will be recored and committed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5401) Client transaction should not be expired once it is failed over
[ https://issues.apache.org/jira/browse/GEODE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-5401: Affects Version/s: 1.7.0 1.1.0 1.2.0 1.3.0 1.4.0 1.5.0 1.6.0 > Client transaction should not be expired once it is failed over > --- > > Key: GEODE-5401 > URL: https://issues.apache.org/jira/browse/GEODE-5401 > Project: Geode > Issue Type: Bug > Components: transactions >Affects Versions: 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0 >Reporter: Eric Shu >Priority: Major > > When a client is disconnected from the server, the client's originated > transactions are scheduled to be expired. However, when the client > transaction failed over, the expire transaction task is not cancelled. If > transaction is not finished/committed within the timeout period > (transactionTimeToLive default to 180 seconds), the transaction will be > expired. > The consequence is that only part of the transaction gets committed. The > expire transaction task will close the transaction and remove it from the > hosted txstates map removing the existing operations. The subsequent > operations will starts a new transaction -- only the operations afterwards > will be recored and committed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5281) Race between registering and unregistering CustomMXBeans in concurrent thread may result in NPE
[
https://issues.apache.org/jira/browse/GEODE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535433#comment-16535433
]
ASF subversion and git services commented on GEODE-5281:
Commit 29c71c96f2933e8380e412e9d14b42beb30ae96b in geode's branch
refs/heads/feature/GEODE-QueryProvider from [~balesh2]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=29c71c9 ]
GEODE-5281: replicate failure and fix bug (#2096)
* GEODE-5281: replicate failure and fix bug
- replicate the bad timing using a DUnit test
- fix the bug by only doing one lookup of MBeans
- add more tests
- fix potential NPE in waiting for regions to be ready on servers
Co-authored-by: Kenneth Howe
* add TestingOnly annotation to setter
add a TestingOnly annotation to setter for ProxyFactory in the
FederatingManager for injecting test spies.
> Race between registering and unregistering CustomMXBeans in concurrent thread
> may result in NPE
> ---
>
> Key: GEODE-5281
> URL: https://issues.apache.org/jira/browse/GEODE-5281
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Stack trace from an example of the unexpected NullPointerException in
> {{MBeanProxyFactory.createProxy()}}
> {code:java}
> [warning 2018/02/03 17:32:13.561 UTC
> managing_1_gemfire2_79a23c4a-f5e3-4c9f-6455-149c397ce13c_38199
> tid=0x5e] Create Proxy failed for
> GemFire:type=CustomMXBean213,member=locator_managing_gemfire1_79a23c4a-f5e3-4c9f-6455-149c397ce13c_37116
> with exception null
> java.lang.NullPointerException
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:83)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The registering thread enters
> {code}
> public void createProxy(DistributedMember member, ObjectName objectName,
> Region monitoringRegion, Object newVal) {
> {code}
> with the {{objectName}} existing in the {{_monitoringRegion}}. A few lines
> further the entry is retrieved from the region, but is now {{null}} due to it
> being removed by the unregistering thread.
> {code}
> String name = objectName.toString();
> FederationComponent federationComponent = (FederationComponent)
> monitoringRegion.get(name);
> String interfaceClassName =
> federationComponent.getMBeanInterfaceClass();
> {code}
> {{federationComponent == null}} results in the NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4803) CI: ConcurrentDeployDUnitTest fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535437#comment-16535437 ] ASF subversion and git services commented on GEODE-4803: Commit 2ba81f6e78e49b515e9271695f160b42218988b8 in geode's branch refs/heads/feature/GEODE-QueryProvider from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ba81f6 ] GEODE-4803: remove flaky category (#2108) Co-authored-by: Finn Southerland > CI: ConcurrentDeployDUnitTest fails intermittently > -- > > Key: GEODE-4803 > URL: https://issues.apache.org/jira/browse/GEODE-4803 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Assignee: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Fix For: 1.7.0 > > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest.html > > Time Spent: 40m > Remaining Estimate: 0h > > The test concurrently runs iterations of gfsh commands to deploy and undeploy > .jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for > the gfsh clients to finish. Sometimes in the CI pipelines one or more of the > clients don't complete their iterations within the 5 minute wait. > Test timing and/or client iterations needs to be adjusted for variations in > machine and network speed. > Also see GEODE-800. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535435#comment-16535435 ] ASF subversion and git services commented on GEODE-5378: Commit 5dfc65c9ebd4f4908994674d4b7abca0e659f902 in geode's branch refs/heads/feature/GEODE-QueryProvider from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dfc65c ] Merge pull request #2110 from smgoller/GEODE-5378 [GEODE-5378] Adjust initdocker script to implement workaround. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5341) Improve debug logging in BackupTask
[ https://issues.apache.org/jira/browse/GEODE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535429#comment-16535429 ] ASF subversion and git services commented on GEODE-5341: Commit 377529c0c1a5b9cd162e22d73154b388755ee8f5 in geode's branch refs/heads/feature/GEODE-QueryProvider from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=377529c ] GEODE-5341: Improve debug logging in BackupTask > Improve debug logging in BackupTask > --- > > Key: GEODE-5341 > URL: https://issues.apache.org/jira/browse/GEODE-5341 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > I need to see log statements about the locks used in BackupTask in order to > debug backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5281) Race between registering and unregistering CustomMXBeans in concurrent thread may result in NPE
[
https://issues.apache.org/jira/browse/GEODE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535432#comment-16535432
]
ASF subversion and git services commented on GEODE-5281:
Commit 29c71c96f2933e8380e412e9d14b42beb30ae96b in geode's branch
refs/heads/feature/GEODE-QueryProvider from [~balesh2]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=29c71c9 ]
GEODE-5281: replicate failure and fix bug (#2096)
* GEODE-5281: replicate failure and fix bug
- replicate the bad timing using a DUnit test
- fix the bug by only doing one lookup of MBeans
- add more tests
- fix potential NPE in waiting for regions to be ready on servers
Co-authored-by: Kenneth Howe
* add TestingOnly annotation to setter
add a TestingOnly annotation to setter for ProxyFactory in the
FederatingManager for injecting test spies.
> Race between registering and unregistering CustomMXBeans in concurrent thread
> may result in NPE
> ---
>
> Key: GEODE-5281
> URL: https://issues.apache.org/jira/browse/GEODE-5281
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Stack trace from an example of the unexpected NullPointerException in
> {{MBeanProxyFactory.createProxy()}}
> {code:java}
> [warning 2018/02/03 17:32:13.561 UTC
> managing_1_gemfire2_79a23c4a-f5e3-4c9f-6455-149c397ce13c_38199
> tid=0x5e] Create Proxy failed for
> GemFire:type=CustomMXBean213,member=locator_managing_gemfire1_79a23c4a-f5e3-4c9f-6455-149c397ce13c_37116
> with exception null
> java.lang.NullPointerException
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:83)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The registering thread enters
> {code}
> public void createProxy(DistributedMember member, ObjectName objectName,
> Region monitoringRegion, Object newVal) {
> {code}
> with the {{objectName}} existing in the {{_monitoringRegion}}. A few lines
> further the entry is retrieved from the region, but is now {{null}} due to it
> being removed by the unregistering thread.
> {code}
> String name = objectName.toString();
> FederationComponent federationComponent = (FederationComponent)
> monitoringRegion.get(name);
> String interfaceClassName =
> federationComponent.getMBeanInterfaceClass();
> {code}
> {{federationComponent == null}} results in the NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5385) hang trying to create a bucket
[ https://issues.apache.org/jira/browse/GEODE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535438#comment-16535438 ] ASF subversion and git services commented on GEODE-5385: Commit dbdbd7a83f70340ab3a8b76823b04780c0b29430 in geode's branch refs/heads/feature/GEODE-QueryProvider from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dbdbd7a ] GEODE-5385: hang trying to create a bucket We now look for a ForceReattemptException when destroying a partitioned region. This prevents a region ID skew that can occur if another node is still initializing its region and is not yet ready to destroy it. I've reenabled the PRSanityCheckMessage that watches for skews like this and reports them. This used to be enabled by default but somehow was disabled a long time ago. This closes #2109 > hang trying to create a bucket > -- > > Key: GEODE-5385 > URL: https://issues.apache.org/jira/browse/GEODE-5385 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It's possible for partitioned region bucket allocation to hang even though > there appears to be plenty of storage available. This can happen if one > server is creating the partitioned region at the same time the region is > being destroyed by another server. > The server creating the partitioned region will send a > ForceReattemptException back to the server destroying the region and that > exception is ignored. The server creating the PR will then be stuck with a > region having a dangling ID that has been removed from the PR metadata > region. If another server then recreates the PR it will assign a new ID to > it and the servers will have skewed IDs. The IDs are sent in partitioned > region messages such as manage-bucket. > The distribution advisors don't recognize that there is a skew and our logs > show nothing about it because a safety mechanism was accidentally turned off > by an engineer in PRSanityCheckMessage. This message performs a check of the > IDs in the servers to make sure they're consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535436#comment-16535436 ] ASF subversion and git services commented on GEODE-5378: Commit 5dfc65c9ebd4f4908994674d4b7abca0e659f902 in geode's branch refs/heads/feature/GEODE-QueryProvider from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dfc65c ] Merge pull request #2110 from smgoller/GEODE-5378 [GEODE-5378] Adjust initdocker script to implement workaround. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5355) Refactor backup code to unify it as one API and make it testable
[ https://issues.apache.org/jira/browse/GEODE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535430#comment-16535430 ] ASF subversion and git services commented on GEODE-5355: Commit bb85e7c32a9cba9717fa22907997ca3c3bdab28a in geode's branch refs/heads/feature/GEODE-QueryProvider from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bb85e7c ] GEODE-5355: Remove BackupUtil and BackupDataStoreHelper * Rename *Operation classes to *Step * Introduce new BackupOperation as internal API for launching backup > Refactor backup code to unify it as one API and make it testable > > > Key: GEODE-5355 > URL: https://issues.apache.org/jira/browse/GEODE-5355 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > BackupUtil and BackupDataStoreHelper are collections of static methods that > aren't easy to test with mocks. > JMX, GFSH and the deprecated Admin API treat BackupUtil and > BackupDataStoreHelper as entry points to the Backup API whereas BackupService > is presented to the User as the only API. We should have one class > (BackupService) be the single entry point to performing a Backup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535434#comment-16535434 ] ASF subversion and git services commented on GEODE-5378: Commit 2c3a7b120b7727e3e5a46aaa8bad1fbb7510b92c in geode's branch refs/heads/feature/GEODE-QueryProvider from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2c3a7b1 ] [GEODE-5378] Adjust initdocker script to implement workaround. Current versions of docker have an issue under linux causing it to fail. This workaround addresses the problem. Once Docker fixes the problem on their end this might need to be removed. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5355) Refactor backup code to unify it as one API and make it testable
[ https://issues.apache.org/jira/browse/GEODE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535431#comment-16535431 ] ASF subversion and git services commented on GEODE-5355: Commit 935743586a874dce4b4b780aefe0c653d42f8902 in geode's branch refs/heads/feature/GEODE-QueryProvider from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9357435 ] GEODE-5355: Fix apache license header of new backup classes > Refactor backup code to unify it as one API and make it testable > > > Key: GEODE-5355 > URL: https://issues.apache.org/jira/browse/GEODE-5355 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > BackupUtil and BackupDataStoreHelper are collections of static methods that > aren't easy to test with mocks. > JMX, GFSH and the deprecated Admin API treat BackupUtil and > BackupDataStoreHelper as entry points to the Backup API whereas BackupService > is presented to the User as the only API. We should have one class > (BackupService) be the single entry point to performing a Backup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed
Eric Shu created GEODE-5400:
---
Summary: JTA transaction locks are not released if the jta
originator is crashed after beforeCompletion is executed
Key: GEODE-5400
URL: https://issues.apache.org/jira/browse/GEODE-5400
Project: Geode
Issue Type: Bug
Components: transactions
Reporter: Eric Shu
Currently when the JTA originator is departed, a membership listener will be
invoked to clean the transactions initiated by the departed member. However, if
the member is departed after JTA beforeCompletion is run, the locks are not
released.
Here is a distributed test failure showing new transaction could not finish
even though the JTA transaction was closed/removed after the memberDeparted
invocation.
{noformat}
rg.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tx.ClientServerJTAFailoverDistributedTest$$Lambda$26/573958827.run
in VM 0 running on Host 10.118.20.64 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
at
org.apache.geode.internal.cache.tx.ClientServerJTAFailoverDistributedTest.locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted(ClientServerJTAFailoverDistributedTest.java:284)
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.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60)
at
org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60)
at
org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60)
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.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.apache.geode.cache.CommitConflictException: The key 1 in
region
/__PR/_B__ClientServerJTAFailoverDistributedTest__locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted__region_0
was being modified by another transaction locally.
at
org.apache.geode.internal.cache.TXReservationMgr.checkSetForConflict(TXReservationMgr.java:107)
at
org.apache.geode.internal.cache.TXReservationMgr.checkForConflict(TXReservationMgr.java:77)
at
org.apache.geode.internal.cache.TXReservationMgr.makeReservation(TXReservationMgr.java:56)
at
org.apache.geode.internal.cache.TXLockRequest.txLocalLock(TXLockRequest.java:151)
at
org.apache.geode.internal.cache.TXLockRequest.obtain(TXLockRequest.java:84)
at
org.apache.geode.internal.cache.TXState.reserveAndCheck(TXState.java:342)
at org.apache.geode.internal.cache.TXState.commit(TXState.java:413)
at
org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:226)
at
org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:413)
[jira] [Assigned] (GEODE-567) CI Failure: FixedPartitioningDUnitTest.testBug43283
[
https://issues.apache.org/jira/browse/GEODE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-567:
---
Assignee: (was: Darrel Schneider)
> CI Failure: FixedPartitioningDUnitTest.testBug43283
> ---
>
> Key: GEODE-567
> URL: https://issues.apache.org/jira/browse/GEODE-567
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Priority: Major
> Labels: CI, Flaky, swat
>
> Geode_develop_DistributedTests
> Private Build #571 (Nov 14, 2015 7:09:09 AM)
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> {noformat}
> junit.framework.AssertionFailedError: exception thrown is not
> PartitionNotAvailableException
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:545)
> {noformat}
> Standard Output shows:
> {noformat}
> Previously run tests: [ReliableMessagingDUnitTest,
> CacheServerTransactionsDUnitTest, ForceInvalidateOffHeapEvictionDUnitTest,
> UnregisterInterestDUnitTest, InterestRegrListenerDUnitTest,
> EventIDVerificationDUnitTest, DataSerializerPropogationDUnitTest,
> CacheServerTransactionsSelectorDUnitTest, Bug36805DUnitTest,
> PersistentColocatedPartitionedRegionDUnitTest, Bug51400DUnitTest,
> PersistPRKRFDUnitTest, StreamingPartitionOperationOneDUnitTest,
> Bug47388DUnitTest, PartitionedRegionMetaDataCleanupDUnitTest,
> PersistentPartitionedRegionOldConfigDUnitTest,
> PartitionedRegionLoaderWriterDUnitTest, ElidedPutAllDUnitTest,
> ShutdownAllDUnitTest, Bug39356DUnitTest, PartitionResolverDUnitTest,
> Bug43684DUnitTest, StreamingPartitionOperationManyDUnitTest,
> PersistentPartitionedRegionWithTransactionDUnitTest,
> PersistentPartitionedRegionDUnitTest,
> FixedPartitioningWithColocationAndPersistenceDUnitTest,
> FixedPartitioningDUnitTest]
> {noformat}
> Standard Error shows:
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningTestBase.putThorughAccessor_Immediate
> in VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:170)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:539)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
> at
>
[jira] [Updated] (GEODE-5399) Remove the flaky category
[ https://issues.apache.org/jira/browse/GEODE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5399: - Description: Based on discussion on the dev list, we want to completely remove the flaky category. We should * Run all flaky tests and establish which ones are still failing (GEODE-5371). Update the associated JIRAs * Remove the Flaky category from all tests marked as flaky * Remove the flakyTest target from gradle * Remove the FlakyTest job from the concourse pipeline. Relevant discussion on the dev list https://markmail.org/thread/n4boyumlzvhrlqpq was: Based on discussion on the dev list, we want to completely remove the flaky category. We should * Run all flaky tests and establish which ones are still failing (GEODE-5371). Update the associated JIRAs * Remove the Flaky category from all tests marked as flaky * Remove the flakyTest target from gradle * Remove the FlakyTest job from the concourse pipeline. > Remove the flaky category > - > > Key: GEODE-5399 > URL: https://issues.apache.org/jira/browse/GEODE-5399 > Project: Geode > Issue Type: Task >Reporter: Dan Smith >Priority: Major > Labels: swat > > Based on discussion on the dev list, we want to completely remove the flaky > category. > We should > * Run all flaky tests and establish which ones are still failing > (GEODE-5371). Update the associated JIRAs > * Remove the Flaky category from all tests marked as flaky > * Remove the flakyTest target from gradle > * Remove the FlakyTest job from the concourse pipeline. > Relevant discussion on the dev list > https://markmail.org/thread/n4boyumlzvhrlqpq -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5399) Remove the flaky category
Dan Smith created GEODE-5399: Summary: Remove the flaky category Key: GEODE-5399 URL: https://issues.apache.org/jira/browse/GEODE-5399 Project: Geode Issue Type: Task Reporter: Dan Smith Based on discussion on the dev list, we want to completely remove the flaky category. We should * Run all flaky tests and establish which ones are still failing (GEODE-5371). Update the associated JIRAs * Remove the Flaky category from all tests marked as flaky * Remove the flakyTest target from gradle * Remove the FlakyTest job from the concourse pipeline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5399) Remove the flaky category
[ https://issues.apache.org/jira/browse/GEODE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5399: - Labels: swat (was: ) > Remove the flaky category > - > > Key: GEODE-5399 > URL: https://issues.apache.org/jira/browse/GEODE-5399 > Project: Geode > Issue Type: Task >Reporter: Dan Smith >Priority: Major > Labels: swat > > Based on discussion on the dev list, we want to completely remove the flaky > category. > We should > * Run all flaky tests and establish which ones are still failing > (GEODE-5371). Update the associated JIRAs > * Remove the Flaky category from all tests marked as flaky > * Remove the flakyTest target from gradle > * Remove the FlakyTest job from the concourse pipeline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-567) CI Failure: FixedPartitioningDUnitTest.testBug43283
[
https://issues.apache.org/jira/browse/GEODE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-567:
Labels: CI Flaky swat (was: CI Flaky)
> CI Failure: FixedPartitioningDUnitTest.testBug43283
> ---
>
> Key: GEODE-567
> URL: https://issues.apache.org/jira/browse/GEODE-567
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: CI, Flaky, swat
>
> Geode_develop_DistributedTests
> Private Build #571 (Nov 14, 2015 7:09:09 AM)
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> {noformat}
> junit.framework.AssertionFailedError: exception thrown is not
> PartitionNotAvailableException
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:545)
> {noformat}
> Standard Output shows:
> {noformat}
> Previously run tests: [ReliableMessagingDUnitTest,
> CacheServerTransactionsDUnitTest, ForceInvalidateOffHeapEvictionDUnitTest,
> UnregisterInterestDUnitTest, InterestRegrListenerDUnitTest,
> EventIDVerificationDUnitTest, DataSerializerPropogationDUnitTest,
> CacheServerTransactionsSelectorDUnitTest, Bug36805DUnitTest,
> PersistentColocatedPartitionedRegionDUnitTest, Bug51400DUnitTest,
> PersistPRKRFDUnitTest, StreamingPartitionOperationOneDUnitTest,
> Bug47388DUnitTest, PartitionedRegionMetaDataCleanupDUnitTest,
> PersistentPartitionedRegionOldConfigDUnitTest,
> PartitionedRegionLoaderWriterDUnitTest, ElidedPutAllDUnitTest,
> ShutdownAllDUnitTest, Bug39356DUnitTest, PartitionResolverDUnitTest,
> Bug43684DUnitTest, StreamingPartitionOperationManyDUnitTest,
> PersistentPartitionedRegionWithTransactionDUnitTest,
> PersistentPartitionedRegionDUnitTest,
> FixedPartitioningWithColocationAndPersistenceDUnitTest,
> FixedPartitioningDUnitTest]
> {noformat}
> Standard Error shows:
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningTestBase.putThorughAccessor_Immediate
> in VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:170)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:539)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown
[jira] [Reopened] (GEODE-567) CI Failure: FixedPartitioningDUnitTest.testBug43283
[
https://issues.apache.org/jira/browse/GEODE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reopened GEODE-567:
-
This reoccurred in a recent CI run
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/125
{noformat}
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest >
testBug43283 FAILED
java.lang.AssertionError: exception thrown is not
PartitionNotAvailableException
at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:497)
Caused by:
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$36/1378474319.run
in VM 3 running on Host d87a7b5c-b782-4947-4b37-4f631d22f321 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:493)
Caused by:
org.apache.geode.cache.PartitionedRegionStorageException: Unable to
find any members to host a bucket in the partitioned region. Advise you to
start enough data store nodes.
Partitioned Region name = /Quarter
Redundancy level set to 0
. Number of available data stores: 0
. Number successfully allocated = 0
. Data stores: []
. Data stores successfully allocated: []
. Equivalent members: [10.254.0.34(8467):32772,
10.254.0.34(8490):32773, 10.254.0.34(8455):32770,
10.254.0.34(8460):32771, 10.254.0.34(8359:locator):32769]
at
org.apache.geode.internal.cache.PRHARedundancyProvider.insufficientStores(PRHARedundancyProvider.java:306)
at
org.apache.geode.internal.cache.PRHARedundancyProvider.createBucketOnDataStore(PRHARedundancyProvider.java:478)
at
org.apache.geode.internal.cache.PartitionedRegion.createBucket(PartitionedRegion.java:3334)
at
org.apache.geode.internal.cache.PartitionedRegion.virtualPut(PartitionedRegion.java:2075)
at
org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:152)
at
org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5086)
at
org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1618)
at
org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1605)
at
org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:413)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningTestBase.putThorughAccessor_Immediate(FixedPartitioningTestBase.java:231)
at
org.apache.geode.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.lambda$testBug43283$bb17a952$10(FixedPartitioningDUnitTest.java:493)
{noformat}
> CI Failure: FixedPartitioningDUnitTest.testBug43283
> ---
>
> Key: GEODE-567
> URL: https://issues.apache.org/jira/browse/GEODE-567
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
> Labels: CI, Flaky
>
> Geode_develop_DistributedTests
> Private Build #571 (Nov 14, 2015 7:09:09 AM)
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> {noformat}
> junit.framework.AssertionFailedError: exception thrown is not
> PartitionNotAvailableException
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:545)
> {noformat}
> Standard Output shows:
> {noformat}
> Previously run tests: [ReliableMessagingDUnitTest,
> CacheServerTransactionsDUnitTest, ForceInvalidateOffHeapEvictionDUnitTest,
> UnregisterInterestDUnitTest, InterestRegrListenerDUnitTest,
> EventIDVerificationDUnitTest, DataSerializerPropogationDUnitTest,
> CacheServerTransactionsSelectorDUnitTest, Bug36805DUnitTest,
> PersistentColocatedPartitionedRegionDUnitTest, Bug51400DUnitTest,
> PersistPRKRFDUnitTest,
[jira] [Updated] (GEODE-5383) DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5383:
--
Labels: pull-request-available swat (was: swat)
> DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
>
>
> Key: GEODE-5383
> URL: https://issues.apache.org/jira/browse/GEODE-5383
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.html
>
>
> This test failed in a recent CI run on 4ec28788d7.
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest$$Lambda$43/701247168.run
> in VM 4 running on Host 747efeba1777 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.testPartitionedRegionParallelPropagation(DistTXWANDUnitTest.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.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.$Proxy1.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
[jira] [Assigned] (GEODE-4791) Update gradle version from 3.5.1 to 4.8
[ https://issues.apache.org/jira/browse/GEODE-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer reassigned GEODE-4791: Assignee: Jens Deppe (was: Udo Kohlmeyer) > Update gradle version from 3.5.1 to 4.8 > --- > > Key: GEODE-4791 > URL: https://issues.apache.org/jira/browse/GEODE-4791 > Project: Geode > Issue Type: Improvement > Components: build, general >Reporter: Udo Kohlmeyer >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 3h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5381) Wrong name for code coverage in BUILDING.md
[ https://issues.apache.org/jira/browse/GEODE-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535365#comment-16535365 ] ASF subversion and git services commented on GEODE-5381: Commit 8e4eede5ca6241372a99dbf0d724a9017b28ff3f in geode-native's branch refs/heads/develop from [~mmartell] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8e4eede ] GEODE-5381: Fixed variable name for code coverage in BUILDIND.md (#310) > Wrong name for code coverage in BUILDING.md > > > Key: GEODE-5381 > URL: https://issues.apache.org/jira/browse/GEODE-5381 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > The BUILDING.md is saying to use -DUSE_CODE_COVERAGE=ON when configuring > geode-native for code coverage. Should be -DUSE_CPP_COVERAGE=ON instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535360#comment-16535360 ] ASF subversion and git services commented on GEODE-4728: Commit 98f101309b036c4910b10be6b77c7965912c0114 in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=98f1013 ] GEODE-4728: api docs - fix SystemProperties docs (#311) * GEODE-4728: api docs - fix SystemProperties docs > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 3h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535361#comment-16535361 ] ASF subversion and git services commented on GEODE-4728: Commit 98f101309b036c4910b10be6b77c7965912c0114 in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=98f1013 ] GEODE-4728: api docs - fix SystemProperties docs (#311) * GEODE-4728: api docs - fix SystemProperties docs > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 3h 40m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5398) Cleanup code and add unit tests for Backups
[ https://issues.apache.org/jira/browse/GEODE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5398: -- Labels: pull-request-available (was: ) > Cleanup code and add unit tests for Backups > --- > > Key: GEODE-5398 > URL: https://issues.apache.org/jira/browse/GEODE-5398 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > Some of the Backup classes are lacking unit tests including BackupOperation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5398) Cleanup code and add unit tests for Backups
Kirk Lund created GEODE-5398: Summary: Cleanup code and add unit tests for Backups Key: GEODE-5398 URL: https://issues.apache.org/jira/browse/GEODE-5398 Project: Geode Issue Type: Improvement Components: persistence Reporter: Kirk Lund Some of the Backup classes are lacking unit tests including BackupOperation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5398) Cleanup code and add unit tests for Backups
[ https://issues.apache.org/jira/browse/GEODE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5398: Assignee: Kirk Lund > Cleanup code and add unit tests for Backups > --- > > Key: GEODE-5398 > URL: https://issues.apache.org/jira/browse/GEODE-5398 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Some of the Backup classes are lacking unit tests including BackupOperation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-5394:
--
Assignee: Mark Hanson
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Mark Hanson
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5383) DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-5383:
Assignee: Dan Smith
> DistTXWANDUnitTest.testPartitionedRegionParallelPropagation failed in CI
>
>
> Key: GEODE-5383
> URL: https://issues.apache.org/jira/browse/GEODE-5383
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.html
>
>
> This test failed in a recent CI run on 4ec28788d7.
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest$$Lambda$43/701247168.run
> in VM 4 running on Host 747efeba1777 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.internal.cache.wan.disttx.DistTXWANDUnitTest.testPartitionedRegionParallelPropagation(DistTXWANDUnitTest.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.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.$Proxy1.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)
> at
>
[jira] [Resolved] (GEODE-5385) hang trying to create a bucket
[ https://issues.apache.org/jira/browse/GEODE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-5385. - Resolution: Fixed Fix Version/s: 1.7.0 > hang trying to create a bucket > -- > > Key: GEODE-5385 > URL: https://issues.apache.org/jira/browse/GEODE-5385 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It's possible for partitioned region bucket allocation to hang even though > there appears to be plenty of storage available. This can happen if one > server is creating the partitioned region at the same time the region is > being destroyed by another server. > The server creating the partitioned region will send a > ForceReattemptException back to the server destroying the region and that > exception is ignored. The server creating the PR will then be stuck with a > region having a dangling ID that has been removed from the PR metadata > region. If another server then recreates the PR it will assign a new ID to > it and the servers will have skewed IDs. The IDs are sent in partitioned > region messages such as manage-bucket. > The distribution advisors don't recognize that there is a skew and our logs > show nothing about it because a safety mechanism was accidentally turned off > by an engineer in PRSanityCheckMessage. This message performs a check of the > IDs in the servers to make sure they're consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5385) hang trying to create a bucket
[ https://issues.apache.org/jira/browse/GEODE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt closed GEODE-5385. --- > hang trying to create a bucket > -- > > Key: GEODE-5385 > URL: https://issues.apache.org/jira/browse/GEODE-5385 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It's possible for partitioned region bucket allocation to hang even though > there appears to be plenty of storage available. This can happen if one > server is creating the partitioned region at the same time the region is > being destroyed by another server. > The server creating the partitioned region will send a > ForceReattemptException back to the server destroying the region and that > exception is ignored. The server creating the PR will then be stuck with a > region having a dangling ID that has been removed from the PR metadata > region. If another server then recreates the PR it will assign a new ID to > it and the servers will have skewed IDs. The IDs are sent in partitioned > region messages such as manage-bucket. > The distribution advisors don't recognize that there is a skew and our logs > show nothing about it because a safety mechanism was accidentally turned off > by an engineer in PRSanityCheckMessage. This message performs a check of the > IDs in the servers to make sure they're consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5397) PulseAcceptanceAuthTest.testDropDownList
[
https://issues.apache.org/jira/browse/GEODE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5397:
-
Attachment: Test results - Class
org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest.html
> PulseAcceptanceAuthTest.testDropDownList
>
>
> Key: GEODE-5397
> URL: https://issues.apache.org/jira/browse/GEODE-5397
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest.html
>
>
> This test failed in CI - 29c71c96f2933e8380e412e9d14b42beb30ae96b
> {noformat}
> org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > testDropDownList
> FAILED
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '7705496b-0b32-4c8b-7588-8c513f288499', ip:
> '10.254.0.6', os.name: 'Linux', os.arch: 'amd64', os.version:
> '4.4.0-124-generic', java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: e0f2f1c3e11599a0254695ccd0227c3a
> {noformat}
>
> Other methods in this same class have failed in the past, see GEODE-5163.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5397) PulseAcceptanceAuthTest.testDropDownList
[
https://issues.apache.org/jira/browse/GEODE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5397:
-
Labels: swat (was: )
> PulseAcceptanceAuthTest.testDropDownList
>
>
> Key: GEODE-5397
> URL: https://issues.apache.org/jira/browse/GEODE-5397
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed in CI - 29c71c96f2933e8380e412e9d14b42beb30ae96b
> {noformat}
> org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > testDropDownList
> FAILED
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '7705496b-0b32-4c8b-7588-8c513f288499', ip:
> '10.254.0.6', os.name: 'Linux', os.arch: 'amd64', os.version:
> '4.4.0-124-generic', java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: e0f2f1c3e11599a0254695ccd0227c3a
> {noformat}
>
> Other methods in this same class have failed in the past, see GEODE-5163.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5397) PulseAcceptanceAuthTest.testDropDownList
Dan Smith created GEODE-5397:
Summary: PulseAcceptanceAuthTest.testDropDownList
Key: GEODE-5397
URL: https://issues.apache.org/jira/browse/GEODE-5397
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
This test failed in CI - 29c71c96f2933e8380e412e9d14b42beb30ae96b
{noformat}
org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > testDropDownList
FAILED
org.openqa.selenium.TimeoutException: timeout
(Session info: headless chrome=67.0.3396.99)
(Driver info: chromedriver=2.35.528139
(47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.9.1', revision: '63f7b50', time:
'2018-02-07T22:25:02.294Z'
System info: host: '7705496b-0b32-4c8b-7588-8c513f288499', ip:
'10.254.0.6', os.name: 'Linux', os.arch: 'amd64', os.version:
'4.4.0-124-generic', java.version: '1.8.0_171'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled:
false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy:
normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect:
true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour:
, unhandledPromptBehavior: , version: 67.0.3396.99, webStorageEnabled: true}
Session ID: e0f2f1c3e11599a0254695ccd0227c3a
{noformat}
Other methods in this same class have failed in the past, see GEODE-5163.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5163) Tests extending PulseAcceptanceTestBase are flaky
[ https://issues.apache.org/jira/browse/GEODE-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5163. -- Resolution: Won't Fix No information other than broken links is provided in this ticket. Closing. > Tests extending PulseAcceptanceTestBase are flaky > - > > Key: GEODE-5163 > URL: https://issues.apache.org/jira/browse/GEODE-5163 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Patrick Rhomberg >Priority: Major > > See these Concourse runs for more context: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/208 > org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > > testDataViewTreeMapPopUpData > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/217 > org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > > testClusterDetailsAndWidgets > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/231 > org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > > testClusterDetailsAndWidgets > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/249 > org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > > testClusterDetailsAndWidgets > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/256 > org.apache.geode.tools.pulse.ui.PulseAcceptanceAuthTest > > testClusterDetailsAndWidgets > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/258 > org.apache.geode.tools.pulse.ui.PulseAcceptanceNoAuthTest > > testClusterDetailsAndWidgets -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5396) PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5396:
-
Attachment: Test results - Class
org.apache.geode.tools.pulse.tests.ui.PulseAutomatedTest.html
> PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
>
>
> Key: GEODE-5396
> URL: https://issues.apache.org/jira/browse/GEODE-5396
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.tools.pulse.tests.ui.PulseAutomatedTest.html
>
>
> This test failed on 6a9a98b0bae561407230c5354fc95af0eae49268
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/131]
>
> {noformat}
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '3d781bee-3034-433d-6295-dafc92f1c71a', ip: '10.254.0.50',
> os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-124-generic',
> java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: 352271503dab2578e934f08be4bfdd50
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
> at
> org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
> at
> org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
> at
> org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:160)
> at
> org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
> at
> org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
> at
> org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:325)
> at
> org.apache.geode.tools.pulse.tests.rules.WebDriverRule.before(WebDriverRule.java:61)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
>
[jira] [Created] (GEODE-5396) PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
Dan Smith created GEODE-5396:
Summary: PulseAutomatedTest.clickRZGridMembersNavigationTest
failed in CI
Key: GEODE-5396
URL: https://issues.apache.org/jira/browse/GEODE-5396
Project: Geode
Issue Type: Bug
Components: pulse
Reporter: Dan Smith
This test failed on 6a9a98b0bae561407230c5354fc95af0eae49268
[https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/131]
{noformat}
org.openqa.selenium.TimeoutException: timeout
(Session info: headless chrome=67.0.3396.99)
(Driver info: chromedriver=2.35.528139
(47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.9.1', revision: '63f7b50', time:
'2018-02-07T22:25:02.294Z'
System info: host: '3d781bee-3034-433d-6295-dafc92f1c71a', ip: '10.254.0.50',
os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-124-generic',
java.version: '1.8.0_171'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled:
false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy:
normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect:
true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour:
, unhandledPromptBehavior: , version: 67.0.3396.99, webStorageEnabled: true}
Session ID: 352271503dab2578e934f08be4bfdd50
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
at
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
at
org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
at
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
at
org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
at
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:160)
at
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
at
org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:325)
at
org.apache.geode.tools.pulse.tests.rules.WebDriverRule.before(WebDriverRule.java:61)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at
[jira] [Assigned] (GEODE-5375) DlockAndTxlockRegressionTest hangs the DUnit pipeline
[ https://issues.apache.org/jira/browse/GEODE-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-5375: -- Assignee: Jinmei Liao > DlockAndTxlockRegressionTest hangs the DUnit pipeline > - > > Key: GEODE-5375 > URL: https://issues.apache.org/jira/browse/GEODE-5375 > Project: Geode > Issue Type: Sub-task > Components: ci >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/88] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/79] > both hangs because of this test. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5396) PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5396:
-
Labels: swat (was: )
> PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
>
>
> Key: GEODE-5396
> URL: https://issues.apache.org/jira/browse/GEODE-5396
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed on 6a9a98b0bae561407230c5354fc95af0eae49268
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/131]
>
> {noformat}
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '3d781bee-3034-433d-6295-dafc92f1c71a', ip: '10.254.0.50',
> os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-124-generic',
> java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: 352271503dab2578e934f08be4bfdd50
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
> at
> org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
> at
> org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
> at
> org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:160)
> at
> org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
> at
> org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
> at
> org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:325)
> at
> org.apache.geode.tools.pulse.tests.rules.WebDriverRule.before(WebDriverRule.java:61)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
>
[jira] [Updated] (GEODE-5375) DlockAndTxlockRegressionTest hangs the DUnit pipeline
[ https://issues.apache.org/jira/browse/GEODE-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-5375: --- Labels: pull-request-available swat (was: pull-request-available) > DlockAndTxlockRegressionTest hangs the DUnit pipeline > - > > Key: GEODE-5375 > URL: https://issues.apache.org/jira/browse/GEODE-5375 > Project: Geode > Issue Type: Sub-task > Components: ci >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/88] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/79] > both hangs because of this test. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5377) LuceneQueriesReindexDUnitTest recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs DUnit pipeline
[
https://issues.apache.org/jira/browse/GEODE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-5377:
---
Labels: pull-request-available swat (was: pull-request-available)
> LuceneQueriesReindexDUnitTest
> recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs
> DUnit pipeline
> -
>
> Key: GEODE-5377
> URL: https://issues.apache.org/jira/browse/GEODE-5377
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1h
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71]
>
> Thread dump analyzer shows these two threads are blocked:
> h3. RMI TCP Connection(9)-172.17.0.4
> RMI TCP Connection(9)-172.17.0.4
> Stack Trace is:
>
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySender.waitForRunningStatus(AbstractGatewaySender.java:738)
> - locked {color:#FF}<0xe0b9cba8>{color} (a java.lang.Object)
> at
> org.apache.geode.cache.asyncqueue.internal.ParallelAsyncEventQueueImpl.start(ParallelAsyncEventQueueImpl.java:83)
> at
> org.apache.geode.cache.asyncqueue.internal.AsyncEventQueueFactoryImpl.create(AsyncEventQueueFactoryImpl.java:162)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:177)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:171)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.beforeDataRegionCreated(LuceneServiceImpl.java:369)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:265)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:221)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:188)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.lambda$recreateIndexWithDifferentFieldsShouldFail$88e94ee2$1(LuceneQueriesReindexDUnitTest.java:156)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest$$Lambda$105/1606286154.run(Unknown
> Source)
> 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 hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:835)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$7/957256838.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> - {color:#FF}<0xe09a0078>{color} (a
> java.util.concurrent.ThreadPoolExecutor$Worker)
> - {color:#FF}<0xe0b8ad88>{color} (a
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
>
>
> h3. RMI TCP Connection(14)-172.17.0.4
> RMI TCP Connection(14)-172.17.0.4
> Stack Trace is:
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for
[jira] [Assigned] (GEODE-5369) CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao reassigned GEODE-5369:
--
Assignee: Jinmei Liao
> CI Failure: LuceneIndexCommandsWithReindexAllowedDUnitTest
> --
>
> Key: GEODE-5369
> URL: https://issues.apache.org/jira/browse/GEODE-5369
> Project: Geode
> Issue Type: Bug
>Reporter: Alexander Murmann
>Assignee: Jinmei Liao
>Priority: Major
> Labels: ci, flaky, swat
>
> See:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/87]
>
> {code:java}
> java.lang.AssertionError:
> Expecting:
> <["3"]>
> to contain exactly in any order:
> <["2"]>
> elements not found:
> <["2"]>
> and elements not expected:
> <["3"]>
> at
> org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnWithExactValuesInAnyOrder(CommandResultAssert.java:185)
> at
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats(LuceneIndexCommandsDUnitTest.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> 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 junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:449)
> at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)
> 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.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.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.$Proxy1.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
[jira] [Resolved] (GEODE-4803) CI: ConcurrentDeployDUnitTest fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-4803. Resolution: Fixed Fix Version/s: 1.7.0 removed the flaky category of this test > CI: ConcurrentDeployDUnitTest fails intermittently > -- > > Key: GEODE-4803 > URL: https://issues.apache.org/jira/browse/GEODE-4803 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Assignee: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Fix For: 1.7.0 > > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest.html > > Time Spent: 40m > Remaining Estimate: 0h > > The test concurrently runs iterations of gfsh commands to deploy and undeploy > .jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for > the gfsh clients to finish. Sometimes in the CI pipelines one or more of the > clients don't complete their iterations within the 5 minute wait. > Test timing and/or client iterations needs to be adjusted for variations in > machine and network speed. > Also see GEODE-800. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5395) LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5395:
-
Attachment: Test results - Class
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.html
> LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> failed in CI
> ---
>
> Key: GEODE-5395
> URL: https://issues.apache.org/jira/browse/GEODE-5395
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.html
>
>
> This test failed in a recent CI run on rev
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/98]
>
> {noformat}
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit >
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v130]
> 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 15631
> [fatal 2018/07/06 00:50:18.077 UTC
> tid=0xab] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> ---
> Found suspect string in log4j at line 15640
> [fatal 2018/07/06 00:50:19.080 UTC
> tid=0xab] Membership service failure: Exiting due to possible network
> partition event due to loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> org.apache.geode.ForcedDisconnectException: Exiting due to possible
> network partition event due to loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2543)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1044)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:91)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2484)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2115)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2193)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5395) LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5395:
-
Labels: swat (was: )
> LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
> failed in CI
> ---
>
> Key: GEODE-5395
> URL: https://issues.apache.org/jira/browse/GEODE-5395
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed in a recent CI run on rev
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/98]
>
> {noformat}
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit >
> luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v130]
> 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 15631
> [fatal 2018/07/06 00:50:18.077 UTC
> tid=0xab] Possible loss of quorum due to the loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> ---
> Found suspect string in log4j at line 15640
> [fatal 2018/07/06 00:50:19.080 UTC
> tid=0xab] Membership service failure: Exiting due to possible network
> partition event due to loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> org.apache.geode.ForcedDisconnectException: Exiting due to possible
> network partition event due to loss of 1 cache processes:
> [172.17.0.2(11555):32772]
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2543)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1044)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:91)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2484)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2115)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2193)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5395) LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled failed in CI
Dan Smith created GEODE-5395:
Summary:
LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled
failed in CI
Key: GEODE-5395
URL: https://issues.apache.org/jira/browse/GEODE-5395
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
This test failed in a recent CI run on rev
10d8dabdfa39dde490ae2ebf7a5ece4786cea661
[https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/98]
{noformat}
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit >
luceneQueryReturnsCorrectResultAfterTwoLocatorsWithTwoServersAreRolled[from_v130]
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 15631
[fatal 2018/07/06 00:50:18.077 UTC
tid=0xab] Possible loss of quorum due to the loss of 1 cache processes:
[172.17.0.2(11555):32772]
---
Found suspect string in log4j at line 15640
[fatal 2018/07/06 00:50:19.080 UTC
tid=0xab] Membership service failure: Exiting due to possible network partition
event due to loss of 1 cache processes: [172.17.0.2(11555):32772]
org.apache.geode.ForcedDisconnectException: Exiting due to possible network
partition event due to loss of 1 cache processes: [172.17.0.2(11555):32772]
at
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2543)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1044)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.access$1500(GMSJoinLeave.java:91)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.prepareAndSendView(GMSJoinLeave.java:2484)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.sendInitialView(GMSJoinLeave.java:2115)
at
org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave$ViewCreator.run(GMSJoinLeave.java:2193)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5394:
-
Labels: swat (was: )
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5394:
-
Attachment: Test results - Class
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
Dan Smith created GEODE-5394:
Summary: ClientServerMiscBCDUnitTest.testRegionClose failed in CI
Key: GEODE-5394
URL: https://issues.apache.org/jira/browse/GEODE-5394
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
This test failed in a recent CI run on 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
{noformat}
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
testRegionClose[3] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
in VM 2 running on Host fe6abf8a5e6f with 5 VMs
Caused by:
java.lang.AssertionError: Event never occurred after 4 ms: null
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5385) hang trying to create a bucket
[ https://issues.apache.org/jira/browse/GEODE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535167#comment-16535167 ] ASF subversion and git services commented on GEODE-5385: Commit dbdbd7a83f70340ab3a8b76823b04780c0b29430 in geode's branch refs/heads/develop from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dbdbd7a ] GEODE-5385: hang trying to create a bucket We now look for a ForceReattemptException when destroying a partitioned region. This prevents a region ID skew that can occur if another node is still initializing its region and is not yet ready to destroy it. I've reenabled the PRSanityCheckMessage that watches for skews like this and reports them. This used to be enabled by default but somehow was disabled a long time ago. This closes #2109 > hang trying to create a bucket > -- > > Key: GEODE-5385 > URL: https://issues.apache.org/jira/browse/GEODE-5385 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > It's possible for partitioned region bucket allocation to hang even though > there appears to be plenty of storage available. This can happen if one > server is creating the partitioned region at the same time the region is > being destroyed by another server. > The server creating the partitioned region will send a > ForceReattemptException back to the server destroying the region and that > exception is ignored. The server creating the PR will then be stuck with a > region having a dangling ID that has been removed from the PR metadata > region. If another server then recreates the PR it will assign a new ID to > it and the servers will have skewed IDs. The IDs are sent in partitioned > region messages such as manage-bucket. > The distribution advisors don't recognize that there is a skew and our logs > show nothing about it because a safety mechanism was accidentally turned off > by an engineer in PRSanityCheckMessage. This message performs a check of the > IDs in the servers to make sure they're consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5393) StateFlushOperation hangs waiting for non-existant operation to complete
[
https://issues.apache.org/jira/browse/GEODE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5393:
--
Labels: pull-request-available (was: )
> StateFlushOperation hangs waiting for non-existant operation to complete
>
>
> Key: GEODE-5393
> URL: https://issues.apache.org/jira/browse/GEODE-5393
> Project: Geode
> Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
>
> We had a state-flush operation hang with no threads performing flushable
> messaging. That indicates that there is a book-keeping error in invoking
> startOperation/endOperation. It looks like it's due to an exception being
> thrown during distribution:
> {noformat}
> Exception occurred while processing
> DistributedPutAllOperation(EntryEventImpl[op=PUTALL_CREATE;region=/replicate_8;key=null;oldValue=null;newValue=null;callbackArg=null;originRemote=true;originMember=10.32.108.122(accessorgemfire1_rs-StorageBTTest30102851a1i3xlarge-hydra-client-5_15068:15068):1033;id=EventID[id=92
> bytes;threadID=97;sequenceID=180]])
> org.apache.geode.cache.persistence.PersistentReplicatesOfflineException
> at
> org.apache.geode.internal.cache.DistributedPutAllOperation.initMessage(DistributedPutAllOperation.java:923)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation._distribute(DistributedCacheOperation.java:506)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation.startOperation(DistributedCacheOperation.java:264)
> at
> org.apache.geode.internal.cache.DistributedRegion.postPutAllSend(DistributedRegion.java:3214)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.postPutAll(LocalRegionDataView.java:326)
> at
> org.apache.geode.internal.cache.LocalRegion.basicPutAll(LocalRegion.java:9745)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicPutAll(DistributedRegion.java:3240)
> at
> org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9493)
> at
> org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9505)
> at
> diskRecovery.StartupShutdownTest.HydraTask_doContinuousUpdates(StartupShutdownTest.java:482)
> at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.execute(MethExecutor.java:181)
> at hydra.MethExecutor.execute(MethExecutor.java:149)
> at hydra.TestTask.execute(TestTask.java:192)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
> {noformat}
> This is causing endOperation to not be invoked with the correct view version.
> Error handling was moved from DistributedCacheOperation to other classes but
> it's incorrectly implemented. The other classes do not know the view version
> and so end up invoking endOperation with an invalid version number.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4803) CI: ConcurrentDeployDUnitTest fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535143#comment-16535143 ] ASF subversion and git services commented on GEODE-4803: Commit 2ba81f6e78e49b515e9271695f160b42218988b8 in geode's branch refs/heads/develop from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2ba81f6 ] GEODE-4803: remove flaky category (#2108) Co-authored-by: Finn Southerland > CI: ConcurrentDeployDUnitTest fails intermittently > -- > > Key: GEODE-4803 > URL: https://issues.apache.org/jira/browse/GEODE-4803 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Assignee: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest.html > > Time Spent: 40m > Remaining Estimate: 0h > > The test concurrently runs iterations of gfsh commands to deploy and undeploy > .jar's from 3 gfsh clients to the same server, then waits up to 5 minutes for > the gfsh clients to finish. Sometimes in the CI pipelines one or more of the > clients don't complete their iterations within the 5 minute wait. > Test timing and/or client iterations needs to be adjusted for variations in > machine and network speed. > Also see GEODE-800. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5393) StateFlushOperation hangs waiting for non-existant operation to complete
[
https://issues.apache.org/jira/browse/GEODE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-5393:
---
Assignee: Bruce Schuchardt
> StateFlushOperation hangs waiting for non-existant operation to complete
>
>
> Key: GEODE-5393
> URL: https://issues.apache.org/jira/browse/GEODE-5393
> Project: Geode
> Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> We had a state-flush operation hang with no threads performing flushable
> messaging. That indicates that there is a book-keeping error in invoking
> startOperation/endOperation. It looks like it's due to an exception being
> thrown during distribution:
> {noformat}
> Exception occurred while processing
> DistributedPutAllOperation(EntryEventImpl[op=PUTALL_CREATE;region=/replicate_8;key=null;oldValue=null;newValue=null;callbackArg=null;originRemote=true;originMember=10.32.108.122(accessorgemfire1_rs-StorageBTTest30102851a1i3xlarge-hydra-client-5_15068:15068):1033;id=EventID[id=92
> bytes;threadID=97;sequenceID=180]])
> org.apache.geode.cache.persistence.PersistentReplicatesOfflineException
> at
> org.apache.geode.internal.cache.DistributedPutAllOperation.initMessage(DistributedPutAllOperation.java:923)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation._distribute(DistributedCacheOperation.java:506)
> at
> org.apache.geode.internal.cache.DistributedCacheOperation.startOperation(DistributedCacheOperation.java:264)
> at
> org.apache.geode.internal.cache.DistributedRegion.postPutAllSend(DistributedRegion.java:3214)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.postPutAll(LocalRegionDataView.java:326)
> at
> org.apache.geode.internal.cache.LocalRegion.basicPutAll(LocalRegion.java:9745)
> at
> org.apache.geode.internal.cache.DistributedRegion.basicPutAll(DistributedRegion.java:3240)
> at
> org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9493)
> at
> org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9505)
> at
> diskRecovery.StartupShutdownTest.HydraTask_doContinuousUpdates(StartupShutdownTest.java:482)
> at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.execute(MethExecutor.java:181)
> at hydra.MethExecutor.execute(MethExecutor.java:149)
> at hydra.TestTask.execute(TestTask.java:192)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
> {noformat}
> This is causing endOperation to not be invoked with the correct view version.
> Error handling was moved from DistributedCacheOperation to other classes but
> it's incorrectly implemented. The other classes do not know the view version
> and so end up invoking endOperation with an invalid version number.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5393) StateFlushOperation hangs waiting for non-existant operation to complete
Bruce Schuchardt created GEODE-5393:
---
Summary: StateFlushOperation hangs waiting for non-existant
operation to complete
Key: GEODE-5393
URL: https://issues.apache.org/jira/browse/GEODE-5393
Project: Geode
Issue Type: Bug
Reporter: Bruce Schuchardt
We had a state-flush operation hang with no threads performing flushable
messaging. That indicates that there is a book-keeping error in invoking
startOperation/endOperation. It looks like it's due to an exception being
thrown during distribution:
{noformat}
Exception occurred while processing
DistributedPutAllOperation(EntryEventImpl[op=PUTALL_CREATE;region=/replicate_8;key=null;oldValue=null;newValue=null;callbackArg=null;originRemote=true;originMember=10.32.108.122(accessorgemfire1_rs-StorageBTTest30102851a1i3xlarge-hydra-client-5_15068:15068):1033;id=EventID[id=92
bytes;threadID=97;sequenceID=180]])
org.apache.geode.cache.persistence.PersistentReplicatesOfflineException
at
org.apache.geode.internal.cache.DistributedPutAllOperation.initMessage(DistributedPutAllOperation.java:923)
at
org.apache.geode.internal.cache.DistributedCacheOperation._distribute(DistributedCacheOperation.java:506)
at
org.apache.geode.internal.cache.DistributedCacheOperation.startOperation(DistributedCacheOperation.java:264)
at
org.apache.geode.internal.cache.DistributedRegion.postPutAllSend(DistributedRegion.java:3214)
at
org.apache.geode.internal.cache.LocalRegionDataView.postPutAll(LocalRegionDataView.java:326)
at
org.apache.geode.internal.cache.LocalRegion.basicPutAll(LocalRegion.java:9745)
at
org.apache.geode.internal.cache.DistributedRegion.basicPutAll(DistributedRegion.java:3240)
at
org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9493)
at
org.apache.geode.internal.cache.LocalRegion.putAll(LocalRegion.java:9505)
at
diskRecovery.StartupShutdownTest.HydraTask_doContinuousUpdates(StartupShutdownTest.java:482)
at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.execute(MethExecutor.java:181)
at hydra.MethExecutor.execute(MethExecutor.java:149)
at hydra.TestTask.execute(TestTask.java:192)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
{noformat}
This is causing endOperation to not be invoked with the correct view version.
Error handling was moved from DistributedCacheOperation to other classes but
it's incorrectly implemented. The other classes do not know the view version
and so end up invoking endOperation with an invalid version number.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5390) Move inner classes to end of persistence impl classes
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5390: -- Labels: pull-request-available (was: ) > Move inner classes to end of persistence impl classes > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Add > @Override where appropriate. > Improve trace level log statement in Oplog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5391) Fix toString of RegionVersionHolder
Kirk Lund created GEODE-5391: Summary: Fix toString of RegionVersionHolder Key: GEODE-5391 URL: https://issues.apache.org/jira/browse/GEODE-5391 Project: Geode Issue Type: Improvement Components: regions Reporter: Kirk Lund The closing "}" is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5391) Fix toString of RegionVersionHolder
[ https://issues.apache.org/jira/browse/GEODE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5391: Assignee: Kirk Lund > Fix toString of RegionVersionHolder > --- > > Key: GEODE-5391 > URL: https://issues.apache.org/jira/browse/GEODE-5391 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > The closing "}" is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5392) Cleanup javadocs and code style in AsyncInvocation
[ https://issues.apache.org/jira/browse/GEODE-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5392: - Component/s: tests > Cleanup javadocs and code style in AsyncInvocation > -- > > Key: GEODE-5392 > URL: https://issues.apache.org/jira/browse/GEODE-5392 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Priority: Major > > Cleanup javadocs and code style in AsyncInvocation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5392) Cleanup javadocs and code style in AsyncInvocation
Kirk Lund created GEODE-5392: Summary: Cleanup javadocs and code style in AsyncInvocation Key: GEODE-5392 URL: https://issues.apache.org/jira/browse/GEODE-5392 Project: Geode Issue Type: Improvement Reporter: Kirk Lund Cleanup javadocs and code style in AsyncInvocation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5392) Cleanup javadocs and code style in AsyncInvocation
[ https://issues.apache.org/jira/browse/GEODE-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5392: Assignee: Kirk Lund > Cleanup javadocs and code style in AsyncInvocation > -- > > Key: GEODE-5392 > URL: https://issues.apache.org/jira/browse/GEODE-5392 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Cleanup javadocs and code style in AsyncInvocation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5390) Move inner classes to end of persistence impl classes
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5390: - Description: Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Add @Override where appropriate. Improve trace level log statement in Oplog. was: Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Improve trace level log statement in Oplog. > Move inner classes to end of persistence impl classes > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Add > @Override where appropriate. > Improve trace level log statement in Oplog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5390) Move inner classes to end of persistence impl classes
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5390: - Summary: Move inner classes to end of persistence impl classes (was: Move inner classes to end of DiskInitFile) > Move inner classes to end of persistence impl classes > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Move inner classes to end of DiskInitFile -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5390) Move inner classes to end of persistence impl classes
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5390: - Description: Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Improve trace level log statement in Oplog. was:Move inner classes to end of DiskInitFile > Move inner classes to end of persistence impl classes > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. > Improve trace level log statement in Oplog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5389) Add a task to generate a code coverage report
Dan Smith created GEODE-5389: Summary: Add a task to generate a code coverage report Key: GEODE-5389 URL: https://issues.apache.org/jira/browse/GEODE-5389 Project: Geode Issue Type: Task Components: tests Reporter: Dan Smith Add a task to the develop pipeline to generate a code coverage report from all of the test jobs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5389) Add a task to generate a code coverage report
[ https://issues.apache.org/jira/browse/GEODE-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5389: - Labels: swat (was: ) > Add a task to generate a code coverage report > - > > Key: GEODE-5389 > URL: https://issues.apache.org/jira/browse/GEODE-5389 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > Add a task to the develop pipeline to generate a code coverage report from > all of the test jobs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5390) Move inner classes to end of DiskInitFile
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5390: Assignee: Kirk Lund > Move inner classes to end of DiskInitFile > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Move inner classes to end of DiskInitFile -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5390) Move inner classes to end of DiskInitFile
Kirk Lund created GEODE-5390: Summary: Move inner classes to end of DiskInitFile Key: GEODE-5390 URL: https://issues.apache.org/jira/browse/GEODE-5390 Project: Geode Issue Type: Improvement Components: persistence Reporter: Kirk Lund Move inner classes to end of DiskInitFile -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5355) Refactor backup code to unify it as one API and make it testable
[ https://issues.apache.org/jira/browse/GEODE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5355. -- Resolution: Fixed Fix Version/s: 1.7.0 > Refactor backup code to unify it as one API and make it testable > > > Key: GEODE-5355 > URL: https://issues.apache.org/jira/browse/GEODE-5355 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > BackupUtil and BackupDataStoreHelper are collections of static methods that > aren't easy to test with mocks. > JMX, GFSH and the deprecated Admin API treat BackupUtil and > BackupDataStoreHelper as entry points to the Backup API whereas BackupService > is presented to the User as the only API. We should have one class > (BackupService) be the single entry point to performing a Backup. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5340) Allow disk store commands to use custom log4j2 config
[
https://issues.apache.org/jira/browse/GEODE-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535117#comment-16535117
]
Kirk Lund commented on GEODE-5340:
--
The fix is on develop with the wrong Jira ticket in the comment:
{noformat}
commit 6a9a98b0bae561407230c5354fc95af0eae49268
Author: Kirk Lund
Date: Thu Jun 21 13:24:46 2018 -0700
GEODE-5430: Allow disk store commands to use custom log4j2 config
If you edit the gfsh script to specify a custom log4j2 xml
configuration file, this change will propagate that custom
config file to any forked disk store commands.
{noformat}
> Allow disk store commands to use custom log4j2 config
> -
>
> Key: GEODE-5340
> URL: https://issues.apache.org/jira/browse/GEODE-5340
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.7.0
>
>
> The GFSH disk store commands such as "validate offline-disk-store" fork a new
> JVM in which to execute the actual command. The code that forks hard-codes
> the Log4j2 configuration:
> {noformat}
> static void configureLogging(final List commandList) {
> URL configUrl = LogService.class.getResource(LogService.CLI_CONFIG);
> String configFilePropertyValue = configUrl.toString();
> commandList.add("-Dlog4j.configurationFile=" + configFilePropertyValue);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5341) Improve debug logging in BackupTask
[ https://issues.apache.org/jira/browse/GEODE-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5341. -- Resolution: Fixed Fix Version/s: 1.7.0 > Improve debug logging in BackupTask > --- > > Key: GEODE-5341 > URL: https://issues.apache.org/jira/browse/GEODE-5341 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > I need to see log statements about the locks used in BackupTask in order to > debug backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5340) Allow disk store commands to use custom log4j2 config
[
https://issues.apache.org/jira/browse/GEODE-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-5340.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> Allow disk store commands to use custom log4j2 config
> -
>
> Key: GEODE-5340
> URL: https://issues.apache.org/jira/browse/GEODE-5340
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.7.0
>
>
> The GFSH disk store commands such as "validate offline-disk-store" fork a new
> JVM in which to execute the actual command. The code that forks hard-codes
> the Log4j2 configuration:
> {noformat}
> static void configureLogging(final List commandList) {
> URL configUrl = LogService.class.getResource(LogService.CLI_CONFIG);
> String configFilePropertyValue = configUrl.toString();
> commandList.add("-Dlog4j.configurationFile=" + configFilePropertyValue);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5388) Add a gradle task to run a test N times in parallel
[ https://issues.apache.org/jira/browse/GEODE-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5388: - Labels: swat (was: ) > Add a gradle task to run a test N times in parallel > --- > > Key: GEODE-5388 > URL: https://issues.apache.org/jira/browse/GEODE-5388 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > Add a gradle task that can run a given test method N number of times, ideally > in parallel using our docker parallel test execution. > This will be useful for reproducing a bug, and potentially for GEODE-5387 as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535110#comment-16535110 ] ASF subversion and git services commented on GEODE-5378: Commit 5dfc65c9ebd4f4908994674d4b7abca0e659f902 in geode's branch refs/heads/develop from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dfc65c ] Merge pull request #2110 from smgoller/GEODE-5378 [GEODE-5378] Adjust initdocker script to implement workaround. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535109#comment-16535109 ] ASF subversion and git services commented on GEODE-5378: Commit 5dfc65c9ebd4f4908994674d4b7abca0e659f902 in geode's branch refs/heads/develop from [~dcavender] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dfc65c ] Merge pull request #2110 from smgoller/GEODE-5378 [GEODE-5378] Adjust initdocker script to implement workaround. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5378) AcceptanceTests fail because they cannot start service db
[ https://issues.apache.org/jira/browse/GEODE-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535108#comment-16535108 ] ASF subversion and git services commented on GEODE-5378: Commit 2c3a7b120b7727e3e5a46aaa8bad1fbb7510b92c in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2c3a7b1 ] [GEODE-5378] Adjust initdocker script to implement workaround. Current versions of docker have an issue under linux causing it to fail. This workaround addresses the problem. Once Docker fixes the problem on their end this might need to be removed. > AcceptanceTests fail because they cannot start service db > - > > Key: GEODE-5378 > URL: https://issues.apache.org/jira/browse/GEODE-5378 > Project: Geode > Issue Type: Task >Reporter: Alexander Murmann >Assignee: Brian Rowe >Priority: Critical > Labels: pull-request-available, swat > Time Spent: 50m > Remaining Estimate: 0h > > The build 125-127 have had 10 failures that were related to failure to start > a service db in the JDBC tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5388) Add a gradle task to run a test N times in parallel
Dan Smith created GEODE-5388: Summary: Add a gradle task to run a test N times in parallel Key: GEODE-5388 URL: https://issues.apache.org/jira/browse/GEODE-5388 Project: Geode Issue Type: Task Components: tests Reporter: Dan Smith Add a gradle task that can run a given test method N number of times, ideally in parallel using our docker parallel test execution. This will be useful for reproducing a bug, and potentially for GEODE-5387 as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5387) Add job to precheckin pipeline to run new or modified tests N times
[ https://issues.apache.org/jira/browse/GEODE-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5387: - Labels: swat (was: ) > Add job to precheckin pipeline to run new or modified tests N times > --- > > Key: GEODE-5387 > URL: https://issues.apache.org/jira/browse/GEODE-5387 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > Add a job to the concourse precheckin pipeline to identify dunit tests that > are newly introduced or modified and run these tests multiple times. > We should have a limit on the number of tests to run, if a diff changes more > than X tests we will not run the additional tests. > The intent is to prevent people from introducing new flaky tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5387) Add job to precheckin pipeline to run new or modified tests N times
Dan Smith created GEODE-5387: Summary: Add job to precheckin pipeline to run new or modified tests N times Key: GEODE-5387 URL: https://issues.apache.org/jira/browse/GEODE-5387 Project: Geode Issue Type: Task Components: tests Reporter: Dan Smith Add a job to the concourse precheckin pipeline to identify dunit tests that are newly introduced or modified and run these tests multiple times. We should have a limit on the number of tests to run, if a diff changes more than X tests we will not run the additional tests. The intent is to prevent people from introducing new flaky tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5281) Race between registering and unregistering CustomMXBeans in concurrent thread may result in NPE
[
https://issues.apache.org/jira/browse/GEODE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Howe resolved GEODE-5281.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> Race between registering and unregistering CustomMXBeans in concurrent thread
> may result in NPE
> ---
>
> Key: GEODE-5281
> URL: https://issues.apache.org/jira/browse/GEODE-5281
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Stack trace from an example of the unexpected NullPointerException in
> {{MBeanProxyFactory.createProxy()}}
> {code:java}
> [warning 2018/02/03 17:32:13.561 UTC
> managing_1_gemfire2_79a23c4a-f5e3-4c9f-6455-149c397ce13c_38199
> tid=0x5e] Create Proxy failed for
> GemFire:type=CustomMXBean213,member=locator_managing_gemfire1_79a23c4a-f5e3-4c9f-6455-149c397ce13c_37116
> with exception null
> java.lang.NullPointerException
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:83)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The registering thread enters
> {code}
> public void createProxy(DistributedMember member, ObjectName objectName,
> Region monitoringRegion, Object newVal) {
> {code}
> with the {{objectName}} existing in the {{_monitoringRegion}}. A few lines
> further the entry is retrieved from the region, but is now {{null}} due to it
> being removed by the unregistering thread.
> {code}
> String name = objectName.toString();
> FederationComponent federationComponent = (FederationComponent)
> monitoringRegion.get(name);
> String interfaceClassName =
> federationComponent.getMBeanInterfaceClass();
> {code}
> {{federationComponent == null}} results in the NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5281) Race between registering and unregistering CustomMXBeans in concurrent thread may result in NPE
[
https://issues.apache.org/jira/browse/GEODE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534953#comment-16534953
]
ASF subversion and git services commented on GEODE-5281:
Commit 29c71c96f2933e8380e412e9d14b42beb30ae96b in geode's branch
refs/heads/develop from [~balesh2]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=29c71c9 ]
GEODE-5281: replicate failure and fix bug (#2096)
* GEODE-5281: replicate failure and fix bug
- replicate the bad timing using a DUnit test
- fix the bug by only doing one lookup of MBeans
- add more tests
- fix potential NPE in waiting for regions to be ready on servers
Co-authored-by: Kenneth Howe
* add TestingOnly annotation to setter
add a TestingOnly annotation to setter for ProxyFactory in the
FederatingManager for injecting test spies.
> Race between registering and unregistering CustomMXBeans in concurrent thread
> may result in NPE
> ---
>
> Key: GEODE-5281
> URL: https://issues.apache.org/jira/browse/GEODE-5281
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Stack trace from an example of the unexpected NullPointerException in
> {{MBeanProxyFactory.createProxy()}}
> {code:java}
> [warning 2018/02/03 17:32:13.561 UTC
> managing_1_gemfire2_79a23c4a-f5e3-4c9f-6455-149c397ce13c_38199
> tid=0x5e] Create Proxy failed for
> GemFire:type=CustomMXBean213,member=locator_managing_gemfire1_79a23c4a-f5e3-4c9f-6455-149c397ce13c_37116
> with exception null
> java.lang.NullPointerException
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:83)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The registering thread enters
> {code}
> public void createProxy(DistributedMember member, ObjectName objectName,
> Region monitoringRegion, Object newVal) {
> {code}
> with the {{objectName}} existing in the {{_monitoringRegion}}. A few lines
> further the entry is retrieved from the region, but is now {{null}} due to it
> being removed by the unregistering thread.
> {code}
> String name = objectName.toString();
> FederationComponent federationComponent = (FederationComponent)
> monitoringRegion.get(name);
> String interfaceClassName =
> federationComponent.getMBeanInterfaceClass();
> {code}
> {{federationComponent == null}} results in the NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5281) Race between registering and unregistering CustomMXBeans in concurrent thread may result in NPE
[
https://issues.apache.org/jira/browse/GEODE-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534952#comment-16534952
]
ASF subversion and git services commented on GEODE-5281:
Commit 29c71c96f2933e8380e412e9d14b42beb30ae96b in geode's branch
refs/heads/develop from [~balesh2]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=29c71c9 ]
GEODE-5281: replicate failure and fix bug (#2096)
* GEODE-5281: replicate failure and fix bug
- replicate the bad timing using a DUnit test
- fix the bug by only doing one lookup of MBeans
- add more tests
- fix potential NPE in waiting for regions to be ready on servers
Co-authored-by: Kenneth Howe
* add TestingOnly annotation to setter
add a TestingOnly annotation to setter for ProxyFactory in the
FederatingManager for injecting test spies.
> Race between registering and unregistering CustomMXBeans in concurrent thread
> may result in NPE
> ---
>
> Key: GEODE-5281
> URL: https://issues.apache.org/jira/browse/GEODE-5281
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.0.0-incubating
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Stack trace from an example of the unexpected NullPointerException in
> {{MBeanProxyFactory.createProxy()}}
> {code:java}
> [warning 2018/02/03 17:32:13.561 UTC
> managing_1_gemfire2_79a23c4a-f5e3-4c9f-6455-149c397ce13c_38199
> tid=0x5e] Create Proxy failed for
> GemFire:type=CustomMXBean213,member=locator_managing_gemfire1_79a23c4a-f5e3-4c9f-6455-149c397ce13c_37116
> with exception null
> java.lang.NullPointerException
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:83)
> at
> org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457)
> at
> org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> {code}
> The registering thread enters
> {code}
> public void createProxy(DistributedMember member, ObjectName objectName,
> Region monitoringRegion, Object newVal) {
> {code}
> with the {{objectName}} existing in the {{_monitoringRegion}}. A few lines
> further the entry is retrieved from the region, but is now {{null}} due to it
> being removed by the unregistering thread.
> {code}
> String name = objectName.toString();
> FederationComponent federationComponent = (FederationComponent)
> monitoringRegion.get(name);
> String interfaceClassName =
> federationComponent.getMBeanInterfaceClass();
> {code}
> {{federationComponent == null}} results in the NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534920#comment-16534920 ] Vadim Lotarev commented on GEODE-4769: -- Does this fix mean that all entries are _always_ stored in serialized form now in the local cache? So in order to get them deserialization is always performed? Don't you think that this will affect cache performance? One of advantages of Geode was the fact that it worked with the local cache really fast because data were stored in not serialized form most of the time ... > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5386) Remove FLAKY label from all appropriate integration tests
Blake Bender created GEODE-5386: --- Summary: Remove FLAKY label from all appropriate integration tests Key: GEODE-5386 URL: https://issues.apache.org/jira/browse/GEODE-5386 Project: Geode Issue Type: Improvement Components: native client Reporter: Blake Bender We have a number of tests labeled FLAKY that seem to pass all of the time. As an experiment, we're going to start removing this label from tests that look like they're passing consistently, i.e. no longer "flaky". NOTE: tests were run _sequentially_, so parallelism in the run may affect us negatively. We're going to give this a go anyway, and if the CI pipeline breaks we'll triage and back out anything we have to. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
