[jira] [Updated] (GEODE-5174) JSON examples for gfsh commands, get, put, locate and remove are not valid

2018-05-02 Thread Jens Deppe (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Deppe updated GEODE-5174:
--
Priority: Minor  (was: Major)

> JSON examples for gfsh commands, get, put, locate and remove are not valid
> --
>
> Key: GEODE-5174
> URL: https://issues.apache.org/jira/browse/GEODE-5174
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Jens Deppe
>Priority: Minor
>
> For the gfsh commands {{get, put, locate and remove}} the documentation shows 
> JSON examples enclosed with parentheses and single quotes. Both of these 
> constructs are invalid JSON - in particular the parentheses. For example: 
> {{('key':'value1')}} should be {{\{"key":"value1"\}}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GEODE-5174) JSON examples for gfsh commands, get, put, locate and remove are not valid

2018-05-02 Thread Jens Deppe (JIRA)
Jens Deppe created GEODE-5174:
-

 Summary: JSON examples for gfsh commands, get, put, locate and 
remove are not valid
 Key: GEODE-5174
 URL: https://issues.apache.org/jira/browse/GEODE-5174
 Project: Geode
  Issue Type: Bug
  Components: docs
Reporter: Jens Deppe


For the gfsh commands {{get, put, locate and remove}} the documentation shows 
JSON examples enclosed with parentheses and single quotes. Both of these 
constructs are invalid JSON - in particular the parentheses. For example: 
{{('key':'value1')}} should be {{\{"key":"value1"\}}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements

2018-05-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461738#comment-16461738
 ] 

ASF subversion and git services commented on GEODE-4728:


Commit 53315985c4386e6781473c5713d638c8139e3e8e in geode-native's branch 
refs/heads/develop from [~dbarnes97]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5331598 ]

GEODE-4728: Docs - update system properties list, including 
‘enable-chunkhandler-thread’


> 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: 2h 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] [Assigned] (GEODE-4657) Geode Native receives timeouts in ms during client/server handshake

2018-05-02 Thread Michael Oleske (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Oleske reassigned GEODE-4657:
-

Assignee: Michael Oleske

> Geode Native receives timeouts in ms during client/server handshake
> ---
>
> Key: GEODE-4657
> URL: https://issues.apache.org/jira/browse/GEODE-4657
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Addison
>Assignee: Michael Oleske
>Priority: Major
>
> Geode changed the protocol to use ms during the client/server handshake. 
> Update Geode Native to support this change and bump the ordinal number of 
> Geode Native.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4987) Add rebalancing tests with colocated PRs and AEQ (colocated region)

2018-05-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461652#comment-16461652
 ] 

ASF subversion and git services commented on GEODE-4987:


Commit a8ae434990553dd15aa972587675a7a530f0b167 in geode's branch 
refs/heads/feature/GEODE-4987 from [~lhughesgodfrey]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a8ae434 ]

GEODE-4987: Add rebalancing tests with colocated PRs and AEQ

* Added new tests for colocated PRs and AEQ


> Add rebalancing tests with colocated PRs and AEQ (colocated region) 
> 
>
> Key: GEODE-4987
> URL: https://issues.apache.org/jira/browse/GEODE-4987
> Project: Geode
>  Issue Type: Test
>  Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> Create tests to add colocated partitioned regions during rebalance to verify 
> co-located region does not hang.
> Create similar test with AEQ (which is a colocated region) to verify that 
> mutating region to add AEQ does not hang during rebalance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4987) Add rebalancing tests with colocated PRs and AEQ (colocated region)

2018-05-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461653#comment-16461653
 ] 

ASF subversion and git services commented on GEODE-4987:


Commit 7729d71c98a7749b72d3e751caa2b2fb29949237 in geode's branch 
refs/heads/feature/GEODE-4987 from [~lhughesgodfrey]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7729d71 ]

GEODE-4987: Add rebalancing tests with colocated PRs and AEQ

* Added new tests for colocated PRs and AEQ


> Add rebalancing tests with colocated PRs and AEQ (colocated region) 
> 
>
> Key: GEODE-4987
> URL: https://issues.apache.org/jira/browse/GEODE-4987
> Project: Geode
>  Issue Type: Test
>  Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> Create tests to add colocated partitioned regions during rebalance to verify 
> co-located region does not hang.
> Create similar test with AEQ (which is a colocated region) to verify that 
> mutating region to add AEQ does not hang during rebalance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GEODE-4860) make sure the extensions xsd is upgradable

2018-05-02 Thread Sai Boorlagadda (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461620#comment-16461620
 ] 

Sai Boorlagadda commented on GEODE-4860:


Currently we store XML as a string in the config region and JAXB seems very 
liberal, from java docs - Schema validation is not performed on the input XML. 
The processing will try to continue even if there are errors in the XML, as 
much as possible. Only as the last resort, this method fails with 
DataBindingException. So during unmarshalling, Jaxb ignores any XML 
element/attribute for which it did not find corresponding fields in POJO and 
the other way is trivial from how optional fields are handled.

An extension's XSD is upgradable (addition/deletion of fields) until we store 
XML as a string in the config region. When we make efforts to store POJOs into 
the config region (and as this is a persistent region) either we need POJOs 
implement DataSerializable or use PDX types to be able to recover form disk.

> 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: 10m
>  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] [Assigned] (GEODE-635) CI failure: TXDistributedDUnitTest.testHighAvailabilityFeatures

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-635:
---

Assignee: Kirk Lund

> CI failure: TXDistributedDUnitTest.testHighAvailabilityFeatures
> ---
>
> Key: GEODE-635
> URL: https://issues.apache.org/jira/browse/GEODE-635
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
>
> git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #809
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache30.TXDistributedDUnitTest$31.run in VM 0 running on 
> Host kuwait.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 
> dunit.DistributedTestCase.invokeInEveryVM(DistributedTestCase.java:180)
>   at 
> com.gemstone.gemfire.cache30.TXDistributedDUnitTest.testHighAvailabilityFeatures(TXDistributedDUnitTest.java:752)
> Caused by: junit.framework.AssertionFailedError: expected: but 
> was:
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:86)
>   at junit.framework.TestCase.assertEquals(TestCase.java:253)
>   at 
> com.gemstone.gemfire.cache30.TXDistributedDUnitTest$31.run(TXDistributedDUnitTest.java:739)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4860) make sure the extensions xsd is upgradable

2018-05-02 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-4860:
--
Labels: pull-request-available  (was: )

> 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
>
> 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] [Assigned] (GEODE-932) CI failure: DiskDistributedNoAckAsyncRegionDUnitTest.testRemoteCacheListener

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-932:
---

Assignee: Kirk Lund

> CI failure: DiskDistributedNoAckAsyncRegionDUnitTest.testRemoteCacheListener
> 
>
> Key: GEODE-932
> URL: https://issues.apache.org/jira/browse/GEODE-932
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Sai Boorlagadda
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
>
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$52.run in VM 1 running on 
> Host cc6-co6.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$52.run in VM 1 running on 
> Host cc6-co6.gemstone.com with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:370)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:313)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:267)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.testRemoteCacheListener(MultiVMRegionTestCase.java:1241)
>   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.GeneratedMethodAccessor220.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.GeneratedMethodAccessor219.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: Event never occurred after 
> 3000 ms: listener was never invoked
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.TestCase.fail(TestCase.java:227)
>   at 
> 

[jira] [Resolved] (GEODE-845) DistTXExpiryJUnitTest.testRegionIdleExpiration

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund resolved GEODE-845.
-
   Resolution: Fixed
Fix Version/s: 1.7.0

> DistTXExpiryJUnitTest.testRegionIdleExpiration
> --
>
> Key: GEODE-845
> URL: https://issues.apache.org/jira/browse/GEODE-845
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: xiaojian zhou
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Revision: 942b89e0b1591a6ccf9cefa4c0e3f5dba8bad34b
> buid 1447 IntegrationTest
> {noformat}
> java.lang.AssertionError: Expiration should not cause commit to fail
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.TXExpiryJUnitTest.generalRegionExpirationTest(TXExpiryJUnitTest.java:397)
>   at 
> com.gemstone.gemfire.TXExpiryJUnitTest.testRegionIdleExpiration(TXExpiryJUnitTest.java:335)
>   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 
> 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.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.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.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 
> 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.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 
> 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)
>  

[jira] [Assigned] (GEODE-845) DistTXExpiryJUnitTest.testRegionIdleExpiration

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-845:
---

Assignee: Kirk Lund

> DistTXExpiryJUnitTest.testRegionIdleExpiration
> --
>
> Key: GEODE-845
> URL: https://issues.apache.org/jira/browse/GEODE-845
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: xiaojian zhou
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky, pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Revision: 942b89e0b1591a6ccf9cefa4c0e3f5dba8bad34b
> buid 1447 IntegrationTest
> {noformat}
> java.lang.AssertionError: Expiration should not cause commit to fail
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.TXExpiryJUnitTest.generalRegionExpirationTest(TXExpiryJUnitTest.java:397)
>   at 
> com.gemstone.gemfire.TXExpiryJUnitTest.testRegionIdleExpiration(TXExpiryJUnitTest.java:335)
>   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 
> 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.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.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.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 
> 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.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 
> 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 
> 

[jira] [Resolved] (GEODE-1139) CI failure: ShorteningExpirationTimeRegressionTest.testPut

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund resolved GEODE-1139.
--
   Resolution: Fixed
Fix Version/s: 1.7.0

