[jira] [Reopened] (GEODE-1420) CI Failure: DistributedAckRegionCCEOffHeapDUnitTest.testTombstones

[Darrel Schneider (JIRA)]

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

Darrel Schneider reopened GEODE-1420:
-

The last fix introduced a 200 millisecond delay is closing a cache.


> CI Failure: DistributedAckRegionCCEOffHeapDUnitTest.testTombstones
> --
>
> Key: GEODE-1420
> URL: https://issues.apache.org/jira/browse/GEODE-1420
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Sai Boorlagadda
>Assignee: Darrel Schneider
>  Labels: CI
> Fix For: 1.0.0-incubating.M3
>
>
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on 
> Host cc1-rh6.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase$288.run in VM 1 running on 
> Host cc1-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.cache30.MultiVMRegionTestCase.versionTestTombstones(MultiVMRegionTestCase.java:8582)
>   at 
> com.gemstone.gemfire.cache30.DistributedAckRegionCCEDUnitTest.testTombstones(DistributedAckRegionCCEDUnitTest.java:301)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java: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] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1647:


Commit 50aedb1fc025f10219f2067967eafddab32d02c5 in incubator-geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=50aedb1 ]

GEODE-1647: add more unit test


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1647:


Commit 16b73564f638aea652842dd071d01e1e3d5ad204 in incubator-geode's branch 
refs/heads/develop from gmeilen
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=16b7356 ]

GEODE-1647: Add Integrated Security to Peer Authentication

* This closes #210


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1647:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/210


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1684) CI Failure: IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade updated GEODE-1684:
-
Description: 
Build #3322
Revision: 701909fd46626774d7b4ce0266a3a1c0340814b3 

Error Message

java.lang.AssertionError: expected: but was:

Stacktrace

java.lang.AssertionError: 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.junit.Assert.assertEquals(Assert.java:144)
at 
com.gemstone.gemfire.management.internal.cli.commands.IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup(IndexCommandsDUnitTest.java:354)
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.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] [Updated] (GEODE-1684) CI Failure: IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade updated GEODE-1684:
-
Labels: CI  (was: )

> CI Failure: IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup
> ---
>
> Key: GEODE-1684
> URL: https://issues.apache.org/jira/browse/GEODE-1684
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Anilkumar Gingade
>  Labels: CI
>
> Error Message
> java.lang.AssertionError: expected: but was:
> Stacktrace
> java.lang.AssertionError: 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.junit.Assert.assertEquals(Assert.java:144)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup(IndexCommandsDUnitTest.java:354)
>   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.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 
> 

[jira] [Created] (GEODE-1684) CI Failure: IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup

[Anilkumar Gingade (JIRA)]

Anilkumar Gingade created GEODE-1684:


 Summary: CI Failure: 
IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup
 Key: GEODE-1684
 URL: https://issues.apache.org/jira/browse/GEODE-1684
 Project: Geode
  Issue Type: Bug
  Components: management
Reporter: Anilkumar Gingade


Error Message

java.lang.AssertionError: expected: but was:

Stacktrace

java.lang.AssertionError: 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.junit.Assert.assertEquals(Assert.java:144)
at 
com.gemstone.gemfire.management.internal.cli.commands.IndexCommandsDUnitTest.testCreateAndDestroyIndexOnGroup(IndexCommandsDUnitTest.java:354)
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.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 

[jira] [Updated] (GEODE-1683) CI Failure: com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit

[Anilkumar Gingade (JIRA)]

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

Anilkumar Gingade updated GEODE-1683:
-
Labels: ci  (was: )

> CI Failure: 
> com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit
> ---
>
> Key: GEODE-1683
> URL: https://issues.apache.org/jira/browse/GEODE-1683
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Anilkumar Gingade
>  Labels: ci
>
> Build #3315 (Jul 18, 2016 11:09:11 AM) 
> Revision: e72831ecb25259ed6ec3879f555c1dc8b872264f 
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.security.ClientAuthenticationTestCase$$Lambda$109/800559148.run
>  in VM 2 running on Host venezuela.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.security.ClientAuthenticationTestCase$$Lambda$109/800559148.run
>  in VM 2 running on Host venezuela.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.security.ClientAuthenticationTestCase.doTestInvalidAuthInit(ClientAuthenticationTestCase.java:224)
>   at 
> com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit(ClientAuthenticationDUnitTest.java:56)
>   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.GeneratedMethodAccessor15.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
>   at 
> 

