[jira] [Commented] (GEODE-3523) AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable to connect to any locators in the list

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3523:


Commit c54e6189a46e4544e096cc817b920ad13b85efe9 in geode's branch 
refs/heads/feature/GEODE-3523 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c54e618 ]

GEODE-3523 AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed

Refactored the test into two smaller tests, one that tests that a client
discovers another locator and another that tests that a client discovers
that a locator has gone away.

I did some general updating of the code in this class to
- replace SerializableCallable/Runnables with lambdas
- replace wait-loops with Awaitility
- replace use of AvailablePortHelper with wildcard binds
- replace ignoring of Exceptions with checks for the correct exception class
- replaced heavy use of deprecated methods with their non-deprecated versions


> AutoConnectionSourceDUnitTest: testDynamicallyFindLocators failed with Unable 
> to connect to any locators in the list
> 
>
> Key: GEODE-3523
> URL: https://issues.apache.org/jira/browse/GEODE-3523
> Project: Geode
>  Issue Type: Bug
>  Components: locator
>Reporter: Hitesh Khamesra
>Assignee: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest > 
> testDynamicallyFindLocators FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest$3.call 
> in VM 2 running on Host 97e556d10832 with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:325)
> at 
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putInVM(AutoConnectionSourceDUnitTest.java:470)
> at 
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.putAndWaitForSuccess(AutoConnectionSourceDUnitTest.java:448)
> at 
> org.apache.geode.cache.client.internal.AutoConnectionSourceDUnitTest.testDynamicallyFindLocators(AutoConnectionSourceDUnitTest.java:199)
> Caused by:
> org.apache.geode.cache.client.NoAvailableLocatorsException: Unable to 
> connect to any locators in the list [LocatorAddress 
> [socketInetAddress=97e556d10832/172.17.0.4:26078, hostname=97e556d10832, 
> isIpString=false], LocatorAddress 
> [socketInetAddress=97e556d10832/172.17.0.4:29796, hostname=172.17.0.4, 
> isIpString=true]]



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

[jira] [Created] (GEODE-5121) CI Failure: org.apache.geode.session.tests.Jetty9Test > failureShouldStillAllowOtherContainersDataAccess

[Barry Oglesby (JIRA)]

Barry Oglesby created GEODE-5121:


 Summary: CI Failure: org.apache.geode.session.tests.Jetty9Test > 
failureShouldStillAllowOtherContainersDataAccess
 Key: GEODE-5121
 URL: https://issues.apache.org/jira/browse/GEODE-5121
 Project: Geode
  Issue Type: Bug
  Components: http session
Reporter: Barry Oglesby


https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/10

[http://files.apachegeode-ci.info/builds/1.6.0-build.9/test-results/distributedTest/1524217535/]
{noformat}
java.lang.RuntimeException: Something very bad happened when trying to start 
container 
JETTY9_peer-to-peer_failureShouldStillAllowOtherContainersDataAccess_1_8563772118360307_
at 
org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:80)
at 
org.apache.geode.session.tests.ContainerManager.startContainers(ContainerManager.java:91)
at 
org.apache.geode.session.tests.ContainerManager.startAllInactiveContainers(ContainerManager.java:98)
at 
org.apache.geode.session.tests.CargoTestBase.failureShouldStillAllowOtherContainersDataAccess(CargoTestBase.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:147)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:129)
at 

[jira] [Created] (GEODE-5120) Remove DistributedSystem

[Ernest Burghardt (JIRA)]

Ernest Burghardt created GEODE-5120:
---

 Summary: Remove DistributedSystem
 Key: GEODE-5120
 URL: https://issues.apache.org/jira/browse/GEODE-5120
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Ernest Burghardt


DistributedSystem does not need to exist as a separate class, it should be 
folded into CacheImpl



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

[jira] [Resolved] (GEODE-5119) Add spruce to ci docker image

[Sean Goller (JIRA)]

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

Sean Goller resolved GEODE-5119.

Resolution: Fixed

> Add spruce to ci docker image
> -
>
> Key: GEODE-5119
> URL: https://issues.apache.org/jira/browse/GEODE-5119
> Project: Geode
>  Issue Type: Task
>  Components: ci
>Reporter: Sean Goller
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> In order to do more complex pipelines, we need spruce installed.



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

[jira] [Commented] (GEODE-4997) Document how to use Geode as an inline cache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4997:


Commit b3ac9a8c2b2e914eb68969736d956ab193727bcf in geode's branch 
refs/heads/feature/GEODE-4997 from [~karensmolermiller]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b3ac9a8 ]

GEODE-4997 WIP Add info on cache loaders for inline caches


> Document how to use Geode as an inline cache
> 
>
> Key: GEODE-4997
> URL: https://issues.apache.org/jira/browse/GEODE-4997
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Describe what an inline cache is and how a Geode region together with 
> deployed code on a server can form an inline cache.
> Describe the code/interface that a developer must implement.
> Document how to configure and/or deploy the code.



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

[jira] [Closed] (GEODE-3464) If multiple MessageHandlers are found user should see exception

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3464.


> If multiple MessageHandlers are found user should see exception
> ---
>
> Key: GEODE-3464
> URL: https://issues.apache.org/jira/browse/GEODE-3464
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Alexander Murmann
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> Currently the system will use the first MessageHandler it finds. If there are 
> multiple it's unclear which one will be used, resulting in potentially 
> nondeterministic behavior. Instead a exception should be thrown if multiple 
> handlers are present. That behavior is still not ideal, but at least it's 
> deterministic.



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

[jira] [Closed] (GEODE-4219) CI suspect string: java.lang.AssertionError: The put operation in queue did not succeed due to CacheClosedException

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4219.


> CI suspect string:  java.lang.AssertionError: The put operation in queue did 
> not succeed due to CacheClosedException
> 
>
> Key: GEODE-4219
> URL: https://issues.apache.org/jira/browse/GEODE-4219
> Project: Geode
>  Issue Type: Bug
>  Components: client queues
>Affects Versions: 1.4.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This suspect string was seen during CI:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/60
> {noformat}
> org.apache.geode.internal.cache.ha.HARegionQueueDUnitTest > 
> testConcurrentOperationsDunitTestOnNonBlockingQueueWithDNoAckRegion 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 2338
> [error 2018/01/04 20:20:27.909 UTC  172.17.0.3(164):32773 shared ordered uid=9 port=47318> tid=0x2a6] 
> Exception occurred in CacheListener
> java.lang.AssertionError: The put operation in queue did not succeed due 
> to exception =
>   at org.apache.geode.test.dunit.Assert.fail(Assert.java:66)
>   at 
> org.apache.geode.internal.cache.ha.HARegionQueueDUnitTest$6$1.afterUpdate(HARegionQueueDUnitTest.java:602)
>   at 
> org.apache.geode.internal.cache.EnumListenerEvent$AFTER_UPDATE.dispatchEvent(EnumListenerEvent.java:119)
>   at 
> org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8450)
>   at 
> org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6953)
>   at 
> org.apache.geode.internal.cache.LocalRegion.invokePutCallbacks(LocalRegion.java:5926)
>   at 
> org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2339)
>   at 
> org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:171)
>   at 
> org.apache.geode.internal.cache.LocalRegion.basicPutPart2(LocalRegion.java:5784)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2864)
>   at 
> org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5622)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:369)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:152)
>   at 
> org.apache.geode.internal.cache.LocalRegion.basicUpdate(LocalRegion.java:5603)
>   at 
> org.apache.geode.internal.cache.AbstractUpdateOperation.doPutOrCreate(AbstractUpdateOperation.java:165)
>   at 
> org.apache.geode.internal.cache.AbstractUpdateOperation$AbstractUpdateMessage.basicOperateOnRegion(AbstractUpdateOperation.java:272)
>   at 
> org.apache.geode.internal.cache.AbstractUpdateOperation$AbstractUpdateMessage.operateOnRegion(AbstractUpdateOperation.java:243)
>   at 
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1189)
>   at 
> org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1090)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:440)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.scheduleIncomingMessage(DistributionManager.java:3209)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.handleIncomingDMsg(DistributionManager.java:2871)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$1500(DistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.DistributionManager$DMListener.messageReceived(DistributionManager.java:3987)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.dispatchMessage(GMSMembershipManager.java:1127)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.handleOrDeferMessage(GMSMembershipManager.java:1045)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager$MyDCReceiver.messageReceived(GMSMembershipManager.java:408)
> 

[jira] [Closed] (GEODE-2418) Add gfsh post execution handler to detect and download file URLs

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2418.


> Add gfsh post execution handler to detect and download file URLs
> 
>
> Key: GEODE-2418
> URL: https://issues.apache.org/jira/browse/GEODE-2418
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration, gfsh
>Reporter: Jared Stewart
>Assignee: Jinmei Liao
>Priority: Major
>
> Rather than return the zip file contents in the 'export logs' command result 
> from a locator to a gfsh client, we will return a URL to the exported zip 
> file (GEODE-2417).  We need to write a gfsh post-execution handler (see 
> `org.apache.geode.management.internal.cli.commands.ExportImportClusterConfigurationCommands.ExportInterceptor`)
>  to extract the file URL from the result JSON and download that file via HTTP 
> onto the gfsh client's disk.



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

[jira] [Closed] (GEODE-3093) Update support for OpenSSL to 1.1

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3093.


> Update support for OpenSSL to 1.1
> -
>
> Key: GEODE-3093
> URL: https://issues.apache.org/jira/browse/GEODE-3093
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, native client
>Reporter: Jacob S. Barrett
>Assignee: Karen Smoler Miller
>Priority: Minor
>
> OpenSSL's current stable line is 1.1 and we should update our support to that 
> line for security purposes.



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

[jira] [Closed] (GEODE-194) Geode Spark Connector does not support Spark 2.0

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-194.
---

> Geode Spark Connector does not support Spark 2.0
> 
>
> Key: GEODE-194
> URL: https://issues.apache.org/jira/browse/GEODE-194
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Jianxia Chen
>Priority: Major
>  Labels: experimental, gsoc2016
>
> The BasicIntegrationTest fails when using spark 1.4. e.g.
> [info] - GemFire OQL query with more complex UDT: Partitioned Region *** 
> FAILED ***
> [info]   org.apache.spark.SparkException: Job aborted due to stage failure: 
> Task 0 in stage 24.0 failed 1 times, most recent failure: Lost task 0.0 in 
> stage 24.0 (TID 48, localhost): scala.MatchError: 
> [info]Portfolio [id=3 status=active type=type3
> [info]AOL:Position [secId=AOL qty=978.0 mktValue=40.373], 
> [info]MSFT:Position [secId=MSFT qty=98327.0 mktValue=23.32]] 
> (of class ittest.io.pivotal.gemfire.spark.connector.Portfolio)
> [info]at 
> org.apache.spark.sql.catalyst.CatalystTypeConverters$$anonfun$createToCatalystConverter$4.apply(CatalystTypeConverters.scala:178)
> [info]at 
> org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:62)
> [info]at 
> org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:59)
> [info]at scala.collection.Iterator$$anon$11.next(Iterator.scala:328)
> [info]at scala.collection.Iterator$$anon$11.next(Iterator.scala:328)
> [info]at scala.collection.Iterator$class.foreach(Iterator.scala:727)
> [info]at 
> scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
> [info]at 
> scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:48)
> [info]at 
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:103)
> [info]at 
> scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:47)
> [info]at 
> scala.collection.TraversableOnce$class.to(TraversableOnce.scala:273)
> [info]at scala.collection.AbstractIterator.to(Iterator.scala:1157)
> [info]at 
> scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:265)
> [info]at 
> scala.collection.AbstractIterator.toBuffer(Iterator.scala:1157)
> [info]at 
> scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:252)
> [info]at 
> scala.collection.AbstractIterator.toArray(Iterator.scala:1157)
> [info]at 
> org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$12.apply(RDD.scala:885)
> [info]at 
> org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$12.apply(RDD.scala:885)
> [info]at 
> org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1765)
> [info]at 
> org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1765)
> [info]at 
> org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:63)
> [info]at org.apache.spark.scheduler.Task.run(Task.scala:70)
> [info]at 
> org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213)
> [info]at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [info]at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [info]at java.lang.Thread.run(Thread.java:745)
> [info] 
> [info] Driver stacktrace:
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1266)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1257)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1256)
> [info]   at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> [info]   at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1256)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:730)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:730)
> [info]   at scala.Option.foreach(Option.scala:236)
> [info]   at 
> org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:730)
> [info]   ...



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

