[jira] [Updated] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

[Jared Stewart (JIRA)]

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

Jared Stewart updated GEODE-1905:
-
Fix Version/s: (was: 1.0.0-incubating.M3)
   1.0.0-incubating

> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>  Labels: build, management
> Fix For: 1.0.0-incubating
>
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



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

[jira] [Resolved] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

[Jared Stewart (JIRA)]

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

Jared Stewart resolved GEODE-1905.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3

> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>  Labels: build, management
> Fix For: 1.0.0-incubating.M3
>
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



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

[jira] [Resolved] (GEODE-1899) Address the custom 'clean' gradle task warning

[Jared Stewart (JIRA)]

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

Jared Stewart resolved GEODE-1899.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
> Fix For: 1.0.0-incubating
>
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



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

[jira] [Updated] (GEODE-1801) nonSingleHopsCount cache-perf statistic is inaccurate

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer updated GEODE-1801:
-
Assignee: (was: Udo Kohlmeyer)

> nonSingleHopsCount cache-perf statistic is inaccurate
> -
>
> Key: GEODE-1801
> URL: https://issues.apache.org/jira/browse/GEODE-1801
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>
> While working on GEODE-1761 I noticed that this statistic is only updated if 
> the metadata for server partitioned-region bucket location is going to be 
> refreshed.  The statistic should actually be incremented any time the servers 
> send a metadata refresh hint in their response.  PutOp, DestroyOp, GetOp, etc 
> need to do this in their processResponse() methods and the current increments 
> of the stat in ClientMetadataService should be removed.



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

[jira] [Created] (GEODE-1911) Provide CqAttributes Builder in addition to existing Factory

[Jared Stewart (JIRA)]

Jared Stewart created GEODE-1911:


 Summary: Provide CqAttributes Builder in addition to existing 
Factory
 Key: GEODE-1911
 URL: https://issues.apache.org/jira/browse/GEODE-1911
 Project: Geode
  Issue Type: Wish
  Components: client queues, querying
Reporter: Jared Stewart


As a user, it requires at three lines of code to create a minimal 
{{CqAttributes}} object with one {{CqListener}}:

{code}
CqAttributesFactory cqf = new CqAttributesFactory();
cqf.addCqListener(new CQListener());
CqAttributes cqa = cqf.create();
{code}

