[jira] [Commented] (GEODE-182) Generate "random" member names if no name is provided

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira commented on GEODE-182:


[~amb] Thanks for bringing this back to life! I did implemented some of that 
with tests in my personal GitHub [1] but testing is still a bit complex to me 
specially around ServerLauncherCommands and 
LauncherLifecycleCommandsJUnitTest...   Maybe I'll be able to continue that 
work and send a PR

[1] 
https://github.com/markito/incubator-geode/commit/aed1f421e2a868f60de8d2958d96a941016c1f36

> Generate "random" member names if no name is provided
> -
>
> Key: GEODE-182
> URL: https://issues.apache.org/jira/browse/GEODE-182
> Project: Geode
>  Issue Type: New Feature
>  Components: configuration
>Reporter: William Markito Oliveira
>Assignee: Jens Deppe
>Priority: Minor
>
> In current cloud and container deployments it's very common to allow the 
> infrastructure to just re-execute the same command in order to provision a 
> new node for a system.
> Since Geode require unique member names on a system I'm proposing to create 
> something similar to what Docker and other projects does and generate 
> "random" names on when none are provided.
> Following the Docker implementation, I'd suggest something like:
> * List of adjectives
> * List of gems 
> and a combination using _ for example:
> {code}
> clever_alexandrite
> sharp_emerald
> tender_sapphire
> {code}
> Those would be server names when *-name* param is not specified OR if a 
> *property file* doesn't have a name as well. 
> From the initial list I'm thinking the model would have:
> * Adjectives = 56
> * Names = 70
> * Total names possible = 3920
> Other benefits I can see for non-cloud deployments as well is for example 
> setting member ports to 0 and by providing no name, it's also easier to 
> create multiple geode nodes on the same physical host without specifying 
> names.
> This wouldn't change current naming features and capabilities.  I'm not 
> planning to implement the feature for locators initially.



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

[jira] [Updated] (GEODE-1871) Update Dockerfile for Geode 1.0.0

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1871:

Summary: Update Dockerfile for Geode 1.0.0  (was: Update Dockerfile for 
Geode M3)

> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for M3.



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

[jira] [Updated] (GEODE-1871) Update Dockerfile for Geode 1.0.0

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1871:

Description: Need to update Dockerfile under incubator-geode/docker for 
1.0.0  (was: Need to update Dockerfile under incubator-geode/docker for M3.)

> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for 1.0.0



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

[jira] [Updated] (GEODE-1011) CI Failure: ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1011:

Fix Version/s: 1.1.0-incubating

> CI Failure: 
> ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode
> --
>
> Key: GEODE-1011
> URL: https://issues.apache.org/jira/browse/GEODE-1011
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Dan Smith
>  Labels: CI, Flaky
> Fix For: 1.1.0-incubating
>
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOperation_1_DUnitTest$$Lambda$388/675257025.run
>  in VM 2 running on Host cc4-rh6.gemstone.com with 8 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
>   at 
> com.gemstone.gemfire.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode(ConcurrentParallelGatewaySenderOperation_1_DUnitTest.java:715)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: 

[jira] [Resolved] (GEODE-1011) CI Failure: ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-1011.
-
Resolution: Fixed

> CI Failure: 
> ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode
> --
>
> Key: GEODE-1011
> URL: https://issues.apache.org/jira/browse/GEODE-1011
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Dan Smith
>  Labels: CI, Flaky
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOperation_1_DUnitTest$$Lambda$388/675257025.run
>  in VM 2 running on Host cc4-rh6.gemstone.com with 8 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:379)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:321)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:272)
>   at 
> com.gemstone.gemfire.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOperation_1_DUnitTest.testParallelPropagationSenderStartAfterStopOnAccessorNode(ConcurrentParallelGatewaySenderOperation_1_DUnitTest.java:715)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.AssertionError: Event never occurred after 24 ms: 

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-37.
---
Resolution: Fixed

> 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-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-420) locator ssl configuration

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-420:
---
Fix Version/s: 1.0.0-incubating

> locator ssl configuration
> -
>
> Key: GEODE-420
> URL: https://issues.apache.org/jira/browse/GEODE-420
> Project: Geode
>  Issue Type: New Feature
>  Components: docs, locator
>Reporter: Darrel Schneider
>Assignee: Udo Kohlmeyer
> Fix For: 1.0.0-incubating
>
>
> We currently allow separate SSL configuration for cluster, server, gateway, 
> jmx-manager, and http-service.
> The "server" attributes configure the ssl connections from clients to a cache 
> server.
> The "gateway" attributes configure the ssl connections between a gateway 
> sender and receiver.
> The "jmx-manager" attributes configure the ssl connections between an admin 
> client (for example gfsh) and the jmx-manager.
> The "http-service" attributes configure the ssl connections between REST 
> clients and the http-service.
> The "cluster" attributes configure the ssl connections between the members of 
> a distributed system (peer-to-peer connections) AND to the locators.
> Using "cluster" for the connections to a locator can be a problem.
> Say you trust all your members of a distributed system since they are running 
> on your private network. So no need for ssl on the p2p connections.
> So you disable cluster-ssl. These means that your peers are locators are all 
> using unsecure connections.
> But some of these members are hosting a cache server and have clients 
> connecting to them. So you configure "server" ssl for the client to server 
> connections. But for your clients to find you servers they need to talk to 
> the locator. Since the clients are coming from the outside world you want 
> them to use SSL. So you configure "server" ssl on them for when they connect 
> to the cache server and "cluster" SSL on them for when they connect to the 
> locator. But your locators are configured with "cluster" SSL disabled so that 
> the p2p connects on the internal network will not be SSL.
> So you are either forced to have you client to locator connections to be 
> unsecure or you need to secure all the cluster connections forcing the peers 
> to also use SSL.
> I think we should introduce "locator" SSL configuration options that would 
> allow you to have just the locator and server using SSL and the "cluster" to 
> have SSL disabled.
> Something else to consider would be for the locator to be able to use SSL for 
> clients but non-SSL for locator-to-locator and peers-to-locator connections. 
> I think this would be more complicated because we would need to have 
> different ports that the locator listens on (one for clients and one for 
> locators and members).
>  



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

[jira] [Updated] (GEODE-1372) Geode UDP communications are not secure when SSL is configured

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1372:

Fix Version/s: 1.0.0-incubating

> Geode UDP communications are not secure when SSL is configured
> --
>
> Key: GEODE-1372
> URL: https://issues.apache.org/jira/browse/GEODE-1372
> Project: Geode
>  Issue Type: New Feature
>  Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Hitesh Khamesra
>  Labels: experimental
> Fix For: 1.0.0-incubating
>
>
> Gemfire servers use UDP requests to communicate membership views, suspect 
> processing and other information. When gemfire SSL is enabled, only the TCP 
> requests are encrypted and UDP requests are not.



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

[jira] [Created] (GEODE-1871) Update Dockerfile for Geode M3

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1871:
---

 Summary: Update Dockerfile for Geode M3
 Key: GEODE-1871
 URL: https://issues.apache.org/jira/browse/GEODE-1871
 Project: Geode
  Issue Type: Improvement
  Components: general
Reporter: William Markito Oliveira


Need to update Dockerfile under incubator-geode/docker for M3.



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

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-37:
--
Component/s: client/server

> 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
>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-37) Package renaming - com.gemstone.gemfire -> org.apache.geode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-37:
--
Summary: Package renaming - com.gemstone.gemfire -> org.apache.geode  (was: 
Package renaming)

> 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: docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>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-37) Package renaming

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-37:
--
Fix Version/s: (was: 2.0.0-incubating)
   1.0.0-incubating

> Package renaming
> 
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>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] [Resolved] (GEODE-1861) Change package name from com.gemstone.gemfire to org.apache.geode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-1861.
-
Resolution: Duplicate

Duplicate of GEODE-37

> Change package name from com.gemstone.gemfire to  org.apache.geode
> --
>
> Key: GEODE-1861
> URL: https://issues.apache.org/jira/browse/GEODE-1861
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Hitesh Khamesra
>Assignee: Hitesh Khamesra
> Fix For: 1.0.0-incubating
>
>
> Need to change package name from com.gemstone.gemfire to  org.apache.geode.



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

[jira] [Resolved] (GEODE-1774) CI failure: PartitionedRegionSingleHopDUnitTest.test_MetadataContents

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-1774.
-
Resolution: Fixed

> CI failure: PartitionedRegionSingleHopDUnitTest.test_MetadataContents
> -
>
> Key: GEODE-1774
> URL: https://issues.apache.org/jira/browse/GEODE-1774
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Hitesh Khamesra
>  Labels: CI
> Fix For: 1.0.0-incubating
>
>
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest that 
> uses java.util.Map was not fulfilled within 60 seconds.
> Stacktrace
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest that 
> uses java.util.Map was not fulfilled within 60 seconds.
>   at 
> com.jayway.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:122)
>   at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:79)
>   at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:27)
>   at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:764)
>   at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:741)
>   at 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.verifyMetadata(PartitionedRegionSingleHopDUnitTest.java:1972)
>   at 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.test_MetadataContents(PartitionedRegionSingleHopDUnitTest.java:368)
>   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.GeneratedMethodAccessor477.invoke(Unknown Source)
>   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 

[jira] [Updated] (GEODE-1774) CI failure: PartitionedRegionSingleHopDUnitTest.test_MetadataContents

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1774:

Fix Version/s: 1.0.0-incubating

> CI failure: PartitionedRegionSingleHopDUnitTest.test_MetadataContents
> -
>
> Key: GEODE-1774
> URL: https://issues.apache.org/jira/browse/GEODE-1774
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Hitesh Khamesra
>  Labels: CI
> Fix For: 1.0.0-incubating
>
>
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest that 
> uses java.util.Map was not fulfilled within 60 seconds.
> Stacktrace
> com.jayway.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest that 
> uses java.util.Map was not fulfilled within 60 seconds.
>   at 
> com.jayway.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:122)
>   at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:79)
>   at 
> com.jayway.awaitility.core.CallableCondition.await(CallableCondition.java:27)
>   at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:764)
>   at 
> com.jayway.awaitility.core.ConditionFactory.until(ConditionFactory.java:741)
>   at 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.verifyMetadata(PartitionedRegionSingleHopDUnitTest.java:1972)
>   at 
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopDUnitTest.test_MetadataContents(PartitionedRegionSingleHopDUnitTest.java:368)
>   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.GeneratedMethodAccessor477.invoke(Unknown Source)
>   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 

