[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #474 was SUCCESSFUL (with 1679 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #474 was successful (rerun once).
---
This build was rerun by John Blum.
1681 tests in total.

https://build.spring.io/browse/SGF-NAG-474/





--
This message is automatically generated by Atlassian Bamboo

Re: Could not create an instance of org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage .

[Anilkumar Gingade]

There seems to be problem with reading member inet address.

Caused by: java.io.IOException: While reading an InetAddress
Caused by: java.net.UnknownHostException: addr is of illegal length

I will let others to comment on this...Meanwhile do you see this problem on
any other m/c.

-Anil



On Thu, Feb 16, 2017 at 6:08 AM, Avinash Dongre  wrote:

> Hi All,
>
> I am getting following exception in my test.
> My Test has 3 VMs + locator and I am doing some puts/gets and restarting.
> I see following exception when 1 node is shutdown and other node receive
> this message and then node which receive this message never shutdown.
>
> Any clue why this is happening ?
>
> I am running with rel/v1.1.0
>
> Thanks
> Avinash
>
>
>
> [severe 2017/02/16 18:56:14.532 IST   192.168.3.76(31930):32772 shared unordered uid=3 port=41938>
> tid=0x52] Error deserializing message
> org.apache.geode.SerializationException: Could not create an instance
> of  org.apache.geode.distributed.internal.locks.
> DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage
> .
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2492)
> at org.apache.geode.internal.DSFIDFactory.create(
> DSFIDFactory.java:1003)
> at org.apache.geode.internal.InternalDataSerializer.readDSFID(
> InternalDataSerializer.java:2718)
> at org.apache.geode.internal.tcp.Connection.processNIOBuffer(
> Connection.java:3607)
> at org.apache.geode.internal.tcp.Connection.runNioReader(
> Connection.java:1865)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1726)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.geode.SerializationException: Could not create
> an instance of  org.apache.geode.internal.cache.TXId .
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2492)
> at org.apache.geode.internal.cache.TXId.createFromData(TXId.java:109)
> at org.apache.geode.internal.DSFIDFactory.create(
> DSFIDFactory.java:966)
> at org.apache.geode.internal.InternalDataSerializer.basicReadObject(
> InternalDataSerializer.java:2836)
> at org.apache.geode.DataSerializer.readObject(
> DataSerializer.java:2897)
> at org.apache.geode.DataSerializer.readObjectArray(
> DataSerializer.java:1860)
> at org.apache.geode.distributed.internal.locks.
> DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage.fromData(
> DLockRecoverGrantorProcessor.java:355)
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2477)
> ... 6 more
> Caused by: org.apache.geode.SerializationException: Could not create
> an instance of
> org.apache.geode.distributed.internal.membership.InternalDistributedMember
> .
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2492)
> at org.apache.geode.internal.DSFIDFactory.
> readInternalDistributedMember(DSFIDFactory.java:1036)
> at org.apache.geode.internal.cache.TXId.fromData(TXId.java:104)
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2477)
> ... 13 more
> Caused by: java.io.IOException: While reading an InetAddress
> at org.apache.geode.DataSerializer.readInetAddress(
> DataSerializer.java:477)
> at org.apache.geode.distributed.internal.membership.
> InternalDistributedMember.fromDataPre_GFE_9_0_0_0(
> InternalDistributedMember.java:961)
> at org.apache.geode.distributed.internal.membership.
> InternalDistributedMember.fromData(InternalDistributedMember.java:948)
> at org.apache.geode.internal.InternalDataSerializer.invokeFromData(
> InternalDataSerializer.java:2477)
> ... 16 more
> Caused by: java.net.UnknownHostException: addr is of illegal length
> at java.net.InetAddress.getByAddress(InetAddress.java:1042)
> at java.net.InetAddress.getByAddress(InetAddress.java:1439)
> at org.apache.geode.DataSerializer.readInetAddress(
> DataSerializer.java:470)
> ... 19 more
>
> [warning 2017/02/16 18:56:29.520 IST   Connection(1)-127.0.0.1> tid=0x12] 15 seconds have elapsed while
> waiting for replies:  replies from [192.168.3.76(31930):32772]> on
> 192.168.3.76(31924):32771 whose current membership list is:
> [[192.168.3.76(31930):32772,
> 192.168.3.76(31859:locator):32769,
> 192.168.3.76(31924):32771]]
>
> [info 2017/02/16 19:15:45.130 IST  
> tid=0x13] VM is exiting - shutting down distributed system
>
> [info 2017/02/16 19:15:45.198 IST   Processor 2> tid=0x3d] received leave request from
> 192.168.3.76(31859:locator):32769 for
> 192.168.3.76(31859:locator):32769
>
> [info 2017/02/16 19:15:45.198 IST   Processor 2> tid=0x3d] This member is becoming the membership
> coordinator with address 192.168.3.76(31924):32771
>
> [info 2017/02/16 19:15:45.203 IST   Processor 2> tid=0x3d] ViewCreator starting
> on:192.168.3.76(31924):32771
>

[jira] [Commented] (GEODE-2309) Replace or add ASF copyright statements in source.

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode-native/pull/12#discussion_r101671763
  
--- Diff: .ratignore ---
@@ -23,10 +23,12 @@
 
 # expect script
 .*changepasswd$
+.*winrm.cloud-init$
 
 # doxygen
 .*package-list$
 .*testframeworkdox.txt$
+docs
--- End diff --

Hmm.. ok.


> Replace or add ASF copyright statements in source.
> --
>
> Key: GEODE-2309
> URL: https://issues.apache.org/jira/browse/GEODE-2309
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #12: GEODE-2309: Remove or ignore apache-rat flagg...

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/12#discussion_r101671763
  
--- Diff: .ratignore ---
@@ -23,10 +23,12 @@
 
 # expect script
 .*changepasswd$
+.*winrm.cloud-init$
 
 # doxygen
 .*package-list$
 .*testframeworkdox.txt$
+docs
--- End diff --

Hmm.. ok.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (GEODE-2402) CI Failure: LuceneQueriesPeerFixedPRDUnitTest.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate

[Dan Smith (JIRA)]

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

Dan Smith resolved GEODE-2402.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> CI Failure: 
> LuceneQueriesPeerFixedPRDUnitTest.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate
> ---
>
> Key: GEODE-2402
> URL: https://issues.apache.org/jira/browse/GEODE-2402
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.2.0
>
>
> This is with 26325b5ef502b6599e9294be41ad96cbf882ab7f
> {noformat}
> 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 
> org.apache.geode.cache.lucene.LuceneQueriesPRBase.putEntriesAndValidateQueryResults(LuceneQueriesPRBase.java:148)
>   at 
> org.apache.geode.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate(LuceneQueriesPRBase.java:59)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> 

[jira] [Assigned] (GEODE-2402) CI Failure: LuceneQueriesPeerFixedPRDUnitTest.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate

[Dan Smith (JIRA)]

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

Dan Smith reassigned GEODE-2402:


Assignee: Dan Smith

> CI Failure: 
> LuceneQueriesPeerFixedPRDUnitTest.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate
> ---
>
> Key: GEODE-2402
> URL: https://issues.apache.org/jira/browse/GEODE-2402
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.2.0
>
>
> This is with 26325b5ef502b6599e9294be41ad96cbf882ab7f
> {noformat}
> 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 
> org.apache.geode.cache.lucene.LuceneQueriesPRBase.putEntriesAndValidateQueryResults(LuceneQueriesPRBase.java:148)
>   at 
> org.apache.geode.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensOnIndexUpdate(LuceneQueriesPRBase.java:59)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 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.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> 

Re: for discussion: separate website into its own repo

[Anthony Baker]

Yes, please.  Let’s call the repo geode-site.  Use two branches:  master and 
asf-site.  If we can auto-build and push to asf-site that would be awesome.

Anthony

> On Feb 16, 2017, at 4:38 PM, Dan Smith  wrote:
> 
> +1
> 
> I think the current setup is confusing, because the website is supposed to
> include docs that are generated from the last release, but the site
> instructions say the site should be generated from develop. A separate repo
> with a single branch will probably reduce confusion.
> 
> We also need to script the website building and publishing, and ideally
> have the publishing done by a CI system based on commits. It looks like
> some other projects are talking about doing this with jenkins jenkins - see
> INFRA-10722 for example.
> 
> -Dan
> 
> On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller  wrote:
> 
>> I think that the website content that is currently in geode/geode-site
>> ought to be moved to its own repository.  The driving reason for this is
>> that changes to the website occur on a different schedule than code
>> releases.  We often want to add a new committer's name or a new
>> event, and these items are not associated with sw releases. A new website
>> release that comes from the develop branch may have commits that
>> should not yet be made public.
>> 
>> Are there downsides to separating the website content into its own repo?
>> 

Re: for discussion: separate website into its own repo

[Anilkumar Gingade]

+1

On Thu, Feb 16, 2017 at 4:45 PM, Joey McAllister 
wrote:

> +1 to Karen's suggestion of moving the website to its own repo.
>
> +1 to Dan's suggestion scripting the website build/publishing with a CI
> system based on commits.
>
> On Thu, Feb 16, 2017 at 4:38 PM Dan Smith  wrote:
>
> > +1
> >
> > I think the current setup is confusing, because the website is supposed
> to
> > include docs that are generated from the last release, but the site
> > instructions say the site should be generated from develop. A separate
> repo
> > with a single branch will probably reduce confusion.
> >
> > We also need to script the website building and publishing, and ideally
> > have the publishing done by a CI system based on commits. It looks like
> > some other projects are talking about doing this with jenkins jenkins -
> see
> > INFRA-10722 for example.
> >
> > -Dan
> >
> > On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller 
> wrote:
> >
> > > I think that the website content that is currently in geode/geode-site
> > > ought to be moved to its own repository.  The driving reason for this
> is
> > > that changes to the website occur on a different schedule than code
> > > releases.  We often want to add a new committer's name or a new
> > > event, and these items are not associated with sw releases. A new
> website
> > > release that comes from the develop branch may have commits that
> > > should not yet be made public.
> > >
> > > Are there downsides to separating the website content into its own
> repo?
> > >
> >
>

Re: Another way to write a DUnit Test

[Anilkumar Gingade]

Its used in LuceneClusterConfigurationDUnitTest

-Anil.


On Thu, Feb 16, 2017 at 4:40 PM, Jinmei Liao  wrote:

> It seems there is no usage of this LocatorServerConfigurationRule. It does
> look like a duplicate.
>
> On Thu, Feb 16, 2017 at 4:37 PM, Anilkumar Gingade 
> wrote:
>
> > I had similar rule added for locator startup...where you can start
> locator
> > by passing required properties.
> > Look for: LocatorServerConfigurationRule (we can remove this, instead of
> > having duplicate rules)
> >
> > -Anil.
> >
> >
> >
> >
> > On Thu, Feb 16, 2017 at 2:26 PM, Jinmei Liao  wrote:
> >
> > > We've created a few JUnit rules to ease the pain of starting up
> > > locator/servers in different vms. Please check these rules out:
> > >
> > > LocatorServerStartupRule:
> > > this rule will allow you to easily start up locator/server in a give VM
> > > with the properties you would like to configure them, and get the
> > member's
> > > name, port, working directory back to work with. To use this rule, your
> > > dunit test DO NOT need to extend Junit4DistributedTest class.
> > >
> > > LocatorStartupRule:
> > > This will allow you to start up a locator in the current VM. good for
> > > integration tests.
> > >
> > > ServerStrartupRule:
> > > This will allow you to start up a server in the current VM. good for
> > > integration tests.
> > >
> > > GfshShellConnectorRule:
> > > This will give allow you to connect to a give jmx manager or a locator
> > and
> > > easily execute gfsh command with it.
> > >
> > > MBeanServerConnectorRule
> > > This will allow you to directly connect to the jmx manager using mbean
> > > connection.
> > >
> > > Please let me know if you run into problems when using these rules.
> There
> > > is always room for improvement.
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> > >
> >
>
>
>
> --
> Cheers
>
> Jinmei
>

Re: for discussion: separate website into its own repo

[Joey McAllister]

+1 to Karen's suggestion of moving the website to its own repo.

+1 to Dan's suggestion scripting the website build/publishing with a CI
system based on commits.

On Thu, Feb 16, 2017 at 4:38 PM Dan Smith  wrote:

> +1
>
> I think the current setup is confusing, because the website is supposed to
> include docs that are generated from the last release, but the site
> instructions say the site should be generated from develop. A separate repo
> with a single branch will probably reduce confusion.
>
> We also need to script the website building and publishing, and ideally
> have the publishing done by a CI system based on commits. It looks like
> some other projects are talking about doing this with jenkins jenkins - see
> INFRA-10722 for example.
>
> -Dan
>
> On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller  wrote:
>
> > I think that the website content that is currently in geode/geode-site
> > ought to be moved to its own repository.  The driving reason for this is
> > that changes to the website occur on a different schedule than code
> > releases.  We often want to add a new committer's name or a new
> > event, and these items are not associated with sw releases. A new website
> > release that comes from the develop branch may have commits that
> > should not yet be made public.
> >
> > Are there downsides to separating the website content into its own repo?
> >
>