> CI failure: ShorteningExpirationTimeRegressionTest.testPut
> --
>
> Key: GEODE-1139
> URL: https://issues.apache.org/jira/browse/GEODE-1139
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Bruce Schuchardt
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
> Fix For: 1.7.0
>
>
> This test failed in revision 274f67cae769fbba1f6e63ff866f7f761b9a4229
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testPut(Bug44418JUnitTest.java:96)
>   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 
> 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.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.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.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 
> 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.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 
> 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 
> 

[jira] [Resolved] (GEODE-924) CI failure: ShorteningExpirationTimeRegressionTest.testGet

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund resolved GEODE-924.
-
   Resolution: Fixed
Fix Version/s: 1.7.0

> CI failure: ShorteningExpirationTimeRegressionTest.testGet
> --
>
> Key: GEODE-924
> URL: https://issues.apache.org/jira/browse/GEODE-924
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Sai Boorlagadda
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> {noformat}
> Error Message
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
> Stacktrace
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testGet(Bug44418JUnitTest.java:145)
>   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 
> 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.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.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.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 
> 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.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 
> 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 
> 

[jira] [Assigned] (GEODE-924) CI failure: ShorteningExpirationTimeRegressionTest.testGet

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-924:
---

Assignee: Kirk Lund

> CI failure: ShorteningExpirationTimeRegressionTest.testGet
> --
>
> Key: GEODE-924
> URL: https://issues.apache.org/jira/browse/GEODE-924
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Sai Boorlagadda
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky, pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> {noformat}
> Error Message
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
> Stacktrace
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testGet(Bug44418JUnitTest.java:145)
>   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 
> 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.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.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.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 
> 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.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 
> 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 
> 

[jira] [Assigned] (GEODE-1139) CI failure: ShorteningExpirationTimeRegressionTest.testPut

2018-05-02 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-1139:


Assignee: Kirk Lund

> CI failure: ShorteningExpirationTimeRegressionTest.testPut
> --
>
> Key: GEODE-1139
> URL: https://issues.apache.org/jira/browse/GEODE-1139
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Bruce Schuchardt
>Assignee: Kirk Lund
>Priority: Major
>  Labels: CI, Flaky
> Fix For: 1.7.0
>
>
> This test failed in revision 274f67cae769fbba1f6e63ff866f7f761b9a4229
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testPut(Bug44418JUnitTest.java:96)
>   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 
> 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.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.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.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 
> 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.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 
> 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)
>  

[jira] [Commented] (GEODE-1139) CI failure: ShorteningExpirationTimeRegressionTest.testPut

2018-05-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461617#comment-16461617
 ] 

ASF subversion and git services commented on GEODE-1139:


Commit 66b9f4298023f962650e75dc2ad31acfc9d179dc in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=66b9f42 ]

GEODE-924: GEODE-1139: Fix flakiness in ShorteningExpirationTimeRegressionTest


> CI failure: ShorteningExpirationTimeRegressionTest.testPut
> --
>
> Key: GEODE-1139
> URL: https://issues.apache.org/jira/browse/GEODE-1139
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: CI, Flaky
>
> This test failed in revision 274f67cae769fbba1f6e63ff866f7f761b9a4229
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testPut(Bug44418JUnitTest.java:96)
>   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 
> 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.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.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.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 
> 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.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 
> 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 
> 

[jira] [Commented] (GEODE-924) CI failure: ShorteningExpirationTimeRegressionTest.testGet

2018-05-02 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461616#comment-16461616
 ] 

ASF subversion and git services commented on GEODE-924:
---

Commit 66b9f4298023f962650e75dc2ad31acfc9d179dc in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=66b9f42 ]

GEODE-924: GEODE-1139: Fix flakiness in ShorteningExpirationTimeRegressionTest


> CI failure: ShorteningExpirationTimeRegressionTest.testGet
> --
>
> Key: GEODE-924
> URL: https://issues.apache.org/jira/browse/GEODE-924
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Sai Boorlagadda
>Priority: Major
>  Labels: CI, Flaky, pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> {noformat}
> Error Message
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
> Stacktrace
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testGet(Bug44418JUnitTest.java:145)
>   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 
> 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.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.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.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 
> 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.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 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> 

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

2018-05-02 Thread Eric Shu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu reassigned GEODE-5173:
---

Assignee: Eric Shu

> Transactional get from a client on a REPLICATE_HEAP_LRU region throws 
> NotSerializableException
> --
>
> Key: GEODE-5173
> URL: https://issues.apache.org/jira/browse/GEODE-5173
> Project: Geode
>  Issue Type: Bug
>  Components: persistence, transactions
>Reporter: Dan Smith
>Assignee: Eric Shu
>Priority: Major
>
> Doing a get from a client within a transaction on a region with persistence 
> and overflow results in the below exception.
> It looks like this issue has to do with some code returning a 
> Token.NOT_AVAILABLE rather than reading the value from disk if the get is 
> performed within a transaction. Without using transactions, this same use 
> case works:
>  
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.1.10.126(15995:loner):34188:40be7322: 
> org.apache.geode.SerializationException: failed serializing object
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:384)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:231)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:140)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>   at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>   at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>   at 
> org.apache.geode.internal.cache.tx.ClientTXRegionStub.findObject(ClientTXRegionStub.java:72)
>   at 
> org.apache.geode.internal.cache.TXStateStub.findObject(TXStateStub.java:472)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.findObject(TXStateProxyImpl.java:536)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1400)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1334)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1319)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:408)
>   at 
> org.apache.geode.internal.cache.ClientPersistentTransactionDUnitTest.lambda$test$2c6907a2$1(ClientPersistentTransactionDUnitTest.java:75)
>   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.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
>   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:568)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>   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)
> Caused by: 

[jira] [Updated] (GEODE-5165) Avoid OOME when scanning for annotated classes

2018-05-02 Thread Patrick Rhomberg (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Rhomberg updated GEODE-5165:

Component/s: docs

> Avoid OOME when scanning for annotated classes
> --
>
> Key: GEODE-5165
> URL: https://issues.apache.org/jira/browse/GEODE-5165
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, docs
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> when we scan the entire classpath for a certain annotated class, we ran into 
> OOME in our test environment. Need to add a capability to limit the packages 
> to scan if geode.packagesToScan system property is set.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2018-05-02 Thread Dan Smith (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461574#comment-16461574
 ] 

Dan Smith commented on GEODE-5173:
--

Geode Dunit test that demonstrates the problem is here: 
https://github.com/upthewaterspout/geode/tree/feature/GEODE-5173

> Transactional get from a client on a REPLICATE_HEAP_LRU region throws 
> NotSerializableException
> --
>
> Key: GEODE-5173
> URL: https://issues.apache.org/jira/browse/GEODE-5173
> Project: Geode
>  Issue Type: Bug
>  Components: persistence, transactions
>Reporter: Dan Smith
>Priority: Major
>
> Doing a get from a client within a transaction on a region with persistence 
> and overflow results in the below exception.
> It looks like this issue has to do with some code returning a 
> Token.NOT_AVAILABLE rather than reading the value from disk if the get is 
> performed within a transaction. Without using transactions, this same use 
> case works:
>  
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.1.10.126(15995:loner):34188:40be7322: 
> org.apache.geode.SerializationException: failed serializing object
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:384)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:231)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:140)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>   at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>   at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>   at 
> org.apache.geode.internal.cache.tx.ClientTXRegionStub.findObject(ClientTXRegionStub.java:72)
>   at 
> org.apache.geode.internal.cache.TXStateStub.findObject(TXStateStub.java:472)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.findObject(TXStateProxyImpl.java:536)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1400)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1334)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1319)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:408)
>   at 
> org.apache.geode.internal.cache.ClientPersistentTransactionDUnitTest.lambda$test$2c6907a2$1(ClientPersistentTransactionDUnitTest.java:75)
>   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.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
>   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:568)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> 

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

2018-05-02 Thread Dan Smith (JIRA)

[ 
https://issues.apache.org/jira/browse/GEODE-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461573#comment-16461573
 ] 

Dan Smith commented on GEODE-5173:
--

This issue was first reported by Pieter van Zyl on the user list - 
https://lists.apache.org/thread.html/bb7ffadb2cab2811a9cff74e296221a1554b7c58d76e8facc76c7e33@%3Cuser.geode.apache.org%3E

> Transactional get from a client on a REPLICATE_HEAP_LRU region throws 
> NotSerializableException
> --
>
> Key: GEODE-5173
> URL: https://issues.apache.org/jira/browse/GEODE-5173
> Project: Geode
>  Issue Type: Bug
>  Components: persistence, transactions
>Reporter: Dan Smith
>Priority: Major
>
> Doing a get from a client within a transaction on a region with persistence 
> and overflow results in the below exception.
> It looks like this issue has to do with some code returning a 
> Token.NOT_AVAILABLE rather than reading the value from disk if the get is 
> performed within a transaction. Without using transactions, this same use 
> case works:
>  
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.1.10.126(15995:loner):34188:40be7322: 
> org.apache.geode.SerializationException: failed serializing object
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:384)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:231)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:140)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>   at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>   at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>   at 
> org.apache.geode.internal.cache.tx.ClientTXRegionStub.findObject(ClientTXRegionStub.java:72)
>   at 
> org.apache.geode.internal.cache.TXStateStub.findObject(TXStateStub.java:472)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.findObject(TXStateProxyImpl.java:536)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1400)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1334)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1319)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:408)
>   at 
> org.apache.geode.internal.cache.ClientPersistentTransactionDUnitTest.lambda$test$2c6907a2$1(ClientPersistentTransactionDUnitTest.java:75)
>   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.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
>   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:568)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>   at 
> 

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

