Build failed in Jenkins: Geode-nightly #820

2017-04-29 Thread Apache Jenkins Server 
See 


Changes:

[jstewart] GEODE-2795: Clean up DUnit VMs after dynamically changing 'user.dir'

[jiliao] GEODE-2840: add a DUnit test to test concurrent deploy

--
[...truncated 161.62 KB...]
: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/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
Note: 

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

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
Download 
https://repo1.maven.org/maven2/com/google/code/gson/gson/2.8.0/gson-2.8.0.pom
Download 
https://repo1.maven.org/maven2/com/google/code/gson/gson-parent/2.8.0/gson-parent-2.8.0.pom
Download 
https://repo1.maven.org/maven2/com/google/code/gson/gson/2.8.0/gson-2.8.0.jar
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:spotlessJavaCheck
:geode-rebalancer:spotlessCheck
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan: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-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:spotlessJavaCheck
:geode-wan:spotlessCheck
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web: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-web:processTestResources UP-TO-DATE
:geode-web:testClasses
:geode-web:checkMissedTests
:geode-web:spotlessJavaCheck
:geode-web:spotlessCheck
:geode-web:test
:geode-web:check
:geode-web:build
:geode-web:distributedTest
:geode-web:fl

[GitHub] geode-examples pull request #5: Fix broken links to geode docs.

2017-04-29 Thread sboorlagadda 
GitHub user sboorlagadda opened a pull request:

https://github.com/apache/geode-examples/pull/5

Fix broken links to geode docs.

   Links to `How To Install` and `Geode in 15 min` are
   now refer to 1.1.0 docs for now.

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

$ git pull https://github.com/sboorlagadda/geode-examples fix_broken_links

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

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


commit 62fdb48caa3277d827b7e8a5bc05daf87252bb25
Author: Sai Boorlagadda 
Date:   2017-04-29T18:43:33Z

Fix broken links to geode docs.

   Links to `How To Install` and `Geode in 15 min` are
   now refer to 1.1.0 docs 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-examples pull request #5: Fix broken links to geode docs.

2017-04-29 Thread sboorlagadda 
Github user sboorlagadda closed the pull request at:

https://github.com/apache/geode-examples/pull/5


---
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-examples pull request #6: Fix broken links to geode docs.

2017-04-29 Thread sboorlagadda 
GitHub user sboorlagadda opened a pull request:

https://github.com/apache/geode-examples/pull/6

Fix broken links to geode docs.

   Links to `How To Install` and `Geode in 15 min` are
   now refer to 1.1.0 docs for now.

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

$ git pull https://github.com/sboorlagadda/geode-examples fix_broken_links

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

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


commit 6e70a0e72e0abb01e414021626f13226683bc460
Author: Sai Boorlagadda 
Date:   2017-04-29T18:43:33Z

Fix broken links to geode docs.

   Links to `How To Install` and `Geode in 15 min` are
   now refer to 1.1.0 docs 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.
---

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

2017-04-29 Thread Spring CI 

---
Spring Data GemFire > Nightly-ApacheGeode > #539 was successful.
---
Scheduled
1845 tests in total.

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





--
This message is automatically generated by Atlassian Bamboo

[jira] [Created] (GEODE-2853) Change of locator list request interval

2017-04-29 Thread Masaki Yamakawa (JIRA) 
Masaki Yamakawa created GEODE-2853:
--

 Summary: Change of locator list request interval
 Key: GEODE-2853
 URL: https://issues.apache.org/jira/browse/GEODE-2853
 Project: Geode
  Issue Type: Improvement
  Components: client/server
Reporter: Masaki Yamakawa


If you connect to a Geode cluster using a locator from the client, the locator 
list request will be executed at regular intervals in the background thread. I 
want to tune this interval. I understand that this interval can be changed by 
the ping-interval of the Pool attribute. However, I think that ping-interval 
originally sets the ping interval for health check to the cache server. 
Therefore, it is not possible to change the locator list request interval 
without changing the health check interval to the cache server. So,I want to 
add a java system property that can change the locator list request interval.

The locator list request interval is determined by the following priority order.

  1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
  2. ping-interval of the Pool attribute

In addition, when changing this time, the background thread is activated only 
when this value is a positive value.




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

[jira] [Updated] (GEODE-2853) Change of locator list request interval

2017-04-29 Thread Masaki Yamakawa (JIRA) 

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

Masaki Yamakawa updated GEODE-2853:
---
Priority: Minor  (was: Major)

> Change of locator list request interval
> ---
>
> Key: GEODE-2853
> URL: https://issues.apache.org/jira/browse/GEODE-2853
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Masaki Yamakawa
>Priority: Minor
>
> If you connect to a Geode cluster using a locator from the client, the 
> locator list request will be executed at regular intervals in the background 
> thread. I want to tune this interval. I understand that this interval can be 
> changed by the ping-interval of the Pool attribute. However, I think that 
> ping-interval originally sets the ping interval for health check to the cache 
> server. Therefore, it is not possible to change the locator list request 
> interval without changing the health check interval to the cache server. So,I 
> want to add a java system property that can change the locator list request 
> interval.
> The locator list request interval is determined by the following priority 
> order.
>   1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
>   2. ping-interval of the Pool attribute
> In addition, when changing this time, the background thread is activated only 
> when this value is a positive value.



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

[jira] [Updated] (GEODE-2832) Fixing the link of README.md

2017-04-29 Thread Masaki Yamakawa (JIRA) 

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

Masaki Yamakawa updated GEODE-2832:
---
Priority: Minor  (was: Major)

> Fixing the link of README.md
> 
>
> Key: GEODE-2832
> URL: https://issues.apache.org/jira/browse/GEODE-2832
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Masaki Yamakawa
>Priority: Minor
>
> Fixed an error in Markdown link notation of README.md.
> - Delete the space between the display name and the destination URL.
> - Fixed link destination of native-client-intro.html
> - Fixed link of BUILDING.md



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

[jira] [Updated] (GEODE-2812) Add API to get list of live locators

2017-04-29 Thread Masaki Yamakawa (JIRA) 

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

Masaki Yamakawa updated GEODE-2812:
---
Priority: Minor  (was: Major)

> Add API to get list of live locators
> 
>
> Key: GEODE-2812
> URL: https://issues.apache.org/jira/browse/GEODE-2812
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Masaki Yamakawa
>Priority: Minor
>
> There is a Geode cluster using a logical member group, and from the client, 
> the connection pool to the logical member group is connected using the 
> PoolFactory API at the timing when connection becomes necessary.
> At this time, even though the locator that was running at the initial 
> connection stops due to reasons such as regular maintenance etc., even if the 
> alternate locator is started before maintenance, I can not connect to the 
> locator in the static initial list.
> # Client side:PoolManager.createFactory().addLocator("localhost", 
> 10334).setServerGroup("GroupA").create("pool1");
> # Geode cluster:start locator [ localhost:10335 ].
> # Geode cluster:stop locator [ localhost:10334 ].
> # Client side:PoolManager.createFactory().addLocator("localhost", 
> 10334).setServerGroup("GroupB").create("pool2");
> Therefore, I would like to decide the connection destination based on the 
> live locator list of another logical member group.
> I added an API that can get the list of live locators from the Pool. Use the 
> API as follows:
> {code:java|borderStyle=solid}
> Pool pool = PoolManager.createFactory()
>   .addLocator("localhost", 10334)
>   .setSubscriptionEnabled(true).setServerGroup("GroupA")
>   .create("GroupAPool");
> List = pool.getLiveLocators();
> {code}
> {quote}
> Note:
> The list of live locators gets the result of the UpdateLocatorListTask 
> periodically running in AutoConnectionSourceImpl.
> Therefore, whether or not it is alive will cause a time lag, depending on the 
> task execution interval.
> Also, the result of ExplicitConnectionSourceImpl without using a locator is 
> always empty.
> {quote}



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

[jira] [Commented] (GEODE-2853) Change of locator list request interval

2017-04-29 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user masaki-yamakawa opened a pull request:

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

GEODE-2853: Change of locator list request interval

If you connect to a Geode cluster using a locator from the client, the 
locator list request will be executed at regular intervals in the background 
thread. I want to tune this interval. I understand that this interval can be 
changed by the ping-interval of the Pool attribute. However, I think that 
ping-interval originally sets the ping interval for health check to the cache 
server. Therefore, it is not possible to change the locator list request 
interval without changing the health check interval to the cache server. So,I 
want to add a java system property that can change the locator list request 
interval.

The locator list request interval is determined by the following priority 
order.

  1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
  2. ping-interval of the Pool attribute

In addition, when changing this time, the background thread is activated 
only when this value is a positive value.

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

$ git pull https://github.com/masaki-yamakawa/geode feature/GEODE-2853

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

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


commit f909d4fb7dcdf5dfc0f122663169324788fe5538
Author: masaki.yamakawa 
Date:   2017-04-30T04:38:10Z

GEODE-2853: Change of locator list request interval

If you connect to a Geode cluster using a locator from the client, the
locator list request will be executed at regular intervals in the
background thread. I want to tune this interval. I understand that this
interval can be changed by the ping-interval of the Pool attribute.
However, I think that ping-interval originally sets the ping interval
for health check to the cache server. Therefore, it is not possible to
change the locator list request interval without changing the health
check interval to the cache server. So,I want to add a java system
property that can change the locator list request interval.

The locator list request interval is determined by the following
priority order.

  1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
  2. ping-interval of the Pool attribute

In addition, when changing this time, the background thread is activated
only when this value is a positive value.




> Change of locator list request interval
> ---
>
> Key: GEODE-2853
> URL: https://issues.apache.org/jira/browse/GEODE-2853
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Masaki Yamakawa
>Priority: Minor
>
> If you connect to a Geode cluster using a locator from the client, the 
> locator list request will be executed at regular intervals in the background 
> thread. I want to tune this interval. I understand that this interval can be 
> changed by the ping-interval of the Pool attribute. However, I think that 
> ping-interval originally sets the ping interval for health check to the cache 
> server. Therefore, it is not possible to change the locator list request 
> interval without changing the health check interval to the cache server. So,I 
> want to add a java system property that can change the locator list request 
> interval.
> The locator list request interval is determined by the following priority 
> order.
>   1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
>   2. ping-interval of the Pool attribute
> In addition, when changing this time, the background thread is activated only 
> when this value is a positive value.



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

[GitHub] geode pull request #483: GEODE-2853: Change of locator list request interval

2017-04-29 Thread masaki-yamakawa 
GitHub user masaki-yamakawa opened a pull request:

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

GEODE-2853: Change of locator list request interval

If you connect to a Geode cluster using a locator from the client, the 
locator list request will be executed at regular intervals in the background 
thread. I want to tune this interval. I understand that this interval can be 
changed by the ping-interval of the Pool attribute. However, I think that 
ping-interval originally sets the ping interval for health check to the cache 
server. Therefore, it is not possible to change the locator list request 
interval without changing the health check interval to the cache server. So,I 
want to add a java system property that can change the locator list request 
interval.

The locator list request interval is determined by the following priority 
order.

  1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
  2. ping-interval of the Pool attribute

In addition, when changing this time, the background thread is activated 
only when this value is a positive value.

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

$ git pull https://github.com/masaki-yamakawa/geode feature/GEODE-2853

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

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


commit f909d4fb7dcdf5dfc0f122663169324788fe5538
Author: masaki.yamakawa 
Date:   2017-04-30T04:38:10Z

GEODE-2853: Change of locator list request interval

If you connect to a Geode cluster using a locator from the client, the
locator list request will be executed at regular intervals in the
background thread. I want to tune this interval. I understand that this
interval can be changed by the ping-interval of the Pool attribute.
However, I think that ping-interval originally sets the ping interval
for health check to the cache server. Therefore, it is not possible to
change the locator list request interval without changing the health
check interval to the cache server. So,I want to add a java system
property that can change the locator list request interval.

The locator list request interval is determined by the following
priority order.

  1. java system property "gemfire.LOCATOR_UPDATE_INTERVAL"
  2. ping-interval of the Pool attribute

In addition, when changing this time, the background thread is activated
only when this value is a positive value.




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