[jira] [Created] (GEODE-1683) CI Failure: com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit

[Anilkumar Gingade (JIRA)]

Anilkumar Gingade created GEODE-1683:


 Summary: CI Failure: 
com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit
 Key: GEODE-1683
 URL: https://issues.apache.org/jira/browse/GEODE-1683
 Project: Geode
  Issue Type: Bug
  Components: security
Reporter: Anilkumar Gingade


Build #3315 (Jul 18, 2016 11:09:11 AM) 
Revision: e72831ecb25259ed6ec3879f555c1dc8b872264f 

Error Message

com.gemstone.gemfire.test.dunit.RMIException: While invoking 
com.gemstone.gemfire.security.ClientAuthenticationTestCase$$Lambda$109/800559148.run
 in VM 2 running on Host venezuela.gemstone.com with 4 VMs

Stacktrace

com.gemstone.gemfire.test.dunit.RMIException: While invoking 
com.gemstone.gemfire.security.ClientAuthenticationTestCase$$Lambda$109/800559148.run
 in VM 2 running on Host venezuela.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.security.ClientAuthenticationTestCase.doTestInvalidAuthInit(ClientAuthenticationTestCase.java:224)
at 
com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testInvalidAuthInit(ClientAuthenticationDUnitTest.java:56)
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.GeneratedMethodAccessor15.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
   

[jira] [Updated] (GEODE-1682) provide ability to start developer REST api from gfsh

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1682:

Description: 
To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
to the {{start server}} command. 

There should be a {noformat}--start-rest-api{noformat} option for the {{start 
server}} command to start the rest api a 
{noformat}--http-service-port{noformat} to configure the port and a 
{noformat}--http-service-bind-address{noformat} option for the bind address.

  was:
To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
to the {{start server}} command. 

There should be a {noformat}--start-rest-api{noformat} option for the {{start 
server}} command to start the rest api and an 
{noformat}--rest-api-port{noformat} to configure the port.


> provide ability to start developer REST api from gfsh
> -
>
> Key: GEODE-1682
> URL: https://issues.apache.org/jira/browse/GEODE-1682
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>
> To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
> to the {{start server}} command. 
> There should be a {noformat}--start-rest-api{noformat} option for the {{start 
> server}} command to start the rest api a 
> {noformat}--http-service-port{noformat} to configure the port and a 
> {noformat}--http-service-bind-address{noformat} option for the bind address.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1682) provide ability to start developer REST api from gfsh

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1682:

Description: 
To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
to the {{start server}} command. 

There should be a {noformat}--start-rest-api{noformat} option for the {{start 
server}} command to start the rest api and an 
{noformat}--rest-api-port{noformat} to configure the port.

  was:
To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
to the {{start server}} command. 

There should be a {{--start-rest-api}} option for the {{start server}} command 
to start the rest api and an {{--rest-api-port}} to configure the port.


> provide ability to start developer REST api from gfsh
> -
>
> Key: GEODE-1682
> URL: https://issues.apache.org/jira/browse/GEODE-1682
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>
> To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
> to the {{start server}} command. 
> There should be a {noformat}--start-rest-api{noformat} option for the {{start 
> server}} command to start the rest api and an 
> {noformat}--rest-api-port{noformat} to configure the port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1682) provide ability to start developer REST api from gfsh

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1682:

Summary: provide ability to start developer REST api from gfsh  (was: 
provide ability to start developer api from gfsh)

> provide ability to start developer REST api from gfsh
> -
>
> Key: GEODE-1682
> URL: https://issues.apache.org/jira/browse/GEODE-1682
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>
> To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
> to the {{start server}} command. 
> There should be a {{--start-rest-api}} option for the {{start server}} 
> command to start the rest api and an {{--rest-api-port}} to configure the 
> port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-1655.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener
> --
>
> Key: GEODE-1655
> URL: https://issues.apache.org/jira/browse/GEODE-1655
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>  Labels: ci
> Fix For: 1.0.0-incubating
>
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> java.lang.AssertionError: expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   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 
> com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
>   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 
> 

[jira] [Created] (GEODE-1682) provide ability to start developer api from gfsh

[Swapnil Bawaskar (JIRA)]

Swapnil Bawaskar created GEODE-1682:
---

 Summary: provide ability to start developer api from gfsh
 Key: GEODE-1682
 URL: https://issues.apache.org/jira/browse/GEODE-1682
 Project: Geode
  Issue Type: Sub-task
  Components: gfsh