This could be done in one line with less boilerplate if we also provided a 
CqAttributesBuilder. (See [the builder 
pattern|http://www.informit.com/articles/article.aspx?p=1216151=2].)
{code}
CqAttributes cqa = new CqAttributes.Builder().withCqListener(new 
CQListener()).build();
{code}



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

[jira] [Created] (GEODE-1910) revise membership properties in internal/cache/properties.html

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-1910:
---

 Summary: revise membership properties in 
internal/cache/properties.html
 Key: GEODE-1910
 URL: https://issues.apache.org/jira/browse/GEODE-1910
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Bruce Schuchardt


The properties.html file has a number of old properties refering to 
com.gemstone.org.jgroups.  These need to be removed and the new GMS properties 
should be added in their place.



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

[jira] [Resolved] (GEODE-1489) The users' password should not be logged

[Jinmei Liao (JIRA)]

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

Jinmei Liao resolved GEODE-1489.

Resolution: Fixed

> The users' password should not be logged
> 
>
> Key: GEODE-1489
> URL: https://issues.apache.org/jira/browse/GEODE-1489
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Jens Deppe
>Assignee: Jinmei Liao
>
> The following currently appears in the member's log file:
> {noformat}
> [info 2016/05/31 15:15:52.475 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] Logging in root
> [info 2016/05/31 15:15:52.665 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] User=root pwd=secret
> {noformat}



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

[jira] [Commented] (GEODE-1489) The users' password should not be logged

[Jinmei Liao (JIRA)]

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

Jinmei Liao commented on GEODE-1489:


these log messages was put out by the SampleSecurityManager, and was removed 
later on.

> The users' password should not be logged
> 
>
> Key: GEODE-1489
> URL: https://issues.apache.org/jira/browse/GEODE-1489
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Jens Deppe
>Assignee: Jinmei Liao
>
> The following currently appears in the member's log file:
> {noformat}
> [info 2016/05/31 15:15:52.475 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] Logging in root
> [info 2016/05/31 15:15:52.665 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] User=root pwd=secret
> {noformat}



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

[jira] [Assigned] (GEODE-1489) The users' password should not be logged

[Jinmei Liao (JIRA)]

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

Jinmei Liao reassigned GEODE-1489:
--

Assignee: Jinmei Liao

> The users' password should not be logged
> 
>
> Key: GEODE-1489
> URL: https://issues.apache.org/jira/browse/GEODE-1489
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Jens Deppe
>Assignee: Jinmei Liao
>
> The following currently appears in the member's log file:
> {noformat}
> [info 2016/05/31 15:15:52.475 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] Logging in root
> [info 2016/05/31 15:15:52.665 PDT locator1  Connection(4)-10.118.33.250> tid=0x14] User=root pwd=secret
> {noformat}



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

[jira] [Assigned] (GEODE-1801) nonSingleHopsCount cache-perf statistic is inaccurate

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer reassigned GEODE-1801:


Assignee: Udo Kohlmeyer

> nonSingleHopsCount cache-perf statistic is inaccurate
> -
>
> Key: GEODE-1801
> URL: https://issues.apache.org/jira/browse/GEODE-1801
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Udo Kohlmeyer
>
> While working on GEODE-1761 I noticed that this statistic is only updated if 
> the metadata for server partitioned-region bucket location is going to be 
> refreshed.  The statistic should actually be incremented any time the servers 
> send a metadata refresh hint in their response.  PutOp, DestroyOp, GetOp, etc 
> need to do this in their processResponse() methods and the current increments 
> of the stat in ClientMetadataService should be removed.



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

[jira] [Resolved] (GEODE-1821) CI Failure: PersistentColocatedPartitionedRegionDUnitTest.testFullTreeOfColocatedChildPRsWithMissingRegions

[Kenneth Howe (JIRA)]

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

Kenneth Howe resolved GEODE-1821.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

PR #237 fixed this issue

> CI Failure: 
> PersistentColocatedPartitionedRegionDUnitTest.testFullTreeOfColocatedChildPRsWithMissingRegions
> ---
>
> Key: GEODE-1821
> URL: https://issues.apache.org/jira/browse/GEODE-1821
> Project: Geode
>  Issue Type: Bug
>  Components: persistence, regions
>Reporter: Anilkumar Gingade
>Assignee: Kenneth Howe
> Fix For: 1.0.0-incubating
>
>
> Build #3755 (Aug 24, 2016 5:09:20 AM)
> Revision: 37269735eec44f51ee53075718afe2fa85edc22e
> refs/remotes/origin/develop
> Error Message
> java.util.concurrent.TimeoutException: Timed out waiting 3 milliseconds 
> for AsyncInvocation to complete.
> Stacktrace
> java.util.concurrent.TimeoutException: Timed out waiting 3 milliseconds 
> for AsyncInvocation to complete.
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.timeoutIfAlive(AsyncInvocation.java:443)
>   at 
> com.gemstone.gemfire.test.dunit.AsyncInvocation.get(AsyncInvocation.java:390)
>   at 
> com.gemstone.gemfire.internal.cache.partitioned.PersistentColocatedPartitionedRegionDUnitTest.testFullTreeOfColocatedChildPRsWithMissingRegions(PersistentColocatedPartitionedRegionDUnitTest.java:1197)
>   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:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 

[jira] [Updated] (GEODE-1524) Swagger UI does not show query errors

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1524:

Fix Version/s: 1.0.0-incubating

> 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
>Assignee: Udo Kohlmeyer
>  Labels: bug-hunt
> Fix For: 1.0.0-incubating
>
>
> 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] [Updated] (GEODE-1513) geode-web-api war contains duplicate jars

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer updated GEODE-1513:
-
Assignee: Anthony Baker

> geode-web-api war contains duplicate jars
> -
>
> Key: GEODE-1513
> URL: https://issues.apache.org/jira/browse/GEODE-1513
> Project: Geode
>  Issue Type: Bug
>  Components: build, rest (dev)
>Reporter: Jens Deppe
>Assignee: Anthony Baker
>
> The war file produced by geode-web-api appears to have all of the 3rd party 
> jars duplicated. 



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

[jira] [Resolved] (GEODE-1524) Swagger UI does not show query errors

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-1524.
--
Resolution: Fixed

> 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
>Assignee: Udo Kohlmeyer
>  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] [Commented] (GEODE-1524) Swagger UI does not show query errors

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1524:


Commit 964ce8379a2bed515fdd9f3d08b1e4d0beb4f39e in incubator-geode's branch 
refs/heads/develop from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=964ce83 ]

GEODE-1524: Updating swagger annotations to 1.3.13
Removing of escape characters out of the return error messages. JSON documents
with "\" are invalid if not escaped.


> 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
>Assignee: Udo Kohlmeyer
>  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 
> 

[jira] [Commented] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1905:


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

GEODE-1905: Address UnknownPropertyException when running tests with Gradle 3.0+

This closes #242


> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>  Labels: build, management
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



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

[jira] [Commented] (GEODE-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[ASF subversion and git services (JIRA)]

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

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

Commit 718bdfcc05f9de1220e72ac5caa5412ce1f3644d in incubator-geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=718bdfc ]

GEODE-37 re-merge commit 6a109a7f57a5402af458d593d93c2e328bd3281b

This was missed during package rename merge


> Package renaming - com.gemstone.gemfire -> org.apache.geode
> ---
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: client/server, docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Assignee: Hitesh Khamesra
>Priority: Blocker
> Fix For: 1.0.0-incubating
>
>
> Geode packages should be renamed from com.gemstone -> org.apache.geode in 
> order to allow an easy transition from incubation to become a TLP. 
> Also, it allow the necessary work that may need to be done at the protocol 
> level in order to allow serialization/message exchange between nodes before 
> an actual release using the definitive class/package naming.
> The issue was discussed in the following thread at dev@:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E



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

[jira] [Updated] (GEODE-1909) A user with no privilege can start a server

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1909:
---
Description: 
1) Start the locator with a security-manager:
start locator --name=loc1 --security-properties-file=security.properties 
--classpath=/Users/jiliao/my_gemfire/security

2) connect to the locator using: guest/guest

3), try start a server as guest:
start server --name=server1 
--security-properties-file=serverSecurity.properties --locators=localhost[10334]

The server will be started.

We should allow only user with CLUSTER:MANAGE permission to start a server.


  was:
1) Start the locator with a security-manager:
start locator --name=loc1 --security-properties-file=security.properties 
--classpath=/Users/jiliao/my_gemfire/security

2) connect to the locator using: guest/guest

3), try start a server as guest:
start server --name=server1 
--security-properties-file=serverSecurity.properties --locators=localhost[10334]

The server will be started.

We should allow only user with DATA:MANAGE permission to start a server.



> A user with no privilege can start a server
> ---
>
> Key: GEODE-1909
> URL: https://issues.apache.org/jira/browse/GEODE-1909
> Project: Geode
>  Issue Type: Bug
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>  Labels: management
> Attachments: security.json, security.properties, 
> serverSecurity.properties
>
>
> 1) Start the locator with a security-manager:
> start locator --name=loc1 --security-properties-file=security.properties 
> --classpath=/Users/jiliao/my_gemfire/security
> 2) connect to the locator using: guest/guest
> 3), try start a server as guest:
> start server --name=server1 
> --security-properties-file=serverSecurity.properties 
> --locators=localhost[10334]
> The server will be started.
> We should allow only user with CLUSTER:MANAGE permission to start a server.



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

[jira] [Resolved] (GEODE-1894) SerialGatewaySenderOperationsDUnitTest test hangs

[xiaojian zhou (JIRA)]

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

xiaojian zhou resolved GEODE-1894.
--
Resolution: Cannot Reproduce

Re-run the test using the current revision and even Sep 12's revision, no 
reproduce so far. 

> SerialGatewaySenderOperationsDUnitTest test hangs
> -
>
> Key: GEODE-1894
> URL: https://issues.apache.org/jira/browse/GEODE-1894
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Hitesh Khamesra
> Attachments: threaddump.txt
>
>
> test tries to stop Serial Gateway Sender and that thread just hangs. Event 
> processors are waiting to become primary. One AckReader thread waiting for 
> ack. Seems like need to interrupt these threads. Attached thread dump 



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

