[jira] [Commented] (GEODE-5087) SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting intermittently fail
[ https://issues.apache.org/jira/browse/GEODE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463361#comment-16463361 ] ASF subversion and git services commented on GEODE-5087: Commit 672286885857025aeacd64f356a7eeddb1cccbc0 in geode's branch refs/heads/feature/GEODE-5087 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6722868 ] GEODE-5087: send a BatchDestroyOperation for each dropped event at serial primary sender > SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting > intermittently fail > --- > > Key: GEODE-5087 > URL: https://issues.apache.org/jira/browse/GEODE-5087 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > I introduced this dunit test for GEODE-4942, while GEODE-4942 is for parallel > gateway sender, the test is for serial gateway sender. And I did reproduce > the issue: event is dropped at primary sender (because it's not running yet), > but event has been put into unprocessedEventsMap at secondary sender's queue > and will stay there forever. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5087) SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting intermittently fail
[ https://issues.apache.org/jira/browse/GEODE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5087: -- Labels: pull-request-available (was: ) > SerialGatewaySenderOperationsDUnitTest.testRestartSerialGatewaySendersWhilePutting > intermittently fail > --- > > Key: GEODE-5087 > URL: https://issues.apache.org/jira/browse/GEODE-5087 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > > I introduced this dunit test for GEODE-4942, while GEODE-4942 is for parallel > gateway sender, the test is for serial gateway sender. And I did reproduce > the issue: event is dropped at primary sender (because it's not running yet), > but event has been put into unprocessedEventsMap at secondary sender's queue > and will stay there forever. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-577) CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
[
https://issues.apache.org/jira/browse/GEODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-577:
-
Labels: CI Flaky pull-request-available (was: CI Flaky)
> CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
> ---
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Jason Huynh
>Priority: Major
> Labels: CI, Flaky, pull-request-available
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM.invoke(VM.java:312)
> at dunit.VM.invoke(VM.java:266)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
> 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.GeneratedMethodAccessor124.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.GeneratedMethodAccessor123.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.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: The query should have been
> canceled by the QueryMonitor. Query: SELECT ID FROM
[jira] [Assigned] (GEODE-577) CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
[
https://issues.apache.org/jira/browse/GEODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Huynh reassigned GEODE-577:
-
Assignee: Jason Huynh
> CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
> ---
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Jason Huynh
>Priority: Major
> Labels: CI, Flaky
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM.invoke(VM.java:312)
> at dunit.VM.invoke(VM.java:266)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
> 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.GeneratedMethodAccessor124.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.GeneratedMethodAccessor123.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.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: The query should have been
> canceled by the QueryMonitor. Query: SELECT ID FROM /root/exampleRegion p
> WHERE p.ID > 100
> at
[jira] [Commented] (GEODE-2953) Code Cleanup: Replace wildcard imports with explicit imports
[ https://issues.apache.org/jira/browse/GEODE-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463199#comment-16463199 ] ASF subversion and git services commented on GEODE-2953: Commit 8bb435ea204776bafb47db69b43974fdc3567bb1 in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8bb435e ] GEODE-2953: Expand wildcard imports in remaining non-core modules and tests. (#1910) > Code Cleanup: Replace wildcard imports with explicit imports > > > Key: GEODE-2953 > URL: https://issues.apache.org/jira/browse/GEODE-2953 > Project: Geode > Issue Type: Sub-task > Components: general >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Minor > Labels: pull-request-available > Time Spent: 8h > Remaining Estimate: 0h > > While optimal import order may be a matter of debate, all style guides seem > to agree that wildcard imports should be avoided for improved readability and > namespace cleanliness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2953) Code Cleanup: Replace wildcard imports with explicit imports
[ https://issues.apache.org/jira/browse/GEODE-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463181#comment-16463181 ] ASF subversion and git services commented on GEODE-2953: Commit 82b79107a93e8c08da85e53eba635dec7adc3d79 in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=82b7910 ] GEODE-2953: Expand wildcard imports in geode-core:test.cache. (#1907) > Code Cleanup: Replace wildcard imports with explicit imports > > > Key: GEODE-2953 > URL: https://issues.apache.org/jira/browse/GEODE-2953 > Project: Geode > Issue Type: Sub-task > Components: general >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Minor > Labels: pull-request-available > Time Spent: 7h 40m > Remaining Estimate: 0h > > While optimal import order may be a matter of debate, all style guides seem > to agree that wildcard imports should be avoided for improved readability and > namespace cleanliness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2542) LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode Nightly Build
[
https://issues.apache.org/jira/browse/GEODE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463172#comment-16463172
]
ASF subversion and git services commented on GEODE-2542:
Commit 91ed05a3d6b195a2f361a166b6c97a745bbb0f59 in geode's branch
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=91ed05a ]
GEODE-2542: Extend timeouts from 10s to 30; cleanup (#1897)
GEODE-2542: Extend timeouts from 10s to 30; cleanup
* Remove usage of Assert.fail()
* Don't use invoke try-catch-throw paradigm.
* Remove dead code
* Un-ignore tests, use implicit default constructors.
> LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode
> Nightly Build
> ---
>
> Key: GEODE-2542
> URL: https://issues.apache.org/jira/browse/GEODE-2542
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Kirk Lund
>Assignee: Brian Baynes
>Priority: Major
> Labels: Flaky, pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> testMultipleLocators:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> asf919.gq1.ygridcore.net with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:280)
> at
> org.apache.geode.distributed.LocatorDUnitTest.testMultipleLocators(LocatorDUnitTest.java:1567)
> 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.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
>
[jira] [Resolved] (GEODE-2542) LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode Nightly Build
[
https://issues.apache.org/jira/browse/GEODE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan resolved GEODE-2542.
-
Resolution: Fixed
Assignee: Galen O'Sullivan (was: Brian Baynes)
I bumped up the timeouts from 10s to 30s and did some test cleanup. Hopefully
this is enough to fix the flakiness.
> LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode
> Nightly Build
> ---
>
> Key: GEODE-2542
> URL: https://issues.apache.org/jira/browse/GEODE-2542
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Kirk Lund
>Assignee: Galen O'Sullivan
>Priority: Major
> Labels: Flaky, pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> testMultipleLocators:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> asf919.gq1.ygridcore.net with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:280)
> at
> org.apache.geode.distributed.LocatorDUnitTest.testMultipleLocators(LocatorDUnitTest.java:1567)
> 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.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Commented] (GEODE-2542) LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode Nightly Build
[
https://issues.apache.org/jira/browse/GEODE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463173#comment-16463173
]
ASF subversion and git services commented on GEODE-2542:
Commit 91ed05a3d6b195a2f361a166b6c97a745bbb0f59 in geode's branch
refs/heads/develop from [~gosullivan]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=91ed05a ]
GEODE-2542: Extend timeouts from 10s to 30; cleanup (#1897)
GEODE-2542: Extend timeouts from 10s to 30; cleanup
* Remove usage of Assert.fail()
* Don't use invoke try-catch-throw paradigm.
* Remove dead code
* Un-ignore tests, use implicit default constructors.
> LocatorDUnitTest and LocatorUDPSecurityDUnitTest fail frequently in Geode
> Nightly Build
> ---
>
> Key: GEODE-2542
> URL: https://issues.apache.org/jira/browse/GEODE-2542
> Project: Geode
> Issue Type: Bug
> Components: locator
>Reporter: Kirk Lund
>Assignee: Brian Baynes
>Priority: Major
> Labels: Flaky, pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> testMultipleLocators:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host
> asf919.gq1.ygridcore.net with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:280)
> at
> org.apache.geode.distributed.LocatorDUnitTest.testMultipleLocators(LocatorDUnitTest.java:1567)
> 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.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
>
[jira] [Updated] (GEODE-4860) make sure the extensions xsd is upgradable
[ https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-4860: -- Fix Version/s: 1.7.0 > make sure the extensions xsd is upgradable > -- > > Key: GEODE-4860 > URL: https://issues.apache.org/jira/browse/GEODE-4860 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > when other module uses a different version of their own xsd (jdbc-2.0.xsd). > We should have a strategy to make sure rolling upgrade still work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4860) make sure the extensions xsd is upgradable
[ https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-4860. --- Resolution: Fixed > make sure the extensions xsd is upgradable > -- > > Key: GEODE-4860 > URL: https://issues.apache.org/jira/browse/GEODE-4860 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > when other module uses a different version of their own xsd (jdbc-2.0.xsd). > We should have a strategy to make sure rolling upgrade still work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5083) Alter region --name option no longer auto completes
[ https://issues.apache.org/jira/browse/GEODE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-5083: -- Fix Version/s: 1.7.0 > Alter region --name option no longer auto completes > --- > > Key: GEODE-5083 > URL: https://issues.apache.org/jira/browse/GEODE-5083 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available, quick_to_fix > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > when "alter region --name=" is typed, tabbing should show a list of available > regions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5083) Alter region --name option no longer auto completes
[ https://issues.apache.org/jira/browse/GEODE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-5083. --- Resolution: Fixed > Alter region --name option no longer auto completes > --- > > Key: GEODE-5083 > URL: https://issues.apache.org/jira/browse/GEODE-5083 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available, quick_to_fix > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > when "alter region --name=" is typed, tabbing should show a list of available > regions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5047) Modify gfsh command 'list Lucene index' to list status of re-indexing.
[ https://issues.apache.org/jira/browse/GEODE-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-5047: --- Component/s: docs > Modify gfsh command 'list Lucene index' to list status of re-indexing. > -- > > Key: GEODE-5047 > URL: https://issues.apache.org/jira/browse/GEODE-5047 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > As a GemFire developer, I want to use gfsh to check if the Lucene index > creation has completed successfully using the 'list lucene indexes' and > 'describe lucene index' commands. > Acceptance criteria: > When I use gfsh to add a new Lucene index to an existing region with data, I > can check its status using 'list lucene index': > * If indexing is in progress, the list command will display this > * If indexing is complete, the list command will display this and I can > execute a Lucene search. > h2. Implementation ideas > Check for completed file. If not present, status is 'initializing'. Once > re-indexing is complete, status changes to 'initialized'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5109) Concurrent create lucene reindex ops must fail
[ https://issues.apache.org/jira/browse/GEODE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5109: -- Labels: pull-request-available (was: ) > Concurrent create lucene reindex ops must fail > -- > > Key: GEODE-5109 > URL: https://issues.apache.org/jira/browse/GEODE-5109 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > > Concurrent lucene reindex ops originating with same index profile must fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5047) Modify gfsh command 'list Lucene index' to list status of re-indexing.
[ https://issues.apache.org/jira/browse/GEODE-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463132#comment-16463132 ] ASF subversion and git services commented on GEODE-5047: Commit 8f0b97a48396d5d1ae23aa28696d2d4786160d4b in geode's branch refs/heads/develop from [~nabarunnag] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f0b97a ] GEODE-5047: list lucene index result modified (#1799) * list lucene index gfsh command will now display on of three states * NOT_INITIALIZED if the index is present in only in defined map * INITIALIZED if the index is present in the index map * INDEXING_IN_PROGRESS if the index creation is in progress. > Modify gfsh command 'list Lucene index' to list status of re-indexing. > -- > > Key: GEODE-5047 > URL: https://issues.apache.org/jira/browse/GEODE-5047 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > As a GemFire developer, I want to use gfsh to check if the Lucene index > creation has completed successfully using the 'list lucene indexes' and > 'describe lucene index' commands. > Acceptance criteria: > When I use gfsh to add a new Lucene index to an existing region with data, I > can check its status using 'list lucene index': > * If indexing is in progress, the list command will display this > * If indexing is complete, the list command will display this and I can > execute a Lucene search. > h2. Implementation ideas > Check for completed file. If not present, status is 'initializing'. Once > re-indexing is complete, status changes to 'initialized'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5172) AbstractRegionMap.txApplyPut should be refactored to use RegionMapPut
[ https://issues.apache.org/jira/browse/GEODE-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5172: -- Labels: pull-request-available (was: ) > AbstractRegionMap.txApplyPut should be refactored to use RegionMapPut > - > > Key: GEODE-5172 > URL: https://issues.apache.org/jira/browse/GEODE-5172 > Project: Geode > Issue Type: Sub-task > Components: transactions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > RegionMapPut (currently used for a non-tx put) and txApplyPut share much the > same code. > txApplyPut should be refactored to use the code in RegionMapPut. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-2709) modify backward-compatibility support to work better with geode
[ https://issues.apache.org/jira/browse/GEODE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-2709: -- Labels: pull-request-available (was: ) > modify backward-compatibility support to work better with geode > --- > > Key: GEODE-2709 > URL: https://issues.apache.org/jira/browse/GEODE-2709 > Project: Geode > Issue Type: Improvement > Components: serialization >Reporter: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > > Backward-compatibility support currently pays attention to a version's > Product name and its compareTo method pays attention to the major/minor/etc > numerals. This is an artifact of the GemFireXD effort at Pivotal a few years > ago and should be removed. The Product name is no longer needed at all and > compareTo should just compare the version ordinals. > All places that compare versions should be scrutinized to make sure this > change doesn't break anything. > All methods with names beginning with toDataPre_ or fromDataPre_ need to be > changed to remove the product name and the sanctionedDataSerializables.txt > database needs to be updated to have these new method names and fingerprints > (generated by the AnalyzeSerializablesJUnitTest). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5032) Massage Configuration Objects for Better Intuition.
[ https://issues.apache.org/jira/browse/GEODE-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463100#comment-16463100 ] ASF subversion and git services commented on GEODE-5032: Commit 7eded7b99d3b87c23f72f8ddfc23e48848d39a2d in geode's branch refs/heads/develop from [~jinmeiliao] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7eded7b ] GEODE-5032: massage configuration objects for better usability. (#1894) > Massage Configuration Objects for Better Intuition. > --- > > Key: GEODE-5032 > URL: https://issues.apache.org/jira/browse/GEODE-5032 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > > For instance, various port fields are declared as Strings where an Integer > makes more sense. This is true for many "count" fields as well. > These may be best resolved via a JAXB bindings file and regenerating the > POJOs from scratch. Additionally if all the minor adjustments that have been > already made (removing the xsd:choice and manually enforcing it, having each > item implement CacheElement and have a getId() method) can also be resolved > via a bindings file, then the POJOs could be removed from the git tree and > generated during the build step, if desired. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5177) InitializedDiskRegionWithIoExceptionRegressionTest fails intermittently with NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5177:
--
Labels: pull-request-available (was: )
> InitializedDiskRegionWithIoExceptionRegressionTest fails intermittently with
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5177
> URL: https://issues.apache.org/jira/browse/GEODE-5177
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
>
> InitializedDiskRegionWithIoExceptionRegressionTest intermittently fails with
> NoSubscriptionServersAvailableException (see other bugs filed for other tests
> with the same symptom). There seems to be something asynchronous down in
> QueueManagerImpl which causes this.
> {noformat}
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> > cacheServerPersistWithIOExceptionShouldShutdown FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
> in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
> Caused by:
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356)
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
> Caused by:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
> at
> org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347)
> at
> org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
> at
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
> at
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164)
> ... 1 more
> {noformat}
> Fortunately, InitializedDiskRegionWithIoExceptionRegressionTest does NOT need
> to use subscription queues so this can easily be fixed by removing the use of
> subscription queues from this test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2709) modify backward-compatibility support to work better with geode
[ https://issues.apache.org/jira/browse/GEODE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463096#comment-16463096 ] ASF subversion and git services commented on GEODE-2709: Commit 5be4e1f66d145af81d44c67c499f10cfd7d8f747 in geode's branch refs/heads/feature/GEODE-2709 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5be4e1f ] GEODE-2709: modify backward-compatibility support to work better with geode Removed the "product name" from toDataPre/fromDataPre methods and from sanctionedDataSerializable.txt files. > modify backward-compatibility support to work better with geode > --- > > Key: GEODE-2709 > URL: https://issues.apache.org/jira/browse/GEODE-2709 > Project: Geode > Issue Type: Improvement > Components: serialization >Reporter: Bruce Schuchardt >Priority: Major > > Backward-compatibility support currently pays attention to a version's > Product name and its compareTo method pays attention to the major/minor/etc > numerals. This is an artifact of the GemFireXD effort at Pivotal a few years > ago and should be removed. The Product name is no longer needed at all and > compareTo should just compare the version ordinals. > All places that compare versions should be scrutinized to make sure this > change doesn't break anything. > All methods with names beginning with toDataPre_ or fromDataPre_ need to be > changed to remove the product name and the sanctionedDataSerializables.txt > database needs to be updated to have these new method names and fingerprints > (generated by the AnalyzeSerializablesJUnitTest). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4860) make sure the extensions xsd is upgradable
[ https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463086#comment-16463086 ] ASF subversion and git services commented on GEODE-4860: Commit db6d865c17f4cb50ac8f88fec16107774028c63a in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=db6d865 ] GEODE-4860: make sure the extensions xsd is upgradable (#1904) JAXB ignores unknown properties during unmarshalling. Added a test to make sure that an xml can be unmarshalled while ignoring any unknown properties. > make sure the extensions xsd is upgradable > -- > > Key: GEODE-4860 > URL: https://issues.apache.org/jira/browse/GEODE-4860 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > when other module uses a different version of their own xsd (jdbc-2.0.xsd). > We should have a strategy to make sure rolling upgrade still work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5177) InitializedDiskRegionWithIoExceptionRegressionTest fails intermittently with NoSubscriptionServersAvailableException
Kirk Lund created GEODE-5177:
Summary: InitializedDiskRegionWithIoExceptionRegressionTest fails
intermittently with NoSubscriptionServersAvailableException
Key: GEODE-5177
URL: https://issues.apache.org/jira/browse/GEODE-5177
Project: Geode
Issue Type: Bug
Components: persistence, tests
Reporter: Kirk Lund
InitializedDiskRegionWithIoExceptionRegressionTest intermittently fails with
NoSubscriptionServersAvailableException (see other bugs filed for other tests
with the same symptom). There seems to be something asynchronous down in
QueueManagerImpl which causes this.
{noformat}
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> cacheServerPersistWithIOExceptionShouldShutdown FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356)
at
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
at
org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
at org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347)
at
org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
at org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
at
org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164)
... 1 more
{noformat}
Fortunately, InitializedDiskRegionWithIoExceptionRegressionTest does NOT need
to use subscription queues so this can easily be fixed by removing the use of
subscription queues from this test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5177) InitializedDiskRegionWithIoExceptionRegressionTest fails intermittently with NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-5177:
Assignee: Kirk Lund
> InitializedDiskRegionWithIoExceptionRegressionTest fails intermittently with
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5177
> URL: https://issues.apache.org/jira/browse/GEODE-5177
> Project: Geode
> Issue Type: Bug
> Components: persistence, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> InitializedDiskRegionWithIoExceptionRegressionTest intermittently fails with
> NoSubscriptionServersAvailableException (see other bugs filed for other tests
> with the same symptom). There seems to be something asynchronous down in
> QueueManagerImpl which causes this.
> {noformat}
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> > cacheServerPersistWithIOExceptionShouldShutdown FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
> in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
> Caused by:
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356)
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
> Caused by:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
> at
> org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347)
> at
> org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
> at
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
> at
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346)
> at
> org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164)
> ... 1 more
> {noformat}
> Fortunately, InitializedDiskRegionWithIoExceptionRegressionTest does NOT need
> to use subscription queues so this can easily be fixed by removing the use of
> subscription queues from this test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5176) make ResultModel public
Jinmei Liao created GEODE-5176: -- Summary: make ResultModel public Key: GEODE-5176 URL: https://issues.apache.org/jira/browse/GEODE-5176 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao commands that uses SingleGfshCommand is required to return ResultModel which is currently an internal api. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4890) intermittent failure of ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest dataWriterCanStillOnlyWriteAfterFailover
[
https://issues.apache.org/jira/browse/GEODE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463034#comment-16463034
]
ASF subversion and git services commented on GEODE-4890:
Commit 839335a845ba6cbd98520676155921c8ee0c195c in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=839335a ]
GEODE-4890: fix to reduce flakiness (#1914)
> intermittent failure of
> ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest
> dataWriterCanStillOnlyWriteAfterFailover
>
>
> Key: GEODE-4890
> URL: https://issues.apache.org/jira/browse/GEODE-4890
> Project: Geode
> Issue Type: Bug
> Components: client/server, security
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Assignee: Jinmei Liao
>Priority: Major
> Labels: ci, pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Looking at this test on line 263 I think we just might need to have the test
> wait a while for the client pool to detect that it has a new primary on the
> "assertThat" line in the following block:
> {noformat}
> server_to_fail.invoke(() -> ClusterStartupRule.getCache().close()); //
> Confirm failover VMProvider secondaryServer =
> (server1.equals(server_to_fail)) ? server2 : server1;
> assertThat(secondaryServer).isEqualTo(determinePrimaryServer(client));
> {noformat}
> {noformat}
> dataWriterCanStillOnlyWriteAfterFailover[clientVersion=130]
> org.junit.ComparisonFailure: expected:<...unit.rules.MemberVM@[19582245]> but
> was:<...unit.rules.MemberVM@[23c51fe4]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.security.ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.dataWriterCanStillOnlyWriteAfterFailover(ClientDataAuthorizationUsingLegacySecurityWithFailoverDUnitTest.java:263)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4889) Make Cache::createDataInput/Output return value type
[ https://issues.apache.org/jira/browse/GEODE-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4889: -- Labels: pull-request-available (was: ) > Make Cache::createDataInput/Output return value type > > > Key: GEODE-4889 > URL: https://issues.apache.org/jira/browse/GEODE-4889 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > There doesn't appear to be any compelling reason why we're handing out shared > pointers here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5057) Remove 'experimental' from JDBC Connector code
[ https://issues.apache.org/jira/browse/GEODE-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5057: Assignee: (was: Kirk Lund) > Remove 'experimental' from JDBC Connector code > -- > > Key: GEODE-5057 > URL: https://issues.apache.org/jira/browse/GEODE-5057 > Project: Geode > Issue Type: Task > Components: extensions >Affects Versions: 1.6.0 >Reporter: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Remove 'experimental' from JDBC Connector code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2953) Code Cleanup: Replace wildcard imports with explicit imports
[ https://issues.apache.org/jira/browse/GEODE-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462835#comment-16462835 ] ASF subversion and git services commented on GEODE-2953: Commit 064a89b40bb98c34225ed40a37df3e5cf5b0394c in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=064a89b ] GEODE-2953: Expand wildcard imports in geode-core.cache. (#1911) > Code Cleanup: Replace wildcard imports with explicit imports > > > Key: GEODE-2953 > URL: https://issues.apache.org/jira/browse/GEODE-2953 > Project: Geode > Issue Type: Sub-task > Components: general >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Minor > Labels: pull-request-available > Time Spent: 7.5h > Remaining Estimate: 0h > > While optimal import order may be a matter of debate, all style guides seem > to agree that wildcard imports should be avoided for improved readability and > namespace cleanliness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5057) Remove 'experimental' from JDBC Connector code
[ https://issues.apache.org/jira/browse/GEODE-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5057: Assignee: Kirk Lund > Remove 'experimental' from JDBC Connector code > -- > > Key: GEODE-5057 > URL: https://issues.apache.org/jira/browse/GEODE-5057 > Project: Geode > Issue Type: Task > Components: extensions >Affects Versions: 1.6.0 >Reporter: Anilkumar Gingade >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Remove 'experimental' from JDBC Connector code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5055) CI failure: LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion
[ https://issues.apache.org/jira/browse/GEODE-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462810#comment-16462810 ] ASF subversion and git services commented on GEODE-5055: Commit be2913392c0edf3ef468729fb09346a4b1d41dff in geode's branch refs/heads/develop from [~nabarunnag] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=be29133 ] GEODE-5055: Handle index creation in progress. (#1847) * If all the servers are above the 1.6.0 version then the LuceneIndexCreationInProgressException will be propogated up to the servers * If there are servers which are lower than 1.6.0 then get repository will be re-executed but it will wait till the indexes are available. > CI failure: > LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion > - > > Key: GEODE-5055 > URL: https://issues.apache.org/jira/browse/GEODE-5055 > Project: Geode > Issue Type: Sub-task > Components: lucene >Reporter: Jason Huynh >Assignee: nabarun >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > This is related to changes for GEODE-3926. The roll is occuring but because > we added the new complete file, the new server is probably "reindexing" at > the moment. > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit > > luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion[from_v140] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit$$Lambda$27/1996438298.run > in VM 0 running on Host eada542bc38a 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.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResultInEachVM(LuceneSearchWithRollingUpgradeDUnit.java:678) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.executeLuceneQueryWithServerRollOvers(LuceneSearchWithRollingUpgradeDUnit.java:572) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.luceneQueryReturnsCorrectResultsAfterServersRollOverOnPartitionRegion(LuceneSearchWithRollingUpgradeDUnit.java:134) > Caused by: > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:661) > at > org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.lambda$verifyLuceneQueryResultInEachVM$b83f705c$2(LuceneSearchWithRollingUpgradeDUnit.java:678) > Caused by: > > org.apache.geode.cache.lucene.internal.LuceneIndexCreationInProgressException: > Lucene Index creation in progress for bucket: 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5175) Remove PersistentPartitionedRegionTestBase
[
https://issues.apache.org/jira/browse/GEODE-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5175:
-
Priority: Minor (was: Major)
> Remove PersistentPartitionedRegionTestBase
> --
>
> Key: GEODE-5175
> URL: https://issues.apache.org/jira/browse/GEODE-5175
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> Remove PersistentPartitionedRegionTestBase and overhaul the tests that extend
> it:
> {noformat}
> JUnit4DistributedTestCase (org.apache.geode.test.dunit.internal)
> JUnit4CacheTestCase (org.apache.geode.test.dunit.cache.internal)
> PersistentPartitionedRegionTestBase
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithTransactionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithDistTXDUnitTest
> (org.apache.geode.disttx)
> PersistentColocatedPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionOldConfigDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> BackupDistributedTest (org.apache.geode.internal.cache.backup)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5175) Remove PersistentPartitionedRegionTestBase
Kirk Lund created GEODE-5175:
Summary: Remove PersistentPartitionedRegionTestBase
Key: GEODE-5175
URL: https://issues.apache.org/jira/browse/GEODE-5175
Project: Geode
Issue Type: Improvement
Components: tests
Reporter: Kirk Lund
Remove PersistentPartitionedRegionTestBase and overhaul the tests that extend
it:
{noformat}
JUnit4DistributedTestCase (org.apache.geode.test.dunit.internal)
JUnit4CacheTestCase (org.apache.geode.test.dunit.cache.internal)
PersistentPartitionedRegionTestBase
(org.apache.geode.internal.cache.partitioned)
PersistentPartitionedRegionWithTransactionDUnitTest
(org.apache.geode.internal.cache.partitioned)
PersistentPartitionedRegionWithDistTXDUnitTest
(org.apache.geode.disttx)
PersistentColocatedPartitionedRegionDUnitTest
(org.apache.geode.internal.cache.partitioned)
PersistentPartitionedRegionDUnitTest
(org.apache.geode.internal.cache.partitioned)
PersistentPartitionedRegionOldConfigDUnitTest
(org.apache.geode.internal.cache.partitioned)
BackupDistributedTest (org.apache.geode.internal.cache.backup)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5175) Remove PersistentPartitionedRegionTestBase
[
https://issues.apache.org/jira/browse/GEODE-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-5175:
Assignee: Kirk Lund
> Remove PersistentPartitionedRegionTestBase
> --
>
> Key: GEODE-5175
> URL: https://issues.apache.org/jira/browse/GEODE-5175
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> Remove PersistentPartitionedRegionTestBase and overhaul the tests that extend
> it:
> {noformat}
> JUnit4DistributedTestCase (org.apache.geode.test.dunit.internal)
> JUnit4CacheTestCase (org.apache.geode.test.dunit.cache.internal)
> PersistentPartitionedRegionTestBase
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithTransactionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithDistTXDUnitTest
> (org.apache.geode.disttx)
> PersistentColocatedPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionOldConfigDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> BackupDistributedTest (org.apache.geode.internal.cache.backup)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5148) CI Failure: InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown
[
https://issues.apache.org/jira/browse/GEODE-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5148:
-
Description:
{noformat}
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> cacheServerPersistWithIOExceptionShouldShutdown FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356)
at
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
at
org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
at org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347)
at
org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
at org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
at
org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164)
... 1 more
{noformat}
was:
{noformat}
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> cacheServerPersistWithIOExceptionShouldShutdown FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
[jira] [Resolved] (GEODE-5111) show missing-disk-stores sometimes does not show the missing disk stores
[ https://issues.apache.org/jira/browse/GEODE-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone resolved GEODE-5111. --- Resolution: Fixed Fix Version/s: 1.7.0 > show missing-disk-stores sometimes does not show the missing disk stores > > > Key: GEODE-5111 > URL: https://issues.apache.org/jira/browse/GEODE-5111 > Project: Geode > Issue Type: Bug >Reporter: Lynn Gallinat >Assignee: Lynn Gallinat >Priority: Major > Labels: persistence, pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When geode logs are showing there is in fact a missing disk store, running > the show-missing-disk-store command sometimes returns that there are no > missing disk stores -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5148) CI Failure: InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown
[
https://issues.apache.org/jira/browse/GEODE-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5148:
-
Description:
{noformat}
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> cacheServerPersistWithIOExceptionShouldShutdown FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356)
at
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
Could not initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
at
org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
at
org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347)
at
org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
at
org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
at
org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346)
at
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164)
... 1 more
{noformat}
was:
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest
> cacheServerPersistWithIOExceptionShouldShutdown FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run
in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539)
at
[jira] [Assigned] (GEODE-5148) CI Failure: InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown
[ https://issues.apache.org/jira/browse/GEODE-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5148: Assignee: Kirk Lund > CI Failure: > InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown > -- > > Key: GEODE-5148 > URL: https://issues.apache.org/jira/browse/GEODE-5148 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > > org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest > > cacheServerPersistWithIOExceptionShouldShutdown FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest$$Lambda$23/1222369873.run > in VM 1 running on Host 0b1780a0efc9 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.InitializedDiskRegionWithIoExceptionRegressionTest.cacheServerPersistWithIOExceptionShouldShutdown(InitializedDiskRegionWithIoExceptionRegressionTest.java:113) > Caused by: > org.apache.geode.cache.NoSubscriptionServersAvailableException: > org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not > initialize a primary queue on startup. No queue servers available. > at > org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187) > at > org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:539) > at > org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:850) > at > org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58) > at > org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:356) > at > org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3749) > at > org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3840) > at > org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3638) > at > org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3633) > at > org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3628) > at > org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:172) > at > org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.lambda$cacheServerPersistWithIOExceptionShouldShutdown$2c6907a2$1(InitializedDiskRegionWithIoExceptionRegressionTest.java:113) > Caused by: > org.apache.geode.cache.NoSubscriptionServersAvailableException: > Could not initialize a primary queue on startup. No queue servers available. > at > org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585) > at > org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296) > at > org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:347) > at > org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172) > at > org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158) > at > org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:346) > at > org.apache.geode.internal.cache.InitializedDiskRegionWithIoExceptionRegressionTest.createClientCache(InitializedDiskRegionWithIoExceptionRegressionTest.java:164) > ... 1 more -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5145: -- Labels: pull-request-available (was: ) > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5010) Introduce *ResultModel objects to replace *ResultData
[ https://issues.apache.org/jira/browse/GEODE-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462586#comment-16462586 ] ASF subversion and git services commented on GEODE-5010: Commit a7c1601708bcf7da6d91b728be8f8a37b8859d90 in geode's branch refs/heads/develop from [~jinmeiliao] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a7c1601 ] GEODE-5010: refactor commands and CommandExecutor to use ResultModel (#1896) > Introduce *ResultModel objects to replace *ResultData > - > > Key: GEODE-5010 > URL: https://issues.apache.org/jira/browse/GEODE-5010 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 3.5h > Remaining Estimate: 0h > > Introduce POJOs to be used as replacements for CompositeResultData, > TabularResultData, InfoResultData and ErrorResultData. > These POJOs will be json serializable using Jackson > Provide ability to use both legacy and these new POJOs until all commands > have been migrated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5083) Alter region --name option no longer auto completes
[ https://issues.apache.org/jira/browse/GEODE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462579#comment-16462579 ] ASF subversion and git services commented on GEODE-5083: Commit 9e4a51f67e7c7a0dd69d5d78bc4f6d8700153382 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9e4a51f ] GEODE-5083: Alter region --name option no longer auto completes (#1898) > Alter region --name option no longer auto completes > --- > > Key: GEODE-5083 > URL: https://issues.apache.org/jira/browse/GEODE-5083 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available, quick_to_fix > Time Spent: 40m > Remaining Estimate: 0h > > when "alter region --name=" is typed, tabbing should show a list of available > regions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir
[ https://issues.apache.org/jira/browse/GEODE-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4218: --- Fix Version/s: (was: 1.6.0) 1.7.0 > load-cluster-configuration-from-dir is no longer required when setting > --cluster-config-dir > --- > > Key: GEODE-4218 > URL: https://issues.apache.org/jira/browse/GEODE-4218 > Project: Geode > Issue Type: Improvement > Components: configuration, docs, management >Reporter: Jinmei Liao >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently if you start a locator with: > load-cluster-configuration-from-dir=true > you would usually need to specify a "cluster-configuration-dir" to go with > it, if you don't, it will default to the locator's working dir which is > usually empty, and when this happens, it will override the entire cluster's > configuration to be empty. > We have deprecated this option. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir
[ https://issues.apache.org/jira/browse/GEODE-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison resolved GEODE-4218. Resolution: Fixed > load-cluster-configuration-from-dir is no longer required when setting > --cluster-config-dir > --- > > Key: GEODE-4218 > URL: https://issues.apache.org/jira/browse/GEODE-4218 > Project: Geode > Issue Type: Improvement > Components: configuration, docs, management >Reporter: Jinmei Liao >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently if you start a locator with: > load-cluster-configuration-from-dir=true > you would usually need to specify a "cluster-configuration-dir" to go with > it, if you don't, it will default to the locator's working dir which is > usually empty, and when this happens, it will override the entire cluster's > configuration to be empty. > We have deprecated this option. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir
[ https://issues.apache.org/jira/browse/GEODE-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4218: --- Fix Version/s: (was: 1.7.0) 1.6.0 > load-cluster-configuration-from-dir is no longer required when setting > --cluster-config-dir > --- > > Key: GEODE-4218 > URL: https://issues.apache.org/jira/browse/GEODE-4218 > Project: Geode > Issue Type: Improvement > Components: configuration, docs, management >Reporter: Jinmei Liao >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently if you start a locator with: > load-cluster-configuration-from-dir=true > you would usually need to specify a "cluster-configuration-dir" to go with > it, if you don't, it will default to the locator's working dir which is > usually empty, and when this happens, it will override the entire cluster's > configuration to be empty. > We have deprecated this option. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir
[ https://issues.apache.org/jira/browse/GEODE-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4218: --- Fix Version/s: (was: 1.6.0) 1.7.0 > load-cluster-configuration-from-dir is no longer required when setting > --cluster-config-dir > --- > > Key: GEODE-4218 > URL: https://issues.apache.org/jira/browse/GEODE-4218 > Project: Geode > Issue Type: Improvement > Components: configuration, docs, management >Reporter: Jinmei Liao >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently if you start a locator with: > load-cluster-configuration-from-dir=true > you would usually need to specify a "cluster-configuration-dir" to go with > it, if you don't, it will default to the locator's working dir which is > usually empty, and when this happens, it will override the entire cluster's > configuration to be empty. > We have deprecated this option. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
[ https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-4833: --- Fix Version/s: (was: 1.6.0) 1.7.0 > JdbcWriter and JdbcAsyncWriter may fail to write null fields to database > > > Key: GEODE-4833 > URL: https://issues.apache.org/jira/browse/GEODE-4833 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method > PreparedStatement.setObject with a value of "null" if the pdx field contains > "null". > This will work with jdbc drivers that support sending "non-typed Null" to the > backend database. > But some drivers do not support this and these puts will fail with a > SQLException. > For portability the jdbc connector should be changed to not pass "null" to > setObject without a type. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5142) new Thread Monitoring Mechanism
[ https://issues.apache.org/jira/browse/GEODE-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-5142: --- Fix Version/s: (was: 1.6.0) 1.7.0 > new Thread Monitoring Mechanism > --- > > Key: GEODE-5142 > URL: https://issues.apache.org/jira/browse/GEODE-5142 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: yossi reginiano >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > One of the most severe issues hitting our real time application is thread > stuck for multiple reasons, such as long lasting locks, deadlocks, threads > which wait for reply forever in case of packet drop issue etc... > Such kind of stuck are under Radar of the existing system health check > methods. In mission critical applications, this will be resulted as an > immediate outage. > Here we introduce thread monitoring mechanism, to detect threads which are > stuck for any reason. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