Reporter: Swapnil Bawaskar


To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}} 
to the {{start server}} command. 

There should be a {{--start-rest-api}} option for the {{start server}} command 
to start the rest api and an {{--rest-api-port}} to configure the port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1681) gfsh start server should support more gemfire properties

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar commented on GEODE-1681:
-

Supporting all gemfire properties is too broad scope for a single JIRA, so 
let's treat this an an umbrella ticket.

> gfsh start server should support more gemfire properties
> 
>
> Key: GEODE-1681
> URL: https://issues.apache.org/jira/browse/GEODE-1681
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Darrel Schneider
>
> The gfsh start server command needs more options for the gemfire properties.
> It has support for a bunch of them but for others customers need to add 
> "--J=-Dgemfire.". If you make a typo in the system property name you will not 
> get any indication of it.
> A user recently was setting the following: 
> "--J=-Dgemfire.start-dev-rest-api=true 
> --J=-Dgemfire.http-service-bind-address=10.205.84.13 
> --J=-Dgemfire.http-service-bind-port=8081  --J=-Dgemfire.jmx-manager=true 
> --J=-Dgemfire.jmx-manager-start=true"
> They should have been able to do this instead: "--start-dev-rest-api=true 
> --http-service-bind-address=10.205.84.13 --http-service-bind-port=8081  
> --jmx-manager=true --jmx-manager-start=true" and would have been told that 
> "--http-service-bind-port" was an unknown option (it should have been 
> "-http-service-port").
> It seems like it would be best for gfsh start server to support all the 
> gemfire properties that are in the ConfigurationProperties class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1680) Change "list regions" to DATA:READ permissions

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1680:

Description: Currently, "list regions" requires CLUSTER:READ permissions. 
Since Region is a data resource, this should be DATA:READ  (was: Currently, 
"list regions" requires CLUSTER:READ permissions.  This should be DATA:READ)

> Change "list regions" to DATA:READ permissions
> --
>
> Key: GEODE-1680
> URL: https://issues.apache.org/jira/browse/GEODE-1680
> Project: Geode
>  Issue Type: Task
>  Components: gfsh, security
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Currently, "list regions" requires CLUSTER:READ permissions. Since Region is 
> a data resource, this should be DATA:READ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1681) gfsh start server should support more gemfire properties

[Darrel Schneider (JIRA)]

Darrel Schneider created GEODE-1681:
---

 Summary: gfsh start server should support more gemfire properties
 Key: GEODE-1681
 URL: https://issues.apache.org/jira/browse/GEODE-1681
 Project: Geode
  Issue Type: Improvement
  Components: gfsh
Reporter: Darrel Schneider


The gfsh start server command needs more options for the gemfire properties.
It has support for a bunch of them but for others customers need to add 
"--J=-Dgemfire.". If you make a typo in the system property name you will not 
get any indication of it.

A user recently was setting the following: 
"--J=-Dgemfire.start-dev-rest-api=true 
--J=-Dgemfire.http-service-bind-address=10.205.84.13 
--J=-Dgemfire.http-service-bind-port=8081  --J=-Dgemfire.jmx-manager=true 
--J=-Dgemfire.jmx-manager-start=true"

They should have been able to do this instead: "--start-dev-rest-api=true 
--http-service-bind-address=10.205.84.13 --http-service-bind-port=8081  
--jmx-manager=true --jmx-manager-start=true" and would have been told that 
"--http-service-bind-port" was an unknown option (it should have been 
"-http-service-port").

It seems like it would be best for gfsh start server to support all the gemfire 
properties that are in the ConfigurationProperties class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1655:


Commit 7c2e21933ecce1602e27e0b74f439fa94ceb8b52 in incubator-geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7c2e219 ]

GEODE-1655: CI Failure in 
AutoConnectionSourceDUnitTest.testClientMembershipListener

Clients may get a memberLeft event instead of a memberCrashed event when
a server is shut down.  I've adjusted the test's expectations and added
some logging in the membership listener to note which events it receives.


> CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener
> --
>
> Key: GEODE-1655
> URL: https://issues.apache.org/jira/browse/GEODE-1655
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>  Labels: ci
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> java.lang.AssertionError: expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   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 
> com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
>   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 
> 

[jira] [Commented] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt commented on GEODE-1655:
-