[jira] [Commented] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

[ASF GitHub Bot (JIRA)]

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

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

GitHub user jaredjstewart opened a pull request:

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

GEODE-1905: Address UnknownPropertyException when running tests with Gradle 
3.0+

AvailablePortFinder was deprecated in [Gradle 
2.8](https://docs.gradle.org/2.8/release-notes#deprecated-classes-and-constants)
 and removed in Gradle 3.0.  

I took a look into how the Gradle project itself dealt with this change, 
and they [use]( 
https://github.com/gradle/gradle/blob/2703311c33e8a295ba7ccb29a62ed8be761ef66f/subprojects/internal-performance-testing/src/main/groovy/org/gradle/performance/fixture/HonestProfilerCollector.groovy)
  the Apache MINA library's 
[org.apache.mina.util.AvailablePortFinder](https://mina.apache.org/mina-project/apidocs/src-html/org/apache/mina/util/AvailablePortFinder.html)
 class.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaredjstewart/incubator-geode 
feature/GEODE-1905

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-geode/pull/242.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #242


commit a609f86ad662c6d501afd068c68e36a8b302eef3
Author: Jared Stewart 
Date:   2016-09-19T17:37:18Z

GEODE-1905: Address UnknownPropertyException when running tests with Gradle 
3.0+




> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>  Labels: build, management
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



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

[jira] [Assigned] (GEODE-1909) A user with no privilege can start a server

[Jinmei Liao (JIRA)]

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

Jinmei Liao reassigned GEODE-1909:
--

Assignee: Jinmei Liao

> A user with no privilege can start a server
> ---
>
> Key: GEODE-1909
> URL: https://issues.apache.org/jira/browse/GEODE-1909
> Project: Geode
>  Issue Type: Bug
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>  Labels: management
> Attachments: security.json, security.properties, 
> serverSecurity.properties
>
>
> 1) Start the locator with a security-manager:
> start locator --name=loc1 --security-properties-file=security.properties 
> --classpath=/Users/jiliao/my_gemfire/security
> 2) connect to the locator using: guest/guest
> 3), try start a server as guest:
> start server --name=server1 
> --security-properties-file=serverSecurity.properties 
> --locators=localhost[10334]
> The server will be started.
> We should allow only user with DATA:MANAGE permission to start a server.



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

[jira] [Updated] (GEODE-1909) A user with no privilege can start a server

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1909:
---
Labels: management  (was: )

> A user with no privilege can start a server
> ---
>
> Key: GEODE-1909
> URL: https://issues.apache.org/jira/browse/GEODE-1909
> Project: Geode
>  Issue Type: Bug
>Reporter: Jinmei Liao
>  Labels: management
> Attachments: security.json, security.properties, 
> serverSecurity.properties
>
>
> 1) Start the locator with a security-manager:
> start locator --name=loc1 --security-properties-file=security.properties 
> --classpath=/Users/jiliao/my_gemfire/security
> 2) connect to the locator using: guest/guest
> 3), try start a server as guest:
> start server --name=server1 
> --security-properties-file=serverSecurity.properties 
> --locators=localhost[10334]
> The server will be started.
> We should allow only user with DATA:MANAGE permission to start a server.



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

[jira] [Updated] (GEODE-1909) A user with no privilege can start a server

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-1909:
---
Attachment: serverSecurity.properties
security.properties
security.json

> A user with no privilege can start a server
> ---
>
> Key: GEODE-1909
> URL: https://issues.apache.org/jira/browse/GEODE-1909
> Project: Geode
>  Issue Type: Bug
>Reporter: Jinmei Liao
> Attachments: security.json, security.properties, 
> serverSecurity.properties
>
>
> 1) Start the locator with a security-manager:
> start locator --name=loc1 --security-properties-file=security.properties 
> --classpath=/Users/jiliao/my_gemfire/security
> 2) connect to the locator using: guest/guest
> 3), try start a server as guest:
> start server --name=server1 
> --security-properties-file=serverSecurity.properties 
> --locators=localhost[10334]
> The server will be started.
> We should allow only user with DATA:MANAGE permission to start a server.



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