[jira] [Updated] (GEODE-1709) LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1709:

Fix Version/s: 1.0.0-incubating

> LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
> 
>
> Key: GEODE-1709
> URL: https://issues.apache.org/jira/browse/GEODE-1709
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Kevin Duling
>Assignee: xiaojian zhou
>  Labels: CI
> Fix For: 1.0.0-incubating
>
>
> In Geode_develop_DistributedTests/3421:
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> venezuela.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> venezuela.gemstone.com with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:125)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:118)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:109)
>   at 
> com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:65)
>   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.RunBefores.evaluate(RunBefores.java:24)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> 

[jira] [Resolved] (GEODE-1761) Clients don't fail back to servers containing non-redundant partitioned regions when they are bounced and rebalanced

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-1761.
-
Resolution: Fixed

> Clients don't fail back to servers containing non-redundant partitioned 
> regions when they are bounced and rebalanced
> 
>
> Key: GEODE-1761
> URL: https://issues.apache.org/jira/browse/GEODE-1761
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
> Fix For: 1.0.0-incubating
>
>
>  Clients don't fail back to servers containing non-redundant partitioned 
> regions when they are bounced and rebalanced.
> When one of the servers is stopped, the client switches to the server(s) 
> containing the new primary. When the server is restarted and rebalanced 
> (which recovers primaryness), the clients do not switch back even though the 
> server continually sends the metadata refresh byte on each operation.
> If the partitioned region has a redundant copy, clients do switch back.



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

[jira] [Updated] (GEODE-1761) Clients don't fail back to servers containing non-redundant partitioned regions when they are bounced and rebalanced

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1761:

Fix Version/s: 1.0.0-incubating

> Clients don't fail back to servers containing non-redundant partitioned 
> regions when they are bounced and rebalanced
> 
>
> Key: GEODE-1761
> URL: https://issues.apache.org/jira/browse/GEODE-1761
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
> Fix For: 1.0.0-incubating
>
>
>  Clients don't fail back to servers containing non-redundant partitioned 
> regions when they are bounced and rebalanced.
> When one of the servers is stopped, the client switches to the server(s) 
> containing the new primary. When the server is restarted and rebalanced 
> (which recovers primaryness), the clients do not switch back even though the 
> server continually sends the metadata refresh byte on each operation.
> If the partitioned region has a redundant copy, clients do switch back.



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

[jira] [Created] (GEODE-1791) Minor LICENSE issues from Geode M3

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1791:
---

 Summary: Minor LICENSE issues from Geode M3
 Key: GEODE-1791
 URL: https://issues.apache.org/jira/browse/GEODE-1791
 Project: Geode
  Issue Type: Bug
  Components: general
Reporter: William Markito Oliveira


LICENSE file issues from M3 release. (Thanks to Justin Mclean) 

- File missing header and missing in LICENSE [1]?
- LICENSE missing Sizzle.js contained within [2]
- LICENSE is missing MooTools contained within [3]
- Only one version of JQuery is mentioned in LICENSE but two versions are 
bundled [4][5]
- This NOTICE file year needs updating? [6]

I notice a number of files are Apache 2.0 license but have copyright lines in 
the header e.g. "Copyright (C) 2011 Clearspring Technologies, Inc.” is this 
correct?

Mail thread: 
http://mail-archives.apache.org/mod_mbox/incubator-general/201608.mbox/%3C513DD920-97CF-4A3F-87C1-43F971339071%40classsoftware.com%3E

1. 
apache-geode-src-1.0.0-incubating.M3/geode-core/src/main/resources/com/gemstone/gemfire/admin/jmx/internal/doc-files/mbeans-descriptors.dtd
2. ./geode-pulse/src/main/webapp/scripts/lib/jquery-1.7.2.js
3. ./geode-pulse/src/main/webapp/scripts/lib/jit.js
4. 
./apache-geode-src-1.0.0-incubating.M3/geode-site/website/content/js/jquery-1.10.1.min.js
5. 
./apache-geode-src-1.0.0-incubating.M3/geode-web-api/src/main/webapp/docs/lib/jquery-1.8.0.min.js
6. ./geode-web/src/main/webapp/META-INF/NOTICE



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

[jira] [Updated] (GEODE-1735) NPE executing LuceneFunction

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1735:

Fix Version/s: 1.0.0-incubating

> NPE executing LuceneFunction
> 
>
> Key: GEODE-1735
> URL: https://issues.apache.org/jira/browse/GEODE-1735
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: William Markito Oliveira
> Fix For: 1.0.0-incubating
>
>
> Stacktrace below.
> {code}
> [info 2016/08/03 16:32:13.923 PDT server1  
> tid=0x588] Unexpected exception during function execution on local node 
> Partitioned Region
> java.lang.NullPointerException
> at 
> com.gemstone.gemfire.cache.lucene.internal.distributed.LuceneFunction.execute(LuceneFunction.java:79)
> at 
> com.gemstone.gemfire.internal.cache.execute.AbstractExecution.executeFunctionLocally(AbstractExecution.java:348)
> at 
> com.gemstone.gemfire.internal.cache.execute.AbstractExecution$1.run(AbstractExecution.java:283)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at 
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at 
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
>
> {code}



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

[jira] [Updated] (GEODE-1737) gfsh query on region that does not exist may cause NPE

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1737:

Fix Version/s: 1.0.0-incubating

> gfsh query on region that does not exist may cause NPE
> --
>
> Key: GEODE-1737
> URL: https://issues.apache.org/jira/browse/GEODE-1737
> Project: Geode
>  Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Jason Huynh
> Fix For: 1.0.0-incubating
>
>
> The lines in DataCommand need to be wrapped with a check for newMember != 
> null.
> Approximately line 1320:
> newMembers.retainAll(members);
> members = newMembers;
> There is a chance that newMembers is null because the region in the query 
> does not exist on any member



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

[jira] [Updated] (GEODE-1372) Geode UDP communications are not secure when SSL is configured

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1372:

Labels: experimental  (was: )

> Geode UDP communications are not secure when SSL is configured
> --
>
> Key: GEODE-1372
> URL: https://issues.apache.org/jira/browse/GEODE-1372
> Project: Geode
>  Issue Type: New Feature
>  Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Hitesh Khamesra
>  Labels: experimental
>
> Gemfire servers use UDP requests to communicate membership views, suspect 
> processing and other information. When gemfire SSL is enabled, only the TCP 
> requests are encrypted and UDP requests are not.



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

[jira] [Updated] (GEODE-9) Spark Integration

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-9:
-
Labels: asf-migration experimental  (was: asf-migration)

> Spark Integration
> -
>
> Key: GEODE-9
> URL: https://issues.apache.org/jira/browse/GEODE-9
> Project: Geode
>  Issue Type: New Feature
>  Components: core, extensions
>Reporter: Dan Smith
>Assignee: Jason Huynh
>  Labels: asf-migration, experimental
> Fix For: 1.0.0-incubating.M1
>
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Geode as a data store for Spark applications is what is being enabled here. 
> By providing a bridge style connector for Spark applications, Geode can 
> become the data store for storing intermediate and final state for Spark 
> applications and allow reference data stored in the in memory tier to be 
> accessed very efficiently for applications
> Expose Geode regions as Spark RDDs
> Write Spark RDDs to Geode Regions
> Execute arbitrary OQL queries in your spark applications



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

[jira] [Updated] (GEODE-46) Provide a Redis protocol adaptor for Geode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-46:
--
Labels: experimental redis  (was: redis)

> Provide a Redis protocol adaptor for Geode
> --
>
> Key: GEODE-46
> URL: https://issues.apache.org/jira/browse/GEODE-46
> Project: Geode
>  Issue Type: New Feature
>  Components: extensions
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Swapnil Bawaskar
>  Labels: experimental, redis
> Fix For: 1.0.0-incubating.M1
>
>
> Redis is an open source, BSD licensed, advanced key-value cache and store. It 
> is often referred to as a data structure server since keys can contain 
> strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs. More at 
> [Redis project page|http://redis.io]
> Providing a Redis protocol adaptor will be beneficial to both Geode and Redis 
> communities.
> * Redis:
> # The Redis community will get a scalable redis implementation where the 
> individual data structures like lists, sets etc will scale across multiple 
> servers.
> # Since the current redis server is single threaded and Geode is good at 
> handling concurrency, this protocol adaptor should be able to provide a 
> highly concurrent redis server.
> * Geode
> # Geode community will be able to use data structures beyond maps (sorted 
> sets, lists)



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

[jira] [Updated] (GEODE-124) Ability to auto-rebalance data

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-124:
---
Labels: experimental  (was: )

> Ability to auto-rebalance data
> --
>
> Key: GEODE-124
> URL: https://issues.apache.org/jira/browse/GEODE-124
> Project: Geode
>  Issue Type: New Feature
>Affects Versions: 1.0.0-incubating
>Reporter: Ashvin
>Assignee: Ashvin
>  Labels: experimental
> Fix For: 1.0.0-incubating.M1
>
> Attachments: GEODE-AutomatedRebalancing-030815.pdf
>
>
> Rebalancing relocates data from heavily loaded members to lightly loaded 
> members. Currently Geode only supports manual rebalancing by issuing a gfsh 
> command or a java function call. In most cases, the decision to rebalance is 
> based on the size of the member. As Geode monitors the data size, it can also 
> automatically trigger rebalancing. Auto-Rebalancing is expected to prevent 
> failures seen in an unbalanced cluster more than with a manual rebalance.
> Latest spec: 
> https://cwiki.apache.org/confluence/display/GEODE/Automated+Rebalancing



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

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-194:
---
Labels: experimental gsoc2016  (was: gsoc2016)

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



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

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-194:
---
Summary: Geode Spark Connector does not support Spark 2.0  (was: Geode 
Spark Connector does not support Spark SQL 1.6)

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



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

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira commented on GEODE-194:


Updated the Spark version for 2.0.

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



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

[jira] [Updated] (GEODE-150) Implementing user defined aggregate functions in OQL

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-150:
---
Labels: experimental  (was: )

> Implementing user defined aggregate functions in OQL
> 
>
> Key: GEODE-150
> URL: https://issues.apache.org/jira/browse/GEODE-150
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Amogh Shetkar
>Assignee: Amogh Shetkar
>  Labels: experimental
>
> Opening this jira for Asif until he gets his jira account working.



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

[jira] [Updated] (GEODE-84) Extract Redis adaptor from core

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-84:
--
Labels: experimental gsoc2016  (was: gsoc2016)

> Extract Redis adaptor from core
> ---
>
> Key: GEODE-84
> URL: https://issues.apache.org/jira/browse/GEODE-84
> Project: Geode
>  Issue Type: Task
>  Components: extensions
>Reporter: Swapnil Bawaskar
>  Labels: experimental, gsoc2016
>
> The Redis adaptor [Geode-46| https://issues.apache.org/jira/browse/GEODE-46] 
> is part of the final code drop in sga2 branch. However it is in gemfire-core 
> directory and needs to be extracted into a new top-level directory 
> gemfire-redis-adaptor.



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

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

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-11:
--
Labels: experimental  (was: )

> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>  Labels: experimental
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Commented] (GEODE-1734) Lucene search for a single entry is returning multiple results

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira commented on GEODE-1734:
-

That also has impact on the "limit" options on GFSH:
{code} 
gfsh>lucene search --name=customerF1 --region=/myCustomer --queryStrings="Wil*" 
--defaultField="f1" --limit=1
key |   value   
| score
--- | 
-
 | -
1   | PDX[1,org.apache.geode.example.lucene.Customer]{f1=William, f2=Oliveira, 
f3=32, f4=97007} | 1
1   | PDX[1,org.apache.geode.example.lucene.Customer]{f1=William, f2=Oliveira, 
f3=32, f4=97007} | 1
{code} 



> Lucene search for a single entry is returning multiple results
> --
>
> Key: GEODE-1734
> URL: https://issues.apache.org/jira/browse/GEODE-1734
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: William Markito Oliveira
>
> Searching for a unique entry is returning multiple results, although the key 
> is the same.  It should return a single result.
> {code}
> gfsh>lucene search --name=customerRegionAll 
> --queryStrings="firstName:Jdfmlevjenzwgd" --region=/customer 
> --defaultField=displayName
> key  |
>value   | score
>  | 
> -
>  | -
> 70dbdb7f-648e-415e-880d-15631f87a523 | 
> PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
> addresses=.. | 12.798602
> 70dbdb7f-648e-415e-880d-15631f87a523 | 
> PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
> addresses=.. | 12.798602
> 70dbdb7f-648e-415e-880d-15631f87a523 | 
> PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
> addresses=.. | 12.798602
> {code}



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

[jira] [Created] (GEODE-1736) Lucene GFSH commands are showing up as off-line commands

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1736:
---

 Summary: Lucene GFSH commands are showing up as off-line commands
 Key: GEODE-1736
 URL: https://issues.apache.org/jira/browse/GEODE-1736
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: William Markito Oliveira


These commands should only available when GFSH is connected to a Locator or 
"online"

{code}
gfsh>l 
list lucene indexes   lucene search
{code}



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

[jira] [Created] (GEODE-1734) Lucene search for a single entry is returning multiple results

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1734:
---

 Summary: Lucene search for a single entry is returning multiple 
results
 Key: GEODE-1734
 URL: https://issues.apache.org/jira/browse/GEODE-1734
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: William Markito Oliveira


Searching for a unique entry is returning multiple results, although the key is 
the same.  It should return a single result.

{code}
gfsh>lucene search --name=customerRegionAll 
--queryStrings="firstName:Jdfmlevjenzwgd" --region=/customer 
--defaultField=displayName
key  |  
 value   | score
 | 
-
 | -
70dbdb7f-648e-415e-880d-15631f87a523 | 
PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
addresses=.. | 12.798602
70dbdb7f-648e-415e-880d-15631f87a523 | 
PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
addresses=.. | 12.798602
70dbdb7f-648e-415e-880d-15631f87a523 | 
PDX[16777220,org.example.domain.model.CustomerEntity]{active=false, 
addresses=.. | 12.798602
{code}



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

[jira] [Created] (GEODE-1733) Lucene indexes stats are zeroed after recovering from indexes from disk

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1733:
---

 Summary: Lucene indexes stats are zeroed after recovering from 
indexes from disk
 Key: GEODE-1733
 URL: https://issues.apache.org/jira/browse/GEODE-1733
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: William Markito Oliveira


When recovering from disk the indexes stats are zeroed until a query is 
executed. 

{code}

gfsh>list lucene indexes --with-stats
   Index Name | Region Path |  Indexed Fields  | Field 
Analyzer |   Status| Query Executions | Updates | Commits | Documents
- | --- |  | 
-- | --- |  | --- | --- | -
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionID  | /customer   | [id] | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionID  | /customer   | [id] | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionID  | /customer   | [id] | {} 
| Initialized | 0| 0   | 0   | 0


After query: 

gfsh>list lucene indexes --with-stats
   Index Name | Region Path |  Indexed Fields  | Field 
Analyzer |   Status| Query Executions | Updates | Commits | Documents
- | --- |  | 
-- | --- |  | --- | --- | -
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionAll | /customer   | [lastUpdateDateTime, displayNa.. | {} 
| Initialized | 0| 0   | 0   | 0
customerRegionID  | /customer   | [id] | {} 
| Initialized | 114  | 0   | 0   | 20644274
customerRegionID  | /customer   | [id] | {} 
| Initialized | 111  | 0   | 0   | 20103890
customerRegionID  | /customer   | [id] | {} 
| Initialized | 114  | 0   | 0   | 20637846
{code}



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

[jira] [Created] (GEODE-1732) "Comparison method violates its general contract!" Exception during Lucene query

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1732:
---

 Summary: "Comparison method violates its general contract!" 
Exception during Lucene query
 Key: GEODE-1732
 URL: https://issues.apache.org/jira/browse/GEODE-1732
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: William Markito Oliveira


This issue is intermittent and the query eventually succeed, but the exception 
still happens after some successful executions. 

Lucene query: 
lucene search --name=customerRegionID 
--queryStrings="id:e4b2a5b6-7dde-46dc-ba04-9ef1242206fe" --region=/customer 
--defaultField=id
Could not process command due to GemFire error. An error occurred while 
searching lucene index across the Geode cluster: Comparison method violates its 
general contract!

{code} 
[error 2016/08/01 15:11:30.914 PDT locator1  tid=0xd4] null
java.lang.IllegalArgumentException: Comparison method violates its general 
contract!
at java.util.TimSort.mergeLo(TimSort.java:773)
at java.util.TimSort.mergeAt(TimSort.java:510)
at java.util.TimSort.mergeForceCollapse(TimSort.java:453)
at java.util.TimSort.sort(TimSort.java:250)
at java.util.Arrays.sort(Arrays.java:1512)
at java.util.ArrayList.sort(ArrayList.java:1454)
at java.util.stream.SortedOps$RefSortingSink.end(SortedOps.java:387)
at java.util.stream.Sink$ChainedReference.end(Sink.java:258)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:513)
at 
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502)
at 
java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at 
java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at 
com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommands.getSearchResults(LuceneIndexCommands.java:407)
at 
com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommands.searchIndex(LuceneIndexCommands.java:297)
at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at 
com.gemstone.gemfire.management.internal.cli.remote.RemoteExecutionStrategy.execute(RemoteExecutionStrategy.java:112)
at 
com.gemstone.gemfire.management.internal.cli.remote.CommandProcessor.executeCommand(CommandProcessor.java:115)
at 
com.gemstone.gemfire.management.internal.cli.remote.CommandStatementImpl.process(CommandStatementImpl.java:66)
at 
com.gemstone.gemfire.management.internal.cli.remote.MemberCommandService.processCommand(MemberCommandService.java:54)
at 
com.gemstone.gemfire.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1681)
at 
com.gemstone.gemfire.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:406)
at 
com.gemstone.gemfire.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:399)
at sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
at 
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
at 
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
at 
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
at 
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
at 
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at 
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1466)
at 
javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
at 

[jira] [Resolved] (GEODE-1671) CI failure: LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnPartialIndexWrite

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira resolved GEODE-1671.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> CI failure: 
> LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnPartialIndexWrite
> ---
>
> Key: GEODE-1671
> URL: https://issues.apache.org/jira/browse/GEODE-1671
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Bruce Schuchardt
>  Labels: ci
> Fix For: 1.0.0-incubating
>
>
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertTrue(Assert.java:52)
>   at 
> com.gemstone.gemfire.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest.putEntriesAndValidateResultsWithRedundancy(LuceneQueriesPeerPRRedundancyDUnitTest.java:109)
>   at 
> com.gemstone.gemfire.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnPartialIndexWrite(LuceneQueriesPeerPRRedundancyDUnitTest.java:87)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>  

[jira] [Assigned] (GEODE-1696) Apache Geode M3 Release

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira reassigned GEODE-1696:
---

Assignee: William Markito Oliveira

> Apache Geode M3 Release 
> 
>
> Key: GEODE-1696
> URL: https://issues.apache.org/jira/browse/GEODE-1696
> Project: Geode
>  Issue Type: Task
>  Components: general
>Reporter: William Markito Oliveira
>Assignee: William Markito Oliveira
> Fix For: 1.0.0-incubating.M3
>
>
> Capturing commits and tasks related to M3 release.



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

[jira] [Created] (GEODE-1696) Apache Geode M3 Release

[William Markito Oliveira (JIRA)]

William Markito Oliveira created GEODE-1696:
---

 Summary: Apache Geode M3 Release 
 Key: GEODE-1696
 URL: https://issues.apache.org/jira/browse/GEODE-1696
 Project: Geode
  Issue Type: Task
  Components: general