This is a problem with the test's expectations.  It shuts down a server and 
expects the client to get a memberCrashed event in its bridge membership 
listener but instead it may get a memberLeft event.

> CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener
> --
>
> Key: GEODE-1655
> URL: https://issues.apache.org/jira/browse/GEODE-1655
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>  Labels: ci
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> java.lang.AssertionError: expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   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 
> com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
>   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-1673) SampleSecurityManager should cause start to fail if security.json cannot be found

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1673:
-
Assignee: Grace Meilen

> SampleSecurityManager should cause start to fail if security.json cannot be 
> found
> -
>
> Key: GEODE-1673
> URL: https://issues.apache.org/jira/browse/GEODE-1673
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> When following the instructions on 
> https://cwiki.apache.org/confluence/display/GEODE/Using+Custom+SecurityManager,
>  if the user forgets to specify "--classpath=." then the locator will start 
> up but cannot be connected to.
> The SampleSecurityManager should instead cause the start to fail if 
> security.json cannot be found.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (GEODE-1680) Change "list regions" to DATA:READ permissions

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-1680.
-
Resolution: Fixed

> Change "list regions" to DATA:READ permissions
> --
>
> Key: GEODE-1680
> URL: https://issues.apache.org/jira/browse/GEODE-1680
> Project: Geode
>  Issue Type: Task
>  Components: gfsh, security
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Currently, "list regions" requires CLUSTER:READ permissions.  This should be 
> DATA:READ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1680) Change "list regions" to DATA:READ permissions

[Kevin Duling (JIRA)]

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

Kevin Duling reassigned GEODE-1680:
---

Assignee: Kevin Duling

> Change "list regions" to DATA:READ permissions
> --
>
> Key: GEODE-1680
> URL: https://issues.apache.org/jira/browse/GEODE-1680
> Project: Geode
>  Issue Type: Task
>  Components: gfsh, security
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Currently, "list regions" requires CLUSTER:READ permissions.  This should be 
> DATA:READ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1655) CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt reassigned GEODE-1655:
---

Assignee: Bruce Schuchardt

> CI failure: AutoConnectionSourceDUnitTest.testClientMembershipListener
> --
>
> Key: GEODE-1655
> URL: https://issues.apache.org/jira/browse/GEODE-1655
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>  Labels: ci
>
> Failed 1 times in the last 30 runs. Stability: 96 %
> Error Message
> java.lang.AssertionError: expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   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 
> com.gemstone.gemfire.cache.client.internal.AutoConnectionSourceDUnitTest.testClientMembershipListener(AutoConnectionSourceDUnitTest.java:390)
>   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 
> 

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71580837
  
--- Diff: 
geode-core/src/test/java/com/gemstone/gemfire/cache/query/QueryJUnitTest.java 
---
@@ -117,6 +118,7 @@ public void test002UnicodeInQuery() {
   }
 
   @Test
+  @Ignore // GEODE-1617 - Regions can be created with a variety of 
characters that are unsupported
--- End diff --