2018-05-02 Thread Dan Smith (JIRA)
Dan Smith created GEODE-5173:


 Summary: Transactional get from a client on a REPLICATE_HEAP_LRU 
region throws NotSerializableException
 Key: GEODE-5173
 URL: https://issues.apache.org/jira/browse/GEODE-5173
 Project: Geode
  Issue Type: Bug
  Components: persistence, transactions
Reporter: Dan Smith


Doing a get from a client within a transaction on a region with persistence and 
overflow results in the below exception.

It looks like this issue has to do with some code returning a 
Token.NOT_AVAILABLE rather than reading the value from disk if the get is 
performed within a transaction. Without using transactions, this same use case 
works:

 
{noformat}
Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
server on 10.1.10.126(15995:loner):34188:40be7322: 
org.apache.geode.SerializationException: failed serializing object
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:384)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithServerAffinity(OpExecutorImpl.java:231)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:140)
at 
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
at 
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
at 
org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
at 
org.apache.geode.internal.cache.tx.ClientTXRegionStub.findObject(ClientTXRegionStub.java:72)
at 
org.apache.geode.internal.cache.TXStateStub.findObject(TXStateStub.java:472)
at 
org.apache.geode.internal.cache.TXStateProxyImpl.findObject(TXStateProxyImpl.java:536)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1400)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1334)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1319)
at 
org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:408)
at 
org.apache.geode.internal.cache.ClientPersistentTransactionDUnitTest.lambda$test$2c6907a2$1(ClientPersistentTransactionDUnitTest.java:75)
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.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
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:568)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
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)
Caused by: org.apache.geode.SerializationException: failed serializing object
at 
org.apache.geode.internal.cache.tier.sockets.Message.serializeAndAddPart(Message.java:401)
at 
org.apache.geode.internal.cache.tier.sockets.Message.addPartInAnyForm(Message.java:362)
at 
org.apache.geode.internal.cache.tier.sockets.command.Get70.writeResponse(Get70.java:424)

[jira] [Updated] (GEODE-5141) Add Geode version reference to LuceneIndexFactory javadocs for setLuceneSerializer method

2018-05-02 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5141:
--
Labels: pull-request-available  (was: )

> Add Geode version reference to LuceneIndexFactory javadocs for 
> setLuceneSerializer method
> -
>
> Key: GEODE-5141
> URL: https://issues.apache.org/jira/browse/GEODE-5141
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Diane Hardman
>Priority: Major
>  Labels: pull-request-available
>
> The setLuceneSerializer method for LuceneIndexFactory was added in Geode 
> 1.4.0. This needs to be added to the javadocs so users know which versions 
> support this method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5132) CI failure: org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest > testParallelPropagationLoopBack3Sites FAILED

2018-05-02 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-5132:
--
Labels: pull-request-available  (was: )

> CI failure: 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
>  > testParallelPropagationLoopBack3Sites FAILED
> ---
>
> Key: GEODE-5132
> URL: https://issues.apache.org/jira/browse/GEODE-5132
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Affects Versions: 1.7.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>  Labels: pull-request-available
>
> This failure occurred during CI:
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/296
> {noformat}
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest
>  > testParallelPropagationLoopBack3Sites FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest$$Lambda$162/1703391551.run
>  in VM 4 running on Host 83b9797d6847 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.parallel.ParallelWANPropagationLoopBackDUnitTest.testParallelPropagationLoopBack3Sites(ParallelWANPropagationLoopBackDUnitTest.java:210)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition defined as a 
> lambda expression in org.apache.geode.internal.cache.wan.WANTestBase that 
> uses int, intorg.apache.geode.cache.Region null within 3 milliseconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at 
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2721)
> at 
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize(WANTestBase.java:2706)
> at 
> org.apache.geode.internal.cache.wan.parallel.ParallelWANPropagationLoopBackDUnitTest.lambda$testParallelPropagationLoopBack3Sites$bb17a952$21(ParallelWANPropagationLoopBackDUnitTest.java:210)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4808) Add performance tests for rebalance simulation

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4808.


> Add performance tests for rebalance simulation
> --
>
> Key: GEODE-4808
> URL: https://issues.apache.org/jira/browse/GEODE-4808
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Create test to measure the computation overhead of rebalance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4902) Log markers filter some messages pathologically

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4902.


> Log markers filter some messages pathologically
> ---
>
> Key: GEODE-4902
> URL: https://issues.apache.org/jira/browse/GEODE-4902
> Project: Geode
>  Issue Type: Bug
>  Components: docs, logging
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Many logging calls across all log levels are marked with 
> {{o.a.g.internal.logging.log4j.LogMarker}} markers for selective enabling and 
> debugging.  All these markers have a parent marker {{GEODE_VERBOSE}}.  
> However, per the default given in 
> {{geode-core/src/main/resources/log4j2.xml}}, this parent marker is set to 
> filter log messages.
> Many of these log messages are invoked at the {{info}} level, suggesting an 
> expectation that the message would be seen.
> These markers should be refactored to (a) include by default markers that 
> commonly or exclusively appear in coarse-grained logging levels, and (b) to 
> reorganize the markers' parent/child relationships so that they are not 
> blanket-disabled by default.  Only those markers attacked to more verbose 
> logging should be disabled by default.
> ---
> Additionally, the log classes {{FastLogger}} and {{LogWriterLogger}} are 
> themselves slightly pathological.  Notably, the former overrides some 
> {{isEnabled}} aliases but leaves exposed default many of the root method 
> signatures.  The latter pathologically includes a reference to itself as a 
> field unto itself in the lines:
> {noformat}
> private final ExtendedLoggerWrapper logWrapper;
> // ...
>   private LogWriterLogger(final Logger logger, final String connectionName,
>   final boolean isSecure) {
> super((AbstractLogger) logger, logger.getName(), 
> logger.getMessageFactory());
> this.logWrapper = this;
> // ...
>   }
> {noformat}
> These classes could use refactoring in their own right, perhaps as a separate 
> child ticket.
> -
> Docs: While only the top-level marker (formerly {{GEMFIRE_VERBOSE}}, now 
> {{GEODE_VERBOSE}}) is documented, it may be worth a release note that the 
> Log4J2 markers have changed, and anyone be using a custom log4j2.xml after 
> discovering these markers will have to update that XML to the new markers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5039) EvictionAttributesMutator.setMaximum does not work

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5039.


> EvictionAttributesMutator.setMaximum does not work
> --
>
> Key: GEODE-5039
> URL: https://issues.apache.org/jira/browse/GEODE-5039
> Project: Geode
>  Issue Type: Bug
>  Components: eviction
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> EvictionAttributesMutator.setMaximum does not change the lru count.
>  
> Given I am configuring eviction
> When setting EvictionAttributesMutator.setMaximum
> Then the lru count should update accordingly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4884) Remove Thread.sleep from ServerLauncherDUnitTest

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4884.


> Remove Thread.sleep from ServerLauncherDUnitTest
> 
>
> Key: GEODE-4884
> URL: https://issues.apache.org/jira/browse/GEODE-4884
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
> Fix For: 1.6.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4989) CQ reply message fromData method deserializes query results

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4989.


> CQ reply message fromData method deserializes query results
> ---
>
> Key: GEODE-4989
> URL: https://issues.apache.org/jira/browse/GEODE-4989
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Recent changes in DataSerializableFixedID serialization have left CQ reply 
> message handling in a bad state.  When results are read they are deserialized 
> into POJOs and this can cause queries to hang if the domain classes aren't 
> available in the server.  Even if they are it will hit performance because 
> the objects are completely deserialized and then have to be re-serialized to 
> be sent to clients.
> If the classes aren't available an exception like this will be thrown:
> {noformat}
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage
>  .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2703)
>   at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3543)
>   at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1827)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1688)
>   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)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.cache.query.internal.CqEntry .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2862)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readUserObject(InternalDataSerializer.java:2817)
>   at 
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage.fromData(StreamingOperation.java:559)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 8 more
> Caused by: org.apache.geode.pdx.PdxSerializationException: Could not create 
> an instance of a class util.PdxVersionedQueryObject
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:239)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.basicGetObject(PdxReaderImpl.java:687)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.getObject(PdxReaderImpl.java:682)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readPdxSerializable(InternalDataSerializer.java:3226)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:3031)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.cache.query.internal.CqEntry.fromData(CqEntry.java:95)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 14 more
> Caused by: java.lang.ClassNotFoundException: util.PdxVersionedQueryObject
>   at 
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
>   at 
> org.apache.geode.internal.InternalDataSerializer.getCachedClass(InternalDataSerializer.java:3870)
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:235)
>   ... 21 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4836) Protobuf getRequest returns VALUE_NOT_SET if a value is null

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4836.


> Protobuf getRequest returns VALUE_NOT_SET if a value is null
> 
>
> Key: GEODE-4836
> URL: https://issues.apache.org/jira/browse/GEODE-4836
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It is bypassing the serializationService and not setting the value. I'm not 
> sure why this didn't break CI earlier but I am fixing it now.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4845) FieldSerializationUtils should be package-private

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4845.


> FieldSerializationUtils should be package-private
> -
>
> Key: GEODE-4845
> URL: https://issues.apache.org/jira/browse/GEODE-4845
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Fix For: 1.6.0
>
>
> FieldSerializationUtils is currently public but should be package-private.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4217) gfsh create jdbc-connection command allows a password to be set without a user name

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4217.