Reporter: William Markito Oliveira


Capturing commits and tasks related to M3 release.



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

[jira] [Updated] (GEODE-1696) Apache Geode M3 Release

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1696:

Fix Version/s: 1.0.0-incubating.M3

> Apache Geode M3 Release 
> 
>
> Key: GEODE-1696
> URL: https://issues.apache.org/jira/browse/GEODE-1696
> Project: Geode
>  Issue Type: Task
>  Components: general
>Reporter: William Markito Oliveira
>Assignee: William Markito Oliveira
> Fix For: 1.0.0-incubating.M3
>
>
> Capturing commits and tasks related to M3 release.



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

[jira] [Updated] (GEODE-1316) Update @since tags to include GemFire or Geode in the version name

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1316:

Component/s: client queues

> Update @since tags to include GemFire or Geode in the version name
> --
>
> Key: GEODE-1316
> URL: https://issues.apache.org/jira/browse/GEODE-1316
> Project: Geode
>  Issue Type: Task
>  Components: client queues, docs
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> Based on [this 
> discussion|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3CCAFh%2B7k1nPayKdS--rvqG4uvB%3DjKnTibNqHkfFJf0Kkiy9wQ7bw%40mail.gmail.com%3E]
>  on the mailing list, we want to update all of our \@since tags to be either 
> Geode x.y.z or GemFire x.y.z, depending on when the new method was added to 
> the public API.
> We need to go through all of the existing tags and update them to match this 
> standard. Almost all of them should become \@since GemFire x.y.z unless they 
> are 1.0 or 9.0, in which case they should probably be \@since Geode 1.0.0.



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

[jira] [Updated] (GEODE-1360) need to support command line parameter to use my own log4j.xml in running tests

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1360:

Fix Version/s: 1.0.0-incubating.M3

> need to support command line parameter to use my own log4j.xml in running 
> tests
> ---
>
> Key: GEODE-1360
> URL: https://issues.apache.org/jira/browse/GEODE-1360
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
> Fix For: 1.0.0-incubating.M3
>
>
> The tests are mainly executed by gradle command line, however, we cannot 
> specify a log4j.xml to turn on trace. 



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

[jira] [Updated] (GEODE-611) Remove Dependency on LGPL Licensed Findbugs Annoations

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-611:
---
Sprint: 1.0.0-incubating.M3

> Remove Dependency on LGPL Licensed Findbugs Annoations
> --
>
> Key: GEODE-611
> URL: https://issues.apache.org/jira/browse/GEODE-611
> Project: Geode
>  Issue Type: Task
>  Components: core
>Affects Versions: 1.0.0-incubating
>Reporter: Niall Pemberton
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
>
> FindBugs Annoations (SuppressWarnings & SuppressFBWarnings) have been used in 
> 27 files in geode-core and the FindBugs LGPL License is not permitted under 
> ASF policy:
>   - http://findbugs.sourceforge.net/
> There is an Apache Licensed "clean room" implementation of the findbugs 
> annotations[1] and I have asked on the legal-discuss list[2] if theres any 
> reason this can't be used
> [1] https://github.com/stephenc/findbugs-annotations
> [2] http://markmail.org/message/ieczgjovzhll76yl



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

[jira] [Updated] (GEODE-904) Update LICENSE for BSD/MIT dependencies

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-904:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Update LICENSE for BSD/MIT dependencies
> ---
>
> Key: GEODE-904
> URL: https://issues.apache.org/jira/browse/GEODE-904
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> The following files need to be listed in the LICENSE:
> {noformat}
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf 
> that should be in license
> 1. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> {noformat}



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

[jira] [Updated] (GEODE-53) Update and fix pages in the website

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-53:
--
Sprint:   (was: 1.0.0-incubating.M2)

> Update and fix pages in the website
> ---
>
> Key: GEODE-53
> URL: https://issues.apache.org/jira/browse/GEODE-53
> Project: Geode
>  Issue Type: Improvement
>  Components: web-content
>Reporter: William Markito Oliveira
>Assignee: William Markito Oliveira
> Fix For: 1.0.0-incubating.M1
>
>
> There are some pages in the website that may need attention and updates. 
> Here is a list of the main pages and initial ideas that can improve and fix 
> it:
> Getting Started:
> - How to section is not well formatted and need a better organization.
> - Learn the Basics (Videos)
>   - Not sure it should be listed here and given that it's all GemFire it's a 
> bit confusing still. 
> - Download Geode link should be removed from this page since it's already in 
> the top.
> - Understand some examples section should also go somewhere
> - Documentation should be a direct link from the main menu and not the last 
> thing of this page. 
> Community
> - Conferences need to be updated ad need to work on some automation here to 
> simplify things.
> - Systems (JIRA, Wiki) and mailing lists links should be more accessible and  
> just listed - not in the middle of text or phrases. Also they should be moved 
> to the Contribute (or How to Contribute) page.
> - Don't know why Project History is here, we should move this to a main 
> "About" page.
> Contribute 
> - This page starts with text about GemFire/Geode history - Which IHMO should 
> also be moved to the "About" page or something like that. As well as the 
> incubator proposal link, etc.
> - The contribute page should probably only have sections about: What can be 
> contributions and how to do them - Code, documentation, bugs,  answers on 
> StackOverflow, etc. 
> Download
> Since we don't have releases yet, as per ASF policy we can point them to the 
> GitHub repo and I'd say we should probably copy the very basics steps to 
> build the project here so people can start, with a pointer for the Wiki for 
> detailed instructions.  Something like:  git clone, build, gfsh..
> - Documentation section on this page should be moved to it's own page.
> - Remove the Coming Soon section about the VM and include a pointer to the 
> Docker image on Docker Hub. 



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

[jira] [Updated] (GEODE-27) Apache Geode POM file(s) are incorrect!

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-27:
--
Sprint: 1.0.0-incubating.M3

> Apache Geode POM file(s) are incorrect!
> ---
>
> Key: GEODE-27
> URL: https://issues.apache.org/jira/browse/GEODE-27
> Project: Geode
>  Issue Type: Bug
>  Components: build, general
>Affects Versions: 1.0.0-incubating
> Environment: Apache Geode in Maven or Gradle-based applications.
>Reporter: John Blum
>Assignee: Dan Smith
>Priority: Critical
>  Labels: ApacheGeode, Maven, POM
> Fix For: 1.0.0-incubating.M2
>
> Attachments: gemfire-8.2.0.pom, 
> gemfire-core-1.0.0-incubating-SNAPSHOT.pom, 
> gemfire-jgroups-1.0.0-incubating-SNAPSHOT.pom, 
> gemfire-joptsimple-1.0.0-incubating-SNAPSHOT.pom, 
> gemfire-json-1.0.0-incubating-SNAPSHOT.pom, 
> geode-core-1.0.0-incubating.M2-SNAPSHOT.pom
>
>
> This JIRA is a followup to [GEODE-23] to note the additional issues that are 
> considered 
> ["out-of-scope"|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3CCA%2BULb%2Btfm4LyjwMaB_B7j8WaBNoAYj1%2BkeZSW-pqv0Gdbq2T8g%40mail.gmail.com%3E]
>  for [GEODE-23], yet need to be fixed, none-the-less.
> Specifically, the changes include...
> 1. The {{}} declarations need to be cleaned up (reduced).  
> Technically, _Apache Geode_ should only require...
> {code:xml}
>   
> 
>   gemstone-release
>   GemStone Maven RELEASE Repository
>   http://dist.gemstone.com/maven/release
>   
> true
> always
>   
> 
> 
>   libs-release
>   Spring Maven libs-release Repository
>   http://repo.spring.io/libs-release
> 
>   
> {code}
> For instance, the "obscure" *jline-1.0.S2-B.jar* dependency is "resolvable" 
> from, for instance...
> http://repo.spring.io/libs-release/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar
> NOTE: by default, and unlike Gradle, Maven searches "Maven Central".
> 2. Add proper "scopes", "optional" settings and "exclusions" to the
> dependencies declared in the POM.
> 3.  Many of the "explicitly" declared dependencies (e.g. spring-beans) need
> to be removed; Maven will resolve dependencies transitively.
> As an example, _Apache Geode's_ Maven POM file should be very similar to the 
> {{Pivotal GemFire}} Maven POM file, as recently updated and validated for 
> *GemFire 8.2* (see attached {{gemfire-8.2.0.pom}} file for further details 
> and reference).  This is particularly important where _Apache Geode_ and 
> _Pivotal GemFire_ intersect.
> There maybe other issues with the POM file that need to be included within 
> the "scope" of this +bug+ as well and should be included as such, otherwise 
> this JIRA should *+not+* be marked "complete".



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

[jira] [Updated] (GEODE-1133) SeparateClassloaderTestRunner has to be re-implemented

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1133:

Sprint: 1.0.0-incubating.M3