[jira] [Closed] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2746.


> Investigate and Evaluate Existing RPC frameworks.
> -
>
> Key: GEODE-2746
> URL: https://issues.apache.org/jira/browse/GEODE-2746
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
>Priority: Major
>
> There are several existing RPC frameworks for which you can define the 
> structure of your protocol and the tool will generate code for talking over 
> the wire, generally down to serialization of objects.
> If one of those RPC frameworks does not fit all our requirements, we'll 
> design our own binary protocol. This protocol would define both what kind of 
> messages can be sent and how they are encoded on the wire. How we encode the 
> objects that we are sending in requests, however, could still be pluggable.
> A few contenders:
> * [BERT|http://bert-rpc.org]
> * [thrift|https://thrift.apache.org/]
> * [gRPC|http://www.grpc.io/]
> * [Avro|https://avro.apache.org/]
> These are two not-entirely-common features we will need to have:
> * support for SSL/TLS, ability to connect to a server with IP & port.
> * support for push messages from the server without polling (this is needed 
> for CQs).
> This is one half of GEODE-2734.



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

[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5104:


Commit 779bc5c96de5d77866dbc99381ecf8c4ac4d8987 in geode's branch 
refs/heads/feature/transcoding_experiments from [~smgoller]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=779bc5c ]

GEODE-5104 - Output git SHA when updating passing reference file.


> CI output git SHA when updating passing reference file.
> ---
>
> Key: GEODE-5104
> URL: https://issues.apache.org/jira/browse/GEODE-5104
> Project: Geode
>  Issue Type: Task
>  Components: ci
>Reporter: Sean Goller
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When concourse updates the file indicating the SHA that has passed all tests, 
> print it out.



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

[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5085:


Commit 08ec4af911baa9eaca05f2aaf5d021618734bfe1 in geode's branch 
refs/heads/feature/transcoding_experiments from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=08ec4af ]

GEODE-5085 authentication failure when auto-reconnecting

Modified auto-reconnect to gather the security properties from the
DistributionConfig and to use the non-parsed values of properties
instead of the parsed versions.

Modified unit tests to gather the security properties and use the
non-parsed values when deciding whether to create a new distributed system.

Added a security manager to all of the ReconnectDUnitTest test cases.

This closes #1807


> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0, 1.7.0
>
> Attachments: geode-server-context.xml
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> 

[jira] [Commented] (GEODE-4838) ClassCastException when registering interest against a Partitioned Region in LonerDistributedSystem

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4838:


Commit 6d3771d9a80d32fdfe2164e3150b46152b28a85e in geode's branch 
refs/heads/feature/transcoding_experiments from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6d3771d ]

GEODE-4838: Throw IllegalStateException when registerinterest on PR in loner 
(#1614)



> ClassCastException when registering interest against a Partitioned Region in 
> LonerDistributedSystem
> ---
>
> Key: GEODE-4838
> URL: https://issues.apache.org/jira/browse/GEODE-4838
> Project: Geode
>  Issue Type: Bug
>  Components: client queues
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This is not a valid use case but we do get a ClassCastException when 
> attempting to register interest on a Partitioned Region in a 
> LonerDistributedSystem (mcast-port=0 and no locator specified).
> Instead we can detect this scenario and throw an IllegalStateException and a 
> better explanation/message
>  
>  



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

[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5070:


Commit a881a790da13c698a38a735d471df0871b552a7b in geode's branch 
refs/heads/feature/transcoding_experiments from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a881a79 ]

GEODE-5070: Support --member option for describe & list jdbc connecto… (#1798)

When cluster configuration service is disabled user
have to provide --member option in-order to describe
and list connections and mappings.

> Support --member option for describe & list jdbc connector commands
> ---
>
> Key: GEODE-5070
> URL: https://issues.apache.org/jira/browse/GEODE-5070
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When cluster configuration service is disabled user have to provide --member 
> option in-order to describe and list connections and mappings. 



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

[jira] [Closed] (GEODE-1964) Add docs for native client to native client repo

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1964.


> Add docs for native client to native client repo
> 
>
> Key: GEODE-1964
> URL: https://issues.apache.org/jira/browse/GEODE-1964
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>
> After the native client code has been merged to develop, the documentation 
> should follow. This subtask allows us to 'park' the existing docs on a 
> feature branch until they're needed.



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

[jira] [Closed] (GEODE-1598) gfsh auto-complete removes previously typed options

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1598.


> gfsh auto-complete removes previously typed options
> ---
>
> Key: GEODE-1598
> URL: https://issues.apache.org/jira/browse/GEODE-1598
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Swapnil Bawaskar
>Priority: Major
>
> This may also be related to fixing GEODE-835.
> When one starts typing in a gfsh command like:
> {noformat}
> gfsh>start server --name=serv1 --se
> {noformat}
> and then hit {{tab}} for autocompletion, the previously completed --name 
> option disappears and all I am left with is:
> {noformat}
> gfsh>start server --se
> {noformat}



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

[jira] [Assigned] (GEODE-4839) Fix type of persistenceInfo parameter on PersistenceManager methods

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett reassigned GEODE-4839:
---

Assignee: Jacob S. Barrett

> Fix type of persistenceInfo parameter on PersistenceManager methods
> ---
>
> Key: GEODE-4839
> URL: https://issues.apache.org/jira/browse/GEODE-4839
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Jacob S. Barrett
>Priority: Major
>
> Most/all of the methods on the PersistenceManager object take a parameter 
> called persistenceInfo with type 'void*&'.  This presents a number of issues, 
> not the least of which is that, were the parameter actually used, it could 
> leak memory on every call.  The callee is allowed to swap out the incoming 
> value for a newly allocated pointer during any call, and the caller has no 
> way to know when _or how_ to free the memory, since it's a void pointer.  If 
> we change the type of persistenceInfo to std::shared_ptr&, it will be 
> properly accounted for and deleted when no longer in use.



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

[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5043:


Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch 
refs/heads/feature/transcoding_experiments from [~geodeintegration]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ]

GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768)

GEODE-5043: Buffering protobuf output to avoid multiple packet sends

Based on the stats all protobuf requests and responses were being sent
as two packets. Using a BufferedOutputStream to make sure we only send 1
packet


> Protobuf server and client are sending multiple packets for a single request
> 
>
> Key: GEODE-5043
> URL: https://issues.apache.org/jira/browse/GEODE-5043
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> While doing some performance testing, we discovered that the protobuf client 
> and protobuf server are actually sending multiple packets per request and 
> response based on the the LinuxSystemStats.xmitPackets. The messages are 
> small enough they should fit in a single packet.
>  
> Looking at the code, it looks like in both the client and the server we are 
> writing directly to socket.getOutputStream(). As soon as data is written to 
> that outputstream it could be sent to the the remote side. Wrapping that in 
> the BufferedOutputStream eleminates the duplicate packets and improves the 
> performance.



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

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5094:


Commit a03bba213a6b5932a9da9c0a4848c94fd485bbfb in geode's branch 
refs/heads/feature/transcoding_experiments from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a03bba2 ]

added flaky category to test method for GEODE-5094


> ProxyJUnitTest fails intermittently in testExpiration
> -
>
> Key: GEODE-5094
> URL: https://issues.apache.org/jira/browse/GEODE-5094
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Darrel Schneider
>Priority: Major
>  Labels: flaky
>
> {noformat}
> org.apache.geode.cache.ProxyJUnitTest > testExpiration FAILED
> org.apache.geode.cache.RegionDestroyedException: 
> org.apache.geode.internal.cache.DistributedRegion[path='/rEMPTY';scope=DISTRIBUTED_NO_ACK';dataPolicy=EMPTY;
>  concurrencyChecksEnabled]
> at 
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at 
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1356)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1314)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1299)
> at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at 
> org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1106)
> {noformat}
> The test is scheduling a region to be destroyed if it is not used for 500 
> miliseconds. It then starting doing gets which will keep using the region. 
> But it is possible for the gets to lose the cpu and be prevented from using 
> the region and it then expiring. That is what is happening in this test.
> This test as currently written is flaky and needs to be rewritten.



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

[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5081:


Commit b9bb961aa28074aa5643550c684614df33b1f613 in geode's branch 
refs/heads/feature/transcoding_experiments from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9bb961 ]

GEODE-5081 ClientCacheFactory is missing the 
setPoolSubscriptionTimeoutMultiplier()

Added the missing method & a test for it

This closes #1804


> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



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

[jira] [Commented] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4716:


Commit d3e6280bc96e3b5b598cee7a92641a88fc6ceb6c in geode's branch 
refs/heads/feature/transcoding_experiments from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d3e6280 ]

GEODE-4716 Document new stats and missing gateway sender/receiver MXBean (#1813)

- found and fixed a subnav typo for a link to the MXBean doc
- corrected a bad Object Name for the AsyncEventQueueMXBean

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



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

[jira] [Commented] (GEODE-5104) CI output git SHA when updating passing reference file.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5104:


Commit 0bc70cac7d91ff3cd9cb41fdcba2528acfcf4245 in geode's branch 
refs/heads/feature/transcoding_experiments from [~dcavender]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0bc70ca ]

Merge pull request #1819 from smgoller/GEODE-5104

GEODE-5104 - Output git SHA when updating passing reference file.

> CI output git SHA when updating passing reference file.
> ---
>
> Key: GEODE-5104
> URL: https://issues.apache.org/jira/browse/GEODE-5104
> Project: Geode
>  Issue Type: Task
>  Components: ci
>Reporter: Sean Goller
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When concourse updates the file indicating the SHA that has passed all tests, 
> print it out.



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

[jira] [Commented] (GEODE-5043) Protobuf server and client are sending multiple packets for a single request

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5043:


Commit c303d01e408bc903f8ff5ac54b551618a4c5e782 in geode's branch 
refs/heads/feature/transcoding_experiments from [~geodeintegration]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c303d01 ]