[jira] [Created] (GEODE-1909) A user with no privilege can start a server

[Jinmei Liao (JIRA)]

Jinmei Liao created GEODE-1909:
--

 Summary: A user with no privilege can start a server
 Key: GEODE-1909
 URL: https://issues.apache.org/jira/browse/GEODE-1909
 Project: Geode
  Issue Type: Bug
Reporter: Jinmei Liao


1) Start the locator with a security-manager:
start locator --name=loc1 --security-properties-file=security.properties 
--classpath=/Users/jiliao/my_gemfire/security

2) connect to the locator using: guest/guest

3), try start a server as guest:
start server --name=server1 
--security-properties-file=serverSecurity.properties --locators=localhost[10334]

The server will be started.

We should allow only user with DATA:MANAGE permission to start a server.




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

[jira] [Commented] (GEODE-1908) DistributedSystem.connect call not configuring p2p server with SSL

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1908:


Commit 3d0dc749259185c266a67db85fb8ef65a4340819 in incubator-geode's branch 
refs/heads/develop from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3d0dc74 ]

GEODE-1908 DS.connect call not configuring p2p server with SSL.

Before initializing the ssl server socket we make sure all config
has been taken care.


> DistributedSystem.connect call not configuring p2p server with SSL
> --
>
> Key: GEODE-1908
> URL: https://issues.apache.org/jira/browse/GEODE-1908
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Hitesh Khamesra
>Assignee: Hitesh Khamesra
> Fix For: 2.0.0-incubating
>
>
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during 
> handshake
>   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
>   at 
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
>   at 
> org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:1058)
>   at 
> org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:947)
>   at 
> org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:907)
>   at 
> org.apache.geode.internal.net.SocketCreator.connectForServer(SocketCreator.java:888)
>   at org.apache.geode.internal.tcp.Connection.(Connection.java:1291)
>   at 
> org.apache.geode.internal.tcp.Connection.createSender(Connection.java:1072)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:366)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.getUnorderedOrConserveSockets(ConnectionTable.java:482)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:669)
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:965)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:560)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:327)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:620)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1685)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1861)
>   at 
> org.apache.geode.distributed.internal.DistributionChannel.send(DistributionChannel.java:88)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.sendOutgoing(DistributionManager.java:3402)
>   at 
> org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:75)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.sendStartupMessage(DistributionManager.java:2649)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:550)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:659)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:299)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:237)
>   at 
> hydra.DistributedSystemHelper._connect(DistributedSystemHelper.java:110)
>   at 
> hydra.DistributedSystemHelper.connect(DistributedSystemHelper.java:73)
>   at hydra.CacheHelper.createCache(CacheHelper.java:95)
>   at hct.HierCache.initServerRegion(HierCache.java:112)
>   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 hydra.MethExecutor.execute(MethExecutor.java:199)
>   at hydra.MethExecutor.execute(MethExecutor.java:163)
>   at hydra.TestTask.execute(TestTask.java:195)
>   at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>   at sun.security.ssl.InputRecord.read(InputRecord.java:505)
>   at 

[jira] [Assigned] (GEODE-1908) DistributedSystem.connect call not configuring p2p server with SSL

[Hitesh Khamesra (JIRA)]

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

Hitesh Khamesra reassigned GEODE-1908:
--

Assignee: Hitesh Khamesra