Shouldn't these tests be removed instead of ignored?


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71579111
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/redis/GeodeRedisServer.java ---
@@ -424,14 +429,26 @@ private void initializeRedis() {
   RegionFactory rfString = 
cache.createRegionFactory(DEFAULT_REGION_TYPE);
   RegionFactory rfHLL = 
cache.createRegionFactory(DEFAULT_REGION_TYPE);
   Region stringsRegion;
-  if ((stringsRegion = this.cache.getRegion(STRING_REGION)) == null)
-stringsRegion = rfString.create(GeodeRedisServer.STRING_REGION);
+  InternalRegionArguments ira = new 
InternalRegionArguments().setInternalRegion(true);
+  AttributesFactory af = new AttributesFactory();
+  af.setScope(Scope.LOCAL);
+  RegionAttributes ra = af.create();
   Region hLLRegion;
-  if ((hLLRegion = this.cache.getRegion(HLL_REGION)) == null)
-hLLRegion = rfHLL.create(HLL_REGION);
   Region redisMetaData;
-  if ((redisMetaData = this.cache.getRegion(REDIS_META_DATA_REGION)) 
== null)
-redisMetaData = rfMeta.create(REDIS_META_DATA_REGION);
+  try {
+if ((stringsRegion = this.cache.getRegion(STRING_REGION)) == null)
+  stringsRegion = rfString.create(GeodeRedisServer.STRING_REGION, 
ra, ira);
+if ((hLLRegion = this.cache.getRegion(HLL_REGION)) == null)
+  hLLRegion = rfHLL.create(HLL_REGION, ra, ira);
+if ((redisMetaData = this.cache.getRegion(REDIS_META_DATA_REGION)) 
== null)
+  redisMetaData = rfMeta.create(REDIS_META_DATA_REGION, ra, ira);
+  }
+  catch (IOException | ClassNotFoundException e) {
--- End diff --

The addition of this try/catch does not look related to region names. Seems 
like it should have its own ticket.


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71578385
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/wan/serial/SerialGatewaySenderQueue.java
 ---
@@ -979,15 +1009,14 @@ private void initializeRegion(AbstractGatewaySender 
sender,
 SerialGatewaySenderQueueMetaRegion meta = new 
SerialGatewaySenderQueueMetaRegion(
 this.regionName, ra, null, gemCache, sender);
 try {
-  this.region = gemCache.createVMRegion(
-  this.regionName,
-  ra,
-  new InternalRegionArguments().setInternalMetaRegion(meta)
-  .setDestroyLockFlag(true).setSnapshotInputStream(null)
-  .setImageTarget(null)
-  .setIsUsedForSerialGatewaySenderQueue(true)
-  .setSerialGatewaySender(sender));
-  
+  this.region = gemCache.createVMRegion(this.regionName, ra, new 
InternalRegionArguments().setInternalMetaRegion(meta)
+   
   .setDestroyLockFlag(true)
+   
   .setSnapshotInputStream(null)
+   
   .setImageTarget(null)
+   
   .setIsUsedForSerialGatewaySenderQueue(true)
+   
   .setInternalRegion(true)
--- End diff --

I would be nice if this diff just showed one line (the addition of 
".setInternalRegion(true)". Are you not using the checked in geode code style? 
I actually like your new indentation better but it seems like we should all use 
a consistent formatter.


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71577700
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/LocalRegion.java 
---
@@ -7769,17 +7879,55 @@ void cleanUpOnIncompleteOp(EntryEventImpl event, 
RegionEntry re) {
 this.entries.removeEntry(event.getKey(), re, false) ;  
   }
 
-  static void validateRegionName(String name)
+  static void validateRegionName(String name, InternalRegionArguments 
internalRegionArgs)
   {
 if (name == null) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_BE_NULL.toLocalizedString());
 }
-if (name.length() == 0) {
+if (name.isEmpty()) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_BE_EMPTY.toLocalizedString());
 }
-if (name.indexOf(SEPARATOR) >= 0) {
+if (name.contains(SEPARATOR)) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_CONTAIN_THE_SEPARATOR_0.toLocalizedString(SEPARATOR));
 }
+
+// Validate the name of the region only if it isn't an internal region
+if (internalRegionArgs.isInternalRegion()){
+  return;
+}
+if (internalRegionArgs.isUsedForMetaRegion()) {
+  return;
+}
+if (internalRegionArgs.isUsedForPartitionedRegionAdmin()) {
+  return;
+}
+if (internalRegionArgs.isUsedForPartitionedRegionBucket()) {
+  return;
+}
+
+//LocalRegion metaRegion = internalRegionArgs.getInternalMetaRegion();
+//if (metaRegion != null) {
+//  if (metaRegion instanceof HARegion) {
+//if (metaRegion.getName().equals(name)) {
+//  return;
+//}
+//  }
+//  if (metaRegion instanceof SerialGatewaySenderQueueMetaRegion) {
+//return;
+//  }
+//}
+
+if (name.startsWith("__")
+&& !name.equals(ClientHealthMonitoringRegion.ADMIN_REGION_NAME)) {
+  throw new IllegalArgumentException("Region names may not begin with 
a double-underscore: " + name);
+}
+
+// Ensure the region only contains valid characters
+Pattern pattern = Pattern.compile("[aA-zZ0-9-_.]+");
--- End diff --

Would it be worth putting this Pattern in a static final so that we don't 
compile it on every name check?


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71577488
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/LocalRegion.java 
---
@@ -7769,17 +7879,55 @@ void cleanUpOnIncompleteOp(EntryEventImpl event, 
RegionEntry re) {
 this.entries.removeEntry(event.getKey(), re, false) ;  
   }
 
-  static void validateRegionName(String name)
+  static void validateRegionName(String name, InternalRegionArguments 
internalRegionArgs)
   {
 if (name == null) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_BE_NULL.toLocalizedString());
 }
-if (name.length() == 0) {
+if (name.isEmpty()) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_BE_EMPTY.toLocalizedString());
 }
-if (name.indexOf(SEPARATOR) >= 0) {
+if (name.contains(SEPARATOR)) {
   throw new 
IllegalArgumentException(LocalizedStrings.LocalRegion_NAME_CANNOT_CONTAIN_THE_SEPARATOR_0.toLocalizedString(SEPARATOR));
 }
+
+// Validate the name of the region only if it isn't an internal region
+if (internalRegionArgs.isInternalRegion()){
+  return;
+}
+if (internalRegionArgs.isUsedForMetaRegion()) {
+  return;
+}
+if (internalRegionArgs.isUsedForPartitionedRegionAdmin()) {
+  return;
+}
+if (internalRegionArgs.isUsedForPartitionedRegionBucket()) {
+  return;
+}
+
+//LocalRegion metaRegion = internalRegionArgs.getInternalMetaRegion();
+//if (metaRegion != null) {
+//  if (metaRegion instanceof HARegion) {
+//if (metaRegion.getName().equals(name)) {
+//  return;
+//}
+//  }
+//  if (metaRegion instanceof SerialGatewaySenderQueueMetaRegion) {
+//return;
+//  }
+//}
+
+if (name.startsWith("__")
--- End diff --

Why was the special case needed? Shouldn't this region have set 
isInternalRegion?


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1680) Change "list regions" to DATA:READ permissions

[Kevin Duling (JIRA)]

Kevin Duling created GEODE-1680:
---

 Summary: Change "list regions" to DATA:READ permissions
 Key: GEODE-1680
 URL: https://issues.apache.org/jira/browse/GEODE-1680
 Project: Geode
  Issue Type: Task
  Components: gfsh, security
Reporter: Kevin Duling


Currently, "list regions" requires CLUSTER:READ permissions.  This should be 
DATA:READ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71577203
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/LocalRegion.java 
---
@@ -17,10 +17,96 @@
 
 package com.gemstone.gemfire.internal.cache;
 
-import com.gemstone.gemfire.*;
--- End diff --

If you want to clean up these imports you should not do it as part of this 
fix. File a new ticket for it. I could be wrong about this but I think you 
should change your IDE to not automatically reorg the imports. Kirk might have 
some good advice on this.


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1617:
---

Github user dschneider-pivotal commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/201#discussion_r71576410
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/cache/RegionFactory.java ---
@@ -823,6 +825,38 @@ public void setPublisher(boolean v) {
 return getCache().createRegion(name, ra);
   }
   /**
+   * Creates a region with the given name in this factory's {@link Cache}
+   * using the provided configuration. Validation of the
+   * provided attributes may cause exceptions to be thrown if there are 
problems
+   * with the configuration data.
+   *
+   * @param name
+   *  the name of the region to create
+   * @param regionAttributes
+   *  the attributes for the region
+   * @param internalRegionArguments
+   *  additional arguments for the region
+   *
+   * @return the region object
+   * @throws LeaseExpiredException
+   *   if lease expired on distributed lock for Scope.GLOBAL
+   * @throws RegionExistsException
+   *   if a region, shared or unshared, is already in this cache
+   * @throws TimeoutException
+   *   if timed out getting distributed lock for Scope.GLOBAL
+   * @throws CacheClosedException
+   *   if the cache is closed
+   * @throws IllegalStateException
+   *   if the supplied RegionAttributes are incompatible with this 
region
+   *   in another cache in the distributed system (see
+   *   {@link AttributesFactory} for compatibility rules)
+   */
+  @SuppressWarnings("unchecked")
+  public Region create(String name, RegionAttributes 
regionAttributes, InternalRegionArguments internalRegionArguments)
--- End diff --

RegionFactory is an external API. So you can't add this "create" method to 
it because it takes "InternalRegionArguments" which is not part of the external 
API.



> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-11) Lucene Integration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-11:
-

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/213


> 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

[ASF subversion and git services (JIRA)]

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

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

Commit 603bae8cfae734602a1ccc77128bdf7965e265de in incubator-geode's branch 
refs/heads/develop from [~adharmakkan]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=603bae8 ]

GEODE-11:Gfsh command for lucene query

Added a gfsh command to execute a basic search operation on the lucene index. 
Added junit and dunit tests to verify.

This closes #213


> 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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-11:
-

Github user gesterzhou commented on the issue:

https://github.com/apache/incubator-geode/pull/213
  
+1


> 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-1647) Enable use of SecurityManager for peer authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1647:
---

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/210
  