GEODE-5043: Buffering protobuf output to avoid multiple packet sends (#1768)

GEODE-5043: Buffering protobuf output to avoid multiple packet sends

Based on the stats all protobuf requests and responses were being sent
as two packets. Using a BufferedOutputStream to make sure we only send 1
packet


> Protobuf server and client are sending multiple packets for a single request
> 
>
> Key: GEODE-5043
> URL: https://issues.apache.org/jira/browse/GEODE-5043
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> While doing some performance testing, we discovered that the protobuf client 
> and protobuf server are actually sending multiple packets per request and 
> response based on the the LinuxSystemStats.xmitPackets. The messages are 
> small enough they should fit in a single packet.
>  
> Looking at the code, it looks like in both the client and the server we are 
> writing directly to socket.getOutputStream(). As soon as data is written to 
> that outputstream it could be sent to the the remote side. Wrapping that in 
> the BufferedOutputStream eleminates the duplicate packets and improves the 
> performance.



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

[jira] [Closed] (GEODE-3010) Update PartitionAttributes for new PartitionByPrefix settings

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3010.


> Update PartitionAttributes for new PartitionByPrefix settings
> -
>
> Key: GEODE-3010
> URL: https://issues.apache.org/jira/browse/GEODE-3010
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>
> Need to add the fields and gettors and settors
> Do the same on PartitionAttributesFactory



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

[jira] [Closed] (GEODE-1488) Consider making SampleJsonAuthorization dynamic

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1488.


> Consider making SampleJsonAuthorization dynamic
> ---
>
> Key: GEODE-1488
> URL: https://issues.apache.org/jira/browse/GEODE-1488
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Jens Deppe
>Priority: Major
>
> This code is only a sample, but it currently requires a full restart whenever 
> the configuration file changes. It would be useful if it could detect a 
> change and re-read the config file so as to dynamically update it's 
> configuration.



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

[jira] [Closed] (GEODE-2971) Inconsistency in gfsh status command

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2971.


> Inconsistency in gfsh status command
> 
>
> Key: GEODE-2971
> URL: https://issues.apache.org/jira/browse/GEODE-2971
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Priority: Major
>
> There is a general inconsistency in gfsh's exit status to the shell.  This 
> makes scripting rather difficult.  For instance:
> * Locator & Server Online (+)
> ** --pid: exit code {{0}} for both, all good.
> ** --name: exit code {{0}} for both, all good.
> ** --dir: exit code {{0}} for both, all good.
> * Locator Online, Server Offline (-)
> ** --pid: exit code is {{0}} for both. Nevertheless, the return string when 
> executing the command for the server returns a {{null}} within the message 
> (where the ip and port should be). As an example: {{Server in 
> /path/to/server/directory on null is currently not responding}}.
> ** --name: exit code is {{0}} for the locator, {{1}} for the server because 
> there's no online member with the specified name... which raises the 
> question: there wasn't any exceptions during the execution, shouldn't we 
> return {{0}}?.
> ** --dir: exit code is {{0}} for both. Nevertheless, the return string when 
> executing the command for the server returns a {{null}} within the message 
> (where the ip and port should be). As an example: {{Server in 
> /path/to/server/directory on null is currently not responding}}.
> * Locator & Server Offline (-)
> ** --pid: exit code for locator is {{1}}, and the return string only contains 
> {{null}}. The exit code for server is {{0}}, but the return string contains a 
> {{null}} within the message (where the ip and port should be). As an example: 
> {{Server in /path/to/server/directory on null is currently not responding}}.
> ** --name: both return {{1}}, which is expected since there's no jmx manager 
> running and this option requires gfsh to be connected.
> ** --dir: exit code for locator is {{1}}, and the return string only contains 
> {{null}}. The exit code for server is {{0}}, but the return string contains a 
> {{null}} within the message (where the ip and port should be). As an example: 
> {{Server in /path/to/server/directory on null is currently not responding}}.



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

[jira] [Assigned] (GEODE-4855) Cache::createPdxInstanceFactory should return an object

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett reassigned GEODE-4855:
---

Assignee: Jacob S. Barrett

> Cache::createPdxInstanceFactory should return an object
> ---
>
> Key: GEODE-4855
> URL: https://issues.apache.org/jira/browse/GEODE-4855
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently it returns a shared_ptr, when it's clearly not shared.  No reason 
> to be allocating memory here, let's just return an object.



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

[jira] [Closed] (GEODE-4842) Remove Cache parameter from PoolFactory::Create in clicache

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4842.


> Remove Cache parameter from PoolFactory::Create in clicache
> ---
>
> Key: GEODE-4842
> URL: https://issues.apache.org/jira/browse/GEODE-4842
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> PoolFactory::Create in clicache takes a Cache parameter which is _completely 
> unused_. This parameter should simply be removed from the API.



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

[jira] [Closed] (GEODE-5037) Tests hangs on windows as a result of long running orphaned grandchildren

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-5037.


> Tests hangs on windows as a result of long running orphaned grandchildren
> -
>
> Key: GEODE-5037
> URL: https://issues.apache.org/jira/browse/GEODE-5037
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>
> Long running grandchildren processes, Geode server, cause stdin pipe to hang. 
> See https://github.com/klemens-morgenstern/boost-process/issues/159



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

[jira] [Closed] (GEODE-2488) Netstat command fails with OutOfMemoryError

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2488.


> Netstat command fails with OutOfMemoryError
> ---
>
> Key: GEODE-2488
> URL: https://issues.apache.org/jira/browse/GEODE-2488
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Kirk Lund
>Assignee: Kenneth Howe
>Priority: Major
>  Labels: MiscellaneousCommands, NetstatCommand, netstat
>
> Note: this can occur outside of dunit tests as well. Just using the gfsh 
> netstat command on locator or server with too little heap space will hit 
> this. See the 1st comment about not streaming the netstat output -- the 
> entire output is held in memory in a string and two byte arrays before 
> sending the result back from NetstatFunction.
> The JUnit controller JVM for NetstatDUnitTest fails with something like the 
> follow stack. The cause appears to be one of the DUnit VMs running out of 
> memory (see the OOME stack down further in this description.
> {noformat}
> org.junit.ComparisonFailure: [{"errorCode":505,"message":["Could not process 
> command due to GemFire error. Error occurred while executing netstat on 
> [server-1]"]}] expected:<[OK]> but was:<[ERROR]>
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at 
> org.apache.geode.test.dunit.rules.GfshShellConnectionRule.executeAndVerifyCommand(GfshShellConnectionRule.java:163)
>   at 
> org.apache.geode.management.internal.cli.NetstatDUnitTest.testConnectToJmxManagerOne(NetstatDUnitTest.java:81)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:37)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> 

[jira] [Closed] (GEODE-3107) Improve gfsh export time when doing a snapshot

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3107.


> Improve gfsh export time when doing a snapshot
> --
>
> Key: GEODE-3107
> URL: https://issues.apache.org/jira/browse/GEODE-3107
> Project: Geode
>  Issue Type: Sub-task
>  Components: snapshot
>Affects Versions: 1.3.0
>Reporter: Fred Krone
>Assignee: Nick Reich
>Priority: Major
>  Labels: storage_1
>
> Currently a large snapshot puts a lot of pressure on the locator which needs 
> to hold all keys and they do not get destroyed.
> Snapshot goes through the JMX manager but snapshots can also be parallelized 
> and in theory this will probably improve performance.
> It would be useful to benchmark the current gfsh export time on 1 TB region 
> and compare it with performance improvements from this ticket.



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

[jira] [Closed] (GEODE-475) Add additional tests for gfsh

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-475.
---

> Add additional tests for gfsh
> -
>
> Key: GEODE-475
> URL: https://issues.apache.org/jira/browse/GEODE-475
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: gfsh
>
> Tests should be able to cover both JMX and HTTP connectivity



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

[jira] [Closed] (GEODE-3309) Update gfsh start locator output in docs

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3309.


> Update gfsh start locator output in docs
> 
>
> Key: GEODE-3309
> URL: https://issues.apache.org/jira/browse/GEODE-3309
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> The sample {{gfsh start locator}} output in section Managing Apache Geode -> 
> Apache Geode Management and Monitoring -> JMX Manager Operations -> Starting 
> a JMX Manager (file managing/management/jmx_manager_operations.html) is too 
> old.  It refers to GemFire version 8.0.  Replace the sample with current gfsh 
> output.
> At the same time, remove the all-but-duplicate version that directly follows 
> the sample.  One sample assumes that gfsh is already invoked, and the other 
> does not.  We can assume that users know how to start gfsh.



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

[jira] [Closed] (GEODE-4387) Remove GemFireCacheImpl.setInstanceForTests

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4387.


> Remove GemFireCacheImpl.setInstanceForTests
> ---
>
> Key: GEODE-4387
> URL: https://issues.apache.org/jira/browse/GEODE-4387
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This is another method that assumes there is a static instance in 
> GemFireCacheImpl



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

[jira] [Closed] (GEODE-2634) gfsh export logs command should be able to filter logs on log-level

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2634.


> gfsh export logs command should be able to filter logs on log-level
> ---
>
> Key: GEODE-2634
> URL: https://issues.apache.org/jira/browse/GEODE-2634
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Jinmei Liao
>Priority: Major
>
> If I try to filter the exported logs by a log level, I get the following 
> exceptions:
> {noformat}
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=warning
> Invalid log level: warning
> {noformat}



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

[jira] [Closed] (GEODE-4985) Updated security implementation example CMake to use FindGeodeNative module.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4985.


> Updated security implementation example CMake to use FindGeodeNative module.
> 
>
> Key: GEODE-4985
> URL: https://issues.apache.org/jira/browse/GEODE-4985
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>




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

[jira] [Closed] (GEODE-4119) Create new geode-example about eviction

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4119.


> Create new geode-example about eviction
> ---
>
> Key: GEODE-4119
> URL: https://issues.apache.org/jira/browse/GEODE-4119
> Project: Geode
>  Issue Type: New Feature
>  Components: examples
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>
> Create a new example that demonstrates eviction.



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

[jira] [Closed] (GEODE-2621) CI Failure: ExportLogsDUnitTest.testExportWithStartAndEndDateTimeFiltering

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2621.


> CI Failure: ExportLogsDUnitTest.testExportWithStartAndEndDateTimeFiltering
> --
>
> Key: GEODE-2621
> URL: https://issues.apache.org/jira/browse/GEODE-2621
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.1.0
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>  Labels: CI, Flaky
>
> {code}
> See 
> 
> Changes:
> [jiliao] GEODE-2267: mark local time sensitive tests as flaky
> [khowe] GEODE-2488: Remove test from flaky category
> [nnag] GEODE-2596: Lucene metrics moved to public API
> [nnag] GEODE-2604: Added javadoc comments to LuceneIndexMetrics.java
> [nnag] GEODE-2604: Added measurement units to the javadoc comments
> --
> [...truncated 99.83 KB...]
> :geode-core:flakyTest
> org.apache.geode.management.internal.cli.commands.ExportLogsDUnitTest > 
> testExportWithStartAndEndDateTimeFiltering FAILED
>java.lang.AssertionError: 
>Expected size:<3> but was:<1> in:
><[/tmp/junit3849272601382305906/unzippedLogs/server-2]>
>at 
> org.apache.geode.management.internal.cli.commands.ExportLogsDUnitTest.verifyZipFileContents(ExportLogsDUnitTest.java:227)
>at 
> org.apache.geode.management.internal.cli.commands.ExportLogsDUnitTest.testExportWithStartAndEndDateTimeFiltering(ExportLogsDUnitTest.java:157)
> {code}



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

[jira] [Closed] (GEODE-4248) PdxSerializable toData/fromData should pass PdxWriter/PdxReader as ref.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4248.


> PdxSerializable toData/fromData should pass PdxWriter/PdxReader as ref.
> ---
>
> Key: GEODE-4248
> URL: https://issues.apache.org/jira/browse/GEODE-4248
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>




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

[jira] [Closed] (GEODE-4038) Convert all size/length/objectSize methods to return size_t

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4038.


> Convert all size/length/objectSize methods to return size_t
> ---
>
> Key: GEODE-4038
> URL: https://issues.apache.org/jira/browse/GEODE-4038
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Use std size_t for all sizing methods.



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

[jira] [Closed] (GEODE-2473) redis-cli hangs if Geode unable to process command properly

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2473.


> redis-cli hangs if Geode unable to process command properly
> ---
>
> Key: GEODE-2473
> URL: https://issues.apache.org/jira/browse/GEODE-2473
> Project: Geode
>  Issue Type: Sub-task
>  Components: redis
>Reporter: Hitesh Khamesra
>Priority: Major
>
> Here is the command  "HSET companies:1000 name "John Smith""
> "GeodeRedisServer-WorkerThread-1" #86 prio=5 os_prio=0 tid=0x7f1a20002800 
> nid=0x4750 sleeping[0x7f1bf0dd9000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at 
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommands.verifyDistributedRegionMbean(CreateAlterDestroyRegionCommands.java:410)
> at 
> org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommands.createRegion(CreateAlterDestroyRegionCommands.java:371)
> at 
> org.apache.geode.redis.internal.RegionProvider.createRegionGlobally(RegionProvider.java:405)
> at 
> org.apache.geode.redis.internal.RegionProvider.getOrCreateRegion0(RegionProvider.java:292)
> at 
> org.apache.geode.redis.internal.RegionProvider.getOrCreateRegion(RegionProvider.java:212)
> at 
> org.apache.geode.redis.internal.executor.hash.HashExecutor.getOrCreateRegion(HashExecutor.java:31)
> at 
> org.apache.geode.redis.internal.executor.hash.HSetExecutor.executeCommand(HSetExecutor.java:48)
> at 
> org.apache.geode.redis.internal.ExecutionHandlerContext.executeWithoutTransaction(ExecutionHandlerContext.java:235)
> at 
> org.apache.geode.redis.internal.ExecutionHandlerContext.executeCommand(ExecutionHandlerContext.java:199)
> at 
> org.apache.geode.redis.internal.ExecutionHandlerContext.channelRead(ExecutionHandlerContext.java:139)
> at 
> io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:368)
> at 
> io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:353)
> at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:173)
> at 
> io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:368)
> at 
> io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:353)
> at 
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:780)
> at 
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:100)
> at 
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:497)
> at 
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:465)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:359)
> at 
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)
> at java.lang.Thread.run(Thread.java:745)



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