> SeparateClassloaderTestRunner has to be re-implemented
> --
>
> Key: GEODE-1133
> URL: https://issues.apache.org/jira/browse/GEODE-1133
> Project: Geode
>  Issue Type: Improvement
>  Components: http session
>Reporter: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M3
>
>
> While working on GEODE-52, it was found that `SeparateClassloaderTestRunner' 
> is copied from stackoverflow 
> (http://stackoverflow.com/questions/42102/using-different-classloaders-for-different-junit-tests)
> Either this code has to be re-implemented or find an appropriate code from 
> another reliable source, so that we can add it to the NOTICE about the 
> license.
> extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/junit/SeparateClassloaderTestRunner.java:



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

[jira] [Updated] (GEODE-1293) Align code and docs for modules

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1293:

Sprint: 1.0.0-incubating.M3

> Align code and docs for modules
> ---
>
> Key: GEODE-1293
> URL: https://issues.apache.org/jira/browse/GEODE-1293
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, extensions, hibernate, http session
>Reporter: Jens Deppe
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M3
>
>
> Need to ensure that the docs for the modules are correct. There are startup 
> script changes as well as config changes.



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

[jira] [Updated] (GEODE-1256) Geode website - Unapproved licenses

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1256:

Sprint: 1.0.0-incubating.M3

> Geode website - Unapproved licenses
> ---
>
> Key: GEODE-1256
> URL: https://issues.apache.org/jira/browse/GEODE-1256
> Project: Geode
>  Issue Type: Improvement
>  Components: web-content
>Reporter: Dave Barnes
>Priority: Minor
> Fix For: 1.0.0-incubating.M3
>
>
> A Geode build (on develop/M3) produces a list of 10 website files with 
> unapproved licenses:
> *
> Summary
> ---
> Generated at: 2016-04-19T09:38:24-07:00
> Notes: 11
> Binaries: 10
> Archives: 1
> Standards: 5974
> Apache Licensed: 5921
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 10 Unknown Licenses
> ***
> Unapproved licenses:
>   
> /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat-extensions.css
>   
> /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat-square.css
>   /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat.css
>   
> /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/font-awesome.min.css
>   
> /Users/dbarnes/Repo/incubator-geode/geode-site/content/font/fontawesome-webfont-svg.svg
>   /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/head.js
>   /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/html5shiv.js
>   
> /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/jquery-1.10.1.min.js
>   /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/jquery.icheck.js
>   /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/respond.min.js



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

[jira] [Updated] (GEODE-1146) CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1146:

Sprint: 1.0.0-incubating.M3

> CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients
> --
>
> Key: GEODE-1146
> URL: https://issues.apache.org/jira/browse/GEODE-1146
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Jianxia Chen
>Assignee: Udo Kohlmeyer
>  Labels: CI, Flaky
> Fix For: 1.0.0-incubating.M3
>
>
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2082/testReport/com.gemstone.gemfire.cache.query.dunit/QueryUsingPoolDUnitTest/testBindParamsWithMulitipleClients/
> 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 1143688
> [fatal 2016/03/29 22:31:26.669 PDT  tid=0xc63] 
> Membership service failure: Member isn't responding to heartbeat requests
> com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to 
> heartbeat requests
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2586)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:885)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:578)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1542)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1089)
>   at org.jgroups.JChannel.invokeCallback(JChannel.java:817)
>   at org.jgroups.JChannel.up(JChannel.java:741)
>   at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
>   at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
>   at org.jgroups.protocols.FlowControl.up(FlowControl.java:392)
>   at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064)
>   at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779)
>   at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:71)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:75)
>   at org.jgroups.protocols.TP.passMessageUp(TP.java:1590)
>   at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802)
>   at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
>   at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1718)
>   at org.jgroups.protocols.TP.receive(TP.java:1643)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160)
>   at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
>   at java.lang.Thread.run(Thread.java:745)



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

[jira] [Updated] (GEODE-1203) gfsh connect --use-http reports a ClassNotFoundException

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1203:

Sprint: 1.0.0-incubating.M3

> gfsh connect --use-http reports a ClassNotFoundException
> 
>
> Key: GEODE-1203
> URL: https://issues.apache.org/jira/browse/GEODE-1203
> Project: Geode
>  Issue Type: Bug
>  Components: rest (admin)
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> Connecting with the admin REST API is now broken. I think it's because the 
> spring-web jar is no longer placed in the lib directory or added to the 
> gfsh-deps.jar. In geode-assembly/build.gradle, the gfshDepsJars tries to add 
> spring-web to the classpath, but it is not actually part of the runtime 
> configuration so this expression evaluates to null
> {code}
>   def springWeb = configurations.runtime.collect { it.getName() }.find { 
> it.contains('spring-web') }
> {code}
> {noformat}
> gfsh>connect --use-http  --url=http://localhost:7070/gemfire/v1
> Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError: 
> org/springframework/http/client/ClientHttpRequestFactory
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.ShellCommands.connect(ShellCommands.java:214)
>   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.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
>   at 
> com.gemstone.gemfire.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:110)
>   at 
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127)
>   at 
> com.gemstone.gemfire.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:891)
>   at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> org.springframework.http.client.ClientHttpRequestFactory
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   ... 11 more
> Exception in thread "main" java.lang.NullPointerException
>   at 
> com.gemstone.gemfire.management.internal.cli.Launcher.parseOptions(Launcher.java:235)
>   at 
> com.gemstone.gemfire.management.internal.cli.Launcher.parseCommandLine(Launcher.java:243)
>   at 
> com.gemstone.gemfire.management.internal.cli.Launcher.main(Launcher.java:95)
> {noformat}



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

[jira] [Updated] (GEODE-1267) NOTICE file improvements

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1267:

Sprint: 1.0.0-incubating.M3

> NOTICE file improvements
> 
>
> Key: GEODE-1267
> URL: https://issues.apache.org/jira/browse/GEODE-1267
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Minor
> Fix For: 1.0.0-incubating.M3
>
>
> See 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201604.mbox/%3c06448bb1-9eac-48c5-9f63-41f09ecfc...@classsoftware.com%3e
> The following changes are suggested:
> 1) Simplify the included Spring NOTICE's to included what's required.  For 
> example:
> {noformat}
> This product includes software developed by the Spring LDAP Project 
> (http://www.springframework.org/ldap).
> {noformat}
> 2) Remove name/copyright of bundled ASF projects from NOTICE.  There are 
> conflicting viewpoints on this one.  We should try to get a consensus from 
> the general@ list and follow their recommendation.  
> We should also update the license wiki:  
> https://cwiki.apache.org/confluence/display/GEODE/License+Guide+for+Contributors
> Affected files:
> * ./geode-assembly/src/main/dist/NOTICE
> * ./geode-pulse/src/main/webapp/META-INF/NOTICE
> * ./geode-web/src/main/webapp/META-INF/NOTICE
> * ./geode-web-api/src/main/webapp/META-INF/NOTICE
> * ./NOTICE



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

[jira] [Updated] (GEODE-1331) gfsh.bat on Windows is incorrect

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1331:

Sprint: 1.0.0-incubating.M3

> gfsh.bat on Windows is incorrect
> 
>
> Key: GEODE-1331
> URL: https://issues.apache.org/jira/browse/GEODE-1331
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
> Fix For: 1.0.0-incubating.M3
>
>
> Initial report:
> {quote}
> I am doing testing in windows STS. I am not adding these dependencies jars, 
> gfsh.bat is what doing this.
>  
> C:\DEV\Pivotal\GemFire_v82014\bin\gfsh.bat has below code, which is setting 
> gemfire, antlr, gfsh-dependencies and pulse-dependencies jars in classpath.
> Line 26 to 29
> @set 
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> @if defined CLASSPATH (
> @set GEMFIRE_JARS=%GEMFIRE_JARS%;%CLASSPATH%
> )
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\antlr.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\pulse-dependencies.jar
>  
> Unix C:\DEV\Pivotal\GemFire_v82014\bin script, does not set these jars in 
> classpath.
>  
>  
> Another observation is that, if I pass --include-system-classpath to gfsh 
> start server command, then it is prepending gemfire.jar and 
> gfsh-dependencies.jar to the system classpath and adding that to the server, 
> that is what is shown in logs
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar
> 
> ………..
> C:\Program Files\Java\jdk1.7.0_67\lib\tools.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>  
> start server \
> --name=${NAME} --server-port=${PORT} \
> --properties-file=${GEMFIRE_PWD}/resources/cache.properties \
> --J=-Dgemfire.distributed-system-id=${DISTRIBUTED_SYSTEM_ID} \
> --J=-Dgemfire.bind-address=${HOST_NAME} 
> --J=-Dgemfire.server-bind-address=${HOST_NAME} \
> --J=-Dgemfire.locators=${HOST_NAME}[${LOCATOR_PORT}] \
> --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true \
> --include-system-classpath
>  
> If I don’t pass this parameter, then it does not add gfsh-dependencies
>   Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>  
> I am trying to do testing without using –include-system-classpath instead add 
> jars in to the start server –classpath as a work around.
> {quote}
> And a subsequent reply from John Blum:
> {quote}
> My apologies.  I was not aware that you were launching your GemFire process 
> (e.g. Server) using Gfsh, and specifically with gfsh.bat on Windows.
> I just confirmed the line(s) you were looking at in gfsh.bat, and indeed the 
> BAT file is wrong!  Specifically, the classpath for the GemFire process is 
> being constructed from the following lines...
> @set 
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> ...
> @set GFSH_JARS=;%GEMFIRE%\lib\gfsh-dependencies.jar
> @set CLASSPATH=%GFSH_JARS%;%GEMFIRE_JARS%
> The Windows BAT file is also inconsistent with the Bash shell version (gfsh), 
> which rightfully only contains...
> GEMFIRE_JARS=$GEMFIRE/lib/gfsh-dependencies.jar
> if [ "x$CLASSPATH" != "x" ]; then
>   GEMFIRE_JARS=$GEMFIRE_JARS:$CLASSPATH
> fi
> CLASSPATH=$GEMFIRE_JARS
> In addition, the Bash shell version launches the Gfsh process using the java 
> -classpath option...
> "$GF_JAVA" -Dgfsh=true 
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
>  ${JLINE_TERMINAL} -classpath "${CLASSPATH}" $JAVA_ARGS $LAUNCHER  "$@"
> Which does not "export", or rather, set the global System CLASSPATH 
> environment variable.  Here it is only setting the Java System property to 
> the Java process, where as, I believe, the Window BAT file is actually 
> setting the System CLASSPATH environment variable, since there is no java 
> -classpath option present in the command to launch Gfsh...
> @"%GF_JAVA%" -Dgfsh=true 
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
>  %JAVA_ARGS% %LAUNCHER% %*
> Regarding...
> > I think we need Pivotal Engineering team to look into gfsh.bat and 
> > –include-system-classpath behavior.
> Not exactly.  --include-system-classpath basically functions such that it 
> appends the value of the System CLASSPATH environment variable to the forked 
> GemFire process launched from Gfsh if the user has set the global variable 
> per environment and wishes to use it.
> In a nutshell, GemFire documentation use to erroneously recommend users to 
> set the System CLASSPATH 

[jira] [Updated] (GEODE-818) Clean up the dependencies of geode-core by moving non-core features to subprojects

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-818:
---
Sprint:   (was: 1.0.0-incubating.M3)

> Clean up the dependencies of geode-core by moving non-core features to 
> subprojects
> --
>
> Key: GEODE-818
> URL: https://issues.apache.org/jira/browse/GEODE-818
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>Assignee: Dan Smith
>
> Maven and POM dependencies are too many for simple
> From [~niall.pember...@btinternet.com]:
> If I'm building a gemfire client and depend on gemfire-core, do I really need 
> all those dependencies? Do I always need them for a gemfire member? Looks to 
> me like some of them should be "optional" or "provided" - especially some of 
> the logging stuff.
> * Spring Framework only referenced in CLI & Web, except XmlEntity (uses 
> org.springframework.util.Assert) and PdxInstanceImpl (uses 
> org.springframework.util.StringUtils)
> * SequenceFile only class to directly reference commons-logging
> * commons-lang only used in hdfs & CLI
> * javax.mail only used in MailManager
> * Jetty only referenced by ManagementAgent & RestAgent, except for 
> CumulativeNonDistinctResults
> * Netty only referenced in the redis package
> * Can't find any reference to slf4j



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

[jira] [Updated] (GEODE-1) Graduate from Apache Incubator and achieve the status of the TLP project

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1:
-
Sprint:   (was: 1.0.0-incubating.M3)

> Graduate from Apache Incubator and achieve the status of the TLP project
> 
>
> Key: GEODE-1
> URL: https://issues.apache.org/jira/browse/GEODE-1
> Project: Geode
>  Issue Type: Wish
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: William Markito Oliveira
>   Original Estimate: 8,736h
>  Remaining Estimate: 8,736h
>
> While achieving the level of maturity required to graduate to the status of 
> the TLP project we might as well take care of world domination while we are 
> at it. After all, it may be possible to do to RAM what HDFS has done to disk 
> and Geode may very well be the thing that does it!



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

[jira] [Updated] (GEODE-828) Callbacks required to implement Declarable during restart

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-828:
---
Sprint:   (was: 1.0.0-incubating.M3)

> Callbacks required to implement Declarable during restart
> -
>
> Key: GEODE-828
> URL: https://issues.apache.org/jira/browse/GEODE-828
> Project: Geode
>  Issue Type: Bug
>  Components: general, tools
>Reporter: William Markito Oliveira
>
> When callbacks get created without implementing {code}Declarable{code} the 
> cluster config seems to be writing them to cache.xml and them requiring that 
> in order to restart the cluster.



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

[jira] [Updated] (GEODE-37) Package renaming

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-37:
--
Sprint:   (was: 1.0.0-incubating.M3)

> Package renaming
> 
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Priority: Blocker
> Fix For: 2.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-818) Clean up the dependencies of geode-core by moving non-core features to subprojects

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-818:
---
Sprint: 1.0.0-incubating.M3

> Clean up the dependencies of geode-core by moving non-core features to 
> subprojects
> --
>
> Key: GEODE-818
> URL: https://issues.apache.org/jira/browse/GEODE-818
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>Assignee: Dan Smith
>
> Maven and POM dependencies are too many for simple
> From [~niall.pember...@btinternet.com]:
> If I'm building a gemfire client and depend on gemfire-core, do I really need 
> all those dependencies? Do I always need them for a gemfire member? Looks to 
> me like some of them should be "optional" or "provided" - especially some of 
> the logging stuff.
> * Spring Framework only referenced in CLI & Web, except XmlEntity (uses 
> org.springframework.util.Assert) and PdxInstanceImpl (uses 
> org.springframework.util.StringUtils)
> * SequenceFile only class to directly reference commons-logging
> * commons-lang only used in hdfs & CLI
> * javax.mail only used in MailManager
> * Jetty only referenced by ManagementAgent & RestAgent, except for 
> CumulativeNonDistinctResults
> * Netty only referenced in the redis package
> * Can't find any reference to slf4j



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

[jira] [Updated] (GEODE-37) Package renaming

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-37:
--
Sprint: 1.0.0-incubating.M3

> Package renaming
> 
>
> Key: GEODE-37
> URL: https://issues.apache.org/jira/browse/GEODE-37
> Project: Geode
>  Issue Type: Task
>  Components: docs, general
>Affects Versions: 1.0.0-incubating
>Reporter: William Markito Oliveira
>Priority: Blocker
> Fix For: 2.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-1) Graduate from Apache Incubator and achieve the status of the TLP project

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1:
-
Sprint: 1.0.0-incubating.M3

> Graduate from Apache Incubator and achieve the status of the TLP project
> 
>
> Key: GEODE-1
> URL: https://issues.apache.org/jira/browse/GEODE-1
> Project: Geode
>  Issue Type: Wish
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Roman Shaposhnik
>Assignee: William Markito Oliveira
>   Original Estimate: 8,736h
>  Remaining Estimate: 8,736h
>
> While achieving the level of maturity required to graduate to the status of 
> the TLP project we might as well take care of world domination while we are 
> at it. After all, it may be possible to do to RAM what HDFS has done to disk 
> and Geode may very well be the thing that does it!



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

[jira] [Updated] (GEODE-914) Review NOTICE (again)

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-914:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Review NOTICE (again)
> -
>
> Key: GEODE-914
> URL: https://issues.apache.org/jira/browse/GEODE-914
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> Thanks to great feedback from IPMC on the general@ list we have a better idea 
> of how to construct the NOTICE file.  Please review the following threads and 
> linked docs:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c7ac725d7-ecec-45ff-95ae-bd77d1b18...@pivotal.io%3e
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e
> https://nifi.apache.org/licensing-guide.html



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

[jira] [Updated] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-946:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and 
> not in {{libs/extensions}}.



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

[jira] [Updated] (GEODE-627) Generate source artifacts from gradle build

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-627:
---
Sprint: 1.0.0-incubating.M3

> Generate source artifacts from gradle build
> ---
>
> Key: GEODE-627
> URL: https://issues.apache.org/jira/browse/GEODE-627
> Project: Geode
>  Issue Type: Task
>Reporter: Nitin Lamba
>Assignee: Anthony Baker
>Priority: Critical
> Fix For: 1.0.0-incubating.M1
>
>
> The current gradle build generated in 'gemfire-assembly' does not include 
> source artifacts. As part of the release process, source distribution task 
> needs to be added.
> Suggested by  Niall Pemberton  on Dec/02/2015. 



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

[jira] [Updated] (GEODE-18) Initial Code Cleanup

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-18:
--
Sprint: 1.0.0-incubating.M3

> Initial Code Cleanup
> 
>
> Key: GEODE-18
> URL: https://issues.apache.org/jira/browse/GEODE-18
> Project: Geode
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Niall Pemberton
>Assignee: Dick Cavender
> Fix For: 1.0.0-incubating.M1
>
> Attachments: 
> 0001-Replace-Pivotal-License-Header-with-Apache-License.patch, 
> 0002-Add-Missing-Apache-License-headers.patch, 
> 0003-Remove-Pivotal-VMWare-AsIs-License-and-add-ASF-Licen.patch, 
> 0004-Add-ASF-License-Header-to-scala-files.patch, 
> 0005-Add-ASF-License-Header-to-XML-files.patch, 
> 0006-Add-ASF-License-Header-to-DTD-XSD-files.patch, 
> 0007-Add-ASF-License-Header-to-HTML-files.patch, 
> 0008-Change-Swagger-ApiInfo-from-Pivotal-Gemfire-to-Apach.patch, 
> 0009-Add-Update-ASF-License-to-java-files.patch, 
> 0010-Add-ASF-License-to-html-xml-xsd-dtd-files.patch, 
> geode-rat-excludes-2015-10-19.txt, geode-rat-excludes-2015-10-24.txt, 
> geode-rat-excludes-2015-11-22.txt, geode-rat-report-2015-05-11.txt, 
> geode-rat-report-2015-05-17.txt, geode-rat-report-2015-10-19.txt, 
> geode-rat-report-2015-10-24.txt, geode-rat-report-2015-11-17.txt, 
> geode-rat-report-2015-11-22.txt
>
>
> Please see the Incubator guide:
> * http://incubator.apache.org/guides/mentor.html#initial-clean-up
> Source & Notice File policy:
> * http://www.apache.org/legal/src-headers.html
> Apache RAT is a tool that can help with source file headers:
>  * http://creadur.apache.org/rat/



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

[jira] [Updated] (GEODE-944) ServerLauncherJUnitTest fails when ISP redirects DNS failures

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-944:
---
Sprint:   (was: 1.0.0-incubating.M2)

> ServerLauncherJUnitTest fails when ISP redirects DNS failures
> -
>
> Key: GEODE-944
> URL: https://issues.apache.org/jira/browse/GEODE-944
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Dan Smith
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails when using a DNS server that redirects DNS lookup failures to 
> an ISP's search page. 
> {noformat}
> om.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> {noformat}
> The test is expecting to see an UnknownHostException, but because the ISP 
> returns a real IP address rather than the expected DNS lookup failure, the 
> test doesn't see the exception.
> We could probably just Use junit's Assume to cause these tests to get skipped 
> in this environment.
> See this email thread for more details:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAOqetn_FTeV9ee4R8mkg4Y%3D8a%3DjedgfdOSjDxcnj2N7W02maCw%40mail.gmail.com%3E
> A little more information on DNS hijacking:
> http://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/



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

[jira] [Updated] (GEODE-903) Update copyright year in website footer

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-903:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Update copyright year in website footer
> ---
>
> Key: GEODE-903
> URL: https://issues.apache.org/jira/browse/GEODE-903
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> The publication year in the copyright notice should be updated to 2016:
> gemfire-site/website/layouts/footer.html



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

[jira] [Updated] (GEODE-1025) Remove compile dependency on spring data gemfire/geode

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-1025:

Sprint: 1.0.0-incubating.M3

> Remove compile dependency on spring data gemfire/geode
> --
>
> Key: GEODE-1025
> URL: https://issues.apache.org/jira/browse/GEODE-1025
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> We have a compile dependency on spring data gemfire in the ServerLauncher 
> class to support launching a server using a spring data gemfire configuration 
> instead of a cache.xml file.
> That's a good feature to have, but it should be part of spring data gemfire, 
> not geode. Because of this compile dependency on SDG, we currently have a 
> circular dependency on SDG -> Geode -> SDG. That makes it difficult to do 
> things like rename packages in geode (GEODE-37) because SDG is still using 
> the old packages.
> Instead of directly depending on spring data gemfire, we should provide an 
> extension point that SDG can plug into to override the cache server startup 
> behavior.
> The easiest place way to do this is just to use the java ServiceLoader 
> mechanism. We can provide an interface for a plugin that replaces startup 
> behavior of the server. SDG can provide an implementation of this interface.



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

[jira] [Updated] (GEODE-906) Clean up source header / modification text

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-906:
---
Sprint: 1.0.0-incubating.M3

> Clean up source header / modification text
> --
>
> Key: GEODE-906
> URL: https://issues.apache.org/jira/browse/GEODE-906
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> IdentityArrayList and HashIndexSet should use the standard Apache source 
> header with a separate modification statement for clarity [1].
> [1] http://www.apache.org/dev/licensing-howto.html#mod-notice
> May be required to add to source NOTICE.



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

[jira] [Updated] (GEODE-906) Clean up source header / modification text

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-906:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Clean up source header / modification text
> --
>
> Key: GEODE-906
> URL: https://issues.apache.org/jira/browse/GEODE-906
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> IdentityArrayList and HashIndexSet should use the standard Apache source 
> header with a separate modification statement for clarity [1].
> [1] http://www.apache.org/dev/licensing-howto.html#mod-notice
> May be required to add to source NOTICE.



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

[jira] [Updated] (GEODE-608) Integrate RAT into build

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-608:
---
Sprint: 1.0.0-incubating.M3

> Integrate RAT into build
> 
>
> Key: GEODE-608
> URL: https://issues.apache.org/jira/browse/GEODE-608
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.0.0-incubating
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
>
> We need to ensure license requirements are met.  See discussion at 
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/%3cCA+ULb+uLyB9_3QSA+qk5UZ5E8idXdCd=1z+9zr9y2c6n1vo...@mail.gmail.com%3e
> Gradle plugin available at
> https://plugins.gradle.org/plugin/org.nosphere.apache.rat



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

[jira] [Updated] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-26:
--
Sprint:   (was: 1.0.0-incubating.M2)

> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in 
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
>  Labels: ApacheGeode, Gradle, Repositories, build.gradle, 
> mavenLocal()
> Fix For: 1.0.0-incubating.M2
>
>
> In the 
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
>  file of the _Apache Geode_ project, the {{repositories}} declaration 
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache 
> Geode_ codebase inadvertently include a "local" dependency to the 
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will 
> build locally but not when the patch is submitted and Geode's build 
> infrastructure runs the same build with the code changes dependent on the 
> (possibly) non-existent, non-resolvable dependency, because, it only exists 
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of 
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without 
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to 
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
>   repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
>   }
> }
> {code}
> See the [Gradle documentation on 
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for 
> more details.



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

[jira] [Updated] (GEODE-608) Integrate RAT into build

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-608:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Integrate RAT into build
> 
>
> Key: GEODE-608
> URL: https://issues.apache.org/jira/browse/GEODE-608
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.0.0-incubating
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
>
> We need to ensure license requirements are met.  See discussion at 
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/%3cCA+ULb+uLyB9_3QSA+qk5UZ5E8idXdCd=1z+9zr9y2c6n1vo...@mail.gmail.com%3e
> Gradle plugin available at
> https://plugins.gradle.org/plugin/org.nosphere.apache.rat



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

[jira] [Updated] (GEODE-904) Update LICENSE for BSD/MIT dependencies

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-904:
---
Sprint: 1.0.0-incubating.M3

> Update LICENSE for BSD/MIT dependencies
> ---
>
> Key: GEODE-904
> URL: https://issues.apache.org/jira/browse/GEODE-904
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> The following files need to be listed in the LICENSE:
> {noformat}
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf 
> that should be in license
> 1. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> {noformat}



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

[jira] [Updated] (GEODE-991) LuceneFunction is not marked as an internal function

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-991:
---
Sprint:   (was: 1.0.0-incubating.M2)

> LuceneFunction is not marked as an internal function
> 
>
> Key: GEODE-991
> URL: https://issues.apache.org/jira/browse/GEODE-991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> LuceneFunction shows up in the output of list functions from gfsh. It should 
> extend the InternalEntity marker interface.



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

[jira] [Updated] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-26:
--
Sprint: 1.0.0-incubating.M3

> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in 
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
>  Labels: ApacheGeode, Gradle, Repositories, build.gradle, 
> mavenLocal()
> Fix For: 1.0.0-incubating.M2
>
>
> In the 
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
>  file of the _Apache Geode_ project, the {{repositories}} declaration 
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache 
> Geode_ codebase inadvertently include a "local" dependency to the 
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will 
> build locally but not when the patch is submitted and Geode's build 
> infrastructure runs the same build with the code changes dependent on the 
> (possibly) non-existent, non-resolvable dependency, because, it only exists 
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of 
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without 
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to 
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
>   repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
>   }
> }
> {code}
> See the [Gradle documentation on 
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for 
> more details.



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

[jira] [Updated] (GEODE-835) Replace joptsimple source with a binary dependency

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-835:
---
Sprint: 1.0.0-incubating.M3

> 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] [Updated] (GEODE-77) Replace JGroups 2.2.9

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-77:
--
Sprint:   (was: 1.0.0-incubating.M2)

> Replace JGroups 2.2.9
> -
>
> Key: GEODE-77
> URL: https://issues.apache.org/jira/browse/GEODE-77
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Blocker
> Fix For: 1.0.0-incubating.M1
>
> Attachments: 
> GEODE-MembershipManagerFunctionalSpecification-130715-1604-29054.pdf
>
>
> The JGroups 2.2.9 sources that are currently included in Geode must be 
> replaced in order for Geode to leave incubation.  A wiki document has been 
> created to investigate alternatives.
> https://cwiki.apache.org/confluence/display/GEODE/Replacing+JGroups+2.2.9



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

[jira] [Updated] (GEODE-610) Review Geode's LICENSE & NOTICE File(s)

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-610:
---
Sprint: 1.0.0-incubating.M3

> Review Geode's LICENSE & NOTICE File(s)
> ---
>
> Key: GEODE-610
> URL: https://issues.apache.org/jira/browse/GEODE-610
> Project: Geode
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Niall Pemberton
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
> Attachments: Geode-Dependency-License-Review-2015-11-28.csv, 
> Geode-Source-License-Review-2015-11-28.csv, NOTICE, NOTICE-2, NOTICE-3.txt, 
> netty-4.0.33.Final-NOTICE.txt, spring-core-3.2.12.RELEASE-notice.txt
>
>
> Need to review Geode's LICENSE & NOTICE File(s).
> Guide on these files is available here:
>   - http://www.apache.org/dev/licensing-howto.html



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

[jira] [Updated] (GEODE-562) Upgrade commons collections to v3.2.2

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-562:
---
Sprint: 1.0.0-incubating.M3

> Upgrade commons collections to v3.2.2
> -
>
> Key: GEODE-562
> URL: https://issues.apache.org/jira/browse/GEODE-562
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Jason Huynh
> Fix For: 1.0.0-incubating.M2
>
>
> The commons-collections jar v3.2.1 is present on the classpath as part of the 
> hdfs integration (see GEODE-10).  We need to upgrade to version 3.2.2 due to 
> COLLECTIONS-580.



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

[jira] [Updated] (GEODE-914) Review NOTICE (again)

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-914:
---
Sprint: 1.0.0-incubating.M3

> Review NOTICE (again)
> -
>
> Key: GEODE-914
> URL: https://issues.apache.org/jira/browse/GEODE-914
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> Thanks to great feedback from IPMC on the general@ list we have a better idea 
> of how to construct the NOTICE file.  Please review the following threads and 
> linked docs:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c7ac725d7-ecec-45ff-95ae-bd77d1b18...@pivotal.io%3e
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e
> https://nifi.apache.org/licensing-guide.html



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

[jira] [Updated] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-946:
---
Sprint: 1.0.0-incubating.M3

> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and 
> not in {{libs/extensions}}.



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

[jira] [Updated] (GEODE-12) Merge Pulse Source Code

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-12:
--
Sprint: 1.0.0-incubating.M3

> Merge Pulse Source Code
> ---
>
> Key: GEODE-12
> URL: https://issues.apache.org/jira/browse/GEODE-12
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Dan Smith
>Assignee: Jinmei Liao
>  Labels: starter
> Fix For: 1.0.0-incubating.M2
>
>
> Pulse is a web application for monitoring a Geode cluster. Pivotal would like 
> to contribute pulse to the Geode project. 



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

[jira] [Updated] (GEODE-902) Remove Apache header from MX4JModelMBean.java

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-902:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Remove Apache header from MX4JModelMBean.java
> -
>
> Key: GEODE-902
> URL: https://issues.apache.org/jira/browse/GEODE-902
> Project: Geode
>  Issue Type: Bug
>  Components: jmx
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> MX4JModelMBean.java has an Apache header but should not as it is under the 
> MX4J license.  Also, we need to handle this appropriately in LICENSE / NOTICE.
> See http://mx4j.sourceforge.net/docs/ch01s06.html.
> Discussion thread:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3ca44698bc-a87b-48e5-bdf2-29c1a1814...@classsoftware.com%3e



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

[jira] [Updated] (GEODE-18) Initial Code Cleanup

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-18:
--
Sprint:   (was: 1.0.0-incubating.M2)

> Initial Code Cleanup
> 
>
> Key: GEODE-18
> URL: https://issues.apache.org/jira/browse/GEODE-18
> Project: Geode
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.0.0-incubating
>Reporter: Niall Pemberton
>Assignee: Dick Cavender
> Fix For: 1.0.0-incubating.M1
>
> Attachments: 
> 0001-Replace-Pivotal-License-Header-with-Apache-License.patch, 
> 0002-Add-Missing-Apache-License-headers.patch, 
> 0003-Remove-Pivotal-VMWare-AsIs-License-and-add-ASF-Licen.patch, 
> 0004-Add-ASF-License-Header-to-scala-files.patch, 
> 0005-Add-ASF-License-Header-to-XML-files.patch, 
> 0006-Add-ASF-License-Header-to-DTD-XSD-files.patch, 
> 0007-Add-ASF-License-Header-to-HTML-files.patch, 
> 0008-Change-Swagger-ApiInfo-from-Pivotal-Gemfire-to-Apach.patch, 
> 0009-Add-Update-ASF-License-to-java-files.patch, 
> 0010-Add-ASF-License-to-html-xml-xsd-dtd-files.patch, 
> geode-rat-excludes-2015-10-19.txt, geode-rat-excludes-2015-10-24.txt, 
> geode-rat-excludes-2015-11-22.txt, geode-rat-report-2015-05-11.txt, 
> geode-rat-report-2015-05-17.txt, geode-rat-report-2015-10-19.txt, 
> geode-rat-report-2015-10-24.txt, geode-rat-report-2015-11-17.txt, 
> geode-rat-report-2015-11-22.txt
>
>
> Please see the Incubator guide:
> * http://incubator.apache.org/guides/mentor.html#initial-clean-up
> Source & Notice File policy:
> * http://www.apache.org/legal/src-headers.html
> Apache RAT is a tool that can help with source file headers:
>  * http://creadur.apache.org/rat/



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

[jira] [Updated] (GEODE-562) Upgrade commons collections to v3.2.2

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-562:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Upgrade commons collections to v3.2.2
> -
>
> Key: GEODE-562
> URL: https://issues.apache.org/jira/browse/GEODE-562
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Jason Huynh
> Fix For: 1.0.0-incubating.M2
>
>
> The commons-collections jar v3.2.1 is present on the classpath as part of the 
> hdfs integration (see GEODE-10).  We need to upgrade to version 3.2.2 due to 
> COLLECTIONS-580.



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

[jira] [Updated] (GEODE-386) Change xsd namespace to apache

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-386:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Change xsd namespace to apache
> --
>
> Key: GEODE-386
> URL: https://issues.apache.org/jira/browse/GEODE-386
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, docs
>Reporter: Dan Smith
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The format cache.xml file for geode is currently specified by a xsd called 
> cache-9.0.xsd. This xsd has a pivotal.io namespace. It should have an apache 
> namespace and be hosted on apache infastructure.
> {code:xml}
>  targetNamespace="http://schema.pivotal.io/gemfire/cache;
> xmlns:gf="http://schema.pivotal.io/gemfire/cache;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema;
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> version="9.0">
>   
> {code}



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

[jira] [Updated] (GEODE-776) Add public KEYS to Apache Geode repo.

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-776:
---
Sprint: 1.0.0-incubating.M3

> Add public KEYS to Apache Geode repo.
> -
>
> Key: GEODE-776
> URL: https://issues.apache.org/jira/browse/GEODE-776
> Project: Geode
>  Issue Type: Task
>Reporter: Nitin Lamba
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
> Attachments: KEYS, KEYS
>
>
> As per release requirement, please comment with your public keys so that a 
> KEYS file can be created in the repo. Few references below:
> http://www.apache.org/dist/ant/KEYS
> https://dist.apache.org/repos/dist/release/bigtop/KEYS



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

[jira] [Updated] (GEODE-907) Remove JSON code from pulse

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-907:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Remove JSON code from pulse
> ---
>
> Key: GEODE-907
> URL: https://issues.apache.org/jira/browse/GEODE-907
> Project: Geode
>  Issue Type: Improvement
>  Components: management
>Reporter: Anthony Baker
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The com.vmware.gemfire.tools.pulse.internal.json package contains the JSON 
> parser source.  We should remove this code in favor of a binary dependency.



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

[jira] [Updated] (GEODE-905) HLL classes should preserve original source header

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-905:
---
Sprint:   (was: 1.0.0-incubating.M2)

> HLL classes should preserve original source header
> --
>
> Key: GEODE-905
> URL: https://issues.apache.org/jira/browse/GEODE-905
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Swapnil Bawaskar
> Fix For: 1.0.0-incubating.M2
>
>
> Classes in the 
> gemfire-core/src/main/java/com/gemstone/gemfire/internal/redis/executor/hll/*.java
>  package have 2 source headers.  We should preserve the original header and 
> remove the extra.  We should also explore if we need to add anything to the 
> LICENSE or NOTICE for this bundled source dependency.



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

[jira] [Updated] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-815:
---
Sprint: 1.0.0-incubating.M3

> RC Feedback: Fix LICENSE and NOTICE files
> -
>
> Key: GEODE-815
> URL: https://issues.apache.org/jira/browse/GEODE-815
> Project: Geode
>  Issue Type: Task
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M1
>
>




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

[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-824:
---
Sprint: 1.0.0-incubating.M3

> Failure from JGroupsMessengerJUnitTest.testMulticastTest
> 
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
>  Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
>  Labels: ci
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this 
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}



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

[jira] [Updated] (GEODE-52) Remove @author tags from Java source

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-52:
--
Sprint: 1.0.0-incubating.M3

> Remove @author tags from Java source
> 
>
> Key: GEODE-52
> URL: https://issues.apache.org/jira/browse/GEODE-52
> Project: Geode
>  Issue Type: Bug
>Reporter: Jakob Homan
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> Apache generally frowns on @author tags (as they imply ownership of the code 
> by a single individual, see 
> https://blogs.oracle.com/ahe/entry/coding_conventions_and_attribution [best 
> asf link is not working, annoyingly] and 
> https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute as an 
> example)



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

[jira] [Updated] (GEODE-901) Remove invalid source headers

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-901:
---
Sprint: 1.0.0-incubating.M3

> Remove invalid source headers
> -
>
> Key: GEODE-901
> URL: https://issues.apache.org/jira/browse/GEODE-901
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> ResultsBagJUnitTest contains an invalid header that should be removed.
> {code}
> //
> //  ResultsBagJUnitTest.java
> //  gemfire
> //
> //  Created by Eric Zoerner on 2/13/08.
> //  Copyright 2008 __MyCompanyName__. All rights reserved.
> //
> {code}
> Also, QueryFromClauseCanonicalizationJUnitTest.java has this comment which 
> should be removed:
> {code}
>   /*
>* 
>* Copyright (C) GemStone Systems, Inc. 2000-2004. All Rights Reserved.
>* 
>* 
>*/
> {code}



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

[jira] [Updated] (GEODE-874) v1.0.0-incubating.M1.RC2: Text file errors in the source distribution

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-874:
---
Sprint: 1.0.0-incubating.M3

> v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
> -
>
> Key: GEODE-874
> URL: https://issues.apache.org/jira/browse/GEODE-874
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Kenneth Howe
>Assignee: Karen Smoler Miller
> Fix For: 1.0.0-incubating.M2
>
>
> gradlew script is not included in the Geode release packages, but it is 
> called out in command examples in the following text files in the release 
> source distribution:
> COMPILING.txt
> RUNNING.txt
> docker/Dockerfile
> gemfire-spark-connector/doc/1_building.md
> The easy fix is to change "gradlew" to "gradle" in affected files and include 
> a requirement for the user to install gradle from gradle.org.
> There was a similar issue with README.md that was fixed for RC2.



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

[jira] [Updated] (GEODE-33) Create project examples

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-33:
--
Sprint:   (was: 1.0.0-incubating.M2)

> 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] [Updated] (GEODE-902) Remove Apache header from MX4JModelMBean.java

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-902:
---
Sprint: 1.0.0-incubating.M3

> Remove Apache header from MX4JModelMBean.java
> -
>
> Key: GEODE-902
> URL: https://issues.apache.org/jira/browse/GEODE-902
> Project: Geode
>  Issue Type: Bug
>  Components: jmx
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> MX4JModelMBean.java has an Apache header but should not as it is under the 
> MX4J license.  Also, we need to handle this appropriately in LICENSE / NOTICE.
> See http://mx4j.sourceforge.net/docs/ch01s06.html.
> Discussion thread:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3ca44698bc-a87b-48e5-bdf2-29c1a1814...@classsoftware.com%3e



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

[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-824:
---
Sprint:   (was: 1.0.0-incubating.M2)

> Failure from JGroupsMessengerJUnitTest.testMulticastTest
> 
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
>  Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
>  Labels: ci
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this 
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}



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

[jira] [Updated] (GEODE-54) Missing javadocs

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-54:
--
Sprint: 1.0.0-incubating.M3

> Missing javadocs
> 
>
> Key: GEODE-54
> URL: https://issues.apache.org/jira/browse/GEODE-54
> Project: Geode
>  Issue Type: Improvement
>  Components: build, docs, general, web-content
>Reporter: William Markito Oliveira
>Assignee: Dave Barnes
> Fix For: 1.0.0-incubating.M2
>
>
> The current build process is not generating javadocs and once they're 
> generated it's still be defined where to host the pages. 
> Current Geode docs are hosted at http://geode-docs.cfapps.io/ but javadocs 
> can be part of that or be hosted under geode.incubator.apache.org.



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

[jira] [Updated] (GEODE-944) ServerLauncherJUnitTest fails when ISP redirects DNS failures

[William Markito Oliveira (JIRA)]

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

William Markito Oliveira updated GEODE-944:
---
Sprint: 1.0.0-incubating.M3

> ServerLauncherJUnitTest fails when ISP redirects DNS failures
> -
>
> Key: GEODE-944
> URL: https://issues.apache.org/jira/browse/GEODE-944
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Dan Smith
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails when using a DNS server that redirects DNS lookup failures to 
> an ISP's search page. 
> {noformat}
> om.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> {noformat}
> The test is expecting to see an UnknownHostException, but because the ISP 
> returns a real IP address rather than the expected DNS lookup failure, the 
> test doesn't see the exception.
> We could probably just Use junit's Assume to cause these tests to get skipped 
> in this environment.
> See this email thread for more details:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAOqetn_FTeV9ee4R8mkg4Y%3D8a%3DjedgfdOSjDxcnj2N7W02maCw%40mail.gmail.com%3E
> A little more information on DNS hijacking:
> http://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/



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