> gfsh create jdbc-connection command  allows a password to be set without a 
> user name
> 
>
> Key: GEODE-4217
> URL: https://issues.apache.org/jira/browse/GEODE-4217
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The gfsh create jdbc-connection command  allows a password to be set without 
> a user name.
> If you configure a password you must also configure a user name and this 
> should be validated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4451) When a gateway sender is created using gfsh and fails to connect due to AuthenticationFailedException, it is left in an inconsistent state

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4451.


> When a gateway sender is created using gfsh and fails to connect due to 
> AuthenticationFailedException, it is left in an inconsistent state
> --
>
> Key: GEODE-4451
> URL: https://issues.apache.org/jira/browse/GEODE-4451
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> If I attempt to create a gateway sender with invalid credentials using gfsh, 
> it fails like:
> {noformat}
> (2) Executing - create gateway-sender --remote-distributed-system-id=1 
> --id=ny --dispatcher-threads=1 --parallel=true
> Member | Status
> -- | 
> --
> ln-1 | ERROR: Could not start a gateway sender ny because of exception Could 
> not start a gateway sender 84 because of exception 
> org.apache.geode.security.AuthenticationFailedException: Authentication 
> error. Please check your credentials.
> {noformat}
> The 84 should be the gateway sender id; instead its the thread id (from 
> \{{ConcurrentParallelGatewaySenderEventProcessor.waitForRunningStatus}}.
> In the server log, I see 5 AuthenticationFailedException stacks like (one per 
> dispatcher-thread):
> {noformat}
> [severe 2018/01/31 16:13:12.638 PST ln-1  GatewaySender_ny_0> tid=0x55] Message dispatch failed due to unexpected 
> exception..
> org.apache.geode.internal.cache.wan.GatewaySenderException: 
> org.apache.geode.security.AuthenticationFailedException: Authentication 
> error. Please check your credentials., caused by 
> org.apache.geode.security.AuthenticationFailedException: Authentication 
> error. Please check your credentials.
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:432)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.(GatewaySenderEventRemoteDispatcher.java:75)
>  at 
> org.apache.geode.internal.cache.wan.parallel.RemoteParallelGatewaySenderEventProcessor.initializeEventDispatcher(RemoteParallelGatewaySenderEventProcessor.java:74)
>  at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.setRunningStatus(AbstractGatewaySenderEventProcessor.java:1078)
>  at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1050)
> Caused by: org.apache.geode.security.AuthenticationFailedException: 
> Authentication error. Please check your credentials.
>  at 
> org.apache.geode.internal.cache.tier.sockets.HandShake.readMessage(HandShake.java:1397)
>  at 
> org.apache.geode.internal.cache.tier.sockets.HandShake.handshakeWithServer(HandShake.java:1253)
>  at 
> org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:118)
>  at 
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:136)
>  at 
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
>  at 
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:206)
>  at 
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:902)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:388)
>  ... 4 more
> {noformat}
> A thread dump shows the Event Processor threads are gone, but 5 
> BatchRemovalThreads like this exist:
> {noformat}
> "BatchRemovalThread" #96 daemon prio=10 os_prio=31 tid=0x7fc1dd009000 
> nid=0xcb03 waiting on condition [0x7e245000]
>  java.lang.Thread.State: TIMED_WAITING (parking)
>  at sun.misc.Unsafe.park(Native Method)
>  - parking to wait for <0x0007a04043c8> (a 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>  at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
>  at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2163)
>  at 
> org.apache.geode.internal.util.concurrent.StoppableCondition.await(StoppableCondition.java:61)
>  at 
> 

[jira] [Closed] (GEODE-5007) Add unit tests for TabularResultData

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5007.


> Add unit tests for TabularResultData
> 
>
> Key: GEODE-5007
> URL: https://issues.apache.org/jira/browse/GEODE-5007
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4681) Remove all static methods involving pdxReadSerialized

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4681.


> Remove all static methods involving pdxReadSerialized 
> --
>
> Key: GEODE-4681
> URL: https://issues.apache.org/jira/browse/GEODE-4681
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> Remove the following static methods after GEODE-4679 is completed.
>  * setPdxReadSerialized()
>  * getPdxReadSerialized()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4520) Remove singleton calls from product code in org.apache.geode.management.internal.configuration.callbacks

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4520.


> Remove singleton calls from product code in 
> org.apache.geode.management.internal.configuration.callbacks
> 
>
> Key: GEODE-4520
> URL: https://issues.apache.org/jira/browse/GEODE-4520
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> These product classes in 
> org.apache.geode.management.internal.configuration.callbacks invoke singleton 
> getters.
> CacheFactory.getAnyInstance():
> * ConfigurationChangeListener



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5068) Upgrade Jackson to 2.9.5

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5068.


> Upgrade Jackson to 2.9.5
> 
>
> Key: GEODE-5068
> URL: https://issues.apache.org/jira/browse/GEODE-5068
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> We're a patch version behind, let's try to stay on the latest.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4750) Add finer grained security to OQL queries with protobuf

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4750.


> Add finer grained security to OQL queries with protobuf
> ---
>
> Key: GEODE-4750
> URL: https://issues.apache.org/jira/browse/GEODE-4750
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Dan Smith
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> After GEODE-3126 and GEODE-4406 are implemented, we should update the 
> OqlOperationHandler to allow queries if the user has access to the individual 
> regions. Currently the changes for GEODE-3126 are validating that the user 
> has DATA:READ access for all regions in order to do a query.
> The QueryCommand class has an example of how to validate the regions involved 
> in the query.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4923) Add Geode extensions jars to Geode's classpath

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4923.


> Add Geode extensions jars to Geode's classpath
> --
>
> Key: GEODE-4923
> URL: https://issues.apache.org/jira/browse/GEODE-4923
> Project: Geode
>  Issue Type: Improvement
>  Components: extensions
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Geode extensions jars will be put in `extensions` directory. And the jars 
> in the `extensions` directory should be added to the classpath of Geode 
> locator/server and `gfsh`. So that Geode will pick up the extensions 
> automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4266) JMX manager should not deserialize exceptions from server

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4266.


> JMX manager should not deserialize exceptions from server
> -
>
> Key: GEODE-4266
> URL: https://issues.apache.org/jira/browse/GEODE-4266
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Assignee: Nick Reich
>Priority: Major
>  Labels: jdbc, pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Steps
> Created a jdbc-connection, jdbc-mapping, region in gfsh
> Tried a .get from the region which attempted to read through with the 
> JdbcLoader
> However it could not connect to the endpoint and threw an exception (fine).  
> But the exception wasn't handled in gfsh -- gfsh appeared hung.
> [info 2018/01/09 13:42:41.338 PST s1  
> tid=0x4b] Exception occurred:
> java.lang.IllegalStateException: Could not connect ...
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.getConnection(SqlHandler.java:59)
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.read(SqlHandler.java:73)
>   at org.apache.geode.connectors.jdbc.JdbcLoader.load(JdbcLoader.java:52)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doLocalLoad(SearchLoadAndWriteProcessor.java:791)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.load(SearchLoadAndWriteProcessor.java:602)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.searchAndLoad(SearchLoadAndWriteProcessor.java:461)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doSearchAndLoad(SearchLoadAndWriteProcessor.java:177)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findUsingSearchLoad(DistributedRegion.java:2338)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findObjectInSystem(DistributedRegion.java:2208)
>   at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1477)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1366)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1300)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1285)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:320)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:443)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:151)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.execute(DataCommandFunction.java:116)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:187)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:987)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: 
> Communications link failure
> The last packet sent successfully to the server was 0 milliseconds ago. The 
> driver has not received any packets from the server.
>   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 com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
>   at 
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:341)
>   at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2186)
>   at 
> 

[jira] [Closed] (GEODE-4770) Destroying an unstarted GatewayReceiver throws an NPE

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4770.


> Destroying an unstarted GatewayReceiver throws an NPE
> -
>
> Key: GEODE-4770
> URL: https://issues.apache.org/jira/browse/GEODE-4770
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Found while writing tests for a new Gfsh command to destroy a GatewayReceiver:
> Create a GatewayReceiver with manualStart = true
> {{create gateway-receiver --manual-start==true ...}}
> NPE is thrown by the {{destroy()}} in the Function that implements the new 
> {{destroy gateway-receiver}} command.
> {code:java}
> if (receiver.isRunning()) {
>   receiver.stop();
> }
> receiver.destroy();
> {code}
> NPE is thrown here:
> {code:java|title=GatewayReceiverImpl}
>   public void destroy() {
> if (receiver.isRunning()) {
> {code}
> because {{receiver}} is not set until the the GatewayReceiver is started.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4872.


> JdbcReader throws serialization exception for byte[] when the field type is 
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Anilkumar Gingade
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> JdbcReader when creating PdxInstance throws serialization exception for 
> byte[] when its field type is treated as Object. This field is mapped in the 
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.118.33.196(66546:loner):64576:da7cbe2f: 
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a 
> PDX field
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>     at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>     at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>     at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>     at 
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
>     at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
>     at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
>     at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
>     at 
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
>     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.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
>     at sun.rmi.transport.Transport$1.run(Transport.java:200)
>     at sun.rmi.transport.Transport$1.run(Transport.java:197)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>     at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>     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)
> Caused by: org.apache.geode.pdx.PdxSerializationException: Exception while 
> serializing a PDX field
>     at 
> org.apache.geode.pdx.internal.PdxOutputStream.writeObject(PdxOutputStream.java:84)
>     at 
> org.apache.geode.pdx.internal.PdxWriterImpl.writeObject(PdxWriterImpl.java:329)
>     at 
> 

[jira] [Closed] (GEODE-4384) gfsh command to destroy jndi binding

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4384.


> gfsh command to destroy jndi binding
> 
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy 
> jndi-binding --name=jndi-binding-name}}
>  Then the datasource will be deleted from the cluster and the binding will be 
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-3237) Loading cluster configuration from a dir that does not have complete CC will throw NPE

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-3237.