I rebased it, and rewrite the GMSAuthenticator. The review is here:
https://reviews.apache.org/r/50245/


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-1647:
---

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/210
  
The changes in this PR are incompatible with the changes Jinmei checked in 
on develop. We'll have to rewrite GMSAuthenticator and its tests.


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1679) Geode UI (Pulse) is not showing Read/Write stats

[Sushil (JIRA)]

Sushil created GEODE-1679:
-

 Summary:  Geode UI (Pulse) is not showing Read/Write stats 
 Key: GEODE-1679
 URL: https://issues.apache.org/jira/browse/GEODE-1679
 Project: Geode
  Issue Type: Bug
  Components: pulse
Reporter: Sushil


It seems we have a bug in the Pulse code then. Swap just verified that this bug 
seems to be introduced in Geode, it was working in Gemfire 8x. Thanks!

On Tue, Jul 19, 2016 at 12:04 PM, Chaudhary, Sushil (CONT) 
 wrote:

Jinmei,

I see the below stats for member server2 on GFSH. But still,   UI does shows 0 
as Read/writes. Is that different stats? Refer the snapshot and stats below:


gfsh>show metrics --member=server2

Member Metrics

  Category|  Metric  | Value
- |  | ---
member| upTime   | 334
  | cpuUsage | 300
  | currentHeapSize  | 599
  | maximumHeapSize  | 51008