[jira] [Closed] (GEODE-2396) Tests using GfshShellConnectionRule leave behind gfsh_files directories

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2396.


> Tests using GfshShellConnectionRule leave behind gfsh_files directories
> ---
>
> Key: GEODE-2396
> URL: https://issues.apache.org/jira/browse/GEODE-2396
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tests
>Reporter: Kirk Lund
>Priority: Major
>  Labels: gfsh
>
> Tests that use GfshShellConnectionRule are leaving behind junk "gfsh_files" 
> directories after running in IntelliJ:
> geode-assembly/gfsh_files/
> Example: PulseDataExportTest
> GfshShellConnectionRule or the tests that use it should be changed to pass in 
> TemporaryFolder. See CliCommandTestBase which passes TemporaryFolder into 
> HeadlessGfsh to ensure that gfsh_files/ ends up in a folder that will be 
> cleaned up during tear down.



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

[jira] [Closed] (GEODE-1535) NullPointerException from SampleJsonAuthorization with valid credentials

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1535.


> NullPointerException from SampleJsonAuthorization with valid credentials
> 
>
> Key: GEODE-1535
> URL: https://issues.apache.org/jira/browse/GEODE-1535
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Dan Smith
>Priority: Major
>  Labels: bug-hunt
>
> I'm trying to configure a client to connect with authorization using the 
> SampleJsonAuthorization class. I got the below NPE when trying to connect.
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on 
> 172.16.115.238(72978:loner):60610:2e0de43c: : While performing a remote put
>   at 
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:445)
>   at 
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:355)
>   at 
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:540)
>   at 
> com.gemstone.gemfire.cache.client.internal.AbstractOp.attempt(AbstractOp.java:378)
>   at 
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
>   at 
> com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:328)
>   at 
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:937)
>   at 
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:155)
>   at 
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
>   at 
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
>   at 
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
>   at 
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
>   at 
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
>   at 
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
>   at 
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
>   at TestClient.test(TestClient.java:20)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
>   at 
> 

[jira] [Closed] (GEODE-2471) AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2471.


> AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching
> --
>
> Key: GEODE-2471
> URL: https://issues.apache.org/jira/browse/GEODE-2471
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: CI
>
> {noformat}
> found in concourse distributedTest #383
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching(AsyncEventListenerDUnitTest.java:1675)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> 

[jira] [Closed] (GEODE-3388) Migrate Cache.hpp/cpp to use std types

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3388.


> Migrate Cache.hpp/cpp to use std types
> --
>
> Key: GEODE-3388
> URL: https://issues.apache.org/jira/browse/GEODE-3388
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Ernest Burghardt
>Assignee: Jacob S. Barrett
>Priority: Major
>
>  virtual void rootRegions(VectorOfRegion& regions);
> =>  virtual std::unique_ptr> 
> rootRegions();
> std::exceptions
>   // TODO what does null do, get rid of null
>   virtual RegionServicePtr createAuthenticatedView(
>   const PropertiesPtr& userSecurityProperties,
>   const std::string* poolName = nullptr);



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

[jira] [Closed] (GEODE-3089) Pulse Logout Url Redirect Incorrect.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3089.


> Pulse Logout Url Redirect Incorrect. 
> -
>
> Key: GEODE-3089
> URL: https://issues.apache.org/jira/browse/GEODE-3089
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Zachary Hansen
>Priority: Major
>
> When clicking the logout button on embedded pulse in browser it redirects to:
> http://localhost:7070/pulse/pulse/clusterLogout
> It should be:
> http://localhost:7070/pulse/clusterLogout
>  



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

[jira] [Closed] (GEODE-2236) Attempting to remove all CacheListeners from a Region using gfsh throws NullPointerException

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2236.


> Attempting to remove all CacheListeners from a Region using gfsh throws 
> NullPointerException
> 
>
> Key: GEODE-2236
> URL: https://issues.apache.org/jira/browse/GEODE-2236
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Deepak Dixit
>Priority: Major
>
> The --cache-listener option to the alter region command replaces the existing 
> CacheListeners with the ones set in the option.
> What happens in RegionAlterFunction is that the existing CacheListeners not 
> included in the new list are removed, then the new ones are added.
> So, in theory, to remove all CacheListeners, an empty string could be passed 
> into the --cache-listener option like:
> {noformat}
> alter region --name=data --cache-listener=''
> Executing - alter region --name=data --cache-listener=""
> Member  | Status
> --- | 
> --
> server2 | ERROR: java.lang.NullPointerException
>   at com.gemstone.gemfire.manag..
> server1 | ERROR: java.lang.NullPointerException
>   at com.gemstone.gemfire.manag..
> {noformat}
> This actually works but it throws the NPE below.
> {noformat}
> [error 2016/09/13 09:48:59.943 PDT server1  
> tid=0x40] 
> java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.newInstance(RegionAlterFunction.java:320)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.alterRegion(RegionAlterFunction.java:228)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.execute(RegionAlterFunction.java:64)
>   at 
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:185)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:386)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:457)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:692)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1149)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> A work-around to this issue is to set a non-existent CacheListener in the 
> --cache-listener option like:
> {noformat}
> alter region --name=data --cache-listener=Fred
> Executing - alter region --name=data --cache-listener=Fred
> Member  | Status
> --- | --
> server1 | ERROR: Could not find class "Fred" specified for "cache-listener".
> server2 | ERROR: Could not find class "Fred" specified for "cache-listener".
> {noformat}
> This correctly throws the ClassNotFoundException below and also removes all 
> the existing CacheListeners.
> {noformat}
> [error 2016/09/13 09:46:40.537 PDT server1  
> tid=0x40] Could not find class "Fred" specified for "cache-listener".
> java.lang.RuntimeException: Could not find class "Fred" specified for 
> "cache-listener".
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.forName(RegionAlterFunction.java:306)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.alterRegion(RegionAlterFunction.java:227)
>   at 
> com.gemstone.gemfire.management.internal.cli.functions.RegionAlterFunction.execute(RegionAlterFunction.java:64)
>   at 
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:185)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:386)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:457)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:692)
>   at 
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1149)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: 

[jira] [Closed] (GEODE-2443) Update to CMake 3.8

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2443.


> Update to CMake 3.8
> ---
>
> Key: GEODE-2443
> URL: https://issues.apache.org/jira/browse/GEODE-2443
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ernest Burghardt
>Priority: Minor
>
> Cmake has RC'd 3.8 with support for C# - this needs to be looked to see if it 
> works well and to see what (if any) changes we need to make in order to 
> migrate to 3.8
> Currently we configurate csproj.in files, this presumably would go away
> We would need to update CI images to have cmake 3.8.
> Fixes issues with detecting CPU counts on Solaris.



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

[jira] [Closed] (GEODE-3943) Make LocalRegion.discoverJTA method public as it was before

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3943.


> Make LocalRegion.discoverJTA method public as it was before
> ---
>
> Key: GEODE-3943
> URL: https://issues.apache.org/jira/browse/GEODE-3943
> Project: Geode
>  Issue Type: Improvement
>  Components: transactions
>Reporter: Vadim Lotarev
>Priority: Major
>
> Please return visibility of the {{LocalRegion.discoverJTA}} method to 
> {{public}} as it was before. I recently invoked this method as a workaround 
> for the bug [GEODE-2349]:
> {code}
> public Collection getAll() {
> ((LocalRegion)region).discoverJTA();
> return region.values();
> }
> {code}



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

[jira] [Closed] (GEODE-4169) Update ACE to 6.4.7

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4169.


> Update ACE to 6.4.7
> ---
>
> Key: GEODE-4169
> URL: https://issues.apache.org/jira/browse/GEODE-4169
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Closed] (GEODE-1337) Define the API for lucene per-field analyzers

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1337.


> Define the API for lucene per-field analyzers
> -
>
> Key: GEODE-1337
> URL: https://issues.apache.org/jira/browse/GEODE-1337
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Barry Oglesby
>Priority: Major
>
> The current API (Map) is used by LuceneService:
> {noformat}
> public void createIndex(String indexName, String regionPath, Map Analyzer> analyzerPerField);
> {noformat}
> It is also used by LuceneIndex:
> {noformat}
> public Map getFieldAnalyzers();
> {noformat}
> Three options are:
> - keep it as it is
> - change it to {{Map}}
> - change it to {{Map}}



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

[jira] [Closed] (GEODE-2437) Integrate native client with travis-ci

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2437.


> Integrate native client with travis-ci
> --
>
> Key: GEODE-2437
> URL: https://issues.apache.org/jira/browse/GEODE-2437
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Anthony Baker
>Priority: Major
>
> We should integrate the native client branch with travis-ci so we can tell if 
> PR's  or other code changes are good.



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

[jira] [Closed] (GEODE-4416) Make CqState an enum class

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4416.