> Loading cluster configuration from a dir that does not have complete CC will 
> throw NPE
> --
>
> Key: GEODE-3237
> URL: https://issues.apache.org/jira/browse/GEODE-3237
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> We should handle the error more gracefully and informatively. Currently if 
> user did the following:
> gfsh> start locator --name=locator
>  gfsh> shutdown --include-lcoator=true
>  gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true
> the console message says "Cluster configuration service has been started, but 
> its not running yet",
>  and there is an NPE in the log:
>  [error 2017/07/18 10:22:38.357 PDT locator  
> tid=0x41] null
>  java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
>  at 
> org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
>  at java.lang.Thread.run(Thread.java:745)
> The error message if no directory is specified, should be saying:
> {code:java}
> The option load-cluster-configuration-from-dir=true is specified but the 
> option -cluster-config-dir needs to be set with a directory to the cluster 
> config file.{code}
> The error message if the directory is specified but cluster config file is 
> not found in that directory:
> {code:java}
> No cluster configuration is found in {code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4868) when member deposed primary buckets, it did not decrease the queue size

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4868.


> when member deposed primary buckets, it did not decrease the queue size
> ---
>
> Key: GEODE-4868
> URL: https://issues.apache.org/jira/browse/GEODE-4868
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> It can use following test code to reproduce the issue:
> diff --git 
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
>  
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> index 545d0cac4..fbc0dc015 100644
> --- 
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> +++ 
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> @@ -717,6 +717,10 @@ public class AsyncEventQueueTestBase extends 
> JUnit4DistributedTestCase {
>        }
>      }
>      final AsyncEventQueueStats statistics = ((AsyncEventQueueImpl) 
> queue).getStatistics();
> +    Awaitility.await().atMost(60, TimeUnit.SECONDS)
> +    .until(() -> assertEquals("Expected queue entries: " + queueSize
> +        + " but actual entries: " + statistics.getEventQueueSize(), 
> queueSize,
> +        statistics.getEventQueueSize()));
>      assertEquals(queueSize, statistics.getEventQueueSize());
>      assertEquals(eventsReceived, statistics.getEventsReceived());
> diff --git 
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
>  
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> index 465f35a87..058bf19cc 100644
> --- 
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> +++ 
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> @@ -1519,6 +1519,11 @@ public class AsyncEventListenerDUnitTest extends 
> AsyncEventQueueTestBase {
>          () -> 
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() + 
> "_PR"));
>  
>      LogWriterUtils.getLogWriter().info("Primary buckets on vm2: " + 
> primaryBucketsvm2);
> +    
> +    // before shutdown vm2, both vm1 and vm2 should have 40 events in 
> primary queue
> +    vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln", 
> 40,
> 80, 80, 0));
> +    vm2.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln", 
> 40, 80, 80, 0));
> +    
>      //  Kill vm2 --
>      vm2.invoke(() -> AsyncEventQueueTestBase.killSender());
>      // 
> @@ -1527,15 +1532,26 @@ public class AsyncEventListenerDUnitTest extends 
> AsyncEventQueueTestBase {
>      vm3.invoke(createCacheRunnable(lnPort));
>      vm3.invoke(() -> 
> AsyncEventQueueTestBase.createAsyncEventQueueWithListener2("ln", true, 100, 5,
>          false, null));
> +    // vm3 will move some primary buckets from vm1, but vm1's primary queue 
> size did not reduce
> +    vm3.invoke(pauseAsyncEventQueueRunnable());
>      vm3.invoke(() -> 
> AsyncEventQueueTestBase.createPRWithRedundantCopyWithAsyncEventQueue(
>          getTestMethodName() + "_PR", "ln", isOffHeap()));
> -
> +    
>      // --
>      String regionName = getTestMethodName() + "_PR";
>      Set primaryBucketsvm3 = (Set) vm3
>          .invoke(() -> 
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(regionName));
> +    LogWriterUtils.getLogWriter().info("Primary buckets on vm3: " + 
> primaryBucketsvm3);
> +    Set primaryBucketsvm1 = (Set) vm1.invoke(
> +            () -> 
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() + 
> "_PR"));
> +    LogWriterUtils.getLogWriter().info("After shutdown vm2, started vm3, 
> Primary buckets on vm1: " + primaryBucketsvm1);
>  
> +//    vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln", 
> 80, 80, 80, 0));
> +    vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln", 
> 40, 80, 80, 0));
> +    vm3.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln", 
> 40, 0, 0, 0));
> +
> +    vm3.invoke(() -> AsyncEventQueueTestBase.resumeAsyncEventQueue("ln"));
>      vm1.invoke(() -> AsyncEventQueueTestBase.resumeAsyncEventQueue("ln"));
>  
>      vm1.invoke(() -> 
> 

[jira] [Closed] (GEODE-4950) Improve spotless -- upgrade version

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4950.


> Improve spotless -- upgrade version
> ---
>
> Key: GEODE-4950
> URL: https://issues.apache.org/jira/browse/GEODE-4950
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Fix For: 1.6.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4936) Update version dependency for jackson-databind

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4936.


> Update version dependency for jackson-databind
> --
>
> Key: GEODE-4936
> URL: https://issues.apache.org/jira/browse/GEODE-4936
> Project: Geode
>  Issue Type: Bug
>  Components: build, pulse
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Priority: Major
> Fix For: 1.6.0
>
>
> jackson-databind version 2.9.5 fixes an incomplete fix in version 2.9.4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4901) CI: destroyAeqWhenQueueDoesNotExist_withIfExistsReturnsSuccess FAILED

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4901.


>  CI: destroyAeqWhenQueueDoesNotExist_withIfExistsReturnsSuccess FAILED
> --
>
> Key: GEODE-4901
> URL: https://issues.apache.org/jira/browse/GEODE-4901
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tests
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest
>  > destroyAeqWhenQueueDoesNotExist_withIfExistsReturnsSuccess FAILED
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:514]
>  org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.MemberVM$$Lambda$47/931061186.run in VM 0 
> running on Host f8202c330a1c with 4 VMs
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:515]
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:516]
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:517]
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:313)
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:518]
>  at 
> org.apache.geode.test.dunit.rules.MemberVM.waitTillAsyncEventQueuesAreReadyOnServers(MemberVM.java:109)
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:519]
>  at 
> org.apache.geode.management.internal.cli.commands.DestroyAsyncEventQueueCommandDUnitTest.destroyAeqWhenQueueDoesNotExist_withIfExistsReturnsSuccess(DestroyAsyncEventQueueCommandDUnitTest.java:105)
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:520]
>  
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:521]
>  Caused by:
> [ 
> |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/185#L5a9dea38:522]
>  org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in org.apache.geode.test.junit.rules.MemberStarterRule was not 
> fulfilled within 2 seconds.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4818) Remove TcpConduit.beSick() and DirectChannel.beSick()

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4818.


> Remove TcpConduit.beSick() and DirectChannel.beSick()
> -
>
> Key: GEODE-4818
> URL: https://issues.apache.org/jira/browse/GEODE-4818
> Project: Geode
>  Issue Type: Improvement
>  Components: messaging
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Trivial
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> These two test methods are no-ops and should therefore be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5027) Bump version to 1.6.0

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5027.


> Bump version to 1.6.0
> -
>
> Key: GEODE-5027
> URL: https://issues.apache.org/jira/browse/GEODE-5027
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> Bump the version to 1.6.0 and add 1.5.0 as an "old version" for backward 
> compatibility tests.
> Also clean up the CommandInitializer tables.  We're creating a new table for 
> every version even when there are no messaging changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5029) Improve docs for query timeout and low memory due to a query

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5029.


> Improve docs for query timeout and low memory due to a query
> 
>
> Key: GEODE-5029
> URL: https://issues.apache.org/jira/browse/GEODE-5029
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The section labeled "Monitoring Queries for Low Memory" can use a bit of 
> improvement. 
> Separate the section into 2 sections:
>  # Queries and low memory
>  # Query timeout 
> Make the prose clear that this is not just about monitoring, but about action 
> that is taken (exceptions thrown) for queries.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4986) Refactor GMSEncrypt

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4986.


> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4930) Add @Disabled annotation to be applied to GfshCommand classes.

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4930.


> Add @Disabled annotation to be applied to GfshCommand classes.
> --
>
> Key: GEODE-4930
> URL: https://issues.apache.org/jira/browse/GEODE-4930
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4755) Jar deploy fails on Windows

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4755.


