Review Request 49102: WAN Ack reader thread needs to be shut down before sending a close connection

2016-06-22 Thread Jason Huynh 

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

Review request for geode, anilkumar gingade, Barry Oglesby, nabarun nag, Dan 
Smith, and xiaojian zhou.


Repository: geode


Description
---

When closing a sender, the close connection message is sent on the same 
connection that is used by the ack reader thread.  This causes an issue as two 
threads are now reading off the same socket concurrently.  The fix is to 
prevent this from happening but to do so, the input stream needs to be closed 
(to free up from a socket read()).  
The dispatcher also needs to shut down before the close connection is sent out 
or it will spawn off another ack reader thread.


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/wan/AbstractGatewaySenderEventProcessor.java
 ce08e8d 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/wan/parallel/ConcurrentParallelGatewaySenderEventProcessor.java
 07a3be5 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/wan/serial/ConcurrentSerialGatewaySenderEventProcessor.java
 ff810ec 
  
geode-wan/src/main/java/com/gemstone/gemfire/internal/cache/wan/GatewaySenderEventRemoteDispatcher.java
 b178192 

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


Testing
---


Thanks,

Jason Huynh

Creating & Destroying Regions programmatically

2016-06-22 Thread Kevin Duling 
I'm trying to figure out how to exercise the CreateRegion and
DestoryRegion classes from a client in order to test authorization.  I
can't figure out what the API would be for a client to trigger the
cmdExecute() call on the server.

For example, I was able to hit it in ClearRegion by having the client
execute the Region.clear() method.  Here's a snippet from the unit
test:

SerializableRunnable clearAuthorized = new SerializableRunnable() {
  @Override
  public void run() {
Cache cache =
SecurityTestUtils.createCacheClient("authRegionUser", "1234567",
serverPort, SecurityTestUtils.NO_EXCEPTION);
final Region region = cache.getRegion(SecurityTestUtils.REGION_NAME);
region.clear();
cache.close();
  }
};
client2.invoke(clearAuthorized);

Build failed in Jenkins: Geode-nightly #507

2016-06-22 Thread Apache Jenkins Server 
See 

Changes:

[jiliao] GEODE-117 - gfsh put ignores --skip-if-exists flag

[jiliao] GEODE-1549: Correct "Help" hyperlink in pulse

[gzhou] GEODE-1572: add a dunit test for client server query for lucene

[klund] GEODE-1565: add quotes around any value starting with hyphen

[jiliao] GEODE-1575 - Unhandled NoClassDefFound Exception when creating regions

[upthewaterspout] GEODE-11: Adding a dunit test of querying with a custom query 
object

[upthewaterspout] GEODE-1494: Fixing javadocs and stats descriptions for stat 
suppliers

--
[...truncated 524 lines...]
:geode-wan:jar
:geode-wan:javadoc
:geode-wan:javadocJar
:geode-wan:sourcesJar
:geode-wan:signArchives SKIPPED
:geode-web:javadoc UP-TO-DATE
:geode-web:javadocJar
:geode-web:sourcesJar
:geode-web:war
:geode-web:signArchives SKIPPED
:geode-web-api:jar
:geode-web-api:javadoc
:geode-web-api:javadocJar
:geode-web-api:sourcesJar
:geode-web-api:war
:geode-web-api:signArchives SKIPPED
:geode-assembly:distTar
:geode-assembly:distZip
:geode-assembly:writeBuildInfo
:geode-assembly:srcDistTar
:geode-assembly:srcDistZip
:geode-assembly:signArchives SKIPPED
:geode-assembly:assemble
:geode-assembly:compileTestJavaNote: 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-assembly:processTestResources
:geode-assembly:testClasses
:geode-assembly:checkMissedTests
:geode-assembly:installDist
:geode-assembly:test
:geode-assembly:check
:geode-assembly:build
:geode-assembly:distributedTest
:geode-assembly:flakyTest
:geode-assembly:integrationTest
:geode-common:assemble
:geode-common:compileTestJava
:geode-common:processTestResources UP-TO-DATE
:geode-common:testClasses
:geode-common:checkMissedTests
:geode-common:test
:geode-common:check
:geode-common:build
:geode-common:distributedTest
:geode-common:flakyTest
:geode-common:integrationTest
:geode-core:assemble
:geode-core:checkMissedTests
:geode-core:test
:geode-core:check
:geode-core:build
:geode-core:distributedTest

com.gemstone.gemfire.distributed.SystemAdminDUnitTest > testPrintStacks FAILED
java.lang.AssertionError: found a Management Task thread in stack dump in 
SystemAdminDUnitTest_testPrintStacks1.txt
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at 
com.gemstone.gemfire.distributed.SystemAdminDUnitTest.checkStackDumps(SystemAdminDUnitTest.java:117)
at 
com.gemstone.gemfire.distributed.SystemAdminDUnitTest.testPrintStacks(SystemAdminDUnitTest.java:84)

7344 tests completed, 1 failed, 554 skipped
:geode-core:distributedTest FAILED
:geode-core:flakyTest
:geode-core:integrationTest
:geode-cq:assemble
:geode-cq:compileTestJavaNote: 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-cq:processTestResources
:geode-cq:testClasses
:geode-cq:checkMissedTests
:geode-cq:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:flakyTest
:geode-cq:integrationTest
:geode-json:assemble
:geode-json:compileTestJava UP-TO-DATE
:geode-json:processTestResources UP-TO-DATE
:geode-json:testClasses UP-TO-DATE
:geode-json:checkMissedTests UP-TO-DATE
: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:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: 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:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile

Re: update website for WAN, CQ and native client

2016-06-22 Thread Roman Shaposhnik 
+1 LGTM!

On Tue, Jun 21, 2016 at 1:55 PM, Swapnil Bawaskar  wrote:
> +1
> I am convinced.
> Made the change: http://i.imgur.com/41w9yWm.png
>
> On Tue, Jun 21, 2016 at 11:54 AM, Gregory Chase  wrote:
>
>> I'm +0 to "Multi-site", but like "multi-cluster" slightly better for two
>> reasons...
>>
>> 1) It comes after "Clustering", showing a ++ more clearly
>> 2) In my opinion its more inclusive of both "multi-site" and also workload
>> partitioning where two clusters might be in the same data center, but have
>> different applications they serve.
>>
>> Thoughts?
>>
>> On Tue, Jun 21, 2016 at 11:49 AM, John Blum  wrote:
>>
>> > +1
>> >
>> > On Tue, Jun 21, 2016 at 11:43 AM, Swapnil Bawaskar > >
>> > wrote:
>> >
>> > > Take 3: http://i.imgur.com/VUQRw4u.png
>> > > 1. Replaced Redis logo with http://fontawesome.io/icon/plug/
>> > > 2. Changed WAN to Multi-Site.
>> > >
>> > > Thanks!
>> > > Swapnil.
>> > >
>> > > On Sat, Jun 18, 2016 at 7:22 PM, theseusyang 
>> > > wrote:
>> > >
>> > > > I agree with Greg, "Multi-Cluster"  is accurated especially for
>> > > > cluster-2-cluster replication in one DC site.
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > View this message in context:
>> > > >
>> > >
>> >
>> http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/update-website-for-WAN-CQ-and-native-client-tp6659p6763.html
>> > > > Sent from the Apache Geode (Incubating) Developers Forum mailing list
>> > > > archive at Nabble.com.
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > -John
>> > 503-504-8657
>> > john.blum10101 (skype)
>> >
>>
>>
>>
>> --
>> Greg Chase
>>
>> Global Head, Big Data Communities
>> http://www.pivotal.io/big-data
>>
>> Pivotal Software
>> http://www.pivotal.io/
>>
>> 650-215-0477
>> @GregChase
>> Blog: http://geekmarketing.biz/
>>

[GitHub] incubator-geode pull request #172: GEODE-1574: Remove quotes for negative nu...

2016-06-22 Thread gracemeilen 
GitHub user gracemeilen opened a pull request:

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

GEODE-1574: Remove quotes for negative numbers in option values


* Test for CommandRequest

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

$ git pull https://github.com/gracemeilen/incubator-geode feature/GEODE-1574

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

https://github.com/apache/incubator-geode/pull/172.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 #172


commit 6d86bd590635af430cd0487aab7b93bee291f183
Author: gmeilen 
Date:   2016-06-22T00:01:28Z

GEODE-1574: Remove quotes around negative numbers in command option values

* Test for CommandRequest




---
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.
---

Re: Apache Geode incubation

2016-06-22 Thread Roman Shaposhnik 
On Tue, Jun 21, 2016 at 7:39 PM, Niall Pemberton
 wrote:
> On Tue, Jun 21, 2016 at 3:13 PM, Greg Chase  wrote:
>
>> The community is of course thinking about it. That is the point of the
>> Incubator program.
>>
>> However, I imagine we will be asking about graduation after the release of
>> Geode 1.0 GA.
>>
>
> Getting the mechanics of releases right and showing the IPMC that the
> project understand how to do that is important. What I particularly liked
> about this projects 2nd (M2) release was not just the +1 votes, but the
> qualifications that accompanied those votes ("I checked the sigs", "I built
> & ran the tests" etc) - I see that and it gives me confidence that this is
> not a rubber stamping exercise, but the project members are exercising
> their responsibilities with care & attention. In terms of meeting the
> graduation criteria, geode will almost certainly have ticked that box in
> terms of graduation with another release. Obviously users place great
> importance and judge releases on labels such as "milestone", "beta" or "GA"
> etc - but from an ASF perspective these are not relevant as "quality of
> release" is judged on different criteria (licensing, process etc) and by
> those criteria theres no difference between an M1 or a GA release. From
> that perspective, my opinion is that geode is doing a great job and will
> probably have nailed it with the upcoming M3 release.
>
> From what I see, geode has got all its legal ducks in a row (code grants,
> source headers, license compatibility) and so the last and main graduation
> criteria it needs to meet relate to community[1]. IMO this is the most
> difficult (and important) of all the criteria, its also more subjective to
> judge and from a project that entered from a single company the hardest to
> satisfy. From what I see on the mailing list, this is a great community and
> meets the "openness" criteria - its a welcoming place, people
> discuss/disagree and come to a consensus in the way that the ASF expects.
> The one question I have is "are all the discussions/decisions being brought
> to this mailing list?" - as an observer, it looks to me like that is
> happening - but only the project members can confirm that. If the answer is
> yes, then thats another tick in the box. New committers have been voted in
> and (AIUI) this is not just from Pivotal, but other "legally independent"
> people, so growing the community is also met. Lastly is the "diversity"
> question and this is probably the hardest to give a definitive answer. The
> IPMC seems to have moved from the prescriptive criteria laid out in the
> link below to a more judgement based approach and it would be a good idea
> to discuss this with your mentors and/or sound out the wider IPMC on how
> geode can meet this criteria. Obviously the more new independent people you
> recruit, the better for this - but would be good to know how near or far
> you are from meeting that. The one thing I would say is that alot of people
> were put on the initial incubator proposal (70+ I believe) and I would
> recommend reviewing that when you decide to go for graduation and removing
> anyone who has not been active (easy enough to vote them back in later if
> they start contributing) as I'm sure that will help with the balance as
> well as reflecting reality.

Niall, thanks a million for your extremely thoughtful reply. With my
mentor hat on,
I wholeheartedly agree with all the points you made. I really do think
the community
is on a trajectory to graduate relatively soon.

Given that, now would be a perfect time to start bringing up concerns
and suggestions
along the lines of what you've mentioned in your last sentence.

Thanks,
Roman.

Re: update website for WAN, CQ and native client

2016-06-22 Thread Udo Kohlmeyer 

+1,

to me "Multi-site" is too rigid. People might forget that this is a 
inter-cluster comms channel. Which would allow them to have many 
clusters running in the same DC, sharing data between them, satisfying 
the data requirements for different systems/applications.



On 22/06/2016 4:54 AM, Gregory Chase wrote:

I'm +0 to "Multi-site", but like "multi-cluster" slightly better for two
reasons...

1) It comes after "Clustering", showing a ++ more clearly
2) In my opinion its more inclusive of both "multi-site" and also workload
partitioning where two clusters might be in the same data center, but have
different applications they serve.

Thoughts?

On Tue, Jun 21, 2016 at 11:49 AM, John Blum  wrote:


+1

On Tue, Jun 21, 2016 at 11:43 AM, Swapnil Bawaskar 
wrote:


Take 3: http://i.imgur.com/VUQRw4u.png
1. Replaced Redis logo with http://fontawesome.io/icon/plug/
2. Changed WAN to Multi-Site.

Thanks!
Swapnil.

On Sat, Jun 18, 2016 at 7:22 PM, theseusyang 
wrote:


I agree with Greg, "Multi-Cluster"  is accurated especially for
cluster-2-cluster replication in one DC site.



--
View this message in context:


http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/update-website-for-WAN-CQ-and-native-client-tp6659p6763.html

Sent from the Apache Geode (Incubating) Developers Forum mailing list
archive at Nabble.com.




--
-John
503-504-8657
john.blum10101 (skype)

Re: Apache Geode incubation

2016-06-22 Thread William Markito 
Thanks a lot Niall and Roman for your thoughtful comments!  It's really
great to read all this and see where we are as a project!!



On Wed, Jun 22, 2016 at 11:12 AM, Roman Shaposhnik 
wrote:

> On Tue, Jun 21, 2016 at 7:39 PM, Niall Pemberton
>  wrote:
> > On Tue, Jun 21, 2016 at 3:13 PM, Greg Chase  wrote:
> >
> >> The community is of course thinking about it. That is the point of the
> >> Incubator program.
> >>
> >> However, I imagine we will be asking about graduation after the release
> of
> >> Geode 1.0 GA.
> >>
> >
> > Getting the mechanics of releases right and showing the IPMC that the
> > project understand how to do that is important. What I particularly liked
> > about this projects 2nd (M2) release was not just the +1 votes, but the
> > qualifications that accompanied those votes ("I checked the sigs", "I
> built
> > & ran the tests" etc) - I see that and it gives me confidence that this
> is
> > not a rubber stamping exercise, but the project members are exercising
> > their responsibilities with care & attention. In terms of meeting the
> > graduation criteria, geode will almost certainly have ticked that box in
> > terms of graduation with another release. Obviously users place great
> > importance and judge releases on labels such as "milestone", "beta" or
> "GA"
> > etc - but from an ASF perspective these are not relevant as "quality of
> > release" is judged on different criteria (licensing, process etc) and by
> > those criteria theres no difference between an M1 or a GA release. From
> > that perspective, my opinion is that geode is doing a great job and will
> > probably have nailed it with the upcoming M3 release.
> >
> > From what I see, geode has got all its legal ducks in a row (code grants,
> > source headers, license compatibility) and so the last and main
> graduation
> > criteria it needs to meet relate to community[1]. IMO this is the most
> > difficult (and important) of all the criteria, its also more subjective
> to
> > judge and from a project that entered from a single company the hardest
> to
> > satisfy. From what I see on the mailing list, this is a great community
> and
> > meets the "openness" criteria - its a welcoming place, people
> > discuss/disagree and come to a consensus in the way that the ASF expects.
> > The one question I have is "are all the discussions/decisions being
> brought
> > to this mailing list?" - as an observer, it looks to me like that is
> > happening - but only the project members can confirm that. If the answer
> is
> > yes, then thats another tick in the box. New committers have been voted
> in
> > and (AIUI) this is not just from Pivotal, but other "legally independent"
> > people, so growing the community is also met. Lastly is the "diversity"
> > question and this is probably the hardest to give a definitive answer.
> The
> > IPMC seems to have moved from the prescriptive criteria laid out in the
> > link below to a more judgement based approach and it would be a good idea
> > to discuss this with your mentors and/or sound out the wider IPMC on how
> > geode can meet this criteria. Obviously the more new independent people
> you
> > recruit, the better for this - but would be good to know how near or far
> > you are from meeting that. The one thing I would say is that alot of
> people
> > were put on the initial incubator proposal (70+ I believe) and I would
> > recommend reviewing that when you decide to go for graduation and
> removing
> > anyone who has not been active (easy enough to vote them back in later if
> > they start contributing) as I'm sure that will help with the balance as
> > well as reflecting reality.
>
> Niall, thanks a million for your extremely thoughtful reply. With my
> mentor hat on,
> I wholeheartedly agree with all the points you made. I really do think
> the community
> is on a trajectory to graduate relatively soon.
>
> Given that, now would be a perfect time to start bringing up concerns
> and suggestions
> along the lines of what you've mentioned in your last sentence.
>
> Thanks,
> Roman.
>



-- 

~/William

Re: Creating & Destroying Regions programmatically

2016-06-22 Thread Swapnil Bawaskar 
Hi Kevin,
You can use com.gemstone.gemfire.cache.DynamicRegionFactory from the client
to exercise CreateRegion and DestroyRegion.

On Wed, Jun 22, 2016 at 8:43 AM, Kevin Duling  wrote:

> I'm trying to figure out how to exercise the CreateRegion and
> DestoryRegion classes from a client in order to test authorization.  I
> can't figure out what the API would be for a client to trigger the
> cmdExecute() call on the server.
>
> For example, I was able to hit it in ClearRegion by having the client
> execute the Region.clear() method.  Here's a snippet from the unit
> test:
>
> SerializableRunnable clearAuthorized = new SerializableRunnable() {
>   @Override
>   public void run() {
> Cache cache =
> SecurityTestUtils.createCacheClient("authRegionUser", "1234567",
> serverPort, SecurityTestUtils.NO_EXCEPTION);
> final Region region = cache.getRegion(SecurityTestUtils.REGION_NAME);
> region.clear();
> cache.close();
>   }
> };
> client2.invoke(clearAuthorized);
>

Review Request 49101: GEODE-1546: Proxy server may not be able to send message to other servers to clean up transactions initiated by a shutdown client

2016-06-22 Thread Eric Shu 

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

Review request for geode, Darrel Schneider and Swapnil Bawaskar.


Bugs: GEODE-1546
https://issues.apache.org/jira/browse/GEODE-1546


Repository: geode


Description
---

Move transactionTimeToLive setting in TXManagerImpl.
Update proxy server to track the latest proxy after failover.
Expire client transactions if they do not fail over to new proxy servers and 
after transaction timeout period.
Add test cases for the above scenario.
Refactored the test code and made transactionTimeToLive setting adjustable to 
reduce test running time.


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/AbstractCacheServer.java
 c9648a3 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/CacheServerImpl.java
 2c72410 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/RemoteOperationMessage.java
 db5bcca 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXManagerImpl.java 
1ea7f71 
  geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXState.java 
c42f63c 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXStateProxy.java 
ba9866e 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/TXStateProxyImpl.java
 0939ab0 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/partitioned/PartitionMessage.java
 14fce08 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/AcceptorImpl.java
 ffcb8c5 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/BaseCommand.java
 bdebb6b 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/CacheClientNotifier.java
 30ab4a4 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/ClientHealthMonitor.java
 eb701fb 
  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/xmlcache/CacheServerCreation.java
 22d684f 
  
geode-core/src/test/java/com/gemstone/gemfire/disttx/DistributedTransactionDUnitTest.java
 8f962f7 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/ClientServerTransactionDUnitTest.java
 860833e 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/tier/sockets/AcceptorImplJUnitTest.java
 7c52a89 

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


Testing
---

precheckin


Thanks,

Eric Shu

Build failed in Jenkins: Geode-nightly #508

2016-06-22 Thread Apache Jenkins Server 
See 

Changes:

[dbarnes] GEODE-1209: Typo repair in javadoc comment (AsynEventQueue ->

--
Started by timer
[EnvInject] - Loading node environment variables.
Installing f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8\jdk.exe
[latest1.8] $ f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8\jdk.exe 
/s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress 
INSTALLDIR=f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8 /L 
f:\jenkins\jenkins-slave\tools\hudson.model.JDK\install2457559931083115432log
Building remotely on windows-2012-1 (Windows) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/incubator-geode.git
 > git init  # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/incubator-geode.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/incubator-geode.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/incubator-geode.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/incubator-geode.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/incubator-geode.git
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/incubator-geode.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision fc42db82e002fbe476fd9ffa01777b568ef58dba 
(refs/remotes/origin/develop)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f fc42db82e002fbe476fd9ffa01777b568ef58dba # timeout=10
 > git branch -a # timeout=10
 > git rev-parse "remotes/origin/GEODE-1372^{commit}" # timeout=10
 > git rev-parse "remotes/origin/asf-site^{commit}" # timeout=10
 > git rev-parse "remotes/origin/asf/asf-site^{commit}" # timeout=10
 > git rev-parse "remotes/origin/develop^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-10^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1017^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1040^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1056^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1096^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-11^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1109^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1153^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1186^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-12^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1209^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1269^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1276^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1369^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1370^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1371^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1372^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1374^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1376^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1392^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-14^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-14-2^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1452^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1464^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1493^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1565^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1567^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1571^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-1573^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-16^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-17^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-17-2^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-178^{commit}" # timeout=10
 > git rev-parse "remotes/origin/feature/GEODE-217^{commit}" # timeout=10
 > git rev-parse

Re: Build failed in Jenkins: Geode-nightly #508

2016-06-22 Thread Mark Bretl 
This was run in a Windows system, which would be fine In the future when
Ubuntu runs on Windows, however until then I will add another exclusion to
the node label.

--Mark

On Wednesday, June 22, 2016, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See 
>
> Changes:
>
> [dbarnes] GEODE-1209: Typo repair in javadoc comment (AsynEventQueue ->
>
> --
> Started by timer
> [EnvInject] - Loading node environment variables.
> Installing
> f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8\jdk.exe
> [latest1.8] $
> f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8\jdk.exe /s
> ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress
> INSTALLDIR=f:\jenkins\jenkins-slave\tools\hudson.model.JDK\latest1.8 /L
> f:\jenkins\jenkins-slave\tools\hudson.model.JDK\install2457559931083115432log
> Building remotely on windows-2012-1 (Windows) in workspace <
> https://builds.apache.org/job/Geode-nightly/ws/>
> Cloning the remote Git repository
> Cloning repository
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git
>  > git init  # timeout=10
> Fetching upstream changes from
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git
>  > git --version # timeout=10
>  > git -c core.askpass=true fetch --tags --progress
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git
> +refs/heads/*:refs/remotes/origin/*
>  > git config remote.origin.url
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git # timeout=10
>  > git config --add remote.origin.fetch
> +refs/heads/*:refs/remotes/origin/* # timeout=10
>  > git config remote.origin.url
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git # timeout=10
> Fetching upstream changes from
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git
>  > git -c core.askpass=true fetch --tags --progress
> https://git-wip-us.apache.org/repos/asf/incubator-geode.git
> +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
>  > git rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
> Checking out Revision fc42db82e002fbe476fd9ffa01777b568ef58dba
> (refs/remotes/origin/develop)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f fc42db82e002fbe476fd9ffa01777b568ef58dba # timeout=10
>  > git branch -a # timeout=10
>  > git rev-parse "remotes/origin/GEODE-1372^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/asf-site^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/asf/asf-site^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/develop^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-10^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1017^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1040^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1056^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1096^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-11^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1109^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1153^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1186^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-12^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1209^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1269^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1276^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1369^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1370^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1371^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1372^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1374^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1376^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1392^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-14^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-14-2^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1452^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1464^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1493^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1565^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1567^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1571^{commit}" # timeout=10
>  > git rev-parse "remotes/origin/feature/GEODE-1573^{commit}" # timeout=10
>  > git rev-parse

Donation of Geode Docs [was: Re: What will it take to release geode 1.0?]

2016-06-22 Thread Niall Pemberton 
On Fri, Apr 29, 2016 at 10:28 PM, Dave Barnes  wrote:

> We plan at some point to donate the docs so they'll be incorporated into
> the repo. Is this a prerequisite to graduating from incubation?
>

What is the status of the docs being donated? I raise this because the
Cassandra project was recently given a hard time by a board member about
docs hosted on a vendor site[1].

[1] http://markmail.org/message/uqsizgjxi7lwjcv7

Niall

Re: Donation of Geode Docs [was: Re: What will it take to release geode 1.0?]

2016-06-22 Thread Gregory Chase 
This is an interesting topic.

I've noted Planet Cassandra has free high quality vendor support on behalf
of the Apache Cassandra project.

What is appropriate in terms of core content in the community versus
adjunct members of the community such as companies to create derivative
works?

I could imagine the collaborative authoring of documentation might take
place on the wiki, for example. However companies interested in creating
commercial derivatives might choose to take this content, do additional
editing, add proprietary value-added information, and lay it out in a more
visually pleasing manner.

-Greg

On Wed, Jun 22, 2016 at 5:54 PM, Niall Pemberton 
wrote:

> On Fri, Apr 29, 2016 at 10:28 PM, Dave Barnes  wrote:
>
> > We plan at some point to donate the docs so they'll be incorporated into
> > the repo. Is this a prerequisite to graduating from incubation?
> >
>
> What is the status of the docs being donated? I raise this because the
> Cassandra project was recently given a hard time by a board member about
> docs hosted on a vendor site[1].
>
> [1] http://markmail.org/message/uqsizgjxi7lwjcv7
>
> Niall
>



-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Donation of Geode Docs [was: Re: What will it take to release geode 1.0?]

2016-06-22 Thread Nitin Lamba 
>From a technology readiness perspective, hosting the docs on a different
(Apache) site should not be too hard; I've built the docs locally and on
AWS without any major issues.

Irrespective of the hosting location, the content license needs to be fixed
- as per the current github repo [1], it still has Pivotal copyright though
the generated pages (ruby/ markdown to HTML) has ASF copyright in the
footer.

Nitin
[1] https://github.com/project-geode/docs


On Wed, Jun 22, 2016 at 6:10 PM, Gregory Chase  wrote:

> This is an interesting topic.
>
> I've noted Planet Cassandra has free high quality vendor support on behalf
> of the Apache Cassandra project.
>
> What is appropriate in terms of core content in the community versus
> adjunct members of the community such as companies to create derivative
> works?
>
> I could imagine the collaborative authoring of documentation might take
> place on the wiki, for example. However companies interested in creating
> commercial derivatives might choose to take this content, do additional
> editing, add proprietary value-added information, and lay it out in a more
> visually pleasing manner.
>
> -Greg
>
> On Wed, Jun 22, 2016 at 5:54 PM, Niall Pemberton <
> niall.pember...@gmail.com>
> wrote:
>
> > On Fri, Apr 29, 2016 at 10:28 PM, Dave Barnes 
> wrote:
> >
> > > We plan at some point to donate the docs so they'll be incorporated
> into
> > > the repo. Is this a prerequisite to graduating from incubation?
> > >
> >
> > What is the status of the docs being donated? I raise this because the
> > Cassandra project was recently given a hard time by a board member about
> > docs hosted on a vendor site[1].
> >
> > [1] http://markmail.org/message/uqsizgjxi7lwjcv7
> >
> > Niall
> >
>
>
>
> --
> Greg Chase
>
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>

Review Request 49103: Removing flaky test label from tests with fixed bugs.

2016-06-22 Thread Dan Smith 

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

Review request for geode, Anthony Baker and Kirk Lund.


Repository: geode


Description
---

Removing flaky test label from tests with fixed bugs.


Diffs
-

  
geode-core/src/test/java/com/gemstone/gemfire/cache/ConnectionPoolDUnitTest.java
 3ae6cf6fd3270ee6d8d75b302d8bd18cf31d4887 
  
geode-core/src/test/java/com/gemstone/gemfire/cache/client/internal/pooling/ConnectionManagerJUnitTest.java
 28a53421792271f0fb6c08176555aa5c51b47eb2 
  
geode-core/src/test/java/com/gemstone/gemfire/cache/query/dunit/QueryUsingPoolDUnitTest.java
 4672a94115e0857dc6eb0bb1346c2bf006693f72 
  
geode-core/src/test/java/com/gemstone/gemfire/cache30/ClientMembershipDUnitTest.java
 dc6af7a3307f9a4ec3ee5166f6e9ea0e55590823 
  
geode-core/src/test/java/com/gemstone/gemfire/distributed/LocatorDUnitTest.java 
197a66595618036d4cf1b0aaffd2c1ad9881aac2 
  
geode-core/src/test/java/com/gemstone/gemfire/distributed/internal/LocatorLoadSnapshotIntegrationTest.java
 08648d9ca94f4fe94c1a7f179dc4f2205c00b50a 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/ScheduledThreadPoolExecutorWithKeepAliveJUnitTest.java
 5aaa124faa08f545019c0d879f3e97b0eff84fd9 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/SingleHopStatsDUnitTest.java
 ffcca1c786a3d4f755172caac8774713e92d7ecb 
  
geode-core/src/test/java/com/gemstone/gemfire/management/UniversalMembershipListenerAdapterDUnitTest.java
 5457ed388f958ca383c87eba5b570c001ffc240d 
  
geode-cq/src/test/java/com/gemstone/gemfire/cache/query/cq/dunit/CqPerfUsingPoolDUnitTest.java
 0168419bea8a39da973a7071224f659c94905fea 
  
geode-cq/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/ClientCommandsDUnitTest.java
 594788342190a15863fbadbb8c37db7b76fe1907 
  
geode-cq/src/test/java/com/gemstone/gemfire/security/ClientAuthzObjectModDUnitTest.java
 12fdea84d1467962ccb18401cd7b12fd66ff5ca6 
  
geode-wan/src/test/java/com/gemstone/gemfire/cache/CacheXml70GatewayDUnitTest.java
 b827ae6b34b67ca499a18bba57658bb3ddd847d7 
  
geode-wan/src/test/java/com/gemstone/gemfire/internal/cache/wan/CacheClientNotifierDUnitTest.java
 64b1906bc63a54af1ac1f99459c5271d4d9f5c63 
  
geode-wan/src/test/java/com/gemstone/gemfire/internal/cache/wan/parallel/ParallelWANPersistenceEnabledGatewaySenderDUnitTest.java
 443d5926ed3d480c14ece03f76ffa5ff000889bc 

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


Testing
---


Thanks,

Dan Smith