> Make CqState an enum class
> --
>
> Key: GEODE-4416
> URL: https://issues.apache.org/jira/browse/GEODE-4416
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently a class with an enum without scope.



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

[jira] [Closed] (GEODE-4572) SerializationRegistry::addType and similar functions should return std::shared_ptr

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4572.


> SerializationRegistry::addType and similar functions should return 
> std::shared_ptr
> --
>
> Key: GEODE-4572
> URL: https://issues.apache.org/jira/browse/GEODE-4572
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Currently these functions return a raw pointer. Returning a std::shared_ptr 
> reduces the chance for memory leaks and improves performance given that all 
> use cases resulted in the raw pointer being wrapped later in std::shared_ptr.



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

[jira] [Closed] (GEODE-2546) RollingUpgradeDUnitTest fails intermittently with ClusterConfigurationNotAvailableException

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2546.


> RollingUpgradeDUnitTest fails intermittently with 
> ClusterConfigurationNotAvailableException
> ---
>
> Key: GEODE-2546
> URL: https://issues.apache.org/jira/browse/GEODE-2546
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, locator
>Reporter: Kirk Lund
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: Flaky
>
> This test might be hitting GEODE-2238. If we change the test to await cluster 
> config readiness it should fix this.
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest > 
> testRollServersOnPartitionedRegion_dataserializable[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest$3.run 
> in VM 0 running on Host e41dd4960b22 with 4 VMs with version 110
> at org.apache.geode.test.dunit.VM.invoke(VM.java:377)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:347)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:292)
> at 
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.invokeRunnableInVMs(RollingUpgradeDUnitTest.java:333)
> at 
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.doTestRollAll(RollingUpgradeDUnitTest.java:177)
> at 
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.testRollServersOnPartitionedRegion_dataserializable(RollingUpgradeDUnitTest.java:129)
> Caused by:
> java.lang.RuntimeException: 
> java.lang.reflect.InvocationTargetException
> Caused by:
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.createCache(RollingUpgradeDUnitTest.java:722)
> Caused by:
> org.apache.geode.GemFireConfigException: cluster 
> configuration service not available
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1067)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1200)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:798)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:783)
> at 
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:178)
> at 
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:218)
> ... 5 more
> Caused by:
> 
> org.apache.geode.internal.process.ClusterConfigurationNotAvailableException: 
> Unable to retrieve cluster configuration from the locator.
> at 
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:245)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1029)
> ... 10 more
> {noformat}



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

[jira] [Closed] (GEODE-4135) CI failure: org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > testWANPDX_PR_ParallelSender FAILED

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4135.


> CI failure: org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > 
> testWANPDX_PR_ParallelSender FAILED
> -
>
> Key: GEODE-4135
> URL: https://issues.apache.org/jira/browse/GEODE-4135
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Affects Versions: 1.4.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > 
> testWANPDX_PR_ParallelSender FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest$$Lambda$128/1003567036.run
>  in VM 2 running on Host a202e17aebfe with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
> at 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest.testWANPDX_PR_ParallelSender(PDXNewWanDUnitTest.java:497)
> Caused by:
> java.lang.AssertionError: keySet = [] values() = [] 
> expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at 
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize_PDX(WANTestBase.java:2761)
> at 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest.lambda$testWANPDX_PR_ParallelSender$bb17a952$6(PDXNewWanDUnitTest.java:497)
> {noformat}



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

[jira] [Closed] (GEODE-1000) LauncherLifecycleCommandsDUnitTest fails on Windows

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1000.


> LauncherLifecycleCommandsDUnitTest fails on Windows
> ---
>
> Key: GEODE-1000
> URL: https://issues.apache.org/jira/browse/GEODE-1000
> Project: Geode
>  Issue Type: Bug
>  Components: management
> Environment: Windows
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: DistributedTest, Windows
>
> A number of tests fail due to file separators being changed from a 
> forward-slash to a back-slash:
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
>  > test001StartLocatorFailsFastOnMissingGemFirePropertiesFile FAILED
> junit.framework.AssertionFailedError:
> Warning: The GemFire properties file 
> C:\path\to\missing\gemfire.properties could not be found.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test001StartLocatorFailsFastOnMissingGemFirePropertiesFile(LauncherLifecycleCommandsDUnitTest.java:384)
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
>  > test002StartLocatorFailsFastOnMissingGemFireSecurityPropertiesFile FAILED
> junit.framework.AssertionFailedError:
> Warning: The GemFire Security properties file 
> C:\path\to\missing\gemfire-security.properties could not be found.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test002StartLocatorFailsFastOnMissingGemFireSecurityPropertiesFile(LauncherLifecycleCommandsDUnitTest.java:409)
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
>  > test003StartServerFailsFastOnMissingCacheXmlFile FAILED
> junit.framework.AssertionFailedError:
> Warning: The GemFire cache XML file C:\path\to\missing\cache.xml could 
> not be found.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnMissingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:429)
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
>  > test004StartServerFailsFastOnMissingGemFirePropertiesFile FAILED
> junit.framework.AssertionFailedError:
> Warning: The GemFire properties file 
> C:\path\to\missing\gemfire.properties could not be found.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test004StartServerFailsFastOnMissingGemFirePropertiesFile(LauncherLifecycleCommandsDUnitTest.java:448)
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
>  > test005StartServerFailsFastOnMissingGemFireSecurityPropertiesFile FAILED
> junit.framework.AssertionFailedError:
> Warning: The GemFire Security properties file 
> C:\path\to\missing\gemfire-securities.properties could not be found.
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test005StartServerFailsFastOnMissingGemFireSecurityPropertiesFile(LauncherLifecycleCommandsDUnitTest.java:468)



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

[jira] [Closed] (GEODE-4419) Convert DiskPolicyType to enum class

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4419.


> Convert DiskPolicyType to enum class
> 
>
> Key: GEODE-4419
> URL: https://issues.apache.org/jira/browse/GEODE-4419
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Closed] (GEODE-4700) Updating help text for create region command to make --skip-if-exists consistent with put command

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4700.


> Updating help text for create region command to make --skip-if-exists 
> consistent with put command
> -
>
> Key: GEODE-4700
> URL: https://issues.apache.org/jira/browse/GEODE-4700
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> On GEODE-4394, we modified the help string on the help put command:
> {code:java}
> --skip-if-exists{code}
> option.
>  We should make the help create region consistent.
> {code:java}
> skip-if-exists
> (Deprecated: Use --if-not-exists) See --if-not-exists for help.
> {code}



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

[jira] [Closed] (GEODE-4426) Refactor RegionShortcut as enum class.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4426.


> Refactor RegionShortcut as enum class.
> --
>
> Key: GEODE-4426
> URL: https://issues.apache.org/jira/browse/GEODE-4426
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>




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

[jira] [Closed] (GEODE-2220) StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives fails with TimeoutException on Windows

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2220.


> StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives
>  fails with TimeoutException on Windows
> 
>
> Key: GEODE-2220
> URL: https://issues.apache.org/jira/browse/GEODE-2220
> Project: Geode
>  Issue Type: Bug
>  Components: statistics, tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Priority: Major
>  Labels: IntegrationTest, Windows
>
> This test had some interesting timing issues when comparing how it runs on 
> Mac vs Linux which seemed to involve the difference in file sizes on file 
> system. It's been tuned to pass on Mac and Linux but probably needs further 
> work for Windows as well.
> {noformat}
> java.util.concurrent.TimeoutException: File 
> C:\cygwin\tmp\junit3404591601445938731\closedInstanceShouldHaveTypeInRolledArchives-01-01.gfs
>  does not exist after 3946 samples within 1 MINUTES
>   at 
> org.apache.geode.internal.statistics.StatTypesAreRolledOverRegressionTest.sampleUntilFileExists(StatTypesAreRolledOverRegressionTest.java:170)
>   at 
> org.apache.geode.internal.statistics.StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives(StatTypesAreRolledOverRegressionTest.java:128)
>   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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 

[jira] [Closed] (GEODE-4166) Setting primary-key-in-value for jdbc mapping gets overriden by entry key

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4166.


> Setting primary-key-in-value for jdbc mapping gets overriden by entry key
> -
>
> Key: GEODE-4166
> URL: https://issues.apache.org/jira/browse/GEODE-4166
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>
> primary-key-in-value' did not seem to work. 
> One issue is that .put(key,value)  the key always becomes the id, no matter 
> what.  
> In the event that the DB key is one of the PDX values and not the key used on 
> the region.put
> we need to do an insert using the values.



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

[jira] [Closed] (GEODE-2333) There is a race in GatewaySenderEventImpl.release() that could lead to offheap to be released more than once

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2333.


> There is a race in GatewaySenderEventImpl.release() that could lead to 
> offheap to be released more than once
> 
>
> Key: GEODE-2333
> URL: https://issues.apache.org/jira/browse/GEODE-2333
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> The following log shows that an offheap memory was unexpectedly freed.
> [severe 2017/01/07 09:14:40.789 UTC 
> bridgegemfire_1_1_rs-QueuesBTTest-2017-01-06-14-07-15-client-12_3912 
>  GatewaySender_sender_bridgeds_1_to_bridgeds_2_0> tid=0x97] Stopping the 
> processor because the following exception occurred while processing a batch:
> java.lang.IllegalStateException: It looks like off heap memory @7f33a8000238 
> was already freed. rawBits=0 history=null
> at 
> org.apache.geode.internal.offheap.OffHeapStoredObject.release(OffHeapStoredObject.java:675)
> at 
> org.apache.geode.internal.offheap.OffHeapStoredObject.release(OffHeapStoredObject.java:659)
> at 
> org.apache.geode.internal.offheap.OffHeapStoredObject.release(OffHeapStoredObject.java:373)
> at 
> org.apache.geode.internal.offheap.OffHeapHelper.releaseAndTrackOwner(OffHeapHelper.java:138)
> at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventImpl.release(GatewaySenderEventImpl.java:1213)
> at 
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.remove(ParallelGatewaySenderQueue.java:1096)
> at 
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.remove(ParallelGatewaySenderQueue.java:1531)
> at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.eventQueueRemove(AbstractGatewaySenderEventProcessor.java:231)
> at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.handleSuccessBatchAck(AbstractGatewaySenderEventProcessor.java:981)
> at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher$AckReaderThread.run(GatewaySenderEventRemoteDispatcher.java:636)



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

[jira] [Closed] (GEODE-2536) DiskId code confusing in how it implements needsToBeWritten

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2536.


> DiskId code confusing in how it implements needsToBeWritten
> ---
>
> Key: GEODE-2536
> URL: https://issues.apache.org/jira/browse/GEODE-2536
> Project: Geode
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Darrel Schneider
>Assignee: Eric Shu
>Priority: Major
>
> DiskId has an abstract method "needsToBeWritten." It is set to true by 
> "markForWriting" and set to false by "unmarkForWriting." DiskId has two types 
> of implementations: one for overflow only regions and one for persistent 
> regions.
> The needsToBeWritten only makes sense for overflow only. But the persistent 
> DiskIds also implement these methods and do so in a way that can be confused 
> with "isKeyIdNegative."
> Since markForWriting will only be called for overflow only disk ids I 
> recommend that the persistent implementation of this method be changed to 
> always throw an exception.
> unmarkForWriting may be called on any type of disk id but for persistent ones 
> should be changed to do nothing.
> needsToBeWritten should be changed to always return false for persistent 
> DiskIds since they are immediately written to disk (or scheduled to be 
> written if async) by whoever gives them a new value. needsToBeWritten is only 
> called by the overflowToDisk method and for a persistent+overflow region it 
> should never need to write the value to disk; all it needs to do is remove 
> the value from memory since it is written to disk.
> The current implementation of these methods on persistent DiskIds do it by 
> negating the keyId. Unfortunately this is also done to indicate that the 
> value was not recovered from disk.



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