> Jar deploy fails on Windows
> ---
>
> Key: GEODE-4755
> URL: https://issues.apache.org/jira/browse/GEODE-4755
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Fails with this exception:
> {noformat}
> java.lang.UnsupportedOperationException: 'posix:permissions' not supported as 
> initial attribute
>at 
> sun.nio.fs.WindowsSecurityDescriptor.fromAttribute(WindowsSecurityDescriptor.java:358)
>at 
> sun.nio.fs.WindowsFileSystemProvider.createDirectory(WindowsFileSystemProvider.java:492)
>at java.nio.file.Files.createDirectory(Files.java:674)
>at java.nio.file.TempFileHelper.create(TempFileHelper.java:136)
>at 
> java.nio.file.TempFileHelper.createTempDirectory(TempFileHelper.java:173)
>at java.nio.file.Files.createTempDirectory(Files.java:991)
>at 
> org.apache.geode.management.internal.beans.FileUploader.uploadFile(FileUploader.java:77)
> {noformat}
> Potential classes affected:
> {noformat}
> org.apache.geode.distributed.internal.ClusterConfigurationService
> org.apache.geode.internal.cache.ClusterConfigurationLoader
> org.apache.geode.management.internal.beans.FileUploader
> org.apache.geode.management.internal.cli.functions.DeployFunction
> org.apache.geode.management.internal.web.controllers.AbstractCommandsController
> {noformat}
> Posixness can be checked with 
> {{FileSystems.getDefault().supportedFileAttributeViews().contains(“posix”);}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5003) Add unit tests for CompositeResultData

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5003.


> Add unit tests for CompositeResultData
> --
>
> Key: GEODE-5003
> URL: https://issues.apache.org/jira/browse/GEODE-5003
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4929) PR Accessor with Overflow should not create DiskStore

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4929.


> PR Accessor with Overflow should not create DiskStore
> -
>
> Key: GEODE-4929
> URL: https://issues.apache.org/jira/browse/GEODE-4929
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> While renaming Bug42055DUnitTest as 
> BucketRegionSizeWithOverflowRegressionTest, I found that the test had never 
> been "completed" so I finished writing it according to the summary and 
> description of the original TRAC bug.
> Javadocs on the test say:
> {noformat}
> Test that the bucket size does not go negative when we fault out and in a 
> delta object.
> {noformat}
> ...but the original bug doesn't seem to be specific to delta, so I recommend 
> writing another test to cover what this javadoc describes.
> The summary of TRAC #42055 is:
> {noformat}
> a pr accessor configured for OverflowToDisk fails during creation because of 
> disk
> {noformat}
> I interpret the bug as saying:
> {noformat}
> PR accessor configured for OverflowToDisk should not create a diskstore.
> {noformat}
> Unfortunately, the test shows that the Accessor does in fact create a 
> diskstore. I'm marking the test with {{\@Ignore("GEODE-4929")}} until we can 
> fix this bug or determine that the assertion is invalid.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4869) Move all the Configuration objects to a public package

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4869.


> Move all the Configuration objects to a public package
> --
>
> Key: GEODE-4869
> URL: https://issues.apache.org/jira/browse/GEODE-4869
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> # Currently the configuration objects generated by the xsd is in  
> org.apache.geode.internal.cache.configuration package. We need to move them 
> all to a public package, probably org.apache.geode.cache.configuration 
> package. 
>  # Consider rename CacheConfig to CacheType and RegionConfig to RegionType 
> for consistency with other classes in the package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4922) JDBC connector does not handle java.util.Date

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4922.


> JDBC connector does not handle java.util.Date
> -
>
> Key: GEODE-4922
> URL: https://issues.apache.org/jira/browse/GEODE-4922
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Pdx types can have java.util.Date fields or object fields that contain 
> java.util.Date.
> When these are written that java.util.Date may cause a failure from the jdbc 
> driver if it does not support java.util.Date. Jdbc drivers must support 
> java.sql.Date, java.sql.Time, and java.sql.Timestamp but may not support 
> java.util.Date.
> The JDBC connector should convert java.util.Date to one of the java.sql 
> interfaces using the data type of the column to determine which one to 
> convert it to.
> When reading from jdbc back into geode if the pdx field is java.util.Date 
> then we should convert the java.sql.* instance to java.util.Date. It is also 
> possible we should do this conversion if the pdx field is of type object.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4669) gfsh start locator hangs under JDK 9

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4669.


> gfsh start locator hangs under JDK 9
> 
>
> Key: GEODE-4669
> URL: https://issues.apache.org/jira/browse/GEODE-4669
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When trying to run geode using JDK 9, gfsh start locator hangs.
> With a little debugging, I tracked the problem down to some code that is 
> trying to find jar file in the JDK directory. It's throwing an exception, 
> which is getting silently swallowed. Below is the exception from a debugger.
> We need to figure out a better way to get the status of a locator with JDK 9.
> {noformat}
> java.io.IOException: JDK management agent not found
>   at 
> org.apache.geode.internal.process.MBeanProcessController.getJMXServiceURL(MBeanProcessController.java:250)
>   at 
> org.apache.geode.internal.process.MBeanProcessController.connect(MBeanProcessController.java:195)
>   at 
> org.apache.geode.internal.process.MBeanProcessController.invokeOperationOnTargetMBean(MBeanProcessController.java:162)
>   at 
> org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:139)
>   at 
> org.apache.geode.internal.process.MBeanProcessController.status(MBeanProcessController.java:84)
>   at 
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:935)
>   at 
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:863)
>   at 
> org.apache.geode.distributed.LocatorLauncher$LocatorState.fromDirectory(LocatorLauncher.java:1985)
>   at 
> org.apache.geode.management.internal.cli.commands.StartLocatorCommand.startLocator(StartLocatorCommand.java:232)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:564)
>   at 
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
>   at 
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
>   at 
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
>   at 
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
>   at 
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
>   at 
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
>   at 
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1014)
>   at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4991.


> JDBC connector should not hard code quotes around identifiers in SQL 
> statements
> ---
>
> Key: GEODE-4991
> URL: https://issues.apache.org/jira/browse/GEODE-4991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently the JDBC connector has double quotes around all identifiers in SQL 
> statements it creates.
> Instead of always using double quotes, it should instead ask JDBC using 
> java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
> and use that.
> For databases that do not support quoting identifiers a space is returned.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4683) Replace setPdxReadSerialized in org.apache.geode.distributed.internal.streaming;

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4683.


> Replace setPdxReadSerialized in 
> org.apache.geode.distributed.internal.streaming;
> 
>
> Key: GEODE-4683
> URL: https://issues.apache.org/jira/browse/GEODE-4683
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> Replace with the fix available from GEODE-4679



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4830) Modify list jndi-binding gfsh command

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4830.


> Modify list jndi-binding gfsh command 
> --
>
> Key: GEODE-4830
> URL: https://issues.apache.org/jira/browse/GEODE-4830
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Joey McAllister
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The list jndi-binding command currently displays jndi-bindings that are 
> active.
> We need to modify the output of this command to list all jndi-bindings that 
> are listed in the cluster config and indicate in the output of this command 
> whether the binding is active or configured.
> We should update the help text to reflect this change. A suggested help text 
> is:
> {code:java}
> List all jndi bindings, active and configured. An active binding is one that 
> is bound to the server's jndi context (and also listed in the cluster 
> config). A configured binding is one that is listed in the cluster config, 
> but is not active.{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4979) Incorrect description in documentation of ResourcePermission in OQL

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4979.


> Incorrect description in documentation of ResourcePermission in OQL
> ---
>
> Key: GEODE-4979
> URL: https://issues.apache.org/jira/browse/GEODE-4979
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Masaki Yamakawa
>Assignee: Dave Barnes
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the OQL Authorization, the description in documentation of 
> ResourcePermission is incorrect. It is 'DATA:READ' in the description, but 
> 'DATA:READ:RegionName' is actually.
> The document page is as follows:
> [https://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4768) protobuf driver is not closing its socket connections to the locator

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4768.


> protobuf driver is not closing its socket connections to the locator
> 
>
> Key: GEODE-4768
> URL: https://issues.apache.org/jira/browse/GEODE-4768
> Project: Geode
>  Issue Type: Task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> While reviewing code in the experimental protobuf driver I noticed that the 
> findAServer method is creating socket connections to locators but is not 
> closing them.  Ideally it would abort the socket connections by setting 
> solinger to zero so the locator doesn't accumulate sockets in a time-wait 
> state.  See GEODE-871.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4911) Remove DataSerializer.TRACE_SERIALIZABLE

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4911.


> Remove DataSerializer.TRACE_SERIALIZABLE
> 
>
> Key: GEODE-4911
> URL: https://issues.apache.org/jira/browse/GEODE-4911
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available, starter
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> This is a boolean that's set from a system property. Since it's never used, 
> we should probably delete it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4859) Create a public version of GfshCommand

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4859.


> Create a public version of GfshCommand 
> ---
>
> Key: GEODE-4859
> URL: https://issues.apache.org/jira/browse/GEODE-4859
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> this would expose
>  # the public Cache interface
>  # the public ClusterConfigurationService
>  # other methods in GfshCommand if appropriate, like findMember, 
> executeFunction etc.
>  # add @experiental to it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4883) ServerLauncherDUnitTest.ensureCleanShutdownFromInProcessServerLauncher fails with BindException

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4883.


> ServerLauncherDUnitTest.ensureCleanShutdownFromInProcessServerLauncher fails 
> with BindException
> ---
>
> Key: GEODE-4883
> URL: https://issues.apache.org/jira/browse/GEODE-4883
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.6.0
>
>
> {noformat}
> org.apache.geode.distributed.ServerLauncherDUnitTest > 
> ensureCleanShutdownFromInProcessServerLauncher 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 1094
> [error 2018/03/17 05:17:22.907 UTC  tid=0x16] Exception in 
> thread "main" java.lang.RuntimeException: An IO error occurred while starting 
> a Server in /tmp/junit574046504456632823/junit5385654653268781087 on 
> 8eb8d57154a4[40404]: Network is unreachable; port (40404) is not available on 
> localhost.
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:804)
>   at 
> org.apache.geode.distributed.ServerLauncherDUnitTestHelper.main(ServerLauncherDUnitTestHelper.java:30)
> Caused by: java.net.BindException: Network is unreachable; port (40404) 
> is not available on localhost.
>   at 
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:129)
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:749)
>   ... 1 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4894) JDBC connector needs to be work with databases support for mixed case identifiers

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4894.