> DistributedSystem.connect call not configuring p2p server with SSL
> --
>
> Key: GEODE-1908
> URL: https://issues.apache.org/jira/browse/GEODE-1908
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Hitesh Khamesra
>Assignee: Hitesh Khamesra
> Fix For: 2.0.0-incubating
>
>
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during 
> handshake
>   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
>   at 
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
>   at 
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
>   at 
> org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:1058)
>   at 
> org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:947)
>   at 
> org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:907)
>   at 
> org.apache.geode.internal.net.SocketCreator.connectForServer(SocketCreator.java:888)
>   at org.apache.geode.internal.tcp.Connection.(Connection.java:1291)
>   at 
> org.apache.geode.internal.tcp.Connection.createSender(Connection.java:1072)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:366)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.getUnorderedOrConserveSockets(ConnectionTable.java:482)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:669)
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:965)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:560)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:327)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:620)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1685)
>   at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1861)
>   at 
> org.apache.geode.distributed.internal.DistributionChannel.send(DistributionChannel.java:88)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.sendOutgoing(DistributionManager.java:3402)
>   at 
> org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:75)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.sendStartupMessage(DistributionManager.java:2649)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:550)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:659)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:299)
>   at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:237)
>   at 
> hydra.DistributedSystemHelper._connect(DistributedSystemHelper.java:110)
>   at 
> hydra.DistributedSystemHelper.connect(DistributedSystemHelper.java:73)
>   at hydra.CacheHelper.createCache(CacheHelper.java:95)
>   at hct.HierCache.initServerRegion(HierCache.java:112)
>   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 hydra.MethExecutor.execute(MethExecutor.java:199)
>   at hydra.MethExecutor.execute(MethExecutor.java:163)
>   at hydra.TestTask.execute(TestTask.java:195)
>   at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>   at sun.security.ssl.InputRecord.read(InputRecord.java:505)
>   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
>   ... 38 more



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

[jira] [Commented] (GEODE-1511) geode-core Maven POM File incorrectly includes the log4j-slf4j-impl bridge JAR

[Anthony Baker (JIRA)]

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

Anthony Baker commented on GEODE-1511:
--

Link to M3 pom: 
https://repository.apache.org/service/local/repositories/releases/content/org/apache/geode/geode-core/1.0.0-incubating.M3/geode-core-1.0.0-incubating.M3.pom

> geode-core Maven POM File incorrectly includes the log4j-slf4j-impl bridge JAR
> --
>
> Key: GEODE-1511
> URL: https://issues.apache.org/jira/browse/GEODE-1511
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: John Blum
>Priority: Critical
>
> The {{log4j-slf4j-impl}} SLF4J bridge JAR has been erroneously declared in 
> the _Apache Geode_ {{geode-core}} Maven POM file.
> The inclusion of this declaration can have unintended consequences in a 
> user's Geode-based application that might potentially rely on different 
> and/or several logging frameworks (e.g. SLF4J, logback, etc), depending on 
> the transitive dependencies of the application.
> Geode should not be including SLF4J bridge JARs in the applications CLASSPATH 
> at runtime or otherwise.
> Additionally, the Geode POM file includes references to *test* dependencies 
> that should be removed, specifically...
> junit
> asm
> system-rules
> mockito-core
> geode-junit
> hadoop-auth
> awaitility
> catch-exception
> cglib
> powermock-module-junit4
> jmock-junit4
> catch-throwable
> tempus-fugit
> commons-collections
> JUnitParams
> bcel
> assertj-core
> powermock-core
> jedis
> jmock-legacy
> powermock-api-mockito
> hamcrest-all
> commons-configuration
> spymemcached
> multithreadedtc
> derby
> The more dependencies you include, the greater chance for conflict an 
> application developer may have when integrating with Apache Geode.  The 
> distributed/deployed (to Maven Central) is less about "building" the Apache 
> Geode project and more about running an application built with Apache Geode.



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

[jira] [Resolved] (GEODE-1644) ClassCastException is thrown with in queries against a map index

[Jason Huynh (JIRA)]

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

Jason Huynh resolved GEODE-1644.

Resolution: Fixed

> ClassCastException is thrown with in queries against a map index
> 
>
> Key: GEODE-1644
> URL: https://issues.apache.org/jira/browse/GEODE-1644
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> When a query with an in clause is used and queries against a map index, a 
> ClassCastException is thrown.  A map index expects an array where the first 
> key is the index key and the second value is the map index key.



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

[jira] [Assigned] (GEODE-1864) CompactMapRangeIndex not updating old keys properly

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-1864:
--

Assignee: Jason Huynh

> CompactMapRangeIndex not updating old keys properly
> ---
>
> Key: GEODE-1864
> URL: https://issues.apache.org/jira/browse/GEODE-1864
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> If an object map field is updated, if the old keys in the map are no longer 
> present in the new map, the index does not update correctly.  Instead it 
> leaves them in the map.
> The fix is to remove the keys associated with the old map that are not part 
> of the new map.



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