Re: for discussion: separate website into its own repo

[Dave Barnes]

The current mechanism for publishing the website is quite convoluted. As
you point out, the software and the website are only loosely coupled. I see
only good outcomes for allowing the repos to reflect that reality.

On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller  wrote:

> I think that the website content that is currently in geode/geode-site
> ought to be moved to its own repository.  The driving reason for this is
> that changes to the website occur on a different schedule than code
> releases.  We often want to add a new committer's name or a new
> event, and these items are not associated with sw releases. A new website
> release that comes from the develop branch may have commits that
> should not yet be made public.
>
> Are there downsides to separating the website content into its own repo?
>

Re: Another way to write a DUnit Test

[Jinmei Liao]

It seems there is no usage of this LocatorServerConfigurationRule. It does
look like a duplicate.

On Thu, Feb 16, 2017 at 4:37 PM, Anilkumar Gingade 
wrote:

> I had similar rule added for locator startup...where you can start locator
> by passing required properties.
> Look for: LocatorServerConfigurationRule (we can remove this, instead of
> having duplicate rules)
>
> -Anil.
>
>
>
>
> On Thu, Feb 16, 2017 at 2:26 PM, Jinmei Liao  wrote:
>
> > We've created a few JUnit rules to ease the pain of starting up
> > locator/servers in different vms. Please check these rules out:
> >
> > LocatorServerStartupRule:
> > this rule will allow you to easily start up locator/server in a give VM
> > with the properties you would like to configure them, and get the
> member's
> > name, port, working directory back to work with. To use this rule, your
> > dunit test DO NOT need to extend Junit4DistributedTest class.
> >
> > LocatorStartupRule:
> > This will allow you to start up a locator in the current VM. good for
> > integration tests.
> >
> > ServerStrartupRule:
> > This will allow you to start up a server in the current VM. good for
> > integration tests.
> >
> > GfshShellConnectorRule:
> > This will give allow you to connect to a give jmx manager or a locator
> and
> > easily execute gfsh command with it.
> >
> > MBeanServerConnectorRule
> > This will allow you to directly connect to the jmx manager using mbean
> > connection.
> >
> > Please let me know if you run into problems when using these rules. There
> > is always room for improvement.
> >
> > --
> > Cheers
> >
> > Jinmei
> >
>



-- 
Cheers

Jinmei

Re: [ANNOUNCE] Apache Geode release 1.1.0

[Nitin Lamba]

Great!
Congrats team!!

On Thu, Feb 16, 2017 at 3:49 PM, Greg Chase  wrote:

> Awesome and congratulations!
>
> This email encrypted by tiny buttons & fat thumbs, beta voice recognition,
> and autocorrect on my iPhone.
>
> > On Feb 15, 2017, at 5:34 PM, Hitesh Khamesra 
> wrote:
> >
> > The Apache Geode team is proud to announce Apache Geode release version
> 1.1.0
> >
> > Apache *Geode* is a data management platform that provides a
> > database-like consistency model, reliable transaction processing and a
> > shared-nothing architecture to maintain very low latency performance with
> > high concurrency processing.
> >
> > The release artifacts are available at:
> >  http://geode.apache.org/releases/
> >
> > To use the artifacts, please use the following documentation:
> >  http://geode.apache.org/docs/guide/11/about_geode.html
> >
> > Git source:
> >  https://git-wip-us.apache.org/repos/asf?p=geode.git;a=tag;h=
> 1d7a03bbab47a154b59dc6a4e811f7fc4a74c941
> >
> > Git commit SHA1: 2286fd064a52173eab8fdcfadfb89a01e81ef728
> >
> > Release Notes:
> >  https://cwiki.apache.org/confluence/display/GEODE/
> Release+Notes#ReleaseNotes-1.1.0
> >
> > We would like to thank all the contributors that made the release
> possible.
> >
> > Regards,
> > Hitesh & Karen on behalf of the Apache Geode team
>

Re: for discussion: separate website into its own repo

[Dan Smith]

+1

I think the current setup is confusing, because the website is supposed to
include docs that are generated from the last release, but the site
instructions say the site should be generated from develop. A separate repo
with a single branch will probably reduce confusion.

We also need to script the website building and publishing, and ideally
have the publishing done by a CI system based on commits. It looks like
some other projects are talking about doing this with jenkins jenkins - see
INFRA-10722 for example.

-Dan

On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller  wrote:

> I think that the website content that is currently in geode/geode-site
> ought to be moved to its own repository.  The driving reason for this is
> that changes to the website occur on a different schedule than code
> releases.  We often want to add a new committer's name or a new
> event, and these items are not associated with sw releases. A new website
> release that comes from the develop branch may have commits that
> should not yet be made public.
>
> Are there downsides to separating the website content into its own repo?
>

Re: Another way to write a DUnit Test

[Anilkumar Gingade]

I had similar rule added for locator startup...where you can start locator
by passing required properties.
Look for: LocatorServerConfigurationRule (we can remove this, instead of
having duplicate rules)

-Anil.




On Thu, Feb 16, 2017 at 2:26 PM, Jinmei Liao  wrote:

> We've created a few JUnit rules to ease the pain of starting up
> locator/servers in different vms. Please check these rules out:
>
> LocatorServerStartupRule:
> this rule will allow you to easily start up locator/server in a give VM
> with the properties you would like to configure them, and get the member's
> name, port, working directory back to work with. To use this rule, your
> dunit test DO NOT need to extend Junit4DistributedTest class.
>
> LocatorStartupRule:
> This will allow you to start up a locator in the current VM. good for
> integration tests.
>
> ServerStrartupRule:
> This will allow you to start up a server in the current VM. good for
> integration tests.
>
> GfshShellConnectorRule:
> This will give allow you to connect to a give jmx manager or a locator and
> easily execute gfsh command with it.
>
> MBeanServerConnectorRule
> This will allow you to directly connect to the jmx manager using mbean
> connection.
>
> Please let me know if you run into problems when using these rules. There
> is always room for improvement.
>
> --
> Cheers
>
> Jinmei
>

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode-native/pull/15#discussion_r101662122
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1113,12 +1117,11 @@ class TcrMessageHelper {
   return NULL_OBJECT;
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
-  char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
-  LOGDEBUG("%s ", exMsg);
+
+  std::stringstream s;
+  s << "TcrMessageHelper::readChunkPartHeader: " << methodName << ": 
part is not object\n";
+  LOGDEBUG("%s ", s.str().c_str());
--- End diff --

Good question. I am still fascinated as to why std::snprintf isn't working 
correctly on Windows too.


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #15: GEODE-2484: Fix snprintf error. Need #include...

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/15#discussion_r101662122
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1113,12 +1117,11 @@ class TcrMessageHelper {
   return NULL_OBJECT;
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
-  char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
-  LOGDEBUG("%s ", exMsg);
+
+  std::stringstream s;
+  s << "TcrMessageHelper::readChunkPartHeader: " << methodName << ": 
part is not object\n";
+  LOGDEBUG("%s ", s.str().c_str());
--- End diff --

Good question. I am still fascinated as to why std::snprintf isn't working 
correctly on Windows too.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode-native pull request #13: GEODE-2476: Replace gfcpp with geode.

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/13#discussion_r101659366
  
--- Diff: src/CMakeLists.txt ---
@@ -224,7 +222,7 @@ add_subdirectory(cppcache)
 add_subdirectory(cryptoimpl)
 add_subdirectory(dhimpl)
 add_subdirectory(sqliteimpl)
-add_subdirectory(gfcpp)
+add_subdirectory(getversion)
--- End diff --

Eeeek! This is the best name we could come up with for this stupid util? 
May we should just delete it?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2476) Replace gfcpp with geode

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode-native/pull/13#discussion_r101659366
  
--- Diff: src/CMakeLists.txt ---
@@ -224,7 +222,7 @@ add_subdirectory(cppcache)
 add_subdirectory(cryptoimpl)
 add_subdirectory(dhimpl)
 add_subdirectory(sqliteimpl)
-add_subdirectory(gfcpp)
+add_subdirectory(getversion)
--- End diff --

Eeeek! This is the best name we could come up with for this stupid util? 
May we should just delete it?


> Replace gfcpp with geode
> 
>
> Key: GEODE-2476
> URL: https://issues.apache.org/jira/browse/GEODE-2476
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>
> The substring "gfcpp" still occurs in some places in the native client 
> codebase. It ought to be replaced with "geode" or "geode-native", whichever 
> makes more sense on a case-by-case basis.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #13: GEODE-2476: Replace gfcpp with geode.

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/13#discussion_r101659601
  
--- Diff: src/cppcache/include/geode/AttributesFactory.hpp ---
@@ -1,7 +1,7 @@
 #pragma once
 
-#ifndef GEODE_GFCPP_ATTRIBUTESFACTORY_H_
-#define GEODE_GFCPP_ATTRIBUTESFACTORY_H_
+#ifndef GEODE_GEODE_ATTRIBUTESFACTORY_H_
--- End diff --

Really? GEODE_GEODE doesn't seem right?!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode-native pull request #13: GEODE-2476: Replace gfcpp with geode.

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/13#discussion_r101659693
  
--- Diff: src/cppcache/include/geode/AttributesFactory.hpp ---
@@ -20,7 +20,7 @@
  * limitations under the License.
  */
 
-#include "gfcpp_globals.hpp"
+#include "geode_globals.hpp"
 #include "gf_types.hpp"
--- End diff --

Why not gf_types.hpp renamed to geode_types.hpp?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (GEODE-2500) network partition wrongly detected when the only server crashes

[Swapnil Bawaskar (JIRA)]

Swapnil Bawaskar created GEODE-2500:
---

 Summary: network partition wrongly detected when the only server 
crashes
 Key: GEODE-2500
 URL: https://issues.apache.org/jira/browse/GEODE-2500
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Swapnil Bawaskar


When the distributed system consists of only one locator and one server, if the 
server crashes then a network partition is wrongly detected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

for discussion: separate website into its own repo

[Karen Miller]

I think that the website content that is currently in geode/geode-site
ought to be moved to its own repository.  The driving reason for this is
that changes to the website occur on a different schedule than code
releases.  We often want to add a new committer's name or a new
event, and these items are not associated with sw releases. A new website
release that comes from the develop branch may have commits that
should not yet be made public.

Are there downsides to separating the website content into its own repo?

[jira] [Commented] (GEODE-2309) Replace or add ASF copyright statements in source.

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode-native/pull/12#discussion_r101658884
  
--- Diff: .ratignore ---
@@ -23,10 +23,12 @@
 
 # expect script
 .*changepasswd$
+.*winrm.cloud-init$
 
 # doxygen
 .*package-list$
 .*testframeworkdox.txt$
+docs
--- End diff --

This will match any file with "docs" in it. Seems like a rather greedy 
regex.


> Replace or add ASF copyright statements in source.
> --
>
> Key: GEODE-2309
> URL: https://issues.apache.org/jira/browse/GEODE-2309
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #12: GEODE-2309: Remove or ignore apache-rat flagg...

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/12#discussion_r101658884
  
--- Diff: .ratignore ---
@@ -23,10 +23,12 @@
 
 # expect script
 .*changepasswd$
+.*winrm.cloud-init$
 
 # doxygen
 .*package-list$
 .*testframeworkdox.txt$
+docs
--- End diff --

This will match any file with "docs" in it. Seems like a rather greedy 
regex.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-1956) CI failure: LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1956:


Commit 639c856021ec9321cdc0895a5e1503a6296dc765 in geode's branch 
refs/heads/develop from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=639c856 ]

Revert "GEODE-1956: fix the race condition that cause the vm only hosts 1 
primary bucket"

This reverts commit c3162e0b9d7315c4665ebd05e26515228f9e89de.


> CI failure: 
> LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate
> -
>
> Key: GEODE-1956
> URL: https://issues.apache.org/jira/browse/GEODE-1956
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Bruce Schuchardt
>Assignee: xiaojian zhou
>  Labels: CI
> Fix For: 1.1.0
>
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest$$Lambda$50/1718051859.run
>  in VM 0 running on Host cc2-rh6.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
>   at 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate(LuceneQueriesPeerPRRedundancyDUnitTest.java:80)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> 

[jira] [Commented] (GEODE-1956) CI failure: LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1956:


Commit c3162e0b9d7315c4665ebd05e26515228f9e89de in geode's branch 
refs/heads/develop from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c3162e0 ]

GEODE-1956: fix the race condition that cause the vm only hosts 1 primary bucket


> CI failure: 
> LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate
> -
>
> Key: GEODE-1956
> URL: https://issues.apache.org/jira/browse/GEODE-1956
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Bruce Schuchardt
>Assignee: xiaojian zhou
>  Labels: CI
> Fix For: 1.1.0
>
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest$$Lambda$50/1718051859.run
>  in VM 0 running on Host cc2-rh6.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
>   at 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate(LuceneQueriesPeerPRRedundancyDUnitTest.java:80)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 

Re: [ANNOUNCE] Apache Geode release 1.1.0

[Greg Chase]

Awesome and congratulations!

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Feb 15, 2017, at 5:34 PM, Hitesh Khamesra  
> wrote:
> 
> The Apache Geode team is proud to announce Apache Geode release version 1.1.0
> 
> Apache *Geode* is a data management platform that provides a
> database-like consistency model, reliable transaction processing and a
> shared-nothing architecture to maintain very low latency performance with
> high concurrency processing.
> 
> The release artifacts are available at:
>  http://geode.apache.org/releases/
> 
> To use the artifacts, please use the following documentation:
>  http://geode.apache.org/docs/guide/11/about_geode.html
> 
> Git source:
>  
> https://git-wip-us.apache.org/repos/asf?p=geode.git;a=tag;h=1d7a03bbab47a154b59dc6a4e811f7fc4a74c941
> 
> Git commit SHA1: 2286fd064a52173eab8fdcfadfb89a01e81ef728
> 
> Release Notes:
>  
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.1.0
> 
> We would like to thank all the contributors that made the release possible.
> 
> Regards,
> Hitesh & Karen on behalf of the Apache Geode team

[jira] [Created] (GEODE-2499) Replace snprintf with

[Michael Martell (JIRA)]

Michael Martell created GEODE-2499:
--

 Summary: Replace snprintf with  
 Key: GEODE-2499
 URL: https://issues.apache.org/jira/browse/GEODE-2499
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Michael Martell


Using snprintf on Windows has problems. These can be avoided by switching to 
newer  construct as below. This task is to replace snprintf everywhere 
in the code (100 or so occurances).

Instead of:

  char exMsg[256];
  std::snprintf(exMsg, 255,
"TcrMessageHelper::readChunkPartHeader: "
"%s: part is not object",
methodName);
  LOGDEBUG("%s ", exMsg);

use:

  std::stringstream s;
  s << "TcrMessageHelper::readChunkPartHeader: " << methodName << ": part 
is not object\n";
  LOGDEBUG("%s ", s.str().c_str());





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user dgkimura commented on a diff in the pull request:

https://github.com/apache/geode-native/pull/15#discussion_r101652960
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -20,6 +20,10 @@
  * limitations under the License.
  */
 
+//#include 
--- End diff --

No need for this line in current revision.


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user dgkimura commented on a diff in the pull request:

https://github.com/apache/geode-native/pull/15#discussion_r101655637
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1113,12 +1117,11 @@ class TcrMessageHelper {
   return NULL_OBJECT;
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
-  char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
-  LOGDEBUG("%s ", exMsg);
+
+  std::stringstream s;
+  s << "TcrMessageHelper::readChunkPartHeader: " << methodName << ": 
part is not object\n";
+  LOGDEBUG("%s ", s.str().c_str());
--- End diff --

I find this line a little suspicious.  If I understand correctly, 
`stringstream.str()` will return a temporary string object and then `c_str()` 
will return a pointer to that temporary object.  Then it seems like it may be 
possible that temporary string is freed after the expression is evaluated.  And 
then we would be referencing a freed object inside `LOGDEBUG` which would lead 
to undefined behavior.  If I am misunderstanding then please educate me how 
this works and why you chose to do it!  :)


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #15: GEODE-2484: Fix snprintf error. Need #include...

[dgkimura]

Github user dgkimura commented on a diff in the pull request:

https://github.com/apache/geode-native/pull/15#discussion_r101652960
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -20,6 +20,10 @@
  * limitations under the License.
  */
 
+//#include 
--- End diff --

No need for this line in current revision.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode-native pull request #15: GEODE-2484: Fix snprintf error. Need #include...

[dgkimura]

Github user dgkimura commented on a diff in the pull request:

https://github.com/apache/geode-native/pull/15#discussion_r101655637
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1113,12 +1117,11 @@ class TcrMessageHelper {
   return NULL_OBJECT;
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
-  char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
-  LOGDEBUG("%s ", exMsg);
+
+  std::stringstream s;
+  s << "TcrMessageHelper::readChunkPartHeader: " << methodName << ": 
part is not object\n";
+  LOGDEBUG("%s ", s.str().c_str());
--- End diff --

I find this line a little suspicious.  If I understand correctly, 
`stringstream.str()` will return a temporary string object and then `c_str()` 
will return a pointer to that temporary object.  Then it seems like it may be 
possible that temporary string is freed after the expression is evaluated.  And 
then we would be referencing a freed object inside `LOGDEBUG` which would lead 
to undefined behavior.  If I am misunderstanding then please educate me how 
this works and why you chose to do it!  :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2142) Remove JSON.org dependency

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett commented on GEODE-2142:
-

[~amb] Yes, the "right" solution will not have a need for any modifications nor 
a dependency on any particular JSON or JAX-B implementations. 

> Remove JSON.org dependency
> --
>
> Key: GEODE-2142
> URL: https://issues.apache.org/jira/browse/GEODE-2142
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
>Priority: Blocker
>  Labels: json
>
> ASF has determined that the JSON library should be treated as Category X and 
> is incompatible with ASLv2.
> We have until Apr-30, 2017 to remove this dependency.  Any release we ship 
> prior to that time must state this usage via NOTICE.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3ccajwfca2ox62mugp+-+-v6ktbkhhgkixucjcr9syes-azfp+...@mail.gmail.com%3e
> There are related reasons for removing the JSON library anyway, but this bug 
> captures the legal reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2142) Remove JSON.org dependency

[Anthony Baker (JIRA)]

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

Anthony Baker commented on GEODE-2142:
--

+1

GEODE-629 discusses some of the parsing modifications.  Eventually it would be 
nice to rely on a binary dependency only for json parsing and not do local 
changes.

> Remove JSON.org dependency
> --
>
> Key: GEODE-2142
> URL: https://issues.apache.org/jira/browse/GEODE-2142
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
>Priority: Blocker
>  Labels: json
>
> ASF has determined that the JSON library should be treated as Category X and 
> is incompatible with ASLv2.
> We have until Apr-30, 2017 to remove this dependency.  Any release we ship 
> prior to that time must state this usage via NOTICE.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3ccajwfca2ox62mugp+-+-v6ktbkhhgkixucjcr9syes-azfp+...@mail.gmail.com%3e
> There are related reasons for removing the JSON library anyway, but this bug 
> captures the legal reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode pull request #400: Add geode-redis to assembly.

[galen-pivotal]

GitHub user galen-pivotal reopened a pull request:

https://github.com/apache/geode/pull/400

Add geode-redis to assembly.

This makes starting a server with Redis actually work, at least on my 
machine.

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

$ git pull https://github.com/galen-pivotal/incubator-geode 
feature/GEODE-2444

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

https://github.com/apache/geode/pull/400.patch

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

This closes #400


commit 3f9e52534a23957744a42487a7f0255dd50f3657
Author: Galen OSullivan 
Date:   2017-02-15T21:55:19Z

Add geode-redis to assembly.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode pull request #400: Add geode-redis to assembly.

[galen-pivotal]

Github user galen-pivotal closed the pull request at:

https://github.com/apache/geode/pull/400


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode issue #400: Add geode-redis to assembly.

[galen-pivotal]

Github user galen-pivotal commented on the issue:

https://github.com/apache/geode/pull/400
  
It doesn't look like it, but this has been merged.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode issue #398: Split the redis adapter into its own package

[galen-pivotal]

Github user galen-pivotal commented on the issue:

https://github.com/apache/geode/pull/398
  
We're now running this as a feature branch for the current round of Redis 
work, `feature/GEODE-2444`. I'm going to close this PR for now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] geode pull request #398: Split the redis adapter into its own package

[galen-pivotal]

Github user galen-pivotal closed the pull request at:

https://github.com/apache/geode/pull/398


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2142) Remove JSON.org dependency

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett commented on GEODE-2142:
-

[~ukohlmeyer] and I spent a bit of time looking into the removal of JSON.org 
sources. The sources have been JSON.org modified and modularized as geode-json. 
The geode-json module is used in several locations but most heavily in the gfsh 
communication layer. We first to a stab at replacing the specific use of one 
library with another but the differences between libraries made the effort 
challenging and the time spent was likely better spent embracing something less 
specific. We then looked at re-implementing using domain objects and JAX-B but 
that again unraveled some very complex issues with the use cases in the gfsh 
communication. We then considered a wholesale re-write of gfsh communication. 
Given the time constraints from Apache to divest of this license we felt too 
much time was needed to do the "right" thing. We have come back to something 
easier and that is to replace the core sources of geode-json with those from 
the [tdunning/open-json|https://github.com/tdunning/open-json] project and 
overlay the local changes. This should take less time than anything else and 
complete this simple goal of removing the incompatible licensed code from our 
project. We will then come back around later with a proposal to overhaul the 
gfsh communication layer as part of a greater scheme to restructure Geode to be 
more modular and extendable.



> Remove JSON.org dependency
> --
>
> Key: GEODE-2142
> URL: https://issues.apache.org/jira/browse/GEODE-2142
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
>Priority: Blocker
>  Labels: json
>
> ASF has determined that the JSON library should be treated as Category X and 
> is incompatible with ASLv2.
> We have until Apr-30, 2017 to remove this dependency.  Any release we ship 
> prior to that time must state this usage via NOTICE.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3ccajwfca2ox62mugp+-+-v6ktbkhhgkixucjcr9syes-azfp+...@mail.gmail.com%3e
> There are related reasons for removing the JSON library anyway, but this bug 
> captures the legal reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56767: GEODE-2402: Write to the lucene region buckets using a callback argument

[Dan Smith]

> On Feb. 16, 2017, 10:45 p.m., Jason Huynh wrote:
> > geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/directory/RegionDirectory.java,
> >  line 38
> > 
> >
> > I don't think we use UUID here?

It looks like we do, actually. Here's a method in RegionDirectory:

public IndexOutput createTempOutput(String prefix, String suffix, IOContext 
context)
  throws IOException {
String name = prefix + "_temp_" + UUID.randomUUID() + suffix;
final File file = fs.createTemporaryFile(name);
final OutputStream out = file.getOutputStream();

return new OutputStreamIndexOutput(name, name, out, 1000);
  }


- Dan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56767/#review165889
---


On Feb. 16, 2017, 9:15 p.m., Dan Smith wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56767/
> ---
> 
> (Updated Feb. 16, 2017, 9:15 p.m.)
> 
> 
> Review request for geode, Jason Huynh, nabarun nag, and xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Adding a callback argument when writing to the file and chunk regions. 
> The file and chunk regions now have a partition listener to
> route the put to the correct bucket.
> 
> The reason for all of this is that in some cases, the core code can can
> send a message that only includes the PR id and the key. We need want
> the core to be able to resolve the correct bucket from just those
> things, which requires having the PartitionListener that uses the 
> callback argument.
> 
> Note that I'm still writing directly to the BucketRegions, rather than
> the partition region. I had some changes to write to the partitioned region,
> but I'm seeing some filesystem corruption with those changes so I'd like
> to just get this much in at that point.
> 
> Added a test of putting to the file and chunk regions during GII, which
> is the case where the core code sends a message that includes only the PR id
> and the key.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/InitialImageOperation.java
>  3ec8152cfe43b7499fe52ba31bdf2d9e1df2d48f 
>   geode-core/src/main/java/org/apache/geode/internal/cache/LocalDataSet.java 
> c4858dc168a0c26750e28dff280197bad3164185 
>   geode-core/src/main/java/org/apache/geode/internal/cache/LocalRegion.java 
> 00401e9ac7adfd5e3e8962476bddc6c9a8281af4 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegion.java
>  44f84277363b9e8f6bba8407c7f02609a2c2150d 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
>  57dd0a56882b4087770348c3f58df29df9fdc893 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneIndexForPartitionedRegion.java
>  53b4e083372127ef5670324bf3b687986d7f58bf 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/directory/RegionDirectory.java
>  362cf932f265cd4b6095cc1c790b7f1bcbc3b259 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/filesystem/FileSystem.java
>  f3975bf4bae8e28d6a9329788e939f101e857897 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingFixedResolver.java
>  PRE-CREATION 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingMap.java
>  PRE-CREATION 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingResolver.java
>  PRE-CREATION 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/IndexRepositoryImpl.java
>  f1ee9871911f7ecfd3084c464ed8b67e9f28800a 
>   
> geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPRBase.java
>  931edc5269fc29de8e29f3099314a12959644f3b 
>   
> geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPeerFixedPRDUnitTest.java
>  dd9fa6b71f1bceccaec56eef1c6b5adc7c88c550 
>   
> geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPeerPRRedundancyDUnitTest.java
>  496721a5c2534e543f4f68d2285cf6e211cd5505 
>   
> geode-lucene/src/test/java/org/apache/geode/cache/lucene/internal/PartitionedRepositoryManagerJUnitTest.java
>  78909034138d9188b19067b5112e4c366750581b 
>   
> geode-lucene/src/test/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingMapTest.java
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/56767/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dan Smith
> 
>

[jira] [Commented] (GEODE-2414) Determine a mechanism to stream a zip file from server to locator

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2414:


Commit d690012f82e68e04c95f840943a5cd71b7f67452 in geode's branch 
refs/heads/feature/GEODE-2267 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d690012 ]

GEODE-2414: Create exportLogs region for all locators


> Determine a mechanism to stream a zip file from server to locator
> -
>
> Key: GEODE-2414
> URL: https://issues.apache.org/jira/browse/GEODE-2414
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration, gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> Our export command will execute a function on servers (one at a time) to 
> build up a zip file of the artifacts for that server.  Then, the zip file 
> needs to be sent back to the locator, so that the locator can aggregate 
> together the files from all servers.  However, we need to make sure to 
> chunk/stream the data that we send from server to locator so that neither 
> member will run out of memory if the file is very large.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Create JUnit Rules instead of extending other test classes

[Kirk Lund]

It's possible this might be caused by a bug in Gradle's JUnit task which is
how Jenkins is running this test. The test method is skipped as expected
when run in IntelliJ.

On Thu, Feb 16, 2017 at 2:17 PM, Kirk Lund  wrote:

> LocatorUDPSecurityDUnitTest extends LocatorDUnitTest.
>
> LocatorDUnitTest has a test named 
> testSSLEnabledLocatorDiesWhenConnectingToNonSSLLocator
> which is currently annotated with @Ignore.
>
> Despite the test being marked with @Ignore, apparently the test still gets
> executed by LocatorUDPSecurityDUnitTest. See last night's Geode Nightly
> Build in which this test failed:
>
> https://builds.apache.org/job/Geode-nightly/750/testReport/
> junit/org.apache.geode.distributed/LocatorUDPSecurityDUnitTest/
> testNonSSLLocatorDiesWhenConnectingToSSLLocator/
>
> I recommend we avoid extending other tests. If you have some
> setup/teardown that you really want to reuse in multiple tests then create
> a custom JUnit rule. Or very carefully put the body of the test in a
> non-test class that is not annotated with JUnit annotations and then have
> two different tests both invoke code in the non-test class -- I would
> recommend avoiding this approach in general to avoid creating spaghetti or
> having multiple tests repeating the same end-to-end code with slight
> variations to config which redundantly extends the run time of precheckin.
>
> I think the only way to get LocatorUDPSecurityDUnitTest to not run the
> @Ignored test is to @Override the test method AND add its own @Ignore
> annotation.
>
> This could be a bug in JUnit, but we're already using JUnit 4.12 which is
> the latest release.
>
> -Kirk
>
>

Another way to write a DUnit Test

[Jinmei Liao]

We've created a few JUnit rules to ease the pain of starting up
locator/servers in different vms. Please check these rules out:

LocatorServerStartupRule:
this rule will allow you to easily start up locator/server in a give VM
with the properties you would like to configure them, and get the member's
name, port, working directory back to work with. To use this rule, your
dunit test DO NOT need to extend Junit4DistributedTest class.

LocatorStartupRule:
This will allow you to start up a locator in the current VM. good for
integration tests.

ServerStrartupRule:
This will allow you to start up a server in the current VM. good for
integration tests.

GfshShellConnectorRule:
This will give allow you to connect to a give jmx manager or a locator and
easily execute gfsh command with it.

MBeanServerConnectorRule
This will allow you to directly connect to the jmx manager using mbean
connection.

Please let me know if you run into problems when using these rules. There
is always room for improvement.

-- 
Cheers

Jinmei

[jira] [Commented] (GEODE-2496) MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: Connection refused (Connection refused)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2496:


Commit c8bf9d0f8a6278db8c666bdcc91edce3da8d6221 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c8bf9d0 ]

GEODE-2496: apply Flaky category to flaky test due to ConnectExceptions


> MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: 
> Connection refused (Connection refused)
> 
>
> Key: GEODE-2496
> URL: https://issues.apache.org/jira/browse/GEODE-2496
> Project: Geode
>  Issue Type: Bug
>  Components: jmx, security
>Reporter: Kirk Lund
>  Labels: Flaky, JMX, Security
>
> Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
> * testClusterAdmin
> * testDataAdmin
> {noformat}
> :geode-core:integrationTest
> org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
> testClusterAdmin FAILED
> java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection refused)]
> Caused by:
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)]
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 
> 10.254.0.30; nested exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection 
> refused)
> {noformat}{noformat}
> org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
> testDataAdmin FAILED
> java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection refused)]
> Caused by:
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)]
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 
> 10.254.0.30; nested exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection 
> refused)
> 3367 tests completed, 2 failed, 165 skipped
> :geode-core:integrationTest FAILED
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Create JUnit Rules instead of extending other test classes

[Kirk Lund]

LocatorUDPSecurityDUnitTest extends LocatorDUnitTest.

LocatorDUnitTest has a test named
testSSLEnabledLocatorDiesWhenConnectingToNonSSLLocator which is currently
annotated with @Ignore.

Despite the test being marked with @Ignore, apparently the test still gets
executed by LocatorUDPSecurityDUnitTest. See last night's Geode Nightly
Build in which this test failed:

https://builds.apache.org/job/Geode-nightly/750/testReport/junit/org.apache.geode.distributed/LocatorUDPSecurityDUnitTest/testNonSSLLocatorDiesWhenConnectingToSSLLocator/

I recommend we avoid extending other tests. If you have some setup/teardown
that you really want to reuse in multiple tests then create a custom JUnit
rule. Or very carefully put the body of the test in a non-test class that
is not annotated with JUnit annotations and then have two different tests
both invoke code in the non-test class -- I would recommend avoiding this
approach in general to avoid creating spaghetti or having multiple tests
repeating the same end-to-end code with slight variations to config which
redundantly extends the run time of precheckin.

I think the only way to get LocatorUDPSecurityDUnitTest to not run the
@Ignored test is to @Override the test method AND add its own @Ignore
annotation.

This could be a bug in JUnit, but we're already using JUnit 4.12 which is
the latest release.

-Kirk

[jira] [Created] (GEODE-2498) Revise 1.1.0 manual to remove references to 1.0.0-incubating

[Karen Smoler Miller (JIRA)]

Karen Smoler Miller created GEODE-2498:
--

 Summary: Revise 1.1.0 manual to remove references to 
1.0.0-incubating
 Key: GEODE-2498
 URL: https://issues.apache.org/jira/browse/GEODE-2498
 Project: Geode
  Issue Type: Bug
  Components: docs, web-content
Reporter: Karen Smoler Miller


There are two errant instances within the Geode 1.1.0 manual that say 
1.0.0-incubating.  This task is to remove these references, and further, to 
revise the prose such that it does not contain a version number that would need 
to be changed in future releases.  That  would avoid the mistake that occurred 
with the 1.1.0 manual.

The 2 instances are within files
* {{geode-docs/about_geode.html.md.erb}}
* {{geode-docs/prereq_and_install.html.md.erb}}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56769: Fix some races in to IndexRepository creation

[nabarun nag]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56769/#review165883
---


Ship it!




Ship It!

- nabarun nag


On Feb. 16, 2017, 9:17 p.m., Dan Smith wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56769/
> ---
> 
> (Updated Feb. 16, 2017, 9:17 p.m.)
> 
> 
> Review request for geode, Jason Huynh, nabarun nag, and xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> 1) Since we have the partition listener on the chunk bucket, we should
> be looking at the chunk bucket to tell if we are primary, not the file
> bucket
> 
> 2)  We were not cleaning up the dlock in some cases if the bucket moved.
> 
> 3) The dlock name was confusing, because we took the bucket name, eg 
> file_B_1, and added the bucket id to it. So we had a lock name like 
> file_B_11 for bucket 1.
> 
> 
> Diffs
> -
> 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
>  57dd0a56882b4087770348c3f58df29df9fdc893 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/IndexRepositoryImpl.java
>  f1ee9871911f7ecfd3084c464ed8b67e9f28800a 
> 
> Diff: https://reviews.apache.org/r/56769/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dan Smith
> 
>

Re: Review Request 56769: Fix some races in to IndexRepository creation

[Jason Huynh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56769/#review165880
---


Ship it!




Ship It!


geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
 (line 108)


does it matter if we use chunk vs file bucket here?


- Jason Huynh


On Feb. 16, 2017, 9:17 p.m., Dan Smith wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56769/
> ---
> 
> (Updated Feb. 16, 2017, 9:17 p.m.)
> 
> 
> Review request for geode, Jason Huynh, nabarun nag, and xiaojian zhou.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> 1) Since we have the partition listener on the chunk bucket, we should
> be looking at the chunk bucket to tell if we are primary, not the file
> bucket
> 
> 2)  We were not cleaning up the dlock in some cases if the bucket moved.
> 
> 3) The dlock name was confusing, because we took the bucket name, eg 
> file_B_1, and added the bucket id to it. So we had a lock name like 
> file_B_11 for bucket 1.
> 
> 
> Diffs
> -
> 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
>  57dd0a56882b4087770348c3f58df29df9fdc893 
>   
> geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/IndexRepositoryImpl.java
>  f1ee9871911f7ecfd3084c464ed8b67e9f28800a 
> 
> Diff: https://reviews.apache.org/r/56769/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dan Smith
> 
>

Review Request 56769: Fix some races in to IndexRepository creation

[Dan Smith]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56769/
---

Review request for geode, Jason Huynh, nabarun nag, and xiaojian zhou.


Repository: geode


Description
---

1) Since we have the partition listener on the chunk bucket, we should
be looking at the chunk bucket to tell if we are primary, not the file
bucket

2)  We were not cleaning up the dlock in some cases if the bucket moved.

3) The dlock name was confusing, because we took the bucket name, eg 
file_B_1, and added the bucket id to it. So we had a lock name like 
file_B_11 for bucket 1.


Diffs
-

  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
 57dd0a56882b4087770348c3f58df29df9fdc893 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/IndexRepositoryImpl.java
 f1ee9871911f7ecfd3084c464ed8b67e9f28800a 

Diff: https://reviews.apache.org/r/56769/diff/


Testing
---


Thanks,

Dan Smith

Review Request 56767: GEODE-2402: Write to the lucene region buckets using a callback argument

[Dan Smith]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56767/
---

Review request for geode, Jason Huynh, nabarun nag, and xiaojian zhou.


Repository: geode


Description
---

Adding a callback argument when writing to the file and chunk regions. 
The file and chunk regions now have a partition listener to
route the put to the correct bucket.

The reason for all of this is that in some cases, the core code can can
send a message that only includes the PR id and the key. We need want
the core to be able to resolve the correct bucket from just those
things, which requires having the PartitionListener that uses the 
callback argument.

Note that I'm still writing directly to the BucketRegions, rather than
the partition region. I had some changes to write to the partitioned region,
but I'm seeing some filesystem corruption with those changes so I'd like
to just get this much in at that point.

Added a test of putting to the file and chunk regions during GII, which
is the case where the core code sends a message that includes only the PR id
and the key.


Diffs
-

  
geode-core/src/main/java/org/apache/geode/internal/cache/InitialImageOperation.java
 3ec8152cfe43b7499fe52ba31bdf2d9e1df2d48f 
  geode-core/src/main/java/org/apache/geode/internal/cache/LocalDataSet.java 
c4858dc168a0c26750e28dff280197bad3164185 
  geode-core/src/main/java/org/apache/geode/internal/cache/LocalRegion.java 
00401e9ac7adfd5e3e8962476bddc6c9a8281af4 
  
geode-core/src/main/java/org/apache/geode/internal/cache/PartitionedRegion.java 
44f84277363b9e8f6bba8407c7f02609a2c2150d 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/IndexRepositoryFactory.java
 57dd0a56882b4087770348c3f58df29df9fdc893 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneIndexForPartitionedRegion.java
 53b4e083372127ef5670324bf3b687986d7f58bf 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/directory/RegionDirectory.java
 362cf932f265cd4b6095cc1c790b7f1bcbc3b259 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/filesystem/FileSystem.java
 f3975bf4bae8e28d6a9329788e939f101e857897 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingFixedResolver.java
 PRE-CREATION 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingMap.java
 PRE-CREATION 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingResolver.java
 PRE-CREATION 
  
geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/repository/IndexRepositoryImpl.java
 f1ee9871911f7ecfd3084c464ed8b67e9f28800a 
  
geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPRBase.java
 931edc5269fc29de8e29f3099314a12959644f3b 
  
geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPeerFixedPRDUnitTest.java
 dd9fa6b71f1bceccaec56eef1c6b5adc7c88c550 
  
geode-lucene/src/test/java/org/apache/geode/cache/lucene/LuceneQueriesPeerPRRedundancyDUnitTest.java
 496721a5c2534e543f4f68d2285cf6e211cd5505 
  
geode-lucene/src/test/java/org/apache/geode/cache/lucene/internal/PartitionedRepositoryManagerJUnitTest.java
 78909034138d9188b19067b5112e4c366750581b 
  
geode-lucene/src/test/java/org/apache/geode/cache/lucene/internal/partition/BucketTargetingMapTest.java
 PRE-CREATION 

Diff: https://reviews.apache.org/r/56767/diff/


Testing
---


Thanks,

Dan Smith

Re: Review Request 56738: GEODE-2489: Avoid sending tombstone GC messages to peer nodes if there is no client registration

[anilkumar gingade]

> On Feb. 16, 2017, 6:47 p.m., Darrel Schneider wrote:
> > geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java,
> >  line 599
> > 
> >
> > instead of size() > 0 is !isEmpty()

New change does not use size.


> On Feb. 16, 2017, 6:47 p.m., Darrel Schneider wrote:
> > geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/PRTombstoneMessage.java,
> >  line 71
> > 
> >
> > If you follow my previous advice then it seems like 
> > adviseAllPRServersWithInterestNodes should be 
> > adviseAllNonReplicatesPRServersWithInterestNodes and then you can get rid 
> > of the call in line 72 of removeAll(adviseReplicates())

We are looking at two different advisor here, for PR and bucket region.


- anilkumar


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56738/#review165874
---


On Feb. 16, 2017, 8:50 p.m., anilkumar gingade wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56738/
> ---
> 
> (Updated Feb. 16, 2017, 8:50 p.m.)
> 
> 
> Review request for geode, Darrel Schneider and Eric Shu.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Tombstone:
> As part of consistency checking, when an entry is destroyed, the member 
> temporarily retains the entry to detect possible conflicts with operations 
> that have occurred. The retained entry is referred to as a tombstone.
> 
> When tombstones are removed, tombstone messages are sent to region replicas; 
> and in case of Partitioned Region (PR) messages are also sent to peer region 
> nodes for client events.
> 
> Currently tombstone messages meant for clients that have all the keys removed 
> are getting sent to peer PR nodes even though no clients are registered on 
> those peers.
> 
> Based on the number tombstone keys processed (by default 10) this could 
> be large message sent to peer node which could impact the performance of the 
> system/cluster.
> 
> 
> Diffs
> -
> 
>   
> geode-core/src/main/java/org/apache/geode/distributed/internal/DistributionAdvisor.java
>  b5b9cf4 
>   geode-core/src/main/java/org/apache/geode/internal/cache/BucketRegion.java 
> 585f4e4 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java
>  ca682bc 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/PRTombstoneMessage.java
>  fa82560 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/RegionAdvisor.java
>  0978585 
>   
> geode-core/src/test/java/org/apache/geode/cache30/ClientServerCCEDUnitTest.java
>  9780563 
> 
> Diff: https://reviews.apache.org/r/56738/diff/
> 
> 
> Testing
> ---
> 
> Added new test
> precheckin
> 
> 
> Thanks,
> 
> anilkumar gingade
> 
>

Re: Review Request 56738: GEODE-2489: Avoid sending tombstone GC messages to peer nodes if there is no client registration

[anilkumar gingade]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56738/
---

(Updated Feb. 16, 2017, 8:50 p.m.)


Review request for geode, Darrel Schneider and Eric Shu.


Changes
---

Incorporated review comments.


Repository: geode


Description
---

Tombstone:
As part of consistency checking, when an entry is destroyed, the member 
temporarily retains the entry to detect possible conflicts with operations that 
have occurred. The retained entry is referred to as a tombstone.

When tombstones are removed, tombstone messages are sent to region replicas; 
and in case of Partitioned Region (PR) messages are also sent to peer region 
nodes for client events.

Currently tombstone messages meant for clients that have all the keys removed 
are getting sent to peer PR nodes even though no clients are registered on 
those peers.

Based on the number tombstone keys processed (by default 10) this could be 
large message sent to peer node which could impact the performance of the 
system/cluster.


Diffs (updated)
-

  
geode-core/src/main/java/org/apache/geode/distributed/internal/DistributionAdvisor.java
 b5b9cf4 
  geode-core/src/main/java/org/apache/geode/internal/cache/BucketRegion.java 
585f4e4 
  
geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java 
ca682bc 
  
geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/PRTombstoneMessage.java
 fa82560 
  
geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/RegionAdvisor.java
 0978585 
  
geode-core/src/test/java/org/apache/geode/cache30/ClientServerCCEDUnitTest.java 
9780563 

Diff: https://reviews.apache.org/r/56738/diff/


Testing
---

Added new test
precheckin


Thanks,

anilkumar gingade

[GitHub] geode-native issue #15: GEODE-2484: Fix snprintf error. Need #include

[mmartell]

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
On Thu, Feb 16, 2017 at 12:09 PM Michael Martell 
wrote:

> Something is screwed up in our #includes. TcrMessage.cpp compiles fine
> leaving the std:: in there. However, other classes that include it don't
> compile (like DistributedSystem).
>
> I'd rather spend time switching to newer constructs ( and
> ). Simple change, and for now we can convert the streamstrimg
> back to char* when passing to logger.
>
> On Thu, Feb 16, 2017 at 11:50 AM Jacob Barrett 
> wrote:
>
> *@pivotal-jbarrett* requested changes on this pull request.
> --
>
> In src/cppcache/src/TcrMessage.hpp
> :
>
> > @@ -1114,10 +1116,10 @@ class TcrMessageHelper {
>  } else if (!isObj) {
>// otherwise we're currently always expecting an object
>char exMsg[256];
> -  std::snprintf(exMsg, 255,
> -"TcrMessageHelper::readChunkPartHeader: "
> -"%s: part is not object",
> -methodName);
> +  snprintf(exMsg, 255,
>
> If you had to remove std:: to make this work then it isn't working like
> you think it is. Let's figure out why and fix correctly,
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>
>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
On Thu, Feb 16, 2017 at 12:09 PM Michael Martell 
wrote:

> Something is screwed up in our #includes. TcrMessage.cpp compiles fine
> leaving the std:: in there. However, other classes that include it don't
> compile (like DistributedSystem).
>
> I'd rather spend time switching to newer constructs ( and
> ). Simple change, and for now we can convert the streamstrimg
> back to char* when passing to logger.
>
> On Thu, Feb 16, 2017 at 11:50 AM Jacob Barrett 
> wrote:
>
> *@pivotal-jbarrett* requested changes on this pull request.
> --
>
> In src/cppcache/src/TcrMessage.hpp
> :
>
> > @@ -1114,10 +1116,10 @@ class TcrMessageHelper {
>  } else if (!isObj) {
>// otherwise we're currently always expecting an object
>char exMsg[256];
> -  std::snprintf(exMsg, 255,
> -"TcrMessageHelper::readChunkPartHeader: "
> -"%s: part is not object",
> -methodName);
> +  snprintf(exMsg, 255,
>
> If you had to remove std:: to make this work then it isn't working like
> you think it is. Let's figure out why and fix correctly,
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>
>



> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
Something is screwed up in our #includes. TcrMessage.cpp compiles fine
leaving the std:: in there. However, other classes that include it don't
compile (like Distributed System).

I'd rather spend time switching to newer constructs ( and
). Simple change, and for now we can convert the streamstrimg
back to char* when passing to logger.

On Thu, Feb 16, 2017 at 11:50 AM Jacob Barrett 
wrote:

> *@pivotal-jbarrett* requested changes on this pull request.
> --
>
> In src/cppcache/src/TcrMessage.hpp
> :
>
> > @@ -1114,10 +1116,10 @@ class TcrMessageHelper {
>  } else if (!isObj) {
>// otherwise we're currently always expecting an object
>char exMsg[256];
> -  std::snprintf(exMsg, 255,
> -"TcrMessageHelper::readChunkPartHeader: "
> -"%s: part is not object",
> -methodName);
> +  snprintf(exMsg, 255,
>
> If you had to remove std:: to make this work then it isn't working like
> you think it is. Let's figure out why and fix correctly,
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>



> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native issue #15: GEODE-2484: Fix snprintf error. Need #include

[mmartell]

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
Something is screwed up in our #includes. TcrMessage.cpp compiles fine
leaving the std:: in there. However, other classes that include it don't
compile (like Distributed System).

I'd rather spend time switching to newer constructs ( and
). Simple change, and for now we can convert the streamstrimg
back to char* when passing to logger.

On Thu, Feb 16, 2017 at 11:50 AM Jacob Barrett 
wrote:

> *@pivotal-jbarrett* requested changes on this pull request.
> --
>
> In src/cppcache/src/TcrMessage.hpp
> :
>
> > @@ -1114,10 +1116,10 @@ class TcrMessageHelper {
>  } else if (!isObj) {
>// otherwise we're currently always expecting an object
>char exMsg[256];
> -  std::snprintf(exMsg, 255,
> -"TcrMessageHelper::readChunkPartHeader: "
> -"%s: part is not object",
> -methodName);
> +  snprintf(exMsg, 255,
>
> If you had to remove std:: to make this work then it isn't working like
> you think it is. Let's figure out why and fix correctly,
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> 
,
> or mute the thread
> 

> .
>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode-native/pull/15#discussion_r101610701
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1114,10 +1116,10 @@ class TcrMessageHelper {
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
   char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
+  snprintf(exMsg, 255,
--- End diff --

If you had to remove std:: to make this work then it isn't working like you 
think it is. Let's figure out why and fix correctly,


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #15: GEODE-2484: Fix snprintf error. Need #include...

[pivotal-jbarrett]

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

https://github.com/apache/geode-native/pull/15#discussion_r101610701
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1114,10 +1116,10 @@ class TcrMessageHelper {
 } else if (!isObj) {
   // otherwise we're currently always expecting an object
   char exMsg[256];
-  std::snprintf(exMsg, 255,
-"TcrMessageHelper::readChunkPartHeader: "
-"%s: part is not object",
-methodName);
+  snprintf(exMsg, 255,
--- End diff --

If you had to remove std:: to make this work then it isn't working like you 
think it is. Let's figure out why and fix correctly,


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2416) Collect together artifacts from individual servers into a single zip file

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2416:


Commit f542a8603662e5ced85f5fdb85f82f8b7102f6a3 in geode's branch 
refs/heads/feature/GEODE-2267 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=f542a86 ]

GEODE-2416: Export logs includes locators


> Collect together artifacts from individual servers into a single zip file
> -
>
> Key: GEODE-2416
> URL: https://issues.apache.org/jira/browse/GEODE-2416
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration, gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> We need a locator to unzip the individual zip files produced by GEODE-2415 
> and re-zip them together into a single zip file (with a directory for each 
> member, containing the artifacts from that member).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2486) Trouble setting cipher on Native Client

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett commented on GEODE-2486:
-

[~ahuddy] Your change to the title does not correctly reflect the problem or 
the solution in the associated fixes. Geode native does not and has not allowed 
for the setting of the SSL cipher. The attached fix does not allow you to set 
the cipher. The fix corrects the error in initialization that prevents the 
client from negotiating anything other than the NULL cipher with the server. 
The server will ultimately control the cipher that the client uses.



> Trouble setting cipher on Native Client
> ---
>
> Key: GEODE-2486
> URL: https://issues.apache.org/jira/browse/GEODE-2486
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.2.0
>
>
> SSLImpl does not correctly initialize the OpenSSL library so ciphers other 
> than the NULL cipher can be used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2430) Remove binary files from test resources

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2430:


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

GEODE-2430: Remove jar and zip files from test resources

This closes #393

(cherry picked from commit e769796)


> Remove binary files from test resources
> ---
>
> Key: GEODE-2430
> URL: https://issues.apache.org/jira/browse/GEODE-2430
> Project: Geode
>  Issue Type: Improvement
>  Components: management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
> Fix For: 1.1.0
>
>
> We have some tests which rely on the following binary files:
> {code}
> + 
> geode-core/src/test/resources/org/apache/geode/management/internal/configuration/cluster.jar
> + 
> geode-core/src/test/resources/org/apache/geode/management/internal/configuration/cluster_config.zip
> + 
> geode-core/src/test/resources/org/apache/geode/management/internal/configuration/cluster_config_security.zip
> + 
> geode-core/src/test/resources/org/apache/geode/management/internal/configuration/group1.jar
> + 
> geode-core/src/test/resources/org/apache/geode/management/internal/configuration/group2.jar
> {code}
> We need to convert our tests to generate these files dynamically instead so 
> that we don't have binary files checked into our repository.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2433) Backwards compatibility tests are not actually running

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2433:


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

GEODE-2433  Backwards compatibility tests are not actually running

The geode-old-versions/build.gradle file was not included in the original
commit for backward-compatibility testing.  It's needed to establish
the old-version source sets and generate the classpaths file used by
VersionManager.


> Backwards compatibility tests are not actually running
> --
>
> Key: GEODE-2433
> URL: https://issues.apache.org/jira/browse/GEODE-2433
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> We have several backwards compatibility tests checked in -
> RollingUpgradeDUnitTest
> RollingUpgrade2DUnitTest
> ClientServerMiscBCDUnitTest
> These tests are all parametered by the list of old versions to run against.
> However, it looks like the code to get the list of old versions incorrectly 
> just logs a message and continues on if it can't find a file called 
> geodeOldVersionClasspaths.txt. That file does not exist and is not being 
> generated as far is I can tell. The entire project - geode-old-versions, is 
> completely empty.
> The net effect is these tests don't actually run, because the list of 
> parameters is an empty list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2433) Backwards compatibility tests are not actually running

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2433:


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

GEODE-2433  Backwards compatibility tests are not actually running

Show current working directory if unable to run backward compatibility
tests.  For some reason we aren't finding the classpaths file when running
under Jenkins.


> Backwards compatibility tests are not actually running
> --
>
> Key: GEODE-2433
> URL: https://issues.apache.org/jira/browse/GEODE-2433
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> We have several backwards compatibility tests checked in -
> RollingUpgradeDUnitTest
> RollingUpgrade2DUnitTest
> ClientServerMiscBCDUnitTest
> These tests are all parametered by the list of old versions to run against.
> However, it looks like the code to get the list of old versions incorrectly 
> just logs a message and continues on if it can't find a file called 
> geodeOldVersionClasspaths.txt. That file does not exist and is not being 
> generated as far is I can tell. The entire project - geode-old-versions, is 
> completely empty.
> The net effect is these tests don't actually run, because the list of 
> parameters is an empty list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2433) Backwards compatibility tests are not actually running

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2433:


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

GEODE-2433 Backwards compatibility tests are not actually running

Tests will now fail of there are no older versions of Geode to test
against.


> Backwards compatibility tests are not actually running
> --
>
> Key: GEODE-2433
> URL: https://issues.apache.org/jira/browse/GEODE-2433
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> We have several backwards compatibility tests checked in -
> RollingUpgradeDUnitTest
> RollingUpgrade2DUnitTest
> ClientServerMiscBCDUnitTest
> These tests are all parametered by the list of old versions to run against.
> However, it looks like the code to get the list of old versions incorrectly 
> just logs a message and continues on if it can't find a file called 
> geodeOldVersionClasspaths.txt. That file does not exist and is not being 
> generated as far is I can tell. The entire project - geode-old-versions, is 
> completely empty.
> The net effect is these tests don't actually run, because the list of 
> parameters is an empty list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2444) Making Redis Adapter easier to use and more robust

[Addison (JIRA)]

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

Addison updated GEODE-2444:
---
Summary: Making Redis Adapter easier to use and more robust  (was: Move 
Redis out of experimental)

> Making Redis Adapter easier to use and more robust
> --
>
> Key: GEODE-2444
> URL: https://issues.apache.org/jira/browse/GEODE-2444
> Project: Geode
>  Issue Type: New Feature
>  Components: redis
>Reporter: Addison
>
> The goal of this effort is to further test and complete the Redis Adapter to 
> make the code more readable and performant. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-2497) surprise members are never timed out during startup

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt reassigned GEODE-2497:
---

Assignee: Bruce Schuchardt

> surprise members are never timed out during startup
> ---
>
> Key: GEODE-2497
> URL: https://issues.apache.org/jira/browse/GEODE-2497
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>
> A system was observed to hang during startup when a "surprise member" was 
> added but then never timed out.  The system hung waiting for a response to a 
> startup message sent to the surprise member.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2444) Move Redis out of experimental

[Addison (JIRA)]

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

Addison updated GEODE-2444:
---
Summary: Move Redis out of experimental  (was: Redis Adapter Performance 
Improvements)

> Move Redis out of experimental
> --
>
> Key: GEODE-2444
> URL: https://issues.apache.org/jira/browse/GEODE-2444
> Project: Geode
>  Issue Type: New Feature
>  Components: redis
>Reporter: Addison
>
> The goal of this effort is to further test and complete the Redis Adapter to 
> make the code more readable and performant. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-2497) surprise members are never timed out during startup

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-2497:
---

 Summary: surprise members are never timed out during startup
 Key: GEODE-2497
 URL: https://issues.apache.org/jira/browse/GEODE-2497
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Bruce Schuchardt


A system was observed to hang during startup when a "surprise member" was added 
but then never timed out.  The system hung waiting for a response to a startup 
message sent to the surprise member.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEODE-2477) CI Failure suspect string from returnCorrectResultsWhenCloseCacheHappensOnPartialIndexWrite

[Jason Huynh (JIRA)]

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

Jason Huynh resolved GEODE-2477.

   Resolution: Fixed
Fix Version/s: 1.2.0

The changes in GEODE-2491 should address this issue.  The exceptions should no 
longer log as warn level and only log at debug level.  As long as the tests are 
run at a higher level than debug, we should no longer see this error when 
running this test

> CI Failure  suspect string from 
> returnCorrectResultsWhenCloseCacheHappensOnPartialIndexWrite
> 
>
> Key: GEODE-2477
> URL: https://issues.apache.org/jira/browse/GEODE-2477
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Dan Smith
>Assignee: Jason Huynh
> Fix For: 1.2.0
>
>
> Revision dbea592cc96f64c9fbc7abf8bbf597a69c5881cd
> {noformat}
> 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 1450
> [error 2017/02/12 06:02:16.915 PST  GatewaySender_AsyncEventQueue_index#_region_1> tid=0x7a8] Unable to save to 
> lucene index
> org.apache.geode.cache.CacheClosedException: The cache has been closed
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.getCacheClosedException(GemFireCacheImpl.java:1621)
>   at 
> org.apache.geode.internal.cache.DistributedCacheOperation.distribute(DistributedCacheOperation.java:498)
>   at 
> org.apache.geode.internal.cache.AbstractUpdateOperation.distribute(AbstractUpdateOperation.java:70)
>   at 
> org.apache.geode.internal.cache.BucketRegion.basicPutPart2(BucketRegion.java:633)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2800)
>   at 
> org.apache.geode.internal.cache.BucketRegion.virtualPut(BucketRegion.java:485)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:151)
>   at 
> org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5194)
>   at 
> org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1605)
>   at 
> org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1592)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:277)
>   at 
> org.apache.geode.cache.lucene.internal.filesystem.FileSystem.putChunk(FileSystem.java:183)
>   at 
> org.apache.geode.cache.lucene.internal.filesystem.FileOutputStream.flushBuffer(FileOutputStream.java:90)
>   at 
> org.apache.geode.cache.lucene.internal.filesystem.FileOutputStream.close(FileOutputStream.java:78)
>   at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
>   at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
>   at 
> org.apache.lucene.store.OutputStreamIndexOutput.close(OutputStreamIndexOutput.java:70)
>   at 
> org.apache.lucene.codecs.compressing.CompressingStoredFieldsIndexWriter.close(CompressingStoredFieldsIndexWriter.java:210)
>   at org.apache.lucene.util.IOUtils.close(IOUtils.java:89)
>   at org.apache.lucene.util.IOUtils.close(IOUtils.java:76)
>   at 
> org.apache.lucene.codecs.compressing.CompressingStoredFieldsWriter.close(CompressingStoredFieldsWriter.java:138)
>   at 
> org.apache.lucene.index.DefaultIndexingChain.flush(DefaultIndexingChain.java:117)
>   at 
> org.apache.lucene.index.DocumentsWriterPerThread.flush(DocumentsWriterPerThread.java:423)
>   at 
> org.apache.lucene.index.DocumentsWriter.doFlush(DocumentsWriter.java:502)
>   at 
> org.apache.lucene.index.DocumentsWriter.flushAllThreads(DocumentsWriter.java:614)
>   at 
> org.apache.lucene.index.IndexWriter.prepareCommitInternal(IndexWriter.java:2815)
>   at 
> org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:2989)
>   at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:2956)
>   at 
> org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImpl.commit(IndexRepositoryImpl.java:144)
>   at 
> org.apache.geode.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:88)
>   at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:154)
>   at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:80)
>   at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:593)
>   at 
> 

[jira] [Resolved] (GEODE-2491) Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

[Jason Huynh (JIRA)]

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

Jason Huynh resolved GEODE-2491.

   Resolution: Fixed
Fix Version/s: 1.2.0

> Reduce logging of handled exceptions in LuceneEventListener and 
> LuceneBucketListeners
> -
>
> Key: GEODE-2491
> URL: https://issues.apache.org/jira/browse/GEODE-2491
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Jason Huynh
> Fix For: 1.2.0
>
>
> Currently we handle specific exception types but continue to log them as 
> warnings.  Instead we should probably log them at a debug level so they won't 
> show up in regular usage of the product because we do expect these exceptions 
> to be thrown/caught for certain scenarios.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56738: GEODE-2489: Avoid sending tombstone GC messages to peer nodes if there is no client registration

[Darrel Schneider]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56738/#review165874
---




geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java 
(line 598)


Instead of creating a set every time by calling 
adviseAllPRServersWithInterestNodes it seems like it would be better to have a 
method on the advisor name "hasPRServersWithInterest" that just returns true as 
soon as it finds a single profile.
This would cut down on the amount of garbage this method generates when it 
is called for every tombstone in the batch



geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java 
(line 599)


instead of size() > 0 is !isEmpty()



geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/PRTombstoneMessage.java
 (line 71)


If you follow my previous advice then it seems like 
adviseAllPRServersWithInterestNodes should be 
adviseAllNonReplicatesPRServersWithInterestNodes and then you can get rid of 
the call in line 72 of removeAll(adviseReplicates())


- Darrel Schneider


On Feb. 15, 2017, 5:56 p.m., anilkumar gingade wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/56738/
> ---
> 
> (Updated Feb. 15, 2017, 5:56 p.m.)
> 
> 
> Review request for geode, Darrel Schneider and Eric Shu.
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> Tombstone:
> As part of consistency checking, when an entry is destroyed, the member 
> temporarily retains the entry to detect possible conflicts with operations 
> that have occurred. The retained entry is referred to as a tombstone.
> 
> When tombstones are removed, tombstone messages are sent to region replicas; 
> and in case of Partitioned Region (PR) messages are also sent to peer region 
> nodes for client events.
> 
> Currently tombstone messages meant for clients that have all the keys removed 
> are getting sent to peer PR nodes even though no clients are registered on 
> those peers.
> 
> Based on the number tombstone keys processed (by default 10) this could 
> be large message sent to peer node which could impact the performance of the 
> system/cluster.
> 
> 
> Diffs
> -
> 
>   geode-core/src/main/java/org/apache/geode/internal/cache/BucketRegion.java 
> 585f4e4 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java
>  ca682bc 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/PRTombstoneMessage.java
>  fa82560 
>   
> geode-core/src/main/java/org/apache/geode/internal/cache/partitioned/RegionAdvisor.java
>  0978585 
>   
> geode-core/src/test/java/org/apache/geode/cache30/ClientServerCCEDUnitTest.java
>  9780563 
> 
> Diff: https://reviews.apache.org/r/56738/diff/
> 
> 
> Testing
> ---
> 
> Added new test
> precheckin
> 
> 
> Thanks,
> 
> anilkumar gingade
> 
>

[jira] [Resolved] (GEODE-2052) Docs to segregate types of properties

[Dave Barnes (JIRA)]

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

Dave Barnes resolved GEODE-2052.

Resolution: Fixed

Table of geode-* (gemfire-*) properties updated with a new column designating 
each property as applicable to Server / Locator / Client. Info was obtained 
from developers and reviewed by the ticket reporter.


> Docs to segregate types of properties
> -
>
> Key: GEODE-2052
> URL: https://issues.apache.org/jira/browse/GEODE-2052
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Pulkit Chandra
>Assignee: Dave Barnes
>
> Geode has a lot of properties. But they are not mentioned in context but 
> rather listed as geode properties which can go in geode.properties and 
> gfsecurity.properties.
> It would nice to have a segregation by Locator and Server under 
> geode.properties. The reason for this ask is that some properties do not 
> apply to both locator and server. Currently the only way to know this is by 
> experience or trial and error.
> ~~We also found out that some of the gemfire.properties do not get applied 
> when supplied in geode.properties but rather have to be passed as command 
> line properties. e.g. enabling rest api.
> It would be nice to call that out clearly in docs.~~
> ~~There are example of properties which have to be applied together in order 
> to enable a functionality e.g. rest api needs bind address property and 
> http-service-port. Its not called out clearly in the docs that they are 
> *mandatory*. ~~
> [link to docs 
> section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html)
> ~~quote ~~
> ~~To enable the developer REST API service in Apache Geode, set the 
> start-dev-rest-api Geode property to true when starting a data node using 
> either gfsh or the ServerLauncher API. Setting this property to true on a 
> data node will start up an embedded Jetty server and deploy the REST 
> developer API WAR file.~~
> ~~It should highlight that its necessary to have 2 more properties 
> bind-address and http-service-port defined to make it work.~~
> We would be happy to provide further details on this matter if needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2052) Docs to segregate types of properties

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2052:


Commit 09a92304a9e2373933c758744c6397fadb1f02d5 in geode's branch 
refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=09a9230 ]

GEODE-2052: Docs to segregate types of properties
Added Server / Locator / Client labels to the list of GemFire properties.


> Docs to segregate types of properties
> -
>
> Key: GEODE-2052
> URL: https://issues.apache.org/jira/browse/GEODE-2052
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Pulkit Chandra
>Assignee: Dave Barnes
>
> Geode has a lot of properties. But they are not mentioned in context but 
> rather listed as geode properties which can go in geode.properties and 
> gfsecurity.properties.
> It would nice to have a segregation by Locator and Server under 
> geode.properties. The reason for this ask is that some properties do not 
> apply to both locator and server. Currently the only way to know this is by 
> experience or trial and error.
> ~~We also found out that some of the gemfire.properties do not get applied 
> when supplied in geode.properties but rather have to be passed as command 
> line properties. e.g. enabling rest api.
> It would be nice to call that out clearly in docs.~~
> ~~There are example of properties which have to be applied together in order 
> to enable a functionality e.g. rest api needs bind address property and 
> http-service-port. Its not called out clearly in the docs that they are 
> *mandatory*. ~~
> [link to docs 
> section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html)
> ~~quote ~~
> ~~To enable the developer REST API service in Apache Geode, set the 
> start-dev-rest-api Geode property to true when starting a data node using 
> either gfsh or the ServerLauncher API. Setting this property to true on a 
> data node will start up an embedded Jetty server and deploy the REST 
> developer API WAR file.~~
> ~~It should highlight that its necessary to have 2 more properties 
> bind-address and http-service-port defined to make it work.~~
> We would be happy to provide further details on this matter if needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2052) Docs to segregate types of properties

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2052:


Commit 35d4ded221c0e235809e5a0c5bff299dd684a746 in geode's branch 
refs/heads/develop from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=35d4ded ]

GEODE-2052 (docs) Add server-only flag to deploy-working-dir property


> Docs to segregate types of properties
> -
>
> Key: GEODE-2052
> URL: https://issues.apache.org/jira/browse/GEODE-2052
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Pulkit Chandra
>Assignee: Dave Barnes
>
> Geode has a lot of properties. But they are not mentioned in context but 
> rather listed as geode properties which can go in geode.properties and 
> gfsecurity.properties.
> It would nice to have a segregation by Locator and Server under 
> geode.properties. The reason for this ask is that some properties do not 
> apply to both locator and server. Currently the only way to know this is by 
> experience or trial and error.
> ~~We also found out that some of the gemfire.properties do not get applied 
> when supplied in geode.properties but rather have to be passed as command 
> line properties. e.g. enabling rest api.
> It would be nice to call that out clearly in docs.~~
> ~~There are example of properties which have to be applied together in order 
> to enable a functionality e.g. rest api needs bind address property and 
> http-service-port. Its not called out clearly in the docs that they are 
> *mandatory*. ~~
> [link to docs 
> section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html)
> ~~quote ~~
> ~~To enable the developer REST API service in Apache Geode, set the 
> start-dev-rest-api Geode property to true when starting a data node using 
> either gfsh or the ServerLauncher API. Setting this property to true on a 
> data node will start up an embedded Jetty server and deploy the REST 
> developer API WAR file.~~
> ~~It should highlight that its necessary to have 2 more properties 
> bind-address and http-service-port defined to make it work.~~
> We would be happy to provide further details on this matter if needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2052) Docs to segregate types of properties

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2052:


Commit 35d4ded221c0e235809e5a0c5bff299dd684a746 in geode's branch 
refs/heads/feature/GEODE-2052 from [~dbarnes97]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=35d4ded ]

GEODE-2052 (docs) Add server-only flag to deploy-working-dir property


> Docs to segregate types of properties
> -
>
> Key: GEODE-2052
> URL: https://issues.apache.org/jira/browse/GEODE-2052
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Pulkit Chandra
>Assignee: Dave Barnes
>
> Geode has a lot of properties. But they are not mentioned in context but 
> rather listed as geode properties which can go in geode.properties and 
> gfsecurity.properties.
> It would nice to have a segregation by Locator and Server under 
> geode.properties. The reason for this ask is that some properties do not 
> apply to both locator and server. Currently the only way to know this is by 
> experience or trial and error.
> ~~We also found out that some of the gemfire.properties do not get applied 
> when supplied in geode.properties but rather have to be passed as command 
> line properties. e.g. enabling rest api.
> It would be nice to call that out clearly in docs.~~
> ~~There are example of properties which have to be applied together in order 
> to enable a functionality e.g. rest api needs bind address property and 
> http-service-port. Its not called out clearly in the docs that they are 
> *mandatory*. ~~
> [link to docs 
> section](http://geode.incubator.apache.org/docs/guide/rest_apps/setup_config.html)
> ~~quote ~~
> ~~To enable the developer REST API service in Apache Geode, set the 
> start-dev-rest-api Geode property to true when starting a data node using 
> either gfsh or the ServerLauncher API. Setting this property to true on a 
> data node will start up an embedded Jetty server and deploy the REST 
> developer API WAR file.~~
> ~~It should highlight that its necessary to have 2 more properties 
> bind-address and http-service-port defined to make it work.~~
> We would be happy to provide further details on this matter if needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (GEODE-2474) netstat command fails to correctly identify OS and --with-lsof fails on Mac

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-2474.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> netstat command fails to correctly identify OS and --with-lsof fails on Mac
> ---
>
> Key: GEODE-2474
> URL: https://issues.apache.org/jira/browse/GEODE-2474
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Affects Versions: 1.0.0-incubating, 1.1.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>  Labels: MiscellaneousCommands, NetstatCommand, gfsh, netstat
> Fix For: 1.2.0
>
>
> The netstat gfsh command uses NetstatFunction which has its own faulty logic 
> for identifying the operating system. This logic identifies Mac as Windows 
> and fails to process --with-lsof.
> NetstatFunction should instead use org.apache.geode.internal.lang.SystemUtils 
> which correctly identifies the operating system.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2491) Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2491:


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

GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and 
LuceneBucketListeners


> Reduce logging of handled exceptions in LuceneEventListener and 
> LuceneBucketListeners
> -
>
> Key: GEODE-2491
> URL: https://issues.apache.org/jira/browse/GEODE-2491
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> Currently we handle specific exception types but continue to log them as 
> warnings.  Instead we should probably log them at a debug level so they won't 
> show up in regular usage of the product because we do expect these exceptions 
> to be thrown/caught for certain scenarios.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2496) MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: Connection refused (Connection refused)

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2496:
-
Labels: Flaky JMX Security  (was: )

> MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: 
> Connection refused (Connection refused)
> 
>
> Key: GEODE-2496
> URL: https://issues.apache.org/jira/browse/GEODE-2496
> Project: Geode
>  Issue Type: Bug
>  Components: jmx, security
>Reporter: Kirk Lund
>  Labels: Flaky, JMX, Security
>
> Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
> * testClusterAdmin
> * testDataAdmin
> {noformat}
> :geode-core:integrationTest
> org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
> testClusterAdmin FAILED
> java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection refused)]
> Caused by:
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)]
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 
> 10.254.0.30; nested exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection 
> refused)
> {noformat}{noformat}
> org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
> testDataAdmin FAILED
> java.io.IOException: Failed to retrieve RMIServer stub: 
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection refused)]
> Caused by:
> javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)]
> Caused by:
> java.rmi.ConnectException: Connection refused to host: 
> 10.254.0.30; nested exception is: 
>   java.net.ConnectException: Connection refused (Connection 
> refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection 
> refused)
> 3367 tests completed, 2 failed, 165 skipped
> :geode-core:integrationTest FAILED
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2496) MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: Connection refused (Connection refused)

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2496:
-
Description: 
Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
* testClusterAdmin
* testDataAdmin
{noformat}
:geode-core:integrationTest
{noformat}
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testClusterAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)
{noformat}{noformat}
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testDataAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

3367 tests completed, 2 failed, 165 skipped
:geode-core:integrationTest FAILED
{noformat}

  was:
Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
* testClusterAdmin
* testDataAdmin
{noformat}
:geode-core:integrationTest

org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testClusterAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testDataAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

3367 tests completed, 2 failed, 165 skipped
:geode-core:integrationTest FAILED
{noformat}


> MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: 
> Connection refused (Connection refused)
> 
>
> Key: GEODE-2496
> URL: https://issues.apache.org/jira/browse/GEODE-2496
> 

[jira] [Updated] (GEODE-2496) MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: Connection refused (Connection refused)

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-2496:
-
Description: 
Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
* testClusterAdmin
* testDataAdmin
{noformat}
:geode-core:integrationTest
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testClusterAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)
{noformat}{noformat}
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testDataAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

3367 tests completed, 2 failed, 165 skipped
:geode-core:integrationTest FAILED
{noformat}

  was:
Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
* testClusterAdmin
* testDataAdmin
{noformat}
:geode-core:integrationTest
{noformat}
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testClusterAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)
{noformat}{noformat}
org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testDataAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

3367 tests completed, 2 failed, 165 skipped
:geode-core:integrationTest FAILED
{noformat}


> MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: 
> Connection refused (Connection refused)
> 
>
> Key: GEODE-2496
> URL: https://issues.apache.org/jira/browse/GEODE-2496

[jira] [Created] (GEODE-2496) MemberMBeanSecurityJUnitTest intermittently fails with rmi ConnectException: Connection refused (Connection refused)

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-2496:


 Summary: MemberMBeanSecurityJUnitTest intermittently fails with 
rmi ConnectException: Connection refused (Connection refused)
 Key: GEODE-2496
 URL: https://issues.apache.org/jira/browse/GEODE-2496
 Project: Geode
  Issue Type: Bug
  Components: jmx, security
Reporter: Kirk Lund


Two tests in MemberMBeanSecurityJUnitTest are failing intermittently:
* testClusterAdmin
* testDataAdmin
{noformat}
:geode-core:integrationTest

org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testClusterAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

org.apache.geode.management.internal.security.MemberMBeanSecurityJUnitTest > 
testDataAdmin FAILED
java.io.IOException: Failed to retrieve RMIServer stub: 
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

Caused by:
javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)]

Caused by:
java.rmi.ConnectException: Connection refused to host: 10.254.0.30; 
nested exception is: 
java.net.ConnectException: Connection refused (Connection 
refused)

Caused by:
java.net.ConnectException: Connection refused (Connection 
refused)

3367 tests completed, 2 failed, 165 skipped
:geode-core:integrationTest FAILED
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2481) Refactor generation of default configuration properties

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2481:


Commit 48e34ac251b9fe006c1b6f71b21c0b26756841ef in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=48e34ac ]

GEODE-2481: extract default properties generation to its own class


> Refactor generation of default configuration properties
> ---
>
> Key: GEODE-2481
> URL: https://issues.apache.org/jira/browse/GEODE-2481
> Project: Geode
>  Issue Type: Wish
>  Components: build, configuration
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> The build currently invokes DistributionConfigImpl.main to generate the 
> default configuration properties file.
> The test for this is currently named GemFireVersionIntegrationJUnitTest.
> The code for generating the default configuration properties file should be 
> extracted to its own class. GemFireVersionIntegrationJUnitTest should be 
> moved to that packaged and renamed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
David,

I had to remove the std:: to get it to build on Windows. I tested my fix on
Windows and Mac only.

On Thu, Feb 16, 2017 at 9:41 AM, Anthony Baker 
wrote:

> Did you tag the wrong JIRA issue? I don't see anything related to
> GEODE-2484.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 

> .
>



> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native issue #15: GEODE-2484: Fix snprintf error. Need #include

[mmartell]

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
David,

I had to remove the std:: to get it to build on Windows. I tested my fix on
Windows and Mac only.

On Thu, Feb 16, 2017 at 9:41 AM, Anthony Baker 
wrote:

> Did you tag the wrong JIRA issue? I don't see anything related to
> GEODE-2484.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 

> .
>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user metatype commented on the issue:

https://github.com/apache/geode-native/pull/15
  
Did you tag the wrong JIRA issue?  I don't see anything related to 
GEODE-2484.


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native pull request #15: GEODE-2484: Fix snprintf error. Need #include...

[dgkimura]

Github user dgkimura commented on a diff in the pull request:

https://github.com/apache/geode-native/pull/15#discussion_r101580799
  
--- Diff: src/cppcache/src/TcrMessage.hpp ---
@@ -1135,7 +1137,7 @@ class TcrMessageHelper {
 return EXCEPTION;
   } else {
 char exMsg[256];
-std::snprintf(
+snprintf(
--- End diff --

Why are you removing the namespace specifier here?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: Geode-nightly #750

[Apache Jenkins Server]

See 

Changes:

[abaker] Update dockerfile for 1.1.0

[kmiller] Update Geode web page's index.html file to include 1.1.0 binaries and

--
[...truncated 710 lines...]
:geode-json:checkMissedTests UP-TO-DATE
:geode-json:spotlessJavaCheck
:geode-json:spotlessCheck
:geode-json:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest UP-TO-DATE
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:spotlessJavaCheck
:geode-junit:spotlessCheck
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJava
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.pom
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-codecs/6.4.1/lucene-codecs-6.4.1.pom
Download 
https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-runner/2.4.0/randomizedtesting-runner-2.4.0.pom
Download 
https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-parent/2.4.0/randomizedtesting-parent-2.4.0.pom
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-test-framework/6.4.1/lucene-test-framework-6.4.1.jar
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-codecs/6.4.1/lucene-codecs-6.4.1.jar
Download 
https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-runner/2.4.0/randomizedtesting-runner-2.4.0.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:spotlessJavaCheck
:geode-lucene:spotlessCheck
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-old-client-support:assemble
:geode-old-client-support:compileTestJava
:geode-old-client-support:processTestResources UP-TO-DATE
:geode-old-client-support:testClasses
:geode-old-client-support:checkMissedTests
:geode-old-client-support:spotlessJavaCheck
:geode-old-client-support:spotlessCheck
:geode-old-client-support:test
:geode-old-client-support:check
:geode-old-client-support:build
:geode-old-client-support:distributedTest
:geode-old-client-support:flakyTest
:geode-old-client-support:integrationTest
:geode-old-versions:javadoc UP-TO-DATE
:geode-old-versions:javadocJar
:geode-old-versions:sourcesJar
:geode-old-versions:signArchives SKIPPED
:geode-old-versions:assemble
:geode-old-versions:compileTestJava UP-TO-DATE
:geode-old-versions:processTestResources UP-TO-DATE
:geode-old-versions:testClasses UP-TO-DATE
:geode-old-versions:checkMissedTests UP-TO-DATE
:geode-old-versions:spotlessJavaCheck
:geode-old-versions:spotlessCheck
:geode-old-versions:test UP-TO-DATE
:geode-old-versions:check
:geode-old-versions:build
:geode-old-versions:distributedTest UP-TO-DATE
:geode-old-versions:flakyTest UP-TO-DATE
:geode-old-versions:integrationTest UP-TO-DATE
:geode-pulse:assemble
:geode-pulse:compileTestJava
Download 
https://repo1.maven.org/maven2/com/codeborne/phantomjsdriver/1.3.0/phantomjsdriver-1.3.0.pom
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-api/3.0.1/selenium-api-3.0.1.pom
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-remote-driver/3.0.1/selenium-remote-driver-3.0.1.pom
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-support/3.0.1/selenium-support-3.0.1.pom
Download 
https://repo1.maven.org/maven2/cglib/cglib-nodep/3.2.4/cglib-nodep-3.2.4.pom
Download 
https://repo1.maven.org/maven2/com/codeborne/phantomjsdriver/1.3.0/phantomjsdriver-1.3.0.jar
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-api/3.0.1/selenium-api-3.0.1.jar
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-remote-driver/3.0.1/selenium-remote-driver-3.0.1.jar
Download 
https://repo1.maven.org/maven2/org/seleniumhq/selenium/selenium-support/3.0.1/selenium-support-3.0.1.jar
Download 
https://repo1.maven.org/maven2/cglib/cglib-nodep/3.2.4/cglib-nodep-3.2.4.jar
Note: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: 

Re: Could not create an instance of org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage .

[Avinash Dongre]

Please ignore. This was my merge issue.

Thanks
Avinash


On Thu, Feb 16, 2017 at 7:38 PM, Avinash Dongre  wrote:

> Hi All,
>
> I am getting following exception in my test.
> My Test has 3 VMs + locator and I am doing some puts/gets and restarting.
> I see following exception when 1 node is shutdown and other node receive
> this message and then node which receive this message never shutdown.
>
> Any clue why this is happening ?
>
> I am running with rel/v1.1.0
>
> Thanks
> Avinash
>
>
>
> [severe 2017/02/16 18:56:14.532 IST   192.168.3.76(31930):32772 shared unordered uid=3 port=41938> tid=0x52] 
> Error deserializing message
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage
>  .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:1003)
> at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2718)
> at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3607)
> at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1865)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1726)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.internal.cache.TXId .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at org.apache.geode.internal.cache.TXId.createFromData(TXId.java:109)
> at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:966)
> at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2836)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2897)
> at 
> org.apache.geode.DataSerializer.readObjectArray(DataSerializer.java:1860)
> at 
> org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage.fromData(DLockRecoverGrantorProcessor.java:355)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 6 more
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  
> org.apache.geode.distributed.internal.membership.InternalDistributedMember .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at 
> org.apache.geode.internal.DSFIDFactory.readInternalDistributedMember(DSFIDFactory.java:1036)
> at org.apache.geode.internal.cache.TXId.fromData(TXId.java:104)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 13 more
> Caused by: java.io.IOException: While reading an InetAddress
> at 
> org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:477)
> at 
> org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromDataPre_GFE_9_0_0_0(InternalDistributedMember.java:961)
> at 
> org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromData(InternalDistributedMember.java:948)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 16 more
> Caused by: java.net.UnknownHostException: addr is of illegal length
> at java.net.InetAddress.getByAddress(InetAddress.java:1042)
> at java.net.InetAddress.getByAddress(InetAddress.java:1439)
> at 
> org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:470)
> ... 19 more
>
> [warning 2017/02/16 18:56:29.520 IST   
> tid=0x12] 15 seconds have elapsed while waiting for replies: 
>  [192.168.3.76(31930):32772]> on 192.168.3.76(31924):32771 whose 
> current membership list is: [[192.168.3.76(31930):32772, 
> 192.168.3.76(31859:locator):32769, 192.168.3.76(31924):32771]]
>
> [info 2017/02/16 19:15:45.130 IST   
> tid=0x13] VM is exiting - shutting down distributed system
>
> [info 2017/02/16 19:15:45.198 IST   
> tid=0x3d] received leave request from 
> 192.168.3.76(31859:locator):32769 for 
> 192.168.3.76(31859:locator):32769
>
> [info 2017/02/16 19:15:45.198 IST   
> tid=0x3d] This member is becoming the membership coordinator with address 
> 192.168.3.76(31924):32771
>
> [info 2017/02/16 19:15:45.203 IST   
> tid=0x3d] ViewCreator starting on:192.168.3.76(31924):32771
>
>

Errored: apache/geode-native#41 (develop - 41d826e)

[Travis CI]

Build Update for apache/geode-native
-

Build: #41
Status: Errored

Duration: 9 seconds
Commit: 41d826e (develop)
Author: Jacob Barrett
Message: GEODE-2486: Fixes casting failure on Windows.

View the changeset: 
https://github.com/apache/geode-native/compare/d4e0a8447b1e...41d826e8203c

View the full build log and details: 
https://travis-ci.org/apache/geode-native/builds/202113123

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications

[jira] [Updated] (GEODE-2486) User having trouble setting cipher on Native Client

[Addison (JIRA)]

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

Addison updated GEODE-2486:
---
Summary: User having trouble setting cipher on Native Client  (was: SSL 
ciphers other than NULL not supported)

> User having trouble setting cipher on Native Client
> ---
>
> Key: GEODE-2486
> URL: https://issues.apache.org/jira/browse/GEODE-2486
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.2.0
>
>
> SSLImpl does not correctly initialize the OpenSSL library so ciphers other 
> than the NULL cipher can be used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2486) Trouble setting cipher on Native Client

[Addison (JIRA)]

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

Addison updated GEODE-2486:
---
Summary: Trouble setting cipher on Native Client  (was: User having trouble 
setting cipher on Native Client)

> Trouble setting cipher on Native Client
> ---
>
> Key: GEODE-2486
> URL: https://issues.apache.org/jira/browse/GEODE-2486
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.2.0
>
>
> SSLImpl does not correctly initialize the OpenSSL library so ciphers other 
> than the NULL cipher can be used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
Whoops. Forgot to format. Fixing now.


> Remove ACE from native client dependencies
> --
>
> Key: GEODE-2484
> URL: https://issues.apache.org/jira/browse/GEODE-2484
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: David Kimura
>
> Remove ACE from native client dependencies.
> Replace ACE usage with C++11 and/or Boost 1.63+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode-native issue #15: GEODE-2484: Fix snprintf error. Need #include

[mmartell]

Github user mmartell commented on the issue:

https://github.com/apache/geode-native/pull/15
  
Whoops. Forgot to format. Fixing now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (GEODE-2471) AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2471:


Commit caafea339afe52bba3be2dda906860d20a045bc4 in geode's branch 
refs/heads/feature/GEODE-2267 from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=caafea3 ]

GEODE-2471: fix the race condition in test code.


> AsyncEventListenerOffHeapDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching
> --
>
> Key: GEODE-2471
> URL: https://issues.apache.org/jira/browse/GEODE-2471
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>  Labels: CI
>
> {noformat}
> found in concourse distributedTest #383
> 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 
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDUnitTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching(AsyncEventListenerDUnitTest.java:1675)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 

1.1.0 is done so let's start work on 1.2.0

[Anthony Baker]

Great job everyone on releasing 1.1.0!  Let’s get organized for the next 
release :-)

Scope:
We definitely need to focus on eliminating JSON.org prior to 4/31.  See 
GEODE-629, GEODE-2142, GEODE-2331, GEODE-2380.
Anything else?

Timing:
I suggest shooting for a release candidate around mid-March if possible 
(release often!)

Release Manager:
Any volunteers?

Note:  as a process reminder please don’t set Fix Version in JIRA unless you 
fix a bug that has been merged to develop or the issue has been prioritized by 
the community for inclusion in a release.

Thanks,
Anthony

[jira] [Updated] (GEODE-2464) Review Redis tests

[Anthony Baker (JIRA)]

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

Anthony Baker updated GEODE-2464:
-
Fix Version/s: (was: 1.2.0)

> Review Redis tests
> --
>
> Key: GEODE-2464
> URL: https://issues.apache.org/jira/browse/GEODE-2464
> Project: Geode
>  Issue Type: Sub-task
>  Components: redis
>Reporter: Galen O'Sullivan
>
> The existing Redis tests could use some cleanup and probably expansion.
> * [~ukohlmeyer] and I ([~gosullivan]) did some common test code with 
> `RedisTestBase`; there is probably some room for improvement there.
> * There is a lot of repetition in the test code for the Redis adapter. We can 
> improve this.
> * Randomization: use junit-quickcheck {{@Property}} tests?
> * Make sure every Redis command gets tested. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2451) Improve storage of key/values

[Anthony Baker (JIRA)]

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

Anthony Baker updated GEODE-2451:
-
Fix Version/s: (was: 1.2.0)

> Improve storage of key/values
> -
>
> Key: GEODE-2451
> URL: https://issues.apache.org/jira/browse/GEODE-2451
> Project: Geode
>  Issue Type: Sub-task
>  Components: redis
>Reporter: Addison
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-2449) Move redis adapter to extension framework

[Anthony Baker (JIRA)]

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

Anthony Baker updated GEODE-2449:
-
Fix Version/s: (was: 1.2.0)

> Move redis adapter to extension framework
> -
>
> Key: GEODE-2449
> URL: https://issues.apache.org/jira/browse/GEODE-2449
> Project: Geode
>  Issue Type: Sub-task
>  Components: redis
>Reporter: Addison
>Assignee: Udo Kohlmeyer
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)