[jira] [Updated] (GEODE-1536) Poor documentation and misleading error messages with multi user security
[
https://issues.apache.org/jira/browse/GEODE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1536:
-
Component/s: security
> Poor documentation and misleading error messages with multi user security
> -
>
> Key: GEODE-1536
> URL: https://issues.apache.org/jira/browse/GEODE-1536
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Dan Smith
> Labels: bug-hunt
>
> I'm trying to connect a client using multi user security authentication.
> I couldn't find any description of how to use this feature in the manuals.
> The javadocs for ClientCacheFactory.setPoolMultiuserAuthentication basically
> provide no information. If you just set that, you get this misleading error
> message:
> {code}
> java.lang.UnsupportedOperationException: Use Pool APIs for doing operations
> when multiuser-secure-mode-enabled is set to true.
> {code}
> What you actually need to do is call cache.createAuthenticatedView. However,
> if you just do that, you get this error message
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(73827:loner):60898:2126f43c:
> com.gemstone.gemfire.security.AuthenticationRequiredException: No security-*
> properties are provided
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:671)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at
> com.gemstone.gemfire.cache.client.internal.ProxyRegion.put(ProxyRegion.java:459)
> at TestClient.test(TestClient.java:29)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
>
[jira] [Updated] (GEODE-1536) Poor documentation and misleading error messages with multi user security
[
https://issues.apache.org/jira/browse/GEODE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1536:
-
Labels: bug-hunt (was: )
> Poor documentation and misleading error messages with multi user security
> -
>
> Key: GEODE-1536
> URL: https://issues.apache.org/jira/browse/GEODE-1536
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Dan Smith
> Labels: bug-hunt
>
> I'm trying to connect a client using multi user security authentication.
> I couldn't find any description of how to use this feature in the manuals.
> The javadocs for ClientCacheFactory.setPoolMultiuserAuthentication basically
> provide no information. If you just set that, you get this misleading error
> message:
> {code}
> java.lang.UnsupportedOperationException: Use Pool APIs for doing operations
> when multiuser-secure-mode-enabled is set to true.
> {code}
> What you actually need to do is call cache.createAuthenticatedView. However,
> if you just do that, you get this error message
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(73827:loner):60898:2126f43c:
> com.gemstone.gemfire.security.AuthenticationRequiredException: No security-*
> properties are provided
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:671)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at
> com.gemstone.gemfire.cache.client.internal.ProxyRegion.put(ProxyRegion.java:459)
> at TestClient.test(TestClient.java:29)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
>
[jira] [Created] (GEODE-1536) Poor documentation and misleading error messages with multi user security
Dan Smith created GEODE-1536:
Summary: Poor documentation and misleading error messages with
multi user security
Key: GEODE-1536
URL: https://issues.apache.org/jira/browse/GEODE-1536
Project: Geode
Issue Type: Bug
Reporter: Dan Smith
I'm trying to connect a client using multi user security authentication.
I couldn't find any description of how to use this feature in the manuals. The
javadocs for ClientCacheFactory.setPoolMultiuserAuthentication basically
provide no information. If you just set that, you get this misleading error
message:
{code}
java.lang.UnsupportedOperationException: Use Pool APIs for doing operations
when multiuser-secure-mode-enabled is set to true.
{code}
What you actually need to do is call cache.createAuthenticatedView. However, if
you just do that, you get this error message
{code}
com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
172.16.115.238(73827:loner):60898:2126f43c:
com.gemstone.gemfire.security.AuthenticationRequiredException: No security-*
properties are provided
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:671)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
at
com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
at
com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
at
com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
at
com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
at
com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
at
com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
at
com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
at
com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
at
com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
at
com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
at
com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
at
com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
at
com.gemstone.gemfire.cache.client.internal.ProxyRegion.put(ProxyRegion.java:459)
at TestClient.test(TestClient.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] [Updated] (GEODE-1535) NullPointerException from SampleJsonAuthorization with valid credentials
[
https://issues.apache.org/jira/browse/GEODE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1535:
-
Labels: bug-hunt (was: )
> NullPointerException from SampleJsonAuthorization with valid credentials
>
>
> Key: GEODE-1535
> URL: https://issues.apache.org/jira/browse/GEODE-1535
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Dan Smith
> Labels: bug-hunt
>
> I'm trying to configure a client to connect with authorization using the
> SampleJsonAuthorization class. I got the below NPE when trying to connect.
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(72978:loner):60610:2e0de43c: : While performing a remote put
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:445)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:355)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:540)
> at
> com.gemstone.gemfire.cache.client.internal.AbstractOp.attempt(AbstractOp.java:378)
> at
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
> at
> com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:328)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:937)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:155)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at TestClient.test(TestClient.java:20)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
> at
>
[jira] [Created] (GEODE-1535) NullPointerException from SampleJsonAuthorization with valid credentials
Dan Smith created GEODE-1535:
Summary: NullPointerException from SampleJsonAuthorization with
valid credentials
Key: GEODE-1535
URL: https://issues.apache.org/jira/browse/GEODE-1535
Project: Geode
Issue Type: Bug
Components: security
Reporter: Dan Smith
I'm trying to configure a client to connect with authorization using the
SampleJsonAuthorization class. I got the below NPE when trying to connect.
{code}
com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
172.16.115.238(72978:loner):60610:2e0de43c: : While performing a remote put
at
com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:445)
at
com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:355)
at
com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:540)
at
com.gemstone.gemfire.cache.client.internal.AbstractOp.attempt(AbstractOp.java:378)
at
com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
at
com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:328)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:937)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:155)
at
com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
at
com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
at
com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
at
com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
at
com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
at
com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
at
com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
at
com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
at
com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
at
com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
at
com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
at
com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
at
com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
at TestClient.test(TestClient.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Created] (GEODE-1534) security-username, security-password should be in ConfigurationProperties
Dan Smith created GEODE-1534: Summary: security-username, security-password should be in ConfigurationProperties Key: GEODE-1534 URL: https://issues.apache.org/jira/browse/GEODE-1534 Project: Geode Issue Type: Improvement Reporter: Dan Smith These two special properties are passed to the users Authorization callback when someone logs in through gfsh. They should probably be documented in the Authenticator javadocs and provided as public constants in ConfigurationProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1534) security-username, security-password should be in ConfigurationProperties
[ https://issues.apache.org/jira/browse/GEODE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1534: - Labels: bug-hunt (was: ) > security-username, security-password should be in ConfigurationProperties > - > > Key: GEODE-1534 > URL: https://issues.apache.org/jira/browse/GEODE-1534 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Dan Smith > Labels: bug-hunt > > These two special properties are passed to the users Authorization callback > when someone logs in through gfsh. They should probably be documented in the > Authenticator javadocs and provided as public constants in > ConfigurationProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1534) security-username, security-password should be in ConfigurationProperties
[ https://issues.apache.org/jira/browse/GEODE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-1534: - Component/s: security > security-username, security-password should be in ConfigurationProperties > - > > Key: GEODE-1534 > URL: https://issues.apache.org/jira/browse/GEODE-1534 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Dan Smith > Labels: bug-hunt > > These two special properties are passed to the users Authorization callback > when someone logs in through gfsh. They should probably be documented in the > Authenticator javadocs and provided as public constants in > ConfigurationProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1533) After gfsh times out a session, user can no longer reconnect for a period of time
[
https://issues.apache.org/jira/browse/GEODE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1533:
-
Component/s: (was: h)
> After gfsh times out a session, user can no longer reconnect for a period of
> time
> -
>
> Key: GEODE-1533
> URL: https://issues.apache.org/jira/browse/GEODE-1533
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Dan Smith
> Labels: bug-hunt
>
> I hit this will following the instructions on
> https://cwiki.apache.org/confluence/display/GEODE/Quickstart+guide+to+securing+JMX%2C+GFSH+and+Pulse
> I launched a locator with a security-client-authorization callback. Then I
> connected gfsh using the super-user account specified in the json file.
> I then walked away for a while. It looks like my session timed out, I see
> this in the console
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> {noformat}
> That's fine, maybe my session timed out. The issue is that even if I
> disconnect and reconnect again, or even exit out of gfsh and try to
> reconnect, I get an authentication error.
> After some more time has elapsed, then I can connect again. Below is my log.
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> gfsh>disconnect
> Disconnecting from: 172.16.115.238[1099]
> Disconnected from : 172.16.115.238[1099]
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> gfsh>
> Exiting...
> scripts> gfsh
> Picked up JAVA_TOOL_OPTIONS:
> _ __
>/ _/ __/ __/ // /
> / / __/ /___ /_ / _ /
> / /__/ / / _/ / // /
> /__/_/ /__/_//_/1.0.0-incubating.M3-SNAPSHOT
> Monitor and Manage Apache Geode (incubating)
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> ***Nothing has changed except some time has gone by in this time ***
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Successfully connected to: [host=172.16.115.238, port=1099]
> gfsh>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1533) After gfsh times out a session, user can no longer reconnect for a period of time
[
https://issues.apache.org/jira/browse/GEODE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1533:
-
Labels: bug-hunt (was: )
> After gfsh times out a session, user can no longer reconnect for a period of
> time
> -
>
> Key: GEODE-1533
> URL: https://issues.apache.org/jira/browse/GEODE-1533
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Dan Smith
> Labels: bug-hunt
>
> I hit this will following the instructions on
> https://cwiki.apache.org/confluence/display/GEODE/Quickstart+guide+to+securing+JMX%2C+GFSH+and+Pulse
> I launched a locator with a security-client-authorization callback. Then I
> connected gfsh using the super-user account specified in the json file.
> I then walked away for a while. It looks like my session timed out, I see
> this in the console
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> {noformat}
> That's fine, maybe my session timed out. The issue is that even if I
> disconnect and reconnect again, or even exit out of gfsh and try to
> reconnect, I get an authentication error.
> After some more time has elapsed, then I can connect again. Below is my log.
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> gfsh>disconnect
> Disconnecting from: 172.16.115.238[1099]
> Disconnected from : 172.16.115.238[1099]
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> gfsh>
> Exiting...
> scripts> gfsh
> Picked up JAVA_TOOL_OPTIONS:
> _ __
>/ _/ __/ __/ // /
> / / __/ /___ /_ / _ /
> / /__/ / / _/ / // /
> /__/_/ /__/_//_/1.0.0-incubating.M3-SNAPSHOT
> Monitor and Manage Apache Geode (incubating)
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> ***Nothing has changed except some time has gone by in this time ***
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Successfully connected to: [host=172.16.115.238, port=1099]
> gfsh>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1532) Pulse is vulnerable to clickjacking
Swapnil Bawaskar created GEODE-1532: --- Summary: Pulse is vulnerable to clickjacking Key: GEODE-1532 URL: https://issues.apache.org/jira/browse/GEODE-1532 Project: Geode Issue Type: Bug Components: pulse Reporter: Swapnil Bawaskar The Pulse application is vulnerable to clickjacking. An attacker could frame in the web application and highjack a click, tricking a client into making an unintentional transaction. Attackers exploit this vulnerability by loading target pages in IFRAMEs but keeping them hidden, and then orienting the frame so that a user click on the embedding page is routed to a UI control on the embedded page. The attack will be hidden from the user and perpetrated without the user’s knowledge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1531) geode-examples add final step to run stop script
[
https://issues.apache.org/jira/browse/GEODE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1531:
---
Labels: bug-hunt (was: )
> geode-examples add final step to run stop script
>
>
> Key: GEODE-1531
> URL: https://issues.apache.org/jira/browse/GEODE-1531
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
> Labels: bug-hunt
>
> {{replicated/README.md}} steps 1-5 of the replicated example in
> geode-examples on the feature/GEODE-33 branch are fine. (Well, step 4 to
> kill a *server* needs to be specified.)
> A Step 6 needs to be added to the {{replicated/README.md}} file to run
> {{$ scripts/stopAll.sh}}
> Without this, novice users will not realize that they still have servers and
> a locator running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1531) geode-examples: add final step to run stop script
[
https://issues.apache.org/jira/browse/GEODE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1531:
---
Summary: geode-examples: add final step to run stop script (was:
geode-examples add final step to run stop script)
> geode-examples: add final step to run stop script
> --
>
> Key: GEODE-1531
> URL: https://issues.apache.org/jira/browse/GEODE-1531
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
> Labels: bug-hunt
>
> {{replicated/README.md}} steps 1-5 of the replicated example in
> geode-examples on the feature/GEODE-33 branch are fine. (Well, step 4 to
> kill a *server* needs to be specified.)
> A Step 6 needs to be added to the {{replicated/README.md}} file to run
> {{$ scripts/stopAll.sh}}
> Without this, novice users will not realize that they still have servers and
> a locator running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1531) geode-examples add final step to run stop script
Karen Smoler Miller created GEODE-1531:
--
Summary: geode-examples add final step to run stop script
Key: GEODE-1531
URL: https://issues.apache.org/jira/browse/GEODE-1531
Project: Geode
Issue Type: Bug
Reporter: Karen Smoler Miller
{{replicated/README.md}} steps 1-5 of the replicated example in geode-examples
on the feature/GEODE-33 branch are fine. (Well, step 4 to kill a *server*
needs to be specified.)
A Step 6 needs to be added to the {{replicated/README.md}} file to run
{{$ scripts/stopAll.sh}}
Without this, novice users will not realize that they still have servers and a
locator running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1530) geode-examples setEnv.sh script needs to export path
Karen Smoler Miller created GEODE-1530:
--
Summary: geode-examples setEnv.sh script needs to export path
Key: GEODE-1530
URL: https://issues.apache.org/jira/browse/GEODE-1530
Project: Geode
Issue Type: Bug
Reporter: Karen Smoler Miller
Work currently on the feature/GEODE-33 branch.
In the replicated example, the {{scripts/setEnv.sh}} script should to prepend
the {{GEODE_HOME}} environment variable it finds to the PATH, so that the
{{startAll.sh}} uses that path.
Append this line to the {{scripts/setEnv.sh}} script:
{{export PATH=$GEODE_HOME/bin:$PATH}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1529) ClientHealthMonitor should log client register-unregister message at info level
Hitesh Khamesra created GEODE-1529: -- Summary: ClientHealthMonitor should log client register-unregister message at info level Key: GEODE-1529 URL: https://issues.apache.org/jira/browse/GEODE-1529 Project: Geode Issue Type: Bug Components: client/server Reporter: Hitesh Khamesra right now CHM logs client register-unregister message as debug level. In production usually it is not debug level. But these particular logs are very important for client-server(specially queue) issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1528) CacheFactory javadocs point to the wrong place for DistributedSystem properties
[ https://issues.apache.org/jira/browse/GEODE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325354#comment-15325354 ] ASF subversion and git services commented on GEODE-1528: Commit e831aa06268e3d80bb13eec56b9da1b863d5e0f1 in incubator-geode's branch refs/heads/feature/GEODE-835 from [~bschuchardt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e831aa0 ] GEODE-1528: CacheFactory javadocs point to the wrong place for DistributedSystem properties Modified DistributedSystem and CacheFactory to point to the new ConfigurationProperties interface for property names and meanings. > CacheFactory javadocs point to the wrong place for DistributedSystem > properties > --- > > Key: GEODE-1528 > URL: https://issues.apache.org/jira/browse/GEODE-1528 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > Fix For: 1.0.0-incubating.M3 > > > The descriptions of DistributedSystem properties have been moved to the new > ConfigurationProperties interface, but there are still pointers to their old > location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325348#comment-15325348 ] ASF subversion and git services commented on GEODE-1377: Commit cc249d5de4c77c9e448a4a2790a54ca9de345ca4 in incubator-geode's branch refs/heads/feature/GEODE-835 from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cc249d5 ] GEODE-1377: Updating JavaDocs to point to the correct property definitions > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Udo Kohlmeyer > Fix For: 1.0.0-incubating.M3 > > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-835) Replace joptsimple source with a binary dependency
[ https://issues.apache.org/jira/browse/GEODE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325355#comment-15325355 ] ASF subversion and git services commented on GEODE-835: --- Commit 0ad4acef15aca9d9d2ddf4f44ea47a8907df4838 in incubator-geode's branch refs/heads/feature/GEODE-835 from [~apa...@the9muses.net] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0ad4ace ] Merge remote-tracking branch 'origin/develop' into feature/GEODE-835 > Replace joptsimple source with a binary dependency > -- > > Key: GEODE-835 > URL: https://issues.apache.org/jira/browse/GEODE-835 > Project: Geode > Issue Type: Bug > Components: build, gfsh >Reporter: Anthony Baker >Assignee: Kirk Lund > Fix For: 1.0.0-incubating.M3 > > Attachments: joptsimple.patch > > > The gemfire-jopsimple folder contains modified source code from the > joptsimple library. We should replace this with a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1528) CacheFactory javadocs point to the wrong place for DistributedSystem properties
[ https://issues.apache.org/jira/browse/GEODE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-1528: --- Assignee: Bruce Schuchardt > CacheFactory javadocs point to the wrong place for DistributedSystem > properties > --- > > Key: GEODE-1528 > URL: https://issues.apache.org/jira/browse/GEODE-1528 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt > > The descriptions of DistributedSystem properties have been moved to the new > ConfigurationProperties interface, but there are still pointers to their old > location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1528) CacheFactory javadocs point to the wrong place for DistributedSystem properties
Bruce Schuchardt created GEODE-1528: --- Summary: CacheFactory javadocs point to the wrong place for DistributedSystem properties Key: GEODE-1528 URL: https://issues.apache.org/jira/browse/GEODE-1528 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt The descriptions of DistributedSystem properties have been moved to the new ConfigurationProperties interface, but there are still pointers to their old location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1527) Locator javadoc mentions the old "gemfire" command
Bruce Schuchardt created GEODE-1527: --- Summary: Locator javadoc mentions the old "gemfire" command Key: GEODE-1527 URL: https://issues.apache.org/jira/browse/GEODE-1527 Project: Geode Issue Type: Bug Components: membership Reporter: Bruce Schuchardt The class javadoc for Locator mentions that a stand-alone locator can be created using the "gemfire" command line utility. This should be changed to "gfsh". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=15325262#comment-15325262 ] Jason Huynh commented on GEODE-1526: Also, not sure it deserves another ticket or not, but where do I stick the security.json? (also I found the security.json file name at the end of the quick start and originally named it something else, so it might be good to tell the reader the name and where to place it...) > 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: 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] [Updated] (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:all-tabpanel ] Jason Huynh updated GEODE-1526: --- Labels: bug-hunt (was: ) > 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: 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] [Created] (GEODE-1525) geode-examples rely on GEODE_HOME env variable
Karen Smoler Miller created GEODE-1525:
--
Summary: geode-examples rely on GEODE_HOME env variable
Key: GEODE-1525
URL: https://issues.apache.org/jira/browse/GEODE-1525
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Karen Smoler Miller
The script {{setEnv.sh}} in the first example (Replicated Region) relies on the
user setting the environment variable, {{GEODE_HOME}}, in order to invoke gfsh.
This is fine, and the script would fail, telling the user to set the variable.
So, things work.
However, it is likely that many examples will want this same env variable set.
Therefore, the top level {{README.md}} should contain a step, perhaps directly
after the link to the installation instructions that directs a user to set a
{{GEODE_HOME}} environment variable.
Then, as more examples are added, they can copy the Replicated Region's
{{setEnv.sh}} script and also use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1524) Swagger UI does not show query errors
[
https://issues.apache.org/jira/browse/GEODE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325191#comment-15325191
]
Jens Deppe commented on GEODE-1524:
---
Even just a query which tries to retrieve from an undefined region doesn't
return anything and just spins in the UI.
> Swagger UI does not show query errors
> -
>
> Key: GEODE-1524
> URL: https://issues.apache.org/jira/browse/GEODE-1524
> Project: Geode
> Issue Type: Improvement
> Components: rest (dev)
>Reporter: Jens Deppe
> Labels: bug-hunt
>
> I'm playing with UDA and running adhoc queries through the Swagger UI.
> However, if I have a catastrophic error in my query the Swagger UI doesn't
> display it and I'm left with a 'progress spinner' bar. However, the same
> query from the command line does produce an appropriate error. For example,
> here I'm trying to use my {{sumuda}} function in a query:
> {noformat}
> (2.7)jdeppe@deppe-mbp bughunt-2016 $ curl -v -H "Accept: application/json"
> 'http://127.0.0.1:8080/gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo'
> * Trying 127.0.0.1...
> * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> > GET /gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo
> > HTTP/1.1
> > Host: 127.0.0.1:8080
> > User-Agent: curl/7.43.0
> > Accept: application/json
> >
> < HTTP/1.1 500 Server Error
> < Date: Fri, 10 Jun 2016 19:52:26 GMT
> < Content-Type: application/json
> < Accept-Charset: big5, big5-hkscs, cesu-8, euc-jp, euc-kr, gb18030, gb2312,
> gbk, ibm-thai, ibm00858, ibm01140, ibm01141, ibm01142, ibm01143, ibm01144,
> ibm01145, ibm01146, ibm01147, ibm01148, ibm01149, ibm037, ibm1026, ibm1047,
> ibm273, ibm277, ibm278, ibm280, ibm284, ibm285, ibm290, ibm297, ibm420,
> ibm424, ibm437, ibm500, ibm775, ibm850, ibm852, ibm855, ibm857, ibm860,
> ibm861, ibm862, ibm863, ibm864, ibm865, ibm866, ibm868, ibm869, ibm870,
> ibm871, ibm918, iso-2022-cn, iso-2022-jp, iso-2022-jp-2, iso-2022-kr,
> iso-8859-1, iso-8859-13, iso-8859-15, iso-8859-2, iso-8859-3, iso-8859-4,
> iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, iso-8859-9, jis_x0201,
> jis_x0212-1990, koi8-r, koi8-u, shift_jis, tis-620, us-ascii, utf-16,
> utf-16be, utf-16le, utf-32, utf-32be, utf-32le, utf-8, windows-1250,
> windows-1251, windows-1252, windows-1253, windows-1254, windows-1255,
> windows-1256, windows-1257, windows-1258, windows-31j, x-big5-hkscs-2001,
> x-big5-solaris, x-compound_text, x-euc-jp-linux, x-euc-tw, x-eucjp-open,
> x-ibm1006, x-ibm1025, x-ibm1046, x-ibm1097, x-ibm1098, x-ibm1112, x-ibm1122,
> x-ibm1123, x-ibm1124, x-ibm1166, x-ibm1364, x-ibm1381, x-ibm1383, x-ibm300,
> x-ibm33722, x-ibm737, x-ibm833, x-ibm834, x-ibm856, x-ibm874, x-ibm875,
> x-ibm921, x-ibm922, x-ibm930, x-ibm933, x-ibm935, x-ibm937, x-ibm939,
> x-ibm942, x-ibm942c, x-ibm943, x-ibm943c, x-ibm948, x-ibm949, x-ibm949c,
> x-ibm950, x-ibm964, x-ibm970, x-iscii91, x-iso-2022-cn-cns, x-iso-2022-cn-gb,
> x-iso-8859-11, x-jis0208, x-jisautodetect, x-johab, x-macarabic,
> x-maccentraleurope, x-maccroatian, x-maccyrillic, x-macdingbat, x-macgreek,
> x-machebrew, x-maciceland, x-macroman, x-macromania, x-macsymbol, x-macthai,
> x-macturkish, x-macukraine, x-ms932_0213, x-ms950-hkscs, x-ms950-hkscs-xp,
> x-mswin-936, x-pck, x-sjis_0213, x-utf-16le-bom, x-utf-32be-bom,
> x-utf-32le-bom, x-windows-50220, x-windows-50221, x-windows-874,
> x-windows-949, x-windows-950, x-windows-iso2022jp
> < Content-Length: 5211
> < Server: Jetty(9.3.6.v20151106)
> <
> {"message" : "Server has encountered while executing Adhoc query!",
> "stackTrace" :
> "com.gemstone.gemfire.rest.internal.web.exception.GemfireRestException:
> Server has encountered while executing Adhoc query!
> at
> com.gemstone.gemfire.rest.internal.web.controllers.QueryAccessController.runAdhocQuery(QueryAccessController.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
> at
>
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325168#comment-15325168 ] ASF subversion and git services commented on GEODE-1377: Commit f8dd6ceea620c865c8bd5c5b5a018b6aa41a8a1e in incubator-geode's branch refs/heads/develop from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f8dd6ce ] GEODE-1377: Fixing spark build issue due to rename of ConfigurationProperties > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt >Assignee: Udo Kohlmeyer > Fix For: 1.0.0-incubating.M3 > > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1524) Swagger UI does not show query errors
Jens Deppe created GEODE-1524:
-
Summary: Swagger UI does not show query errors
Key: GEODE-1524
URL: https://issues.apache.org/jira/browse/GEODE-1524
Project: Geode
Issue Type: Improvement
Components: rest (dev)
Reporter: Jens Deppe
I'm playing with UDA and running adhoc queries through the Swagger UI. However,
if I have a catastrophic error in my query the Swagger UI doesn't display it
and I'm left with a 'progress spinner' bar. However, the same query from the
command line does produce an appropriate error. For example, here I'm trying to
use my {{sumuda}} function in a query:
{noformat}
(2.7)jdeppe@deppe-mbp bughunt-2016 $ curl -v -H "Accept: application/json"
'http://127.0.0.1:8080/gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo'
* Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo
> HTTP/1.1
> Host: 127.0.0.1:8080
> User-Agent: curl/7.43.0
> Accept: application/json
>
< HTTP/1.1 500 Server Error
< Date: Fri, 10 Jun 2016 19:52:26 GMT
< Content-Type: application/json
< Accept-Charset: big5, big5-hkscs, cesu-8, euc-jp, euc-kr, gb18030, gb2312,
gbk, ibm-thai, ibm00858, ibm01140, ibm01141, ibm01142, ibm01143, ibm01144,
ibm01145, ibm01146, ibm01147, ibm01148, ibm01149, ibm037, ibm1026, ibm1047,
ibm273, ibm277, ibm278, ibm280, ibm284, ibm285, ibm290, ibm297, ibm420, ibm424,
ibm437, ibm500, ibm775, ibm850, ibm852, ibm855, ibm857, ibm860, ibm861, ibm862,
ibm863, ibm864, ibm865, ibm866, ibm868, ibm869, ibm870, ibm871, ibm918,
iso-2022-cn, iso-2022-jp, iso-2022-jp-2, iso-2022-kr, iso-8859-1, iso-8859-13,
iso-8859-15, iso-8859-2, iso-8859-3, iso-8859-4, iso-8859-5, iso-8859-6,
iso-8859-7, iso-8859-8, iso-8859-9, jis_x0201, jis_x0212-1990, koi8-r, koi8-u,
shift_jis, tis-620, us-ascii, utf-16, utf-16be, utf-16le, utf-32, utf-32be,
utf-32le, utf-8, windows-1250, windows-1251, windows-1252, windows-1253,
windows-1254, windows-1255, windows-1256, windows-1257, windows-1258,
windows-31j, x-big5-hkscs-2001, x-big5-solaris, x-compound_text,
x-euc-jp-linux, x-euc-tw, x-eucjp-open, x-ibm1006, x-ibm1025, x-ibm1046,
x-ibm1097, x-ibm1098, x-ibm1112, x-ibm1122, x-ibm1123, x-ibm1124, x-ibm1166,
x-ibm1364, x-ibm1381, x-ibm1383, x-ibm300, x-ibm33722, x-ibm737, x-ibm833,
x-ibm834, x-ibm856, x-ibm874, x-ibm875, x-ibm921, x-ibm922, x-ibm930, x-ibm933,
x-ibm935, x-ibm937, x-ibm939, x-ibm942, x-ibm942c, x-ibm943, x-ibm943c,
x-ibm948, x-ibm949, x-ibm949c, x-ibm950, x-ibm964, x-ibm970, x-iscii91,
x-iso-2022-cn-cns, x-iso-2022-cn-gb, x-iso-8859-11, x-jis0208, x-jisautodetect,
x-johab, x-macarabic, x-maccentraleurope, x-maccroatian, x-maccyrillic,
x-macdingbat, x-macgreek, x-machebrew, x-maciceland, x-macroman, x-macromania,
x-macsymbol, x-macthai, x-macturkish, x-macukraine, x-ms932_0213,
x-ms950-hkscs, x-ms950-hkscs-xp, x-mswin-936, x-pck, x-sjis_0213,
x-utf-16le-bom, x-utf-32be-bom, x-utf-32le-bom, x-windows-50220,
x-windows-50221, x-windows-874, x-windows-949, x-windows-950,
x-windows-iso2022jp
< Content-Length: 5211
< Server: Jetty(9.3.6.v20151106)
<
{"message" : "Server has encountered while executing Adhoc query!",
"stackTrace" :
"com.gemstone.gemfire.rest.internal.web.exception.GemfireRestException: Server
has encountered while executing Adhoc query!
at
com.gemstone.gemfire.rest.internal.web.controllers.QueryAccessController.runAdhocQuery(QueryAccessController.java:208)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
at
[jira] [Updated] (GEODE-1524) Swagger UI does not show query errors
[
https://issues.apache.org/jira/browse/GEODE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-1524:
--
Labels: bug-hunt (was: )
> Swagger UI does not show query errors
> -
>
> Key: GEODE-1524
> URL: https://issues.apache.org/jira/browse/GEODE-1524
> Project: Geode
> Issue Type: Improvement
> Components: rest (dev)
>Reporter: Jens Deppe
> Labels: bug-hunt
>
> I'm playing with UDA and running adhoc queries through the Swagger UI.
> However, if I have a catastrophic error in my query the Swagger UI doesn't
> display it and I'm left with a 'progress spinner' bar. However, the same
> query from the command line does produce an appropriate error. For example,
> here I'm trying to use my {{sumuda}} function in a query:
> {noformat}
> (2.7)jdeppe@deppe-mbp bughunt-2016 $ curl -v -H "Accept: application/json"
> 'http://127.0.0.1:8080/gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo'
> * Trying 127.0.0.1...
> * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> > GET /gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo
> > HTTP/1.1
> > Host: 127.0.0.1:8080
> > User-Agent: curl/7.43.0
> > Accept: application/json
> >
> < HTTP/1.1 500 Server Error
> < Date: Fri, 10 Jun 2016 19:52:26 GMT
> < Content-Type: application/json
> < Accept-Charset: big5, big5-hkscs, cesu-8, euc-jp, euc-kr, gb18030, gb2312,
> gbk, ibm-thai, ibm00858, ibm01140, ibm01141, ibm01142, ibm01143, ibm01144,
> ibm01145, ibm01146, ibm01147, ibm01148, ibm01149, ibm037, ibm1026, ibm1047,
> ibm273, ibm277, ibm278, ibm280, ibm284, ibm285, ibm290, ibm297, ibm420,
> ibm424, ibm437, ibm500, ibm775, ibm850, ibm852, ibm855, ibm857, ibm860,
> ibm861, ibm862, ibm863, ibm864, ibm865, ibm866, ibm868, ibm869, ibm870,
> ibm871, ibm918, iso-2022-cn, iso-2022-jp, iso-2022-jp-2, iso-2022-kr,
> iso-8859-1, iso-8859-13, iso-8859-15, iso-8859-2, iso-8859-3, iso-8859-4,
> iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, iso-8859-9, jis_x0201,
> jis_x0212-1990, koi8-r, koi8-u, shift_jis, tis-620, us-ascii, utf-16,
> utf-16be, utf-16le, utf-32, utf-32be, utf-32le, utf-8, windows-1250,
> windows-1251, windows-1252, windows-1253, windows-1254, windows-1255,
> windows-1256, windows-1257, windows-1258, windows-31j, x-big5-hkscs-2001,
> x-big5-solaris, x-compound_text, x-euc-jp-linux, x-euc-tw, x-eucjp-open,
> x-ibm1006, x-ibm1025, x-ibm1046, x-ibm1097, x-ibm1098, x-ibm1112, x-ibm1122,
> x-ibm1123, x-ibm1124, x-ibm1166, x-ibm1364, x-ibm1381, x-ibm1383, x-ibm300,
> x-ibm33722, x-ibm737, x-ibm833, x-ibm834, x-ibm856, x-ibm874, x-ibm875,
> x-ibm921, x-ibm922, x-ibm930, x-ibm933, x-ibm935, x-ibm937, x-ibm939,
> x-ibm942, x-ibm942c, x-ibm943, x-ibm943c, x-ibm948, x-ibm949, x-ibm949c,
> x-ibm950, x-ibm964, x-ibm970, x-iscii91, x-iso-2022-cn-cns, x-iso-2022-cn-gb,
> x-iso-8859-11, x-jis0208, x-jisautodetect, x-johab, x-macarabic,
> x-maccentraleurope, x-maccroatian, x-maccyrillic, x-macdingbat, x-macgreek,
> x-machebrew, x-maciceland, x-macroman, x-macromania, x-macsymbol, x-macthai,
> x-macturkish, x-macukraine, x-ms932_0213, x-ms950-hkscs, x-ms950-hkscs-xp,
> x-mswin-936, x-pck, x-sjis_0213, x-utf-16le-bom, x-utf-32be-bom,
> x-utf-32le-bom, x-windows-50220, x-windows-50221, x-windows-874,
> x-windows-949, x-windows-950, x-windows-iso2022jp
> < Content-Length: 5211
> < Server: Jetty(9.3.6.v20151106)
> <
> {"message" : "Server has encountered while executing Adhoc query!",
> "stackTrace" :
> "com.gemstone.gemfire.rest.internal.web.exception.GemfireRestException:
> Server has encountered while executing Adhoc query!
> at
> com.gemstone.gemfire.rest.internal.web.controllers.QueryAccessController.runAdhocQuery(QueryAccessController.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
> at
>
[jira] [Updated] (GEODE-1523) geode-examples README.md markdown improvement
[
https://issues.apache.org/jira/browse/GEODE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1523:
---
Labels: bug-hunt (was: )
> geode-examples README.md markdown improvement
> -
>
> Key: GEODE-1523
> URL: https://issues.apache.org/jira/browse/GEODE-1523
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Karen Smoler Miller
> Labels: bug-hunt
>
> The markdown in the feature/GEODE-33 branch file {{geode-examples/README.md}}
> is not yet right.
> There are problems with the references and with the bulleted list.
> (A separate ticket will address the content of the file. This ticket is only
> to fix the markdown, so it displays correctly.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1523) geode-examples README.md markdown improvement
Karen Smoler Miller created GEODE-1523:
--
Summary: geode-examples README.md markdown improvement
Key: GEODE-1523
URL: https://issues.apache.org/jira/browse/GEODE-1523
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Karen Smoler Miller
The markdown in the feature/GEODE-33 branch file {{geode-examples/README.md}}
is not yet right.
There are problems with the references and with the bulleted list.
(A separate ticket will address the content of the file. This ticket is only
to fix the markdown, so it displays correctly.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1504) Remove unused test classes
[ https://issues.apache.org/jira/browse/GEODE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1504: - Description: Remove these unused test classes from Geode: * com/gemstone/gemfire/JUnitTestSetup.java * com/gemstone/gemfire/TimingTestCase.java * com/gemstone/gemfire/UnitTestDoclet.java * com/gemstone/gemfire/cache/query/functional/IndexUsageWithAliasAsProjAtrbt.java (misnamed duplicate of IndexUsageWithAliasAsProjAtrbtJUnitTest.java) * com/gemstone/gemfire/pdx/VersionClassLoader.java was: Remove these unused test classes from Geode: * com/gemstone/gemfire/JUnitTestSetup.java * com/gemstone/gemfire/UnitTestDoclet.java * com/gemstone/gemfire/pdx/VersionClassLoader.java * com/gemstone/gemfire/TimingTestCase.java * com/gemstone/gemfire/cache/query/functional/IndexUsageWithAliasAsProjAtrbt.java (misnamed duplicate of IndexUsageWithAliasAsProjAtrbtJUnitTest.java) > Remove unused test classes > -- > > Key: GEODE-1504 > URL: https://issues.apache.org/jira/browse/GEODE-1504 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund > > Remove these unused test classes from Geode: > * com/gemstone/gemfire/JUnitTestSetup.java > * com/gemstone/gemfire/TimingTestCase.java > * com/gemstone/gemfire/UnitTestDoclet.java > * > com/gemstone/gemfire/cache/query/functional/IndexUsageWithAliasAsProjAtrbt.java > (misnamed duplicate of IndexUsageWithAliasAsProjAtrbtJUnitTest.java) > * com/gemstone/gemfire/pdx/VersionClassLoader.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1522) Lucene WiKi page issues
[ https://issues.apache.org/jira/browse/GEODE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-1522: --- Labels: bug-hunt (was: ) > Lucene WiKi page issues > --- > > Key: GEODE-1522 > URL: https://issues.apache.org/jira/browse/GEODE-1522 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao > Labels: bug-hunt > > 1. The Gfsh support isn't implemented yet. Maybe mention that in the doc, say > "to be coming later". > 2. The LuceneService.createIndex returns null instead of a lucene index, but > the code sample indicates otherwise. > 3. In section "Key Points" #4, the index should be created before the region > is created, not before inserting data. > 4. The xml sample provided in the wiki doesn't work out of the box. I think > it's missing a quote and an ending cache for it to be a valid xml, but even > if we added those, it's still complaining something about "Cannot find the > declaration of element 'cache'.". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1522) Lucene WiKi page issues
Jinmei Liao created GEODE-1522: -- Summary: Lucene WiKi page issues Key: GEODE-1522 URL: https://issues.apache.org/jira/browse/GEODE-1522 Project: Geode Issue Type: Bug Reporter: Jinmei Liao 1. The Gfsh support isn't implemented yet. Maybe mention that in the doc, say "to be coming later". 2. The LuceneService.createIndex returns null instead of a lucene index, but the code sample indicates otherwise. 3. In section "Key Points" #4, the index should be created before the region is created, not before inserting data. 4. The xml sample provided in the wiki doesn't work out of the box. I think it's missing a quote and an ending cache for it to be a valid xml, but even if we added those, it's still complaining something about "Cannot find the declaration of element 'cache'.". -- 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=15325006#comment-15325006 ] ASF subversion and git services commented on GEODE-33: -- Commit 4b6200d0ffc92c1e9fe9b1695c0f5ccd99e6c387 in incubator-geode's branch refs/heads/feature/GEODE-33 from William Markito [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=4b6200d ] [GEODE-33] - Adding geode-example module Creating a simple example for replicated regions to test the proposed example model Adding script tests Adding server folders to gitignore Adding gitignore and readme files > 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-1470) Upgrade log4j to 2.6
[ https://issues.apache.org/jira/browse/GEODE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324833#comment-15324833 ] ASF GitHub Bot commented on GEODE-1470: --- Github user kirklund commented on the issue: https://github.com/apache/incubator-geode/pull/154 This change looks good. I'll handle this pull request and determine why Travis failed. > Upgrade log4j to 2.6 > > > Key: GEODE-1470 > URL: https://issues.apache.org/jira/browse/GEODE-1470 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > The new version of log4j (2.6) has made improvements to make it "garbage > free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We > should upgrade to this version to reap the benefits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-744.
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
Resolving this ticket as is. Opening another for the {{count(*)}} issue.
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1520) Swagger UI can appear broken depending on the URL used
Jens Deppe created GEODE-1520:
-
Summary: Swagger UI can appear broken depending on the URL used
Key: GEODE-1520
URL: https://issues.apache.org/jira/browse/GEODE-1520
Project: Geode
Issue Type: Improvement
Components: docs, rest (dev)
Reporter: Jens Deppe
I'm playing with the Swagger UI and followed the docs here:
http://gemfire.docs.pivotal.io/docs-gemfire/latest/rest_apps/using_swagger.html
Specifically I set {{--J=-Dgemfire.http-service-bind-address=localhost}}.
However, browsing to http://127.0.0.1:8080/gemfire-api/docs/index.html shows me
a minor error on the page {{Unable to read api 'region' from path
http://localhost:8080/gemfire-api/api-docs/gemfireApi/region (server returned
undefined)}} and I cannot interact with it.
Looking at the browser console I see this error: {{No
'Access-Control-Allow-Origin' header is present on the requested resource.}}.
It turns out you *MUST* use the same, literal value in the URL that you used
for bind address. If you used an IP then your URL must also use an IP.
This should be documented and/or fixed if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1518) miscellaneouscommandsdunittest.testshutdownfortime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Jinmei Liao created GEODE-1518: -- Summary: miscellaneouscommandsdunittest.testshutdownfortime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1518 URL: https://issues.apache.org/jira/browse/GEODE-1518 Project: Geode Issue Type: Bug Reporter: Jinmei Liao Geode_develop_DistributedTests/2857/ java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- Found suspect string in log4j at line 617 [fatal 2016/06/09 22:41:13.751 PDT tid=0x1629] org.eclipse.jetty.io.EofException at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) at org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) at org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) at org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119) at org.eclipse.jetty.server.Server.handle(Server.java:517) at