[jira] [Resolved] (GEODE-1873) Update gemfire session modules to support Tomcat 7.0.70

[Jason Huynh (JIRA)]

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

Jason Huynh resolved GEODE-1873.

Resolution: Fixed

> Update gemfire session modules to support Tomcat 7.0.70 
> 
>
> Key: GEODE-1873
> URL: https://issues.apache.org/jira/browse/GEODE-1873
> Project: Geode
>  Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> There have been changes in Tomcat 7 that have broken the session modules.  
> They have modified the class type of the field attributes in Session, among 
> other things. 



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

[jira] [Resolved] (GEODE-1840) Certain map queries combine OR predicates into an AND junction

[Jason Huynh (JIRA)]

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

Jason Huynh resolved GEODE-1840.

Resolution: Fixed

> Certain map queries combine OR predicates into an AND junction
> --
>
> Key: GEODE-1840
> URL: https://issues.apache.org/jira/browse/GEODE-1840
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> The following query that uses a map index, will return an incorrect result 
> because the or predicates will incorrectly be combines as AND clauses.  This 
> error only happens in certain paths in the query engine.
> select * from /ExampleRegion er where er[‘codeNumber']=1 and 
> er[‘src']='src_common' and (er[‘country']='JP' or er[‘country']='US')



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

[jira] [Resolved] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-1467.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> Branding: Rename servlet URLs from gemfire to geode
> ---
>
> Key: GEODE-1467
> URL: https://issues.apache.org/jira/browse/GEODE-1467
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, rest (admin), rest (dev)
>Reporter: Nitin Lamba
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating
>
>
> There are a few locations where gemfire references are used (excluding 
> package hierarchy covered in GEODE-37):
> 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1)
> 2. extension modules (http session mgmt)
> 3. others (spring-data?)
> (2) and (3) can be hairy as it may impact existing applications. A change 
> post 1.0 would create complexity, therefore, should be carefully considered 
> for 1.0 release.



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

[jira] [Updated] (GEODE-1659) Prevent misconfiguration of Integrated Security

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1659:

Description: 
All the locators and all the servers need to be configured with 
{{security-manager}} geode property to enable integrated security. If a user 
misses specifying this property even on one member, we end up compromising the 
entire cluster.

We need to make security-manager part of cluster config properties, so that any 
new member joining the system will be able to inherit this property.
We should also reject members that have disabled security and cluster 
configuration from joining the cluster.

  was:
All the locators and all the servers need to be configured with 
{{security-manager}} geode property to enable integrated security. If a user 
misses specifying this property even on one member, we end up compromising the 
entire cluster.
To prevent this, we should log a warning message in the logs and in gfsh 
console when a member is started without security when existing members are 
configured with security.
In the long term we need to make security-manager part of cluster config 
properties, so that any new member joining the system will be able to inherit 
this property.


> Prevent misconfiguration of Integrated Security
> ---
>
> Key: GEODE-1659
> URL: https://issues.apache.org/jira/browse/GEODE-1659
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> All the locators and all the servers need to be configured with 
> {{security-manager}} geode property to enable integrated security. If a user 
> misses specifying this property even on one member, we end up compromising 
> the entire cluster.
> We need to make security-manager part of cluster config properties, so that 
> any new member joining the system will be able to inherit this property.
> We should also reject members that have disabled security and cluster 
> configuration from joining the cluster.



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

[jira] [Updated] (GEODE-1659) Prevent misconfiguration of Integrated Security

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1659:

Summary: Prevent misconfiguration of Integrated Security  (was: Help 
prevent misconfiguration of Integrated Security)

> Prevent misconfiguration of Integrated Security
> ---
>
> Key: GEODE-1659
> URL: https://issues.apache.org/jira/browse/GEODE-1659
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> All the locators and all the servers need to be configured with 
> {{security-manager}} geode property to enable integrated security. If a user 
> misses specifying this property even on one member, we end up compromising 
> the entire cluster.
> To prevent this, we should log a warning message in the logs and in gfsh 
> console when a member is started without security when existing members are 
> configured with security.
> In the long term we need to make security-manager part of cluster config 
> properties, so that any new member joining the system will be able to inherit 
> this property.



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