[jira] [Commented] (GEODE-1526) Typo with example command on wiki for gfsh security example
[ https://issues.apache.org/jira/browse/GEODE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348920#comment-15348920 ] Dave Barnes commented on GEODE-1526: Fixed the (locators -> locator) typo (3 occurrences). > Typo with example command on wiki for gfsh security example > --- > > Key: GEODE-1526 > URL: https://issues.apache.org/jira/browse/GEODE-1526 > Project: Geode > Issue Type: Task > Components: docs, management >Reporter: Jason Huynh > Labels: bug-hunt > > https://cwiki.apache.org/confluence/display/GEODE/Quickstart+guide+to+securing+JMX,+GFSH+and+Pulse > The example shows : > gfsh>connect --locators=localhost[10334] --user=super-user --password=1234567 > However I believe the correct parameter is --locator and not plural locators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-33) Create project examples
[ https://issues.apache.org/jira/browse/GEODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348899#comment-15348899 ] ASF GitHub Bot commented on GEODE-33: - Github user scmbuildguy commented on the issue: https://github.com/apache/incubator-geode/pull/173 +1 > Create project examples > --- > > Key: GEODE-33 > URL: https://issues.apache.org/jira/browse/GEODE-33 > Project: Geode > Issue Type: Improvement > Components: docs, general, web-content >Reporter: William Markito Oliveira > Labels: gsoc2016 > Fix For: 1.0.0-incubating.M3 > > > Currently the project doesn't have examples. > Ideally it should be created as a separated project, include tests and be > used as part of build process tests as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348884#comment-15348884 ] ASF subversion and git services commented on GEODE-1576: Commit 38b524e8d31edbbc37b600efede3bc6f0f7cea3b in incubator-geode's branch refs/heads/asf-site from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=38b524e ] Revert "GEODE-1576: Website needs to be upgraded to include WAN and CQ" This reverts commit 3bd91ee3782e868048d3deda87752d2bbe685d84. The fonts were broken for some reason > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1595) CI failure: PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException
Hitesh Khamesra created GEODE-1595: -- Summary: CI failure: PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException Key: GEODE-1595 URL: https://issues.apache.org/jira/browse/GEODE-1595 Project: Geode Issue Type: Bug Components: functions Reporter: Hitesh Khamesra https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/3018/testReport/com.gemstone.gemfire.internal.cache.execute/PRClientServerRegionFunctionExecutionDUnitTest/testserverMultiKeyExecution_ThrowException/ com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest$$Lambda$89/649451082.run in VM 3 running on Host cc2-rh6.gemstone.com with 4 VMs Stacktrace com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest$$Lambda$89/649451082.run in VM 3 running on Host cc2-rh6.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) at com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException(PRClientServerRegionFunctionExecutionDUnitTest.java:365) 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.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: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
[jira] [Updated] (GEODE-1595) CI failure: PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException
[ https://issues.apache.org/jira/browse/GEODE-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra updated GEODE-1595: --- Labels: CI (was: ) > CI failure: > PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException > - > > Key: GEODE-1595 > URL: https://issues.apache.org/jira/browse/GEODE-1595 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: Hitesh Khamesra > Labels: CI > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/3018/testReport/com.gemstone.gemfire.internal.cache.execute/PRClientServerRegionFunctionExecutionDUnitTest/testserverMultiKeyExecution_ThrowException/ > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest$$Lambda$89/649451082.run > in VM 3 running on Host cc2-rh6.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest$$Lambda$89/649451082.run > in VM 3 running on Host cc2-rh6.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) > at > com.gemstone.gemfire.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest.testserverMultiKeyExecution_ThrowException(PRClientServerRegionFunctionExecutionDUnitTest.java:365) > 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.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: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) >
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348875#comment-15348875 ] ASF subversion and git services commented on GEODE-1576: Commit 3bd91ee3782e868048d3deda87752d2bbe685d84 in incubator-geode's branch refs/heads/asf-site from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3bd91ee ] GEODE-1576: Website needs to be upgraded to include WAN and CQ > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1594) CI failure: RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers
[ https://issues.apache.org/jira/browse/GEODE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348868#comment-15348868 ] Hitesh Khamesra commented on GEODE-1594: Skip to content titletitle log in search ENABLE AUTO REFRESH Jenkins Geode_develop_DistributedTests #3016 Test Results com.gemstone.gemfire.rest.internal.web.controllers RestAPIsOnMembersFunctionExecutionDUnitTest testFunctionExecutionOnAllMembers Back to Project Status Changes Console Output View Build Information History Parameters Metadata Environment Variables Git Build Data Test Result Changes since last success Compare environment JS Widgets Previous Build Next Build Regression com.gemstone.gemfire.rest.internal.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers Failing for the past 1 build (Since Failed#3016 ) Took 12 sec. Failed 1 times in the last 30 runs. Stability: 96 % Error Message java.lang.AssertionError: unexpected exception Stacktrace java.lang.AssertionError: unexpected exception at com.gemstone.gemfire.test.dunit.Assert.fail(Assert.java:64) at com.gemstone.gemfire.rest.internal.web.controllers.RestAPITestBase.executeFunctionThroughRestCall(RestAPITestBase.java:151) at com.gemstone.gemfire.rest.internal.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers(RestAPIsOnMembersFunctionExecutionDUnitTest.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.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: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
[jira] [Created] (GEODE-1594) CI failure: RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers
Hitesh Khamesra created GEODE-1594: -- Summary: CI failure: RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers Key: GEODE-1594 URL: https://issues.apache.org/jira/browse/GEODE-1594 Project: Geode Issue Type: Bug Components: rest (dev) Reporter: Hitesh Khamesra java.lang.AssertionError: unexpected exception at com.gemstone.gemfire.test.dunit.Assert.fail(Assert.java:64) at com.gemstone.gemfire.rest.internal.web.controllers.RestAPITestBase.executeFunctionThroughRestCall(RestAPITestBase.java:151) at com.gemstone.gemfire.rest.internal.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest.testFunctionExecutionOnAllMembers(RestAPIsOnMembersFunctionExecutionDUnitTest.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.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: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
[jira] [Commented] (GEODE-1583) CI failure: DurableClientSimpleDUnitTest.testSimpleDurableClient2
[ https://issues.apache.org/jira/browse/GEODE-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348862#comment-15348862 ] Dan Smith commented on GEODE-1583: -- Looking at the stack, and the logs for this issue, it looks like maybe the client is disconnecting by sending the wrong flag or something. The test closes the cache on the client with keepAlive=false, which is supposed to cause the server to clean up the clients queue. However, the test fails because there is still a CacheClientProxy present on the server. In the logs, we can see that the client health monitor stops watching this client, but the CacheClientProxy remains. It even logs a message saying "Keeping proxy for durable client named test39630_client for 60 seconds" which makes me think it got a close connection request from the client, but decided to keep the proxy anyway. {noformat} [vm_0][info 2016/06/24 08:52:23.867 PDT tid=0x5d] Before CCP states: [CacheClientProxy[identity(cc2-rh6(28071:loner):51817:28b21c83,connection=1,durableAttributes=DurableClientAttributes[id=test39630_client; timeout=60]); port=51819; primary=true; version=GFE 9.0; paused=true; alive=false; connected=true; isMarkedForRemoval=false] ] [vm_0][info 2016/06/24 08:52:23.867 PDT tid=0x5d] Before CHM states: size = 1 {cc2-rh6(28071:loner):51817:28b21c83, {[host name=/10.118.33.92 host ip=10.118.33.92 client port=51817 client member id=cc2-rh6(28071:loner):51817:28b21c83, 2]}} [vm_0][info 2016/06/24 08:52:23.867 PDT tid=0x5d] Got result: null [vm_0] from com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$5.run with 0 args on object: "Loggiog CCCP and ServerConnetcion state" (took 0 ms) [vm_2][info 2016/06/24 08:52:23.868 PDT tid=0x8e7] Received method: com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$$Lambda$70/529615275.run with 0 args on object: com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$$Lambda$70/529615275@2e083615 [vm_2][info 2016/06/24 08:52:23.868 PDT tid=0x8e7] GemFireCache[id = 800029409; isClosing = true; isShutDownAll = false; created = Fri Jun 24 08:52:23 PDT 2016; server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing. [vm_2][info 2016/06/24 08:52:23.869 PDT tid=0x8e7] Destroying connection pool CacheServerTestUtil [vm_0][info 2016/06/24 08:52:23.873 PDT tid=0x1dcb] CacheClientNotifier: Keeping proxy for durable client named test39630_client for 60 seconds CacheClientProxy[identity(cc2-rh6(28071:loner):51817:28b21c83,connection=1,durableAttributes=DurableClientAttributes[id=test39630_client; timeout=60]); port=51819; primary=true; version=GFE 9.0]. [vm_2][info 2016/06/24 08:52:23.876 PDT tid=0x8e7] Got result: null [vm_2] from com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$$Lambda$70/529615275.run with 0 args on object: com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$$Lambda$70/529615275@2e083615 (took 8 ms) [info 2016/06/24 08:52:23.877 PDT tid=0xa] Pausing for 1000 ms... [vm_0][info 2016/06/24 08:52:24.878 PDT tid=0x5d] Received method: com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$5.run with 0 args on object: "Loggiog CCCP and ServerConnetcion state" [vm_0][info 2016/06/24 08:52:24.878 PDT tid=0x5d] after CCP states: [CacheClientProxy[identity(cc2-rh6(28071:loner):51817:28b21c83,connection=1,durableAttributes=DurableClientAttributes[id=test39630_client; timeout=60]); port=51819; primary=true; version=GFE 9.0; paused=true; alive=false; connected=false; isMarkedForRemoval=false] ] [vm_0][info 2016/06/24 08:52:24.878 PDT tid=0x5d] after CHM states: size = 0 [vm_0][info 2016/06/24 08:52:24.878 PDT tid=0x5d] Got result: null [vm_0] from com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$5.run with 0 args on object: "Loggiog CCCP and ServerConnetcion state" (took 0 ms) {noformat} > CI failure: DurableClientSimpleDUnitTest.testSimpleDurableClient2 > - > > Key: GEODE-1583 > URL: https://issues.apache.org/jira/browse/GEODE-1583 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Hitesh Khamesra > Labels: CI > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2986/testReport/com.gemstone.gemfire.internal.cache.tier.sockets/DurableClientSimpleDUnitTest/testSimpleDurableClient2/ > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$6.run > in VM 0 running on Host timor.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.tier.sockets.DurableClientTestCase$6.run > in VM 0 running
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348832#comment-15348832 ] ASF subversion and git services commented on GEODE-1576: Commit 30928d923effd8aed8c376ac1cbaf4d8948c7a3a in incubator-geode's branch refs/heads/develop from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=30928d9 ] GEODE-1576: Website needs to be upgraded to include WAN and CQ upgrading font-awesome to v4.6.3. > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348834#comment-15348834 ] ASF subversion and git services commented on GEODE-1576: Commit 95eff4811bbdb7464f7d10fa24e15465015bb86d in incubator-geode's branch refs/heads/develop from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=95eff48 ] GEODE-1576: Website needs to be upgraded to include WAN and CQ adding WAN, CQ, native client and Adapters to the list of features > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348835#comment-15348835 ] ASF subversion and git services commented on GEODE-1576: Commit 7ad9cc9451212f1c8a0acba3ec78a9eb562d3780 in incubator-geode's branch refs/heads/develop from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7ad9cc9 ] GEODE-1576: Website needs to be upgraded to include WAN and CQ fixed icons in the header > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1576) Website needs to be upgraded to include WAN and CQ
[ https://issues.apache.org/jira/browse/GEODE-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348833#comment-15348833 ] ASF subversion and git services commented on GEODE-1576: Commit e987e5d90347c7520cd04043ee6d92d633322a76 in incubator-geode's branch refs/heads/develop from [~swapnil.bawaskar] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e987e5d ] GEODE-1576: Website needs to be upgraded to include WAN and CQ upgrade nanoc to 4.2.0 > Website needs to be upgraded to include WAN and CQ > -- > > Key: GEODE-1576 > URL: https://issues.apache.org/jira/browse/GEODE-1576 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Swapnil Bawaskar >Assignee: Swapnil Bawaskar > > Since WAN and CQ are new features included in M2 release, we should update > the website to highlight their availability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1593) optimized offheap size too small for many customers
Darrel Schneider created GEODE-1593: --- Summary: optimized offheap size too small for many customers Key: GEODE-1593 URL: https://issues.apache.org/jira/browse/GEODE-1593 Project: Geode Issue Type: Bug Components: offheap Reporter: Darrel Schneider The largest offheap memory allocation that will be optimally reused is 132k. A recent survey of customers found that 35% of them had an average object size greater than 132k. This can be increased by setting the system property "gemfire.OFF_HEAP_FREE_LIST_COUNT". The default for this property is "16384". This results in the jvm heap allocating a single array of this size. If this property defaulted to "65535" then we could optimally reuse allocations smaller than 528k. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348759#comment-15348759 ] ASF subversion and git services commented on GEODE-11: -- Commit 850e143d35c1cde4975a312349b33b4cbd97d6ce in incubator-geode's branch refs/heads/develop from [~upthewaterspout] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=850e143 ] GEODE-11: Fixing compilation failure from LuceneQueriesBase > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348749#comment-15348749 ] ASF subversion and git services commented on GEODE-11: -- Commit 8bbea5b5809ffefb43f669b3ab59830797f50897 in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8bbea5b ] GEODE-11: PageableLuceneQueryResults extends Iterator Changing PageableLuceneQueryResults to extend Iteratorso that it can be used with utilities that expect an iterator. This closes #169 > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348750#comment-15348750 ] ASF GitHub Bot commented on GEODE-11: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-geode/pull/169 > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348747#comment-15348747 ] ASF subversion and git services commented on GEODE-11: -- Commit 001015665c15ec99895c0ae236b56bc0e2b28986 in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0010156 ] GEODE-11: Parameterized EntryScore and TopEntries Added a parameter for the type of the key for EntryScore and TopEntries. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348748#comment-15348748 ] ASF subversion and git services commented on GEODE-11: -- Commit 2c4e17fbbf57daa123d623700489831e519d273c in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=2c4e17f ] GEODE-11: Added findResults() to LuceneQuery Added findResults() to LuceneQuery which returns a list of LuceneResultStruct objects > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348746#comment-15348746 ] ASF subversion and git services commented on GEODE-11: -- Commit 59d471c051932fb509214024117b8b7c6ccb5d28 in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=59d471c ] GEODE-11: Added findValues() to LuceneQuery Added findValues() to LuceneQuery and added unit and intergration tests. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348744#comment-15348744 ] ASF subversion and git services commented on GEODE-11: -- Commit d0e61ecd59d33e628ebe340fd6835d6b4656997c in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=d0e61ec ] GEODE-11 Renamed LuceneQueryResults and search Renamed LuceneQueryResults to PageableLuceneQueryResults and search to findPages. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348745#comment-15348745 ] ASF subversion and git services commented on GEODE-11: -- Commit 14437b72e1600233173586444e8a9d4f7ac88335 in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=14437b7 ] GEODE-11 Added the findKeys method to LuceneQuery Added the findKeys method to LuceneQuery that returns the list of keys. Added unit and intergration to test findKeys. Added an integration test for pagination. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1591) OffHeapMemoryStats should have a defragmentationInProgress stat
[ https://issues.apache.org/jira/browse/GEODE-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-1591. - Resolution: Duplicate > OffHeapMemoryStats should have a defragmentationInProgress stat > --- > > Key: GEODE-1591 > URL: https://issues.apache.org/jira/browse/GEODE-1591 > Project: Geode > Issue Type: Bug > Components: offheap >Reporter: Darrel Schneider > > We need a stat that indicates that an off-heap defragmentation is in progress. > Currently we only have stats that get incremented when it completes. If we > have a defragment that takes a long time we need a stat that will show that > while the defragment is still in progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1592) OffHeapMemoryStats should have a defragmentationInProgress stat
[ https://issues.apache.org/jira/browse/GEODE-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-1592. - Resolution: Duplicate > OffHeapMemoryStats should have a defragmentationInProgress stat > --- > > Key: GEODE-1592 > URL: https://issues.apache.org/jira/browse/GEODE-1592 > Project: Geode > Issue Type: Bug > Components: offheap >Reporter: Darrel Schneider > > We need a stat that indicates that an off-heap defragmentation is in progress. > Currently we only have stats that get incremented when it completes. If we > have a defragment that takes a long time we need a stat that will show that > while the defragment is still in progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-33) Create project examples
[ https://issues.apache.org/jira/browse/GEODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348565#comment-15348565 ] ASF GitHub Bot commented on GEODE-33: - Github user davebarnes97 commented on the issue: https://github.com/apache/incubator-geode/pull/173 +1 > Create project examples > --- > > Key: GEODE-33 > URL: https://issues.apache.org/jira/browse/GEODE-33 > Project: Geode > Issue Type: Improvement > Components: docs, general, web-content >Reporter: William Markito Oliveira > Labels: gsoc2016 > Fix For: 1.0.0-incubating.M3 > > > Currently the project doesn't have examples. > Ideally it should be created as a separated project, include tests and be > used as part of build process tests as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1564) GFSH help incorrectly reports that "start vsd" is available
[ https://issues.apache.org/jira/browse/GEODE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348552#comment-15348552 ] Srikanth Manvi commented on GEODE-1564: --- Thanks [~dbarnes97]. BTW I am working on this JIRA, but I don`t see the button to mark this JIRA as in-progress. Is it permissioning issue ? Can someone give me the correct permission ? > GFSH help incorrectly reports that "start vsd" is available > --- > > Key: GEODE-1564 > URL: https://issues.apache.org/jira/browse/GEODE-1564 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Kirk Lund >Assignee: Srikanth Manvi > > GFSH help incorrectly reports that "start vsd" is available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-33) Create project examples
[ https://issues.apache.org/jira/browse/GEODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348539#comment-15348539 ] ASF GitHub Bot commented on GEODE-33: - GitHub user karensmolermiller opened a pull request: https://github.com/apache/incubator-geode/pull/173 GEODE-33: clarify GEODE_HOME value Clarify prose that identifies value to set for GEODE_HOME, based on dev feedback. You can merge this pull request into a Git repository by running: $ git pull https://github.com/karensmolermiller/incubator-geode feature/GEODE-33 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-geode/pull/173.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #173 commit d6a7f300255cf0311f679d60df8303555d90758f Author: Karen MillerDate: 2016-06-24T16:27:51Z GEODE-33: clarify GEODE_HOME value Clarify prose that identifies value to set for GEODE_HOME, based on dev feedback. > Create project examples > --- > > Key: GEODE-33 > URL: https://issues.apache.org/jira/browse/GEODE-33 > Project: Geode > Issue Type: Improvement > Components: docs, general, web-content >Reporter: William Markito Oliveira > Labels: gsoc2016 > Fix For: 1.0.0-incubating.M3 > > > Currently the project doesn't have examples. > Ideally it should be created as a separated project, include tests and be > used as part of build process tests as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)