jvm   | jvmThreads   | 109
  | fileDescriptorLimit  | 4096
  | totalFileDescriptorOpen  | 178
region| totalRegionCount | 1
  | listOfRegions| regionB
  | rootRegions  | /regionB
  | totalRegionEntryCount| 357753
  | totalBucketCount | 211
  | totalPrimaryBucketCount  | 211
  | getsAvgLatency   | 8163
  | putsAvgLatency   | 35892
  | createsRate  | 2765
  | destroyRate  | 0
  | putAllAvgLatency | 0
  | totalMissCount   | 7248392
  | totalHitCount| 5816410
  | getsRate | 84149
  | putsRate | 21031
  | cacheWriterCallsAvgLatency   | 0
  | cacheListenerCallsAvgLatency | 5471
  | totalLoadsCompleted  | 0
serialization | serializationRate| 57567
  | serializationLatency | 57567
  | deserializationRate  | 105163
  | deserializationLatency   | 11803
  | deserializationAvgLatency| 11717
  | PDXDeserializationAvgLatency | 0
  | PDXDeserializationRate   | 0
communication | bytesSentRate| 45173
  | bytesReceivedRate| 14520
function  | numRunningFunctions  | 0
  | functionExecutionRate| 1
  | numRunningFunctionsHavingResults | 0
transaction   | totalTransactionsCount   | 0
  | transactionCommitsAvgLatency | 0
  | transactionCommittedTotalCount   | 0
  | transactionRolledBackTotalCount  | 0
  | transactionCommitsRate   | 0
diskstore | totalDiskUsage   | 0
  | diskReadsRate| 0
  | diskWritesRate   | 0
  | flushTimeAvgLatency  | 0
  | totalQueueSize   | 0
  | totalBackupInProgress| 0
lock  | lockWaitsInProgress  | 0
  | totalLockWaitTime| 0
  | totalNumberOfLockService | 0
  | requestQueues| 0
eviction  | lruEvictionRate  | 0
  | lruDestroyRate   | 0
distribution  | getInitialImagesInProgress   | 0
  | getInitialImageTime  | 0
  | getInitialImageKeysReceived  | 0
offheap   | maxMemory| 10737418235
  | freeMemory   | 10737418235
  | usedMemory   | 0
  | objects  | 0
  | fragmentation| 0
  | compactionTime   | 0


Sushil Chaudhary
Cell #: 408-466-2004
Email: sushil.chaudh...@capitalone.com

From: Jinmei Liao 
Reply-To: "u...@geode.incubator.apache.org" 
Date: Tuesday, July 19, 2016 at 1:48 PM

To: "u...@geode.incubator.apache.org" 
Subject: Re: Geode UI (Pulse) is not showing Read/Write etc

What Pulse is showing on the cluster view screen is the statistics on the 
member itself, not on the region. If you do a "show metrics --member=xxx", you 
will get those statics. Looks like the jmx manager reports the