> JDBC connector needs to be work with databases support for mixed case 
> identifiers
> -
>
> Key: GEODE-4894
> URL: https://issues.apache.org/jira/browse/GEODE-4894
> Project: Geode
>  Issue Type: Bug
>  Components: docs, extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, the jdbc connector will convert a database column name to all 
> lower case if a region mapping for that column does not exist. But it is 
> possible that the database supports mixed case identifiers in which case the 
> connector should honor the mixed case column name.
> Also, when the connector is creating the prepared statement, the string it 
> uses does not quote the column names in that string. They should be quoted 
> since the database may support mixed case quoted identifiers.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4644) Remove static ClientSideHandshake.deltaEnabledOnServer

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4644.


> Remove static ClientSideHandshake.deltaEnabledOnServer
> --
>
> Key: GEODE-4644
> URL: https://issues.apache.org/jira/browse/GEODE-4644
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This static is used by the cache



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4888) Document security-udp-dhalgo property

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4888.


> Document security-udp-dhalgo property
> -
>
> Key: GEODE-4888
> URL: https://issues.apache.org/jira/browse/GEODE-4888
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Document the security-udp-dhalgo property.  It is a string that defines the 
> name of a valid symmetric key cipher supported by the JDK.  When defined, the 
> cipher will be used for server to server UDP communications.
> Also update the ssl-enabled-components property definition to recommend to 
> users that when ssl-enabled-components is defined, they should also set 
> security-udp-dhalgo to secure cluster communications.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4735) All CliUtils functions should take cache as a parameter if it needs one.

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4735.


> All CliUtils functions should take cache as a parameter if it needs one. 
> -
>
> Key: GEODE-4735
> URL: https://issues.apache.org/jira/browse/GEODE-4735
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> get rid of Cache.getInstance call from CliUtils and GfshCommand. 
> Commands/functions/tests that use CliUtils should supply its own cache when 
> using these functions.
> Commands's access to cache should be injected when the commands are 
> initialized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4974) JDBC connector is creating one connection pool per region

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4974.


> JDBC connector is creating one connection pool per region
> -
>
> Key: GEODE-4974
> URL: https://issues.apache.org/jira/browse/GEODE-4974
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The issue is worse with partitioned regions, where a pool is created per 
> bucket region. Need to move the pool creation to a centralized location used 
> by all regions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4945) InternalGfshCommand should not have to implement CommandMarker directly

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4945.


> InternalGfshCommand should not have to implement CommandMarker directly
> ---
>
> Key: GEODE-4945
> URL: https://issues.apache.org/jira/browse/GEODE-4945
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> InternalGfshCommand should only need to implement GfshCommand (as GfshCommand 
> already implements CommandMarker)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4518) make DSCODE an enum

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4518.


> make DSCODE an enum
> ---
>
> Key: GEODE-4518
> URL: https://issues.apache.org/jira/browse/GEODE-4518
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: Starter, pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> From DSCODE:
> {color:#629755}/**
> {color}{color:#629755} * An interface that contains a bunch of static final 
> values used for the implementation of
> {color}{color:#629755} * {{color}{color:#629755}@link 
> {color}{color:#629755}DataSerializer}. It is basically an Enum and could be 
> changed to one once we drop 1.4. The
> {color}{color:#629755} * allowed range of these codes is -128..127 inclusive 
> (i.e. byte).
> {color}{color:#629755} *
> {color}{color:#629755} * {color}{color:#629755}@since 
> {color}{color:#629755}GemFire 5.7{color}
> {color:#33}Since we no longer support Java 4, let's make this an 
> enum.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4666) CI failures in geode examples - Network is unreachable; port (10334) is not available on localhost

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4666.


> CI failures in geode examples - Network is unreachable; port (10334) is not 
> available on localhost
> --
>
> Key: GEODE-4666
> URL: https://issues.apache.org/jira/browse/GEODE-4666
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Dan Smith
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> The geode-examples jobs are sometimes failing with port conflicts. Below is 
> an example
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/TestExamples/builds/24]
> {noformat}
> :serialization:start
> 1. Executing - start locator --name=locator --bind-address=127.0.0.1
> The Locator process terminated unexpectedly with exit status 1. Please 
> refer to the log file in 
> /tmp/build/ea3e9ea4/geode-examples/serialization/locator for full details.
> Feb 12, 2018 11:25:19 PM org.apache.geode.distributed.LocatorLauncher 
> failOnStart
> INFO: locator is exiting due to an exception
> java.net.BindException: Network is unreachable; port (10334) is not available 
> on localhost.
>     at 
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:131)
>     at 
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:635)
>     at 
> org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:549)
>     at 
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:192)
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred 
> while starting a Locator in 
> /tmp/build/ea3e9ea4/geode-examples/serialization/locator on localhost[10334]: 
> Network is unreachable; port (10334) is not available on localhost.
>     at 
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:655)
>     at 
> org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:549)
>     at 
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:192)
> Caused by: java.net.BindException: Network is unreachable; port (10334) is 
> not available on localhost.
>     at 
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:131)
>     at 
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:635)
>     ... 2 more
> :serialization:start FAILED
> {noformat}
> I did some digging, and I think the cause is that the gfsh shutdown command 
> from a previous test has not finished shutting down the locator.
> Looking at the code, it looks like there is some code that is intended to 
> shutdown and wait for a certain amount of time. But the logic is flawed, 
> because it is executing a function and not waiting for the results.
> {code:java}
>   Callable shutdownNodes = () -> {
> try {
>   Execution execution = FunctionService.onMembers(includeMembers);
>   
>//** HERE, execute submits the function asynchronously
>execution.execute(shutDownFunction);
> } catch (FunctionException functionEx) {
>   // Expected Exception as the function is shutting down the target 
> members and the result
>   // collector will get member departed exception
> }
> return "SUCCESS";
>   };
>   Future result = exec.submit(shutdownNodes);
>   result.get(timeout, TimeUnit.MILLISECONDS);
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4972) Move VersionManager into geode-old-versions module

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4972.


> Move VersionManager into geode-old-versions module
> --
>
> Key: GEODE-4972
> URL: https://issues.apache.org/jira/browse/GEODE-4972
> Project: Geode
>  Issue Type: Task
>  Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This is a precursor to GEODE-4971



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5004) Add unit tests for ErrorResultData

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5004.


> Add unit tests for ErrorResultData
> --
>
> Key: GEODE-5004
> URL: https://issues.apache.org/jira/browse/GEODE-5004
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4885) DistributedRestoreSystemPropertiesTest is failing

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4885.


> DistributedRestoreSystemPropertiesTest is failing
> -
>
> Key: GEODE-4885
> URL: https://issues.apache.org/jira/browse/GEODE-4885
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> This test is supposedly checking for any {{DUnitTest}} that inadvertently 
> runs under the {{test}} gradle task or, more specifically, is categorized as 
> a {{UnitTest}}.
> Unfortunately, due to the way that Junit determines what category a test is 
> in (by creating an instance of the class), it will also invoke any static 
> declarations. It also triggers parameterized values. The result is that some 
> {{DistributedTests}} actually end up launching DUnit VMs even though the 
> actual tests don't run. Depending on test ordering this can lead to 
> {{DistributedRestoreSystemPropertiesTest}} failing intermittently.
> By examining the test report, it appears that the following DUnit tests are 
> triggering this problem:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShowLogCommandDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest
> org.apache.geode.security.ClientAuthenticationPart2DUnitTest
> org.apache.geode.cache.lucene.LuceneCommandsSecurityDUnitTest
> org.apache.geode.management.internal.configuration.ClusterConfigurationIndexWithFromClauseDUnitTest
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgrade2DUnitTest
> org.apache.geode.security.ClientAuthenticationDUnitTest
> org.apache.geode.security.ClientAuthorizationCQDUnitTest
> org.apache.geode.internal.cache.TxCommitMessageBackwardCompatibilityDUnitTest
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4810) Create model subpackage for rebalance

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4810.


> Create model subpackage for rebalance
> -
>
> Key: GEODE-4810
> URL: https://issues.apache.org/jira/browse/GEODE-4810
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
> Fix For: 1.6.0
>
>
> Move classes for the purpose of modeling the cluster for rebalance purposes 
> into their own package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4927) CI failure: configureClientSSLSocketCanTimeOut can time out

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4927.


> CI failure: configureClientSSLSocketCanTimeOut can time out
> ---
>
> Key: GEODE-4927
> URL: https://issues.apache.org/jira/browse/GEODE-4927
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
> Fix For: 1.6.0
>
>
> Nevermind, I was looking at a bad branch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5046) RemotePutMessage.distribute should handle RegionDestoryedException

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5046.


> RemotePutMessage.distribute should handle RegionDestoryedException
> --
>
> Key: GEODE-5046
> URL: https://issues.apache.org/jira/browse/GEODE-5046
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> RemotePutMessage.distribute() tries to get a version tag from a remote member 
> in a loop. It tries another member if one member failed. 
> It is possible that a region is destroyed on a member, and the method should 
> handle it and retry to another member instead of failing the operation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4878) Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4878.


> Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest
> -
>
> Key: GEODE-4878
> URL: https://issues.apache.org/jira/browse/GEODE-4878
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4864) Document new gfsh create jndi binding command

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4864.


> Document new gfsh create jndi binding command
> -
>
> Key: GEODE-4864
> URL: https://issues.apache.org/jira/browse/GEODE-4864
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The new gfsh command to create a JNDI binding was included in Geode 1.5, but 
> the documentation of the command was forgotten.  This ticket is to complete 
> the documentation of the new gfsh command.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4798) JdbcConnectorException can not be deserialized

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4798.


> JdbcConnectorException can not be deserialized
> --
>
> Key: GEODE-4798
> URL: https://issues.apache.org/jira/browse/GEODE-4798
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
> Fix For: 1.6.0
>
>
> The JdbcConnectorException cannot be deserialized because it is not a 
> "trusted" class. Also the SQLException it usually wraps will also fail 
> deserialization so it might be better to not create JdbcConnectorException 
> instances whose cause is a SQLException. Instead do some type of conversion 
> of the SQLException.
> The following is some information about how to get JdbcConnectorException to 
> be trusted by the serialization code:
> Create a new DistributionService like this lucene one:
> LuceneDistributedSystemService
> geode-lucene/src/main/resources/META-INF/services/org.apache.geode.distributed.internal.DistributedSystemService
> It returns a text file with a whitelist.
> Add a test like 
> org.apache.geode.codeAnalysis.AnalyzeLuceneSerializablesJUnitTest



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4386) gfsh command to describe jndi binding

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4386.


> gfsh command to describe jndi binding
> -
>
> Key: GEODE-4386
> URL: https://issues.apache.org/jira/browse/GEODE-4386
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Joey McAllister
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to describe a datasource using the gfsh command 
> {{describe jndi-binding --name=jndi-binding-name}}
>  Then list the particular datasource with attributes and don't display the 
> password.
>  The
> {code:java}
> describe  jndi-binding{code} command should be able to describe any 
> jndi-binding that is output by the {code} list jndi-binding{code} command. 
> The output of the {code} describe jndi-binding{code} needs to indicate 
> whether a binding is active or not.
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5026) Do not run AcceptanceTests under docker

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5026.


> Do not run AcceptanceTests under docker
> ---
>
> Key: GEODE-5026
> URL: https://issues.apache.org/jira/browse/GEODE-5026
> Project: Geode
>  Issue Type: Task
>  Components: build, tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Newer AcceptanceTests are trying to launch their own docker containers which 
> causes a problem when they themselves are already running in a docker 
> container.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4662) Protobuf: Add GetEntryCount message

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4662.


> Protobuf: Add GetEntryCount message
> ---
>
> Key: GEODE-4662
> URL: https://issues.apache.org/jira/browse/GEODE-4662
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I need to be able to retrive the entry count 
> for a given region.
> Add GetEntryCount message, returning the count of entries for the provided 
> region.  Return an error if the region does not exist.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-5005) Add unit tests for InfoResultData

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-5005.


> Add unit tests for InfoResultData
> -
>
> Key: GEODE-5005
> URL: https://issues.apache.org/jira/browse/GEODE-5005
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4795.


> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4793) DUnit tests fail on Windows

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4793.


> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:699)
> [vm0] ... 33 more
> {noformat}
> The problem boils down to the use of `Files.list` which sometimes will hold 
> open a directory and prevent its cleanup between tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4943) Add isConnectedAndReady method to GfshCommand

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4943.


> Add isConnectedAndReady method to GfshCommand
> -
>
> Key: GEODE-4943
> URL: https://issues.apache.org/jira/browse/GEODE-4943
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We did not originally make this public, but it may be used when a command 
> checks for availability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4804) Docs: How to install

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4804.


> Docs: How to install
> 
>
> Key: GEODE-4804
> URL: https://issues.apache.org/jira/browse/GEODE-4804
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Assignee: Dave Barnes
>Priority: Major
> Fix For: 1.6.0
>
>
> Users can see how to install the client on the following system 
> configurations.
> * Linux C++
> * Solaris C++
> * Windows C++
> * Windows C#



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4882) AnalyzeConnectorsSerializablesJUnitTest failing intermittently with CacheClosedException

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4882.


> AnalyzeConnectorsSerializablesJUnitTest failing intermittently with 
> CacheClosedException
> 
>
> Key: GEODE-4882
> URL: https://issues.apache.org/jira/browse/GEODE-4882
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The following failure has happened twice this week but not in a row. So this 
> test is intermittently failing.
> {noformat}
> :geode-connectors:integrationTest
>  
> org.apache.geode.codeAnalysis.AnalyzeConnectorsSerializablesJUnitTest > 
> testSanctionedClassesExistAndDoDeserialize FAILED
> org.apache.geode.cache.CacheClosedException: Could not PDX serialize because 
> the cache was closed
>  {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4801) Readme should link to "how to contribute" on wiki

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4801.


> Readme should link to "how to contribute" on wiki
> -
>
> Key: GEODE-4801
> URL: https://issues.apache.org/jira/browse/GEODE-4801
> Project: Geode
>  Issue Type: Improvement
>  Components: website
>Reporter: Alexander Murmann
>Assignee: Alexander Murmann
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-2999) New flow: Put if absent

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-2999.


> New flow: Put if absent
> ---
>
> Key: GEODE-2999
> URL: https://issues.apache.org/jira/browse/GEODE-2999
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Galen O'Sullivan
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I need to be able to put an entry only if it 
> doesn't already exist in the cache.
> Create proto message definitions and op handler for "put-if-absent" messages.
> Client should receive error if key already exists. Put should only succeed if 
> key did not already exist.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4832) CacheWriterGetOldValueIntegrationTest can fail because previous test left disk store around

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4832.


> CacheWriterGetOldValueIntegrationTest can fail because previous test left 
> disk store around
> ---
>
> Key: GEODE-4832
> URL: https://issues.apache.org/jira/browse/GEODE-4832
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: Flaky, pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The following failure was seen once. It is hard to say what was left around 
> from a previous test that impacted this one. But if this one would use a tmp 
> directory for its disk store then it would not accidently use a disk store 
> that a previous test left around.
> Also if it used a unique region name, instead of "/region" it would not have 
> had the following failure.
> {noformat}
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest > 
> getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted 
> to disk so it can not be recreated on the same disk store without 
> persistence. Either destroy the persistent region, recreate it as overflow 
> and persistent, or create the overflow only region on a different disk store.
> at 
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at 
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at 
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at 
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at 
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at 
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at 
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at 
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doTest(CacheWriterGetOldValueIntegrationTest.java:110)
> at 
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.getOldValueWithTransactionInCacheWriterReturnsValueOfEvictedEntry(CacheWriterGetOldValueIntegrationTest.java:71)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest > 
> doRemoveAll FAILED
> java.lang.IllegalStateException: The region "/region" has been persisted 
> to disk so it can not be recreated on the same disk store without 
> persistence. Either destroy the persistent region, recreate it as overflow 
> and persistent, or create the overflow only region on a different disk store.
> at 
> org.apache.geode.internal.cache.DiskRegion.(DiskRegion.java:97)
> at 
> org.apache.geode.internal.cache.DiskInitFile.createDiskRegion(DiskInitFile.java:861)
> at 
> org.apache.geode.internal.cache.DiskRegion.create(DiskRegion.java:175)
> at 
> org.apache.geode.internal.cache.LocalRegion.createDiskRegion(LocalRegion.java:7634)
> at 
> org.apache.geode.internal.cache.LocalRegion.(LocalRegion.java:618)
> at 
> org.apache.geode.internal.cache.DistributedRegion.(DistributedRegion.java:191)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3026)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2957)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2945)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:756)
> at 
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.createOverflowRegion(CacheWriterGetOldValueIntegrationTest.java:283)
> at 
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest.doRemoveAll(CacheWriterGetOldValueIntegrationTest.java:93)
> org.apache.geode.internal.cache.CacheWriterGetOldValueIntegrationTest > 
> getOldValueInCacheWriterReturnsValueOfEvictedEntry FAILED
> java.lang.IllegalStateException: The region 

[jira] [Closed] (GEODE-4817) Enhance experimental driver with SSL

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4817.


> Enhance experimental driver with SSL
> 
>
> Key: GEODE-4817
> URL: https://issues.apache.org/jira/browse/GEODE-4817
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> The experimental driver does not experiment with SSL. It ought.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4924) gfsh only accepts a single JAVA_ARGS argument on Windows.

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4924.


> gfsh only accepts a single JAVA_ARGS argument on Windows.
> -
>
> Key: GEODE-4924
> URL: https://issues.apache.org/jira/browse/GEODE-4924
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> {{gfsh.bat}} incorrectly escapes {{AVA_ARG}} environment variable resulting 
> in passing them as a single argument to the {{java.exe}}. 
>  
> {noformat}
> > set JAVA_ARGS=-Xmx1g -client
> > gfsh
> Invalid maximum heap size: -Xmx1g -client{noformat}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (GEODE-4816) Enhance experimental driver with authentication

2018-05-02 Thread Anthony Baker (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anthony Baker closed GEODE-4816.


> Enhance experimental driver with authentication
> ---
>
> Key: GEODE-4816
> URL: https://issues.apache.org/jira/browse/GEODE-4816
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The experimental driver does not experiment with authentication. It ought.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   3   >