[jira] [Closed] (GEODE-2588) OQL's ORDER BY takes 13x (1300%) more time compared to plain java sort for the same amount of data and same resources

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2588.


> OQL's ORDER BY takes 13x (1300%) more time compared to plain java sort for 
> the same amount of data and same resources
> -
>
> Key: GEODE-2588
> URL: https://issues.apache.org/jira/browse/GEODE-2588
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Christian Tzolov
>Priority: Major
> Attachments: flight_recording_OQL_ORDER_BY.jfr, 
> gemfire-oql-orderby-vs-on-client-sort-test-cases.zip, 
> gemfire_OQL_ORDER_BY.log, myStats_OQL_ORDER_BY.gfs, 
> oql_with_order_by_hot_methods.png
>
>
> For Partition Region with 1 500 000 entries running on a single Geode member.
> The OQL query *SELECT DISTINCT a, b FROM /region ORDER BY b* takes *13x* 
> times (*1300%*) more time compared to OQL *SELECT a, b FROM /region* +  
> manual Java sort of the result for the same dataset.
> Setup: Geode 1.0.0 with Partition region with 1 500 000 objects, 4GB memory
> 1. OQL with DISTINCT/ORDER BY
> {code}SELECT DISTINCT e.key,e.day FROM /partitionRegion e ORDER BY e.day{code}
> OQL execution time: 64899 ms = *~65 sec*
> 2. OQL with manual sort
> {code}SELECT e.key,e.day FROM /partitionRegion e{code}
> and then
> {code}
> //OQL all -> 3058 ms
> SelectResults result = (SelectResults) query.execute(bindings);
> //Client-side sort -> 1830 ms
> List result2 = (List) result.asList().parallelStream().sorted((o1, o2) 
> -> {
> Struct st1 = (Struct) o1;
> Struct st2 = (Struct) o2;
> return ((Date) st1.get("day")).compareTo((Date) st2.get("day"));
> }).collect(toList());
> {code}
> OQL execution time: 3058 ms,
> Client-side sort time: 1830 ms
> Total time: 4888 ms = *~5 sec*
> Attached [^gemfire-oql-orderby-vs-on-client-sort-test-cases.zip] can demo the 
> problem (check the comments below).
> Attached are also the JMC profiler [^flight_recording_OQL_ORDER_BY.jfr], logs 
> and vsd stats
> The profiler suggests that most  of the CPU goes to the 
> *OrderByComparator#evaluateSortCriteria* method:
> !oql_with_order_by_hot_methods.png!



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

[jira] [Closed] (GEODE-834) Java Util Logging not showing up on server logs

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-834.
---

> Java Util Logging not showing up on server logs
> ---
>
> Key: GEODE-834
> URL: https://issues.apache.org/jira/browse/GEODE-834
> Project: Geode
>  Issue Type: Bug
>  Components: logging
>Affects Versions: 1.0.0-incubating, 1.1.0
>Reporter: William Markito Oliveira
>Priority: Major
>
> When trying to use java.util.logging.Logger from a callback (CacheWriter, 
> Listeners..) it looks like the output is not being displayed on .log 
> I've checked gemfire-core-dependencies/META-INF/MANIFEST.mf and we are 
> including log4j-jul-2.5.jar which was supposed to the bridge and capture 
> those calls. 



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

[jira] [Closed] (GEODE-3100) expose authorize* call in the SecurityService interface

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3100.


> expose authorize* call in the SecurityService interface
> ---
>
> Key: GEODE-3100
> URL: https://issues.apache.org/jira/browse/GEODE-3100
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>
> these authorizeXXX calls are useful for function developers to call to 
> authorize operations in the function. This gives function users freedom to 
> choose what permissions are needed to execute this function.



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

[jira] [Closed] (GEODE-4423) Convert PdxFieldTypes to enum class

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4423.


> Convert PdxFieldTypes to enum class
> ---
>
> Key: GEODE-4423
> URL: https://issues.apache.org/jira/browse/GEODE-4423
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>




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

[jira] [Closed] (GEODE-4282) createKey, createValue functions missing for many Serializable types.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4282.


> createKey, createValue functions missing for many Serializable types.
> -
>
> Key: GEODE-4282
> URL: https://issues.apache.org/jira/browse/GEODE-4282
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>
> Serializable/CacheableKey::create method needs namespace functions 
> createValue/createKey for each of the supported primitive types. Many of 
> these types are missing as a result of bad refactoring. 



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

[jira] [Closed] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-308.
---

> Separate hydra from dunit and junit tests in gemfire-core
> -
>
> Key: GEODE-308
> URL: https://issues.apache.org/jira/browse/GEODE-308
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>Priority: Major
>  Labels: hydra
>
> Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core 
> and any other project.
> The following hydra classes in gemfire-core should be removed (and replaced 
> if needed by dunit/junit tests):
> src/test/java/hydra/GsRandom.java
> src/test/java/hydra/HydraRuntimeException.java
> src/test/java/hydra/Log.java
> src/test/java/hydra/LogVersionHelper.java
> src/test/java/hydra/MethExecutor.java
> src/test/java/hydra/MethExecutorResult.java
> src/test/java/hydra/SchedulingOrder.java
> src/test/java/hydra/log/AnyLogWriter.java
> src/test/java/hydra/log/CircularOutputStream.java
> The following are also not com.gemstone packages and should be removed if 
> they're specific to Hydra (or Hydra tests) or repackaged if they're actually 
> used in dunit/junit tests:
> src/test/java/batterytest/greplogs/ExpectedStrings.java
> src/test/java/batterytest/greplogs/LogConsumer.java
> src/test/java/cacheRunner/Portfolio.java
> src/test/java/cacheRunner/Position.java
> src/test/java/parReg/query/unittest/NewPortfolio.java
> src/test/java/parReg/query/unittest/Position.java
> src/test/java/perffmwk/Formatter.java
> src/test/java/templates/security/DummyAuthenticator.java
> src/test/java/templates/security/DummyAuthorization.java
> src/test/java/templates/security/FunctionSecurityPrmsHolder.java
> src/test/java/templates/security/LdapUserAuthenticator.java
> src/test/java/templates/security/PKCSAuthenticator.java
> src/test/java/templates/security/PKCSAuthInt.java
> src/test/java/templates/security/PKCSPrincipal.java
> src/test/java/templates/security/UsernamePrincipal.java
> src/test/java/templates.security/UserPasswordAuthInit.java
> src/test/java/templates.security/XmlAuthorization.java
> src/test/java/templates.security/XmlErrorHandler.java
> src/test/java/util/TestException.java
> The following are Hydra-related resources in src/test/resources that also 
> need to be removed:
> src/test/resources/jta/cachejta.xml
> src/test/resources/ssl/trusted.keystore
> src/test/resources/templates/security/authz5_5.dtd
> src/test/resources/templates/security/authz6_0.dtd



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

[jira] [Closed] (GEODE-2646) PulseDataExportTest.dataBrowserExportWorksAsExpected fails with BindException

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2646.


> PulseDataExportTest.dataBrowserExportWorksAsExpected fails with BindException
> -
>
> Key: GEODE-2646
> URL: https://issues.apache.org/jira/browse/GEODE-2646
> Project: Geode
>  Issue Type: Bug
>  Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: Flaky
>
> {noformat}
> :geode-assembly:flakyTest
> org.apache.geode.tools.pulse.PulseDataExportTest > 
> dataBrowserExportWorksAsExpected 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 1371
> [error 2017/03/08 04:58:14.240 UTC  tid=0x31] 
> Jmx manager could not be started because java.rmi.server.ExportException: 
> Port already in use: 1099; nested exception is:
> java.net.BindException: Failed to create server socket on  null[1,099]
> org.apache.geode.management.ManagementException: 
> java.rmi.server.ExportException: Port already in use: 1099; nested exception 
> is:
> java.net.BindException: Failed to create server socket on  null[1,099]
> at 
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:149)
> at 
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:469)
> at 
> org.apache.geode.management.internal.JmxManagerLocator.findJmxManager(JmxManagerLocator.java:105)
> at 
> org.apache.geode.management.internal.JmxManagerLocator.processRequest(JmxManagerLocator.java:55)
> at 
> org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1318)
> at 
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:392)
> 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: java.rmi.server.ExportException: Port already in use: 1099; 
> nested exception is:
> java.net.BindException: Failed to create server socket on  null[1,099]
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:341)
> at 
> sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249)
> at 
> sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
> at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147)
> at 
> sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:234)
> at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:195)
> at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:155)
> at 
> java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239)
> at 
> org.apache.geode.management.internal.ManagementAgent.configureAndStart(ManagementAgent.java:398)
> at 
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:147)
> ... 8 more
> Caused by: java.net.BindException: Failed to create server socket on  
> null[1,099]
> at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:782)
> at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:739)
> at 
> org.apache.geode.management.internal.ManagementAgent$GemFireRMIServerSocketFactory.createServerSocket(ManagementAgent.java:556)
> at 
> sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666)
> at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330)
> ... 17 more
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:778)
> ... 21 more
> 2 tests completed, 1 failed
> {noformat}



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

[jira] [Closed] (GEODE-4733) Replace and remove trivial methods from ObjectUtils

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4733.


> Replace and remove trivial methods from ObjectUtils
> ---
>
> Key: GEODE-4733
> URL: https://issues.apache.org/jira/browse/GEODE-4733
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> For instance, {{defaultIfNull(T... values)}} is exclusively called with two 
> input parameters, while the method name and signature makes it unclear that 
> the second value is meant to be the default value if the first parameter is 
> null.
> This method can be cleanly replaced by a ternary {{v1 != null ? v1 : v2}}.



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

[jira] [Closed] (GEODE-1175) Remove random integers from GemfireDataCommandsDUnitTest

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1175.


> Remove random integers from GemfireDataCommandsDUnitTest
> 
>
> Key: GEODE-1175
> URL: https://issues.apache.org/jira/browse/GEODE-1175
> Project: Geode
>  Issue Type: Test
>  Components: gfsh, tests
>Reporter: Kirk Lund
>Priority: Major
>
> GemfireDataCommandsDUnitTest uses java.util.Random to generate data for use 
> in its tests. This should change to make the tests deterministic and 
> repeatable.



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

[jira] [Closed] (GEODE-4246) Remove mcast-port from build generated gemfire.properties

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4246.


> Remove mcast-port from build generated gemfire.properties
> -
>
> Key: GEODE-4246
> URL: https://issues.apache.org/jira/browse/GEODE-4246
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>
> Originally from [~upthewaterspout]:
> Nick and I discovered that the gradle build is  generating a 
> {{gemfire.properties}} in the {{integrationTest}} directory (and maybe 
> others). This {{gemfire.properties}} contains an {{mcast-port}}.
> Unfortunately, this means that all of our tests run with different properties 
> when run through gradle as when run through the IDE. 
> The default mcast port is 0, which seems like a way better default than 
> having all tests run with mcast enabled. We should remove this property from 
> the build generated gemfire.properties and fix whatever tests fail.
> See {{gradlet/test.gradle}} and {{TestPropertiesWriter.groovy}}.



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

[jira] [Closed] (GEODE-4288) Add gfsh command to describe async-event-queue

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4288.


> Add gfsh command to describe async-event-queue
> --
>
> Key: GEODE-4288
> URL: https://issues.apache.org/jira/browse/GEODE-4288
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> Currently, there is a {code}create async-event-queue{code} command, but no 
> corresponding describe async-event-queue command.



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

[jira] [Closed] (GEODE-3757) CI failure: HARQueueNewImplDUnitTest.testRefCountForNormalAndGIIPut failed with AssertionError

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3757.


> CI failure: HARQueueNewImplDUnitTest.testRefCountForNormalAndGIIPut failed 
> with AssertionError
> --
>
> Key: GEODE-3757
> URL: https://issues.apache.org/jira/browse/GEODE-3757
> Project: Geode
>  Issue Type: Bug
>  Components: client queues
>Reporter: Barry Oglesby
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest > 
> testRefCountForNormalAndGIIPut FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest$$Lambda$131/162404556.run
>  in VM 1 running on Host bba527347bdd with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
> at 
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.testRefCountForNormalAndGIIPut(HARQueueNewImplDUnitTest.java:389)
> Caused by:
> java.lang.AssertionError: expected:<3> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.verifyQueueData(HARQueueNewImplDUnitTest.java:1080)
> at 
> org.apache.geode.internal.cache.ha.HARQueueNewImplDUnitTest.lambda$testRefCountForNormalAndGIIPut$bb17a952$13(HARQueueNewImplDUnitTest.java:389)
> {noformat}



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

[jira] [Closed] (GEODE-2662) Gfsh displays field value on wrong line!

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2662.


> Gfsh displays field value on wrong line!
> 
>
> Key: GEODE-2662
> URL: https://issues.apache.org/jira/browse/GEODE-2662
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Eitan Suez
>Assignee: Patrick Rhomberg
>Priority: Major
>
> scenario:
> start a locator, a server
> write a client that stores several records of a given type, using pdx 
> serialization
> modify the type in question by adding a field
> write one more record to gemfire, populating all fields, including the new 
> field
> invoke a gfsh query command "select * from /"
> the new field value will display always on the first line of the result set, 
> not on the line associated with the object it actually belongs to.
> example:
> Customer
>  firstName, lastName
> write a customer object:
>  John Doe
> now modify Customer, add telephoneNumber
>  write another customer object:
> Sam Smith, 512.333.
> now run:
> query --query="select c from /Customer c"
> will print:
> firstName | lastName | telephoneNumber
> - |  | ---
> John  | Doe  | 512.333.
> Sam   | Smith| null
> even though the query "select c from /Customer c where c.firstName = 'Sam'" 
> clearly shows the phone number is associated with sam.
> this bug has existed in gemfire at least since v8 and verified to still exist 
> in latest version 9.0.1



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

[jira] [Closed] (GEODE-2464) Review Redis tests

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2464.


> Review Redis tests
> --
>
> Key: GEODE-2464
> URL: https://issues.apache.org/jira/browse/GEODE-2464
> Project: Geode
>  Issue Type: Sub-task
>  Components: redis
>Reporter: Galen O'Sullivan
>Priority: Major
>
> The existing Redis tests could use some cleanup and probably expansion.
> * [~ukohlmeyer] and I ([~gosullivan]) did some common test code with 
> `RedisTestBase`; there is probably some room for improvement there.
> * There is a lot of repetition in the test code for the Redis adapter. We can 
> improve this.
> * Randomization: use junit-quickcheck {{@Property}} tests?
> * Make sure every Redis command gets tested. 



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

[jira] [Closed] (GEODE-4570) Remove singleton calls from product code in org.apache.geode.internal.security

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4570.


> Remove singleton calls from product code in org.apache.geode.internal.security
> --
>
> Key: GEODE-4570
> URL: https://issues.apache.org/jira/browse/GEODE-4570
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> These product classes in org.apache.geode.internal.security invoke singleton 
> getters.
> GemFireCacheImpl.getInstance():
> * SecurityServiceFactory



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

[jira] [Closed] (GEODE-2444) Making Redis Adapter easier to use and more robust

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2444.


> Making Redis Adapter easier to use and more robust
> --
>
> Key: GEODE-2444
> URL: https://issues.apache.org/jira/browse/GEODE-2444
> Project: Geode
>  Issue Type: Wish
>  Components: redis
>Reporter: Addison
>Priority: Major
>
> The goal of this effort is to further test and complete the Redis Adapter to 
> make the code more readable and performant. 



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

[jira] [Closed] (GEODE-4231) FunctionAdapter.serializedFunctionAdapterWithDifferentSerialVersionUID fails rat checker

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4231.


> FunctionAdapter.serializedFunctionAdapterWithDifferentSerialVersionUID fails 
> rat checker
> 
>
> Key: GEODE-4231
> URL: https://issues.apache.org/jira/browse/GEODE-4231
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> The Apache Geode Jenkins build rat check fails for the following file:
> FunctionAdapter.serializedFunctionAdapterWithDifferentSerialVersionUID
> This probably just needs to be renamed to a txt file or added to the ignored 
> list.



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

[jira] [Closed] (GEODE-3009) Implement key String parser

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3009.


> Implement key String parser
> ---
>
> Key: GEODE-3009
> URL: https://issues.apache.org/jira/browse/GEODE-3009
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>
> Parse the key according to the configured delimiter.
> Route the Entry correctly.



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

[jira] [Closed] (GEODE-2585) Client can get an object from the server

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2585.


> Client can get an object from the server
> 
>
> Key: GEODE-2585
> URL: https://issues.apache.org/jira/browse/GEODE-2585
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Addison
>Priority: Major
>
> The client should be able to send a message to the server with a region and a 
> key and get the serialized object back.



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

[jira] [Closed] (GEODE-2584) Client can put a register object on the server

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2584.


> Client can put a register object on the server
> --
>
> Key: GEODE-2584
> URL: https://issues.apache.org/jira/browse/GEODE-2584
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Addison
>Priority: Major
>
> Client should be able to send a put method, a region, a key, and a registered 
> object to the server so that it can be storied there.



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

[jira] [Closed] (GEODE-1815) ConfigurationProperties javadocs need to be more descriptive in a number of cases

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1815.


> ConfigurationProperties javadocs need to be more descriptive in a number of 
> cases
> -
>
> Key: GEODE-1815
> URL: https://issues.apache.org/jira/browse/GEODE-1815
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: javadocs
>
> There are a number of new SECURITY properties in ConfigurationProperties that 
> have a "geode 1.0" tag that have inadequate javadocs.  This is the primary 
> location for documenting distribution config properties, so they need to have 
> a good description like all of the other properties.
> This is one such property:
> {noformat}
>   /**
>* The static String definition of the "security-manager"
>* property
>* @since Geode 1.0
>*/
>   String SECURITY_MANAGER = SECURITY_PREFIX + "manager";
> {noformat}
> this is a properly documented property:
> {noformat}
>   /**
>* The static String definition of the "remote-locators" property
>* 
>* Description: A list of locators (host and port) that a cluster
>* will use in order to connect to a remote site in a multi-site (WAN)
>* configuration. This attribute's value is a possibly comma separated list.
>* For each remote locator, provide a hostname and/or address
>* (separated by '@', if you use both), followed by a port number in 
> brackets.
>* Examples:
>* remote-locators=address1[port1],address2[port2]
>* 
>* remote-locators=hostName1@address1[port1],hostName2@address2[port2]
>* 
>* remote-locators=hostName1[port1],hostName2[port2]
>* 
>* Default: ""
>*/
>   String REMOTE_LOCATORS = "remote-locators";
> {noformat}



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

[jira] [Closed] (GEODE-2032) gfsh show metrics --member should list "offheap" category

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2032.


> gfsh show metrics --member should list "offheap" category
> -
>
> Key: GEODE-2032
> URL: https://issues.apache.org/jira/browse/GEODE-2032
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Darrel Schneider
>Priority: Major
>
> http://geode.docs.pivotal.io/docs/tools_modules/gfsh/command-pages/show.html#topic_6EB786C63AEB46179EEE8FA18624295A
> lists all the member metric categories like so:
> member specified: member, jvm, region, serialization, communication, 
> function, transaction, diskstore, lock, eviction, distribution
> I should also list "offheap".



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

[jira] [Closed] (GEODE-3496) ExportLogsIntegrationTest fails on Windows

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3496.


> ExportLogsIntegrationTest fails on Windows
> --
>
> Key: GEODE-3496
> URL: https://issues.apache.org/jira/browse/GEODE-3496
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tests
> Environment: Windows
>Reporter: Kirk Lund
>Priority: Major
>  Labels: IntegrationTest, Windows
>
> {noformat}
> org.apache.geode.management.internal.cli.commands.ExportLogsIntegrationTest > 
> withFiles_savedToLocatorSpecifiedRelativeDir FAILED
> java.lang.AssertionError: 
> Expecting actual not to be empty
> at 
> org.apache.geode.management.internal.cli.commands.ExportLogsIntegrationTest.withFiles_savedToLocatorSpecifiedRelativeDir(ExportLogsIntegrationTest.java:81)
> {noformat}



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

[jira] [Closed] (GEODE-921) InternalGemFireError: No cache client proxy on this node

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-921.
---

> InternalGemFireError: No cache client proxy on this node
> 
>
> Key: GEODE-921
> URL: https://issues.apache.org/jira/browse/GEODE-921
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Darrel Schneider
>Assignee: William Markito Oliveira
>Priority: Major
>
> On a private build of git rev ab25e41c6281ef90f04c7534e4d65ba4f24d7fc9 this 
> test CqDataUsingPoolOptimizedExecuteDUnitTest.testCQHAWithState failed with 
> the following suspect string. InternalGemFireError should never happen so 
> this bug should have a higher priority than most suspect string failures.
> [vm_2][info 2016/02/05 06:11:28.175 UTC  
> tid=0x2d9] ### Close CacheServer. ###
> [vm_3][info 2016/02/05 06:11:28.175 UTC  ip-10-32-38-194(18458):1027 port 21058> tid=0x1e2] Redundant 
> subscription endpoint ip-10-32-38-194.ore1.vpc.pivotal.io:21058 crashed. 
> Scheduling recovery.
> [vm_3][info 2016/02/05 06:11:28.175 UTC  
> tid=0x1e4] SubscriptionManager redundancy satisfier - primary endpoint has 
> been lost. Attempting to recover.
> [vm_3][info 2016/02/05 06:11:28.177 UTC  ip-10-32-38-194(18458):1027 port 21058> tid=0x1e2] Cache client 
> updater for Queue on endpoint ip-10-32-38-194.ore1.vpc.pivotal.io:21058 
> exiting. Scheduling recovery.
> [vm_2][info 2016/02/05 06:11:28.177 UTC  
> tid=0x2d9] Cache server on port 27,672 is shutting down.
> [vm_3][warn 2016/02/05 06:11:28.178 UTC  
> tid=0x1e0] Could not connect to: ip-10-32-38-194.ore1.vpc.pivotal.io:27672
> [vm_3]java.io.EOFException
> [vm_3]at java.io.DataInputStream.readBoolean(DataInputStream.java:244)
> [vm_3]at 
> com.gemstone.gemfire.internal.cache.tier.sockets.HandShake.greet(HandShake.java:1343)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:115)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:144)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:261)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefillConnection(ConnectionManagerImpl.java:805)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefill(ConnectionManagerImpl.java:748)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl$PrefillConnectionsTask.run2(ConnectionManagerImpl.java:899)
> [vm_3]at 
> com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1259)
> [vm_3]at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [vm_3]at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [vm_3]at java.lang.Thread.run(Thread.java:745)
> [vm_3][info 2016/02/05 06:11:28.179 UTC  ip-10-32-38-194(18472):1028 port 27672> tid=0x1e7] Redundant 
> subscription endpoint ip-10-32-38-194.ore1.vpc.pivotal.io:27672 crashed. 
> Scheduling recovery.
> [vm_3][warn 2016/02/05 06:11:28.179 UTC  
> tid=0x1e4] Pool unexpected closed socket on server 
> connection=Connection[ip-10-32-38-194.ore1.vpc.pivotal.io:27672]@211338577). 
> Server unreachable: could not connect after 1 attempts
> [vm_3][info 2016/02/05 06:11:28.180 UTC  
> tid=0x1e4] SubscriptionManager redundancy satisfier - redundant endpoint has 
> been lost. Attempting to recover.
> [vm_3][error 2016/02/05 06:11:28.180 UTC  
> tid=0x1e4] Could not find any server to create redundant client queue on. 
> Number of excluded servers is 3 and exception is no exception.
> [vm_3][info 2016/02/05 06:11:28.180 UTC  
> tid=0x1e4] Redundancy level 1 is not satisfied, but there are no more servers 
> available. Redundancy is currently 0.
> [vm_3][info 2016/02/05 06:11:28.181 UTC  ip-10-32-38-194(18472):1028 port 27672> tid=0x1e7] Cache client 
> updater for Queue on endpoint ip-10-32-38-194.ore1.vpc.pivotal.io:27672 
> exiting. Scheduling recovery.
> [vm_2][fatal 2016/02/05 06:11:28.186 UTC  Thread 0> tid=0x571] Server connection from 
> [identity(ip-10-32-38-194(18478):1029,connection=1; port=36151] : 
> Unexpected Error on server
> [vm_2]com.gemstone.gemfire.InternalGemFireError: No cache client proxy on 
> this node for proxyId 
> identity(ip-10-32-38-194(18478):1029,connection=1
> [vm_2]at 
> com.gemstone.gemfire.internal.cache.tier.sockets.CacheClientNotifier.makePrimary(CacheClientNotifier.java:711)
> [vm_2]at 
> 

[jira] [Closed] (GEODE-3109) Correct artifacts published for Geode modules

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3109.


> Correct artifacts published for Geode modules
> -
>
> Key: GEODE-3109
> URL: https://issues.apache.org/jira/browse/GEODE-3109
> Project: Geode
>  Issue Type: Task
>  Components: http session
>Reporter: Jens Deppe
>Priority: Major
>
> Currently we are publishing Geode modules artifacts (jars) but these are not 
> useful in themselves. We should be publishing the artifacts produced by 
> {{geode-modules-assembly}} (zips) which contain not just the necessary code, 
> but also configuration files.



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

[jira] [Closed] (GEODE-4164) Setting specific pdx field to db column mapping all columns are required

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4164.


> Setting specific pdx field to db column mapping all columns are required
> 
>
> Key: GEODE-4164
> URL: https://issues.apache.org/jira/browse/GEODE-4164
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>
> For gfsh create jdbc-mapping and setting field-mapping did not seem to work. 
> Example: if I set 
> --field-mapping=age:name
> it should put the age into the name column of the table. But throws:
> Column name 'NAME' appears more than once times in the column list of an 
> INSERT statement.
> It works fine if I set all the k,v like this:
> --field-mapping=age:age,id:name,name:id
> So either all the fields should be required and this should be noted in gfsh 
> help (I actually think this is the least problematic but obviously the most 
> verbose)
> or it should check for a set mapping when doing the insert statement and add 
> in remaining values by default.



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

[jira] [Closed] (GEODE-1550) CI Failure: MembershipJUnitTest.testMultipleManagersInSameProcess assertion failure

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1550.


> CI Failure: MembershipJUnitTest.testMultipleManagersInSameProcess assertion 
> failure
> ---
>
> Key: GEODE-1550
> URL: https://issues.apache.org/jira/browse/GEODE-1550
> Project: Geode
>  Issue Type: Bug
>  Components: membership, messaging
>Reporter: Scott Jewell
>Priority: Major
>  Labels: CI
>
> java.lang.AssertionError: Expected a multicast message to be received
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.MembershipJUnitTest.testMultipleManagersInSameProcess(MembershipJUnitTest.java:178)
>   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.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   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:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java: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:109)
>   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)
>   at 
> 

[jira] [Closed] (GEODE-1320) gfsh function execution does not report errors correctly

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1320.


> gfsh function execution does not report errors correctly
> 
>
> Key: GEODE-1320
> URL: https://issues.apache.org/jira/browse/GEODE-1320
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>
> I have a locator and a server and am trying to execute a simple function 
> using a {{ResultCollector}} as follows:
> {noformat}
> gfsh> execute function --id=basic-function --region=FOO -\
> -result-collector=io.pivotal.gemfire.ToUpperResultCollector
> {noformat}
> The result is simply:
> {noformat}
> io.pivotal.gemfire.ToUpperResultCollector
> {noformat}
> This occurs if my collector class is not on the classpath of the locator. in 
> {{FunctionCommands.executeFunction}} the collector is trying to be 
> instantiated but a {{ClassNotFoundException}} is generated and does not make 
> it back to the client.
> Here is the code for the collector:
> {code:java}
> public class ToUpperResultCollector implements ResultCollector {
>   private List results = new ArrayList<>();
>   private CountDownLatch latch = new CountDownLatch(1);
>   @Override
>   public Object getResult() throws FunctionException {
> try {
>   latch.await();
> } catch (InterruptedException e) {
>   throw new FunctionException("Interrupted waiting for results", e);
> }
> return results;
>   }
>   @Override
>   public Object getResult(long timeout, TimeUnit unit) throws 
> FunctionException, InterruptedException {
> latch.await(timeout, unit);
> return results;
>   }
>   @Override
>   public void addResult(DistributedMember memberID, Object 
> resultOfSingleExecution) {
> results.add(resultOfSingleExecution.toString().toUpperCase());
>   }
>   @Override
>   public void endResults() {
> latch.countDown();
>   }
>   @Override
>   public void clearResults() {
> results.clear();
> latch = new CountDownLatch(1);
>   }
> }
> {code}



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

[jira] [Closed] (GEODE-3793) Test/prove out new protocol's versioning/message additions

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3793.


> Test/prove out new protocol's versioning/message additions
> --
>
> Key: GEODE-3793
> URL: https://issues.apache.org/jira/browse/GEODE-3793
> Project: Geode
>  Issue Type: Task
>  Components: client/server
>Reporter: Geode Integration
>Priority: Major
>
> Test and prove out the new protocol's versioning/addition of messages.
> Expected: 
> Clients on a different major version will receive a helpful error message 
> (and are not supported)
> Clients on the same major version (but possibly different minor version) will 
> be supported.
> So, devs should be able to add new messages to the protocol, bumping the 
> minor version, and clients without knowledge of that message should still be 
> supported (as long as they're on the same major version).



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

[jira] [Closed] (GEODE-4408) ChacheableKeys.hpp provides incorrect hashcode functions.

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-4408.


> ChacheableKeys.hpp provides incorrect hashcode functions.
> -
>
> Key: GEODE-4408
> URL: https://issues.apache.org/jira/browse/GEODE-4408
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> ChacheableKeys.hpp provides incorrect hashcode functions returning uint32_t. 
> Used mostly internally. Consider removing or moving internal. 



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

[jira] [Closed] (GEODE-1884) Users should be able to parse the output of gfsh start command

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-1884.


> Users should be able to parse the output of gfsh start command
> --
>
> Key: GEODE-1884
> URL: https://issues.apache.org/jira/browse/GEODE-1884
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>
> Geode servers can be started on a ephemeral port and the output does contain 
> the port number on which the server has started to listen, but the output is 
> not parseable for integration tests; example:
> {noformat}
> gfsh>start server --name=serv1 --server-port=0
> Starting a Geode Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1...
> ..
> Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1
>  on 192.168.0.21[57851] as serv1 is currently online.
> Process ID: 19039
> Uptime: 3 seconds
> GemFire Version: 1.0.0-incubating-SNAPSHOT
> Java Version: 1.8.0_45
> Log File: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1/serv1.log
> JVM Arguments: -Dgemfire.default.locators=192.168.0.21[10334] 
> -Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080 
> -Dgemfire.start-dev-rest-api=false -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The output of the above command needs to presented as a json so that it can 
> be parsed. We need an additional {{--output-format}} option to the start 
> server command:
> {noformat}
> gfsh start server --server-port=0 --output-format=json
> {noformat}
> which should result in the above output be returned as a json. The bind 
> address and the port should be available as separate elements in the json 
> output.



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

[jira] [Closed] (GEODE-3696) New protocol - create region message

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3696.


> New protocol - create region message
> 
>
> Key: GEODE-3696
> URL: https://issues.apache.org/jira/browse/GEODE-3696
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Priority: Major
>
> As a dev using the new protocol, I'd like to be able to create new regions 
> using the protocol.
> [Scope/additional details forthcoming]



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

[jira] [Closed] (GEODE-2781) Test framework Perfomance: Serialization Frameworks

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2781.


> Test framework Perfomance: Serialization Frameworks
> ---
>
> Key: GEODE-2781
> URL: https://issues.apache.org/jira/browse/GEODE-2781
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Brian Baynes
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> Test framework gRPC, referring to 
> https://cwiki.apache.org/confluence/display/GEODE/Message+Serialization+and+Transmission



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

[jira] [Closed] (GEODE-2787) state flush did not wait for notifyGateway

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-2787.


> state flush did not wait for notifyGateway
> --
>
> Key: GEODE-2787
> URL: https://issues.apache.org/jira/browse/GEODE-2787
> Project: Geode
>  Issue Type: Bug
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: lucene
>
> When distribution happened, it calls startOperation() to increase a count, 
> then call an endOperation() to decrease the count. 
> state flush will wait for this count to become 0. 
> But notifyGateway() is called after distribute(). So there's race that 
> stateflush finished but notifyGateway has not done yet. 
> The fix is to move the endOperation() after callbacks. 



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

[jira] [Closed] (GEODE-3570) Standardize on model for infinity that doesn't use int overloading

[Anthony Baker (JIRA)]

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

Anthony Baker closed GEODE-3570.


> Standardize on model for infinity that doesn't use int overloading
> --
>
> Key: GEODE-3570
> URL: https://issues.apache.org/jira/browse/GEODE-3570
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Mark Hanson
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>
> See discussion here http://markmail.org/thread/hwrkg5cra57lyvo3
> Currently the code in the native client follows various conventions. We would 
> like to standardize the code to use a model where instead of overloading int 
> to mean infinity on a wait, to create two separate function calls. One for 
> wait indefinitely wait()  and one to wait for a duration 
> waitDuration(duration)
> ThinClientRegion.cpp:2996 executeFunction needs refactoring.
> PoolAttributes.hpp:69 setRetryAttempts needs to be retitled attempts and then 
> the using functions need to use it appropriately.



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