[GitHub] geode pull request #506: GEODE-2900: DUnit test of moving primary during AEQ...

[upthewaterspout]

GitHub user upthewaterspout opened a pull request:

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

GEODE-2900: DUnit test of moving primary during AEQ dispatching

Adding a dunit test that moves the primary and moves it again during AEQ
dispatching.

@jhuynh1  - I based this test on top of your PR for GEODE-2900. Feel free 
to merge it in if the test looks good to you. This test fails without your 
changes and passes with those changes.

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

$ git pull https://github.com/upthewaterspout/incubator-geode 
feature/GEODE-2900-test

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

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


commit 7cf0be13ed2abe9a707a2b4fe0ded66f0870da77
Author: Dan Smith 
Date:   2017-05-10T23:32:05Z

GEODE-2900: DUnit test of moving primary during AEQ dispatching

Adding a dunit test that moves the primary and moves it again during AEQ
dispatching.




---
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-2898) A non-responsive SSL client can block a server's "acceptor" thread

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-2898.
-
   Resolution: Fixed
Fix Version/s: 1.2.0

> A non-responsive SSL client can block a server's "acceptor" thread
> --
>
> Key: GEODE-2898
> URL: https://issues.apache.org/jira/browse/GEODE-2898
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> During the handoff to the handshake thread pool the accept thread can be 
> blocked in the SSL handshake. The SSL handshake should be moved to the 
> handshake thread pool. The goal is allow the server to reject clients that 
> haven't finished the handshake in the allotted time.



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

[jira] [Closed] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt closed GEODE-2898.
---

> A non-responsive SSL client can block a server's "acceptor" thread
> --
>
> Key: GEODE-2898
> URL: https://issues.apache.org/jira/browse/GEODE-2898
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
> Fix For: 1.2.0
>
>
> During the handoff to the handshake thread pool the accept thread can be 
> blocked in the SSL handshake. The SSL handshake should be moved to the 
> handshake thread pool. The goal is allow the server to reject clients that 
> haven't finished the handshake in the allotted time.



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

[jira] [Commented] (GEODE-2898) A non-responsive SSL client can block a server's "acceptor" thread

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2898:


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

GEODE-2898 A non-responsive SSL client can block a server's "acceptor" thread

This moves the SSL handshake from the acceptor thread to the handshake thread
and adds a unit test.


> A non-responsive SSL client can block a server's "acceptor" thread
> --
>
> Key: GEODE-2898
> URL: https://issues.apache.org/jira/browse/GEODE-2898
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Bruce Schuchardt
>
> During the handoff to the handshake thread pool the accept thread can be 
> blocked in the SSL handshake. The SSL handshake should be moved to the 
> handshake thread pool. The goal is allow the server to reject clients that 
> haven't finished the handshake in the allotted time.



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

[jira] [Commented] (GEODE-2788) Add official Socket timeout parameter when connecting to servers/locators

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/geode/pull/474#discussion_r115865619
  
--- Diff: 
geode-core/src/main/resources/META-INF/schemas/geode.apache.org/schema/cache/cache-1.0.xsd
 ---
@@ -1191,6 +1191,7 @@ As of 6.5 disk-dirs is deprecated on 
region-attributes. Use disk-store-name inst
 
   
 
+
--- End diff --

BTW, if we change the XSD it needs to get posted on geode.apache.org via 
the asf-site branch of geode-site.


> Add official Socket timeout parameter when connecting to servers/locators
> -
>
> Key: GEODE-2788
> URL: https://issues.apache.org/jira/browse/GEODE-2788
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server, docs
>Reporter: Masaki Yamakawa
>Priority: Minor
>  Labels: patch
>
> When connecting from the client to the servers/locators, if the 
> servers/locators is not started, the connection can not be established and a 
> Socket timeout occurs.
> This timeout value is 59 seconds by default. This timeout value is too long. 
> This timeout value can be changed by specifying the unofficial parameter 
> "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I 
> corresponded so that it can be specified by official parameters.
> Like the NativeClient, the official parameters should be specified by 
> "connect-timeout" in gemfire.properties.
> Timeout values ​​are determined in the following order of priority.
> 1. java system property:gemfire.PoolImpl.HANDSHAKE_TIMEOUT
> 2. java system property:gemfire.connect-timeout
> 3. gemfire.properties:connect-timeout
> 4. default:59000 milli seconds
> As another idea, there is also an idea to make it possible to specify it as 
> an attribute of Pool. In that case NativeClient needs the same modification.



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

[GitHub] geode pull request #474: GEODE-2788: Add official Socket timeout parameter w...

[metatype]

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

https://github.com/apache/geode/pull/474#discussion_r115865619
  
--- Diff: 
geode-core/src/main/resources/META-INF/schemas/geode.apache.org/schema/cache/cache-1.0.xsd
 ---
@@ -1191,6 +1191,7 @@ As of 6.5 disk-dirs is deprecated on 
region-attributes. Use disk-store-name inst
 
   
 
+
--- End diff --

BTW, if we change the XSD it needs to get posted on geode.apache.org via 
the asf-site branch of geode-site.


---
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-2788) Add official Socket timeout parameter when connecting to servers/locators

[ASF GitHub Bot (JIRA)]

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

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

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/474
  
Masaki, this change set is breaking unit tests because the new XSD 
attribute is being put into XML files generated for older versions.  
CacheXml80DUnitTest, for instance, is breaking.  l80Please run the precheckin 
target before posting a fix and ensure that you're not breaking anything.  
Thanks

You should also add a test case in CacheXmlGeode10DUnitTest for the new 
attribute.

org.apache.geode.cache30.CacheXml80DUnitTest > testDefaultConnectionPool 
FAILED
org.apache.geode.cache.CacheXmlException: While reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML, caused by org.xml.sax.SAXParseException; lineNumber: 
4; columnNumber: 528; Attribute "socket-connect-timeout" must be declared for 
element type "pool".

org.xml.sax.SAXParseException; lineNumber: 4; columnNumber: 528; 
Attribute "socket-connect-timeout" must be declared for element type "pool".

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 91

[error 2017/05/10 12:12:11.923 PDT  tid=0x13] While 
reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML



> Add official Socket timeout parameter when connecting to servers/locators
> -
>
> Key: GEODE-2788
> URL: https://issues.apache.org/jira/browse/GEODE-2788
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server, docs
>Reporter: Masaki Yamakawa
>Priority: Minor
>  Labels: patch
>
> When connecting from the client to the servers/locators, if the 
> servers/locators is not started, the connection can not be established and a 
> Socket timeout occurs.
> This timeout value is 59 seconds by default. This timeout value is too long. 
> This timeout value can be changed by specifying the unofficial parameter 
> "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I 
> corresponded so that it can be specified by official parameters.
> Like the NativeClient, the official parameters should be specified by 
> "connect-timeout" in gemfire.properties.
> Timeout values ​​are determined in the following order of priority.
> 1. java system property:gemfire.PoolImpl.HANDSHAKE_TIMEOUT
> 2. java system property:gemfire.connect-timeout
> 3. gemfire.properties:connect-timeout
> 4. default:59000 milli seconds
> As another idea, there is also an idea to make it possible to specify it as 
> an attribute of Pool. In that case NativeClient needs the same modification.



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

[GitHub] geode issue #474: GEODE-2788: Add official Socket timeout parameter when con...

[bschuchardt]

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/474
  
Masaki, this change set is breaking unit tests because the new XSD 
attribute is being put into XML files generated for older versions.  
CacheXml80DUnitTest, for instance, is breaking.  l80Please run the precheckin 
target before posting a fix and ensure that you're not breaking anything.  
Thanks

You should also add a test case in CacheXmlGeode10DUnitTest for the new 
attribute.

org.apache.geode.cache30.CacheXml80DUnitTest > testDefaultConnectionPool 
FAILED
org.apache.geode.cache.CacheXmlException: While reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML, caused by org.xml.sax.SAXParseException; lineNumber: 
4; columnNumber: 528; Attribute "socket-connect-timeout" must be declared for 
element type "pool".

org.xml.sax.SAXParseException; lineNumber: 4; columnNumber: 528; 
Attribute "socket-connect-timeout" must be declared for element type "pool".

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 91

[error 2017/05/10 12:12:11.923 PDT  tid=0x13] While 
reading Cache XML 
file:/export/india2/users/bschuchardt/devel/gfdev/open/geode-core/build/distributedTest/XML_8_0/CacheXml80DUnitTest_testDefaultConnectionPool.xml.
 Error while parsing XML



---
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-254) Remove deprecated Region.keys and Region.entries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-254:
--

Github user dschneider-pivotal commented on the issue:

https://github.com/apache/geode/pull/504
  
+1 LGTM


> Remove deprecated Region.keys and Region.entries
> 
>
> Key: GEODE-254
> URL: https://issues.apache.org/jira/browse/GEODE-254
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Region.keys and Region.entries. Any calls can be simply 
> changed to Region.keySet and Region.entrySet so this should be an easy change.
> A large number of tests call the deprecated methods.



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

[GitHub] geode issue #504: GEODE-254: Removed deprecated Region.keys and Region.entri...

[dschneider-pivotal]

Github user dschneider-pivotal commented on the issue:

https://github.com/apache/geode/pull/504
  
+1 LGTM


---
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-2902) OffHeapLRURecoveryRegressionTest recoveringTooMuchDataDoesNotRunOutOfOffHeapMemory fails intermittently

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2902:


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

GEODE-2902: fix intermittent unit test failure


> OffHeapLRURecoveryRegressionTest 
> recoveringTooMuchDataDoesNotRunOutOfOffHeapMemory fails intermittently
> ---
>
> Key: GEODE-2902
> URL: https://issues.apache.org/jira/browse/GEODE-2902
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> org.apache.geode.internal.offheap.OffHeapLRURecoveryRegressionTest > 
> recoveringTooMuchDataDoesNotRunOutOfOffHeapMemory FAILED
> java.lang.AssertionError: expected:<10> but was:<11>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.geode.internal.offheap.OffHeapLRURecoveryRegressionTest.recoveringTooMuchDataDoesNotRunOutOfOffHeapMemory(OffHeapLRURecoveryRegressionTest.java:74)



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

[jira] [Commented] (GEODE-2876) CI Failure: org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest#testMultipleGfshClientToOneServer

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2876:


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

GEODE-2876: add logging to diagnose test failure


> CI Failure: 
> org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest#testMultipleGfshClientToOneServer
> -
>
> Key: GEODE-2876
> URL: https://issues.apache.org/jira/browse/GEODE-2876
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Jared Stewart
>
> ConcurrentDeployDUnitTest is failing due to a parsing error.
> {noformat}
> Error
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
> Stacktrace
> java.lang.AssertionError: An exception occurred during asynchronous 
> invocation.
>   at 
> org.apache.geode.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:148)
>   at 
> org.apache.geode.test.dunit.AsyncInvocation.await(AsyncInvocation.java:341)
>   at 
> org.apache.geode.test.dunit.AsyncInvocation.await(AsyncInvocation.java:364)
>   at 
> org.apache.geode.management.internal.cli.commands.ConcurrentDeployDUnitTest.testMultipleGfshClientToOneServer(ConcurrentDeployDUnitTest.java:67)
>   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.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   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.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 

[jira] [Resolved] (GEODE-2904) PRTXJUnitTest testEntryNotFound failing intermittently

[Darrel Schneider (JIRA)]

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

Darrel Schneider resolved GEODE-2904.
-
   Resolution: Fixed
Fix Version/s: 1.2.0

This issue has already been fixed by changes to the LonerDistributionManager 
thread pool.


> PRTXJUnitTest testEntryNotFound failing intermittently
> --
>
> Key: GEODE-2904
> URL: https://issues.apache.org/jira/browse/GEODE-2904
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Reporter: Darrel Schneider
> Fix For: 1.2.0
>
>
> org.apache.geode.internal.cache.PRTXJUnitTest > testEntryNotFound FAILED
> java.util.concurrent.RejectedExecutionException: Task 
> org.apache.geode.internal.cache.BucketAdvisor$VolunteeringDelegate$2@4a31a107 
> rejected from java.util.concurrent.ThreadPoolExecutor@68710006[Terminated, 
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]



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

Build failed in Jenkins: Geode-nightly #831

[Apache Jenkins Server]

See 


Changes:

[bschuchardt] GEODE-2875 shutdown is taking as long as 20 seconds

[ukohlmeyer] GEODE-2875: SpotlessApply

[klund] Revert "GEODE-2708: Update Minimum Gradle Version To 3.4.1"

[klund] Revert "GEODE-2708: Update Gradle Wrapper To 3.4.1"

[nnag] GEODE-2896: Changing the test category to IntegrationTest

[dschneider] GEODE-236: fix javadoc warnings

[upthewaterspout] GEODE-2889: Update the last access time of native sessions

[dschneider] GEODE-2895: fix flaky test

--
[...truncated 174.65 KB...]
: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/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
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest

Re: ASF Board Report for Geode - Initial Reminder for May 2017

[Mark Bretl]

Thanks Anthony! This is great.

I will follow up with infra about our stats on the issues mailing list, I
think you are right about it being something with configuration.

--Mark

On Tue, May 9, 2017 at 4:51 PM, Dan Smith  wrote:

> +1 - Thanks for taking this on Anthony!
>
> -Dan
>
> On Tue, May 9, 2017 at 4:47 PM, Anthony Baker  wrote:
>
> >
> > Here’s a rough draft, please review and comment:
> >
> > (@Mark, I noticed that issues@geode has 0 emails.  Is that a
> > configuration issue?)
> >
> > ## Description:
> >  - Apache Geode provides a database-like consistency model, reliable
> > transaction processing and a shared-nothing architecture to maintain very
> > low latency performance with high concurrency processing.
> >
> > ## Issues:
> >  - There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >  - The Geode PMC issued CVE-2017-5649 and released v1.1.1 to address this
> > vulnerability.
> >  - The geode-examples have been improved significantly to make it easier
> > to add new examples and provide a better learning experience.
> >  - The geode-native source and documentation has undergone significant
> > changes to prepare it for inclusion in a Geode release.
> >  - The community has discussed a number of new proposals on
> > modularization, binary protocol, redis adapter, class loading, and
> > finer-grained security.
> >
> > ## Health report:
> >  - We’re continuing to work on attracting new contributors and making it
> > easier to participate in the community.
> >  - Mailing list activity is healthy and discussions are productive.
> >  - Work is progressing towards the next Geode release, 1.2.0.
> >
> > ## PMC changes:
> >
> >  - Currently 35 PMC members.
> >  - New PMC members:
> > - Jacob Barrett was added to the PMC on Mon May 8 2017
> > - Ernest Burghardt was added to the PMC on Mon Mar 20 2017
> > - Jared Stewart was added to the PMC on Sun Feb 12 2017
> >
> > ## Committer base changes:
> >
> >  - Currently 79 committers.
> >  - Ernest Burghardt was added as a committer on Tue Mar 21 2017
> >
> > ## Releases:
> >
> > - 1.1.1 was released on Sat Apr 1 2017
> > - 1.1.0 was released on Wed Feb 15 2017
> >
> > ## Mailing list activity:
> >
> >  - Mailing lists remain active and we’re seeing continued growth in
> > subscriber counts.  The dev@geode list in particular is highly active.
> >
> >  - dev@geode.apache.org:
> > - 159 subscribers (up 3 in the last 3 months):
> > - 7550 emails sent to list (4317 in previous quarter)
> >
> >  - iss...@geode.apache.org:
> > - 55 subscribers (down -1 in the last 3 months):
> > - 0 emails sent to list (1042 in previous quarter)
> >
> >  - u...@geode.apache.org:
> > - 218 subscribers (up 12 in the last 3 months):
> > - 215 emails sent to list (305 in previous quarter)
> >
> > ## JIRA activity:
> >
> >  - 461 JIRA tickets created in the last 3 months
> >  - 327 JIRA tickets closed/resolved in the last 3 months
> >
> > Anthony
> >
> > > On May 8, 2017, at 9:14 AM, Mark Bretl  wrote:
> > >
> > > We need to submit a report by Friday and I have not seen any takers to
> > > creating the report. If there are no volunteers, I will create a draft
> on
> > > Wednesday.
> > >
> > > --Mark
> > >
> > > On Thu, Apr 27, 2017 at 12:48 PM, Mark Bretl 
> wrote:
> > >
> > >> Hi Everyone,
> > >>
> > >> Amazing how three months goes by so fast! We are approaching six
> months
> > >> since our TLP graduation and its time for another board report.
> > >>
> > >> Do we have any volunteers to create a draft? No need to be a PMC
> member
> > >> either, anyone can be involved with writing the report. There is a
> > template
> > >> on the Geode wiki [1].
> > >>
> > >> Best regards,
> > >>
> > >> --Mark
> > >>
> > >> [1]: https://cwiki.apache.org/confluence/display/GEODE/ASF+
> > >> Board+Report+Template
> > >>
> > >>
> > >> -- Forwarded message --
> > >> From: Brett Porter 
> > >> Date: Wed, Apr 26, 2017 at 6:16 AM
> > >> Subject: ASF Board Report for Geode - Initial Reminder for May 2017
> > >> To: Mark Bretl 
> > >> Cc: priv...@geode.apache.org
> > >>
> > >>
> > >> This email was sent on behalf of the ASF Board.  It is an initial
> > reminder
> > >> to
> > >> give you plenty of time to prepare the report.
> > >>
> > >> According to board records, you are listed as the chair of a committee
> > >> that is
> > >> due to submit a report this month. [1] [2]
> > >>
> > >> The meeting is scheduled for Wed, 17 May 2017 at 10:30 PDT and the
> > >> deadline for
> > >> submitting your report is 1 full week prior to that (Wed May 10th)!
> > >>
> > >> Meeting times in other time zones:
> > >>
> > >>  https://timeanddate.com/s/38ta
> > >>
> > >> Please submit your report with sufficient time to allow the board
> > members
> > >> to review and digest. Again, the very latest you should submit your
> > report
> > 

[jira] [Assigned] (GEODE-269) Remove deprecated methods on FunctionService

[Deepak Dixit (JIRA)]

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

Deepak Dixit reassigned GEODE-269:
--

Assignee: Deepak Dixit

> Remove deprecated methods on FunctionService
> 
>
> Key: GEODE-269
> URL: https://issues.apache.org/jira/browse/GEODE-269
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>Assignee: Deepak Dixit
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> FunctionService has a three deprecated methods that should be easy to remove. 
> All the deprecated methods have a DistributedSystem parameter. New flavors of 
> these methods exist that do not take the DistributedSystem since it is known 
> implicitly by the FunctionService.
> Many tests use the deprecated methods but it should be easy to change them.



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

Re: Review Request 59035: GEODE-2883: Fix GFSH gc heap size output

[Jared Stewart]

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

(Updated May 10, 2017, 4:28 p.m.)


Review request for geode, Barry Oglesby, Jinmei Liao, Ken Howe, Kirk Lund, and 
Patrick Rhomberg.


Repository: geode


Description
---

GEODE-2883: Fix GFSH gc heap size output


Diffs
-

  
geode-core/src/main/java/org/apache/geode/management/internal/cli/functions/GarbageCollectionFunction.java
 354d353 
  
geode-core/src/main/java/org/apache/geode/management/internal/cli/util/BytesToString.java
 PRE-CREATION 
  
geode-core/src/test/java/org/apache/geode/management/internal/cli/util/BytesToStringTest.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/59035/diff/4/


Testing (updated)
---

Precheckin passed (as of revision 4)


Thanks,

Jared Stewart

[jira] [Resolved] (GEODE-2728) Client quickstarts: CMake for security fails to build library

[Dave Barnes (JIRA)]

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

Dave Barnes resolved GEODE-2728.

   Resolution: Fixed
Fix Version/s: 1.2.0

Security quickstart examples removed from code & docs.

> Client quickstarts: CMake for security fails to build library
> -
>
> Key: GEODE-2728
> URL: https://issues.apache.org/jira/browse/GEODE-2728
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Dave Barnes
> Fix For: 1.2.0
>
>
> In the geode-native client distribution, the CMake code for building the 
> security library fails in a couple of ways. Symptoms:
> - CMake still relies on finding $GFCPP in the environment and complains if 
> it's not found.
> - CMake will install only to /lib, ignoring CMAKE_INSTALL_PREFIX if it is 
> specified on the command line.



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

[jira] [Commented] (GEODE-2788) Add official Socket timeout parameter when connecting to servers/locators

[ASF GitHub Bot (JIRA)]

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

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

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/474
  
I am running precheckin on this PR and will merge it to develop afterward.


> Add official Socket timeout parameter when connecting to servers/locators
> -
>
> Key: GEODE-2788
> URL: https://issues.apache.org/jira/browse/GEODE-2788
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server, docs
>Reporter: Masaki Yamakawa
>Priority: Minor
>  Labels: patch
>
> When connecting from the client to the servers/locators, if the 
> servers/locators is not started, the connection can not be established and a 
> Socket timeout occurs.
> This timeout value is 59 seconds by default. This timeout value is too long. 
> This timeout value can be changed by specifying the unofficial parameter 
> "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I 
> corresponded so that it can be specified by official parameters.
> Like the NativeClient, the official parameters should be specified by 
> "connect-timeout" in gemfire.properties.
> Timeout values ​​are determined in the following order of priority.
> 1. java system property:gemfire.PoolImpl.HANDSHAKE_TIMEOUT
> 2. java system property:gemfire.connect-timeout
> 3. gemfire.properties:connect-timeout
> 4. default:59000 milli seconds
> As another idea, there is also an idea to make it possible to specify it as 
> an attribute of Pool. In that case NativeClient needs the same modification.



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

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

[ASF GitHub Bot (JIRA)]

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

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

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/475
  
I am running precheckin on this PR and will merge it to develop afterward.


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

[GitHub] geode issue #474: GEODE-2788: Add official Socket timeout parameter when con...

[bschuchardt]

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/474
  
I am running precheckin on this PR and will merge it to develop afterward.


---
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 #475: GEODE-2812: Add API to get list of live locators

[bschuchardt]

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/475
  
I am running precheckin on this PR and will merge it to develop afterward.


---
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-2812) Add API to get list of live locators

[ASF GitHub Bot (JIRA)]

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

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

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/475
  
Hi Masaki,

I will do the merge for you

Le 5/10/2017 à 4:00 AM, Masaki Yamakawa a écrit :
>
> Thanks @bschuchardt  @kirklund 
>  for review.
> Is this PR OK to merge?
> If it is possible to merge, I do not have the merge permission, so I 
> would appreciate if you could please merge it.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub 
> , or 
> mute the thread 
> 
.
>




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

[GitHub] geode issue #475: GEODE-2812: Add API to get list of live locators

[bschuchardt]

Github user bschuchardt commented on the issue:

https://github.com/apache/geode/pull/475
  
Hi Masaki,

I will do the merge for you

Le 5/10/2017 à 4:00 AM, Masaki Yamakawa a écrit :
>
> Thanks @bschuchardt  @kirklund 
>  for review.
> Is this PR OK to merge?
> If it is possible to merge, I do not have the merge permission, so I 
> would appreciate if you could please merge it.
>
> —
> You are receiving this because you were mentioned.
> 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-2890) Incorrect debug log location in AbstractGatewaySenderEventProcessor.processQueue()

[ASF GitHub Bot (JIRA)]

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

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

GitHub user ameybarve15 opened a pull request:

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

[GEODE-2890]: Corrected debug log location in 
AbstractGatewaySenderEventProcessor.processQueue().

Corrected debug log location in 
AbstractGatewaySenderEventProcessor.processQueue().

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

$ git pull https://github.com/ameybarve15/incubator-geode feature/GEODE-2890

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

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


commit a787737f9ad6656e7da382b35c49ecf622900bf0
Author: Amey Barve 
Date:   2017-05-10T09:17:30Z

GEODE-2890: Corrected debug log location in
AbstractGatewaySenderEventProcessor.processQueue().




> Incorrect debug log location in 
> AbstractGatewaySenderEventProcessor.processQueue() 
> ---
>
> Key: GEODE-2890
> URL: https://issues.apache.org/jira/browse/GEODE-2890
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Jason Huynh
>Assignee: Amey Barve
>
> The following code snippet in processQueue() for AEQ's appears to be outside 
> of an if condition where we check to see if the node is primary still or not. 
>  This line prints for every event and I believe it should be inside the 
> previous if condition. 
> {noformat}
> if (qpr != null) {
>BucketRegion bucket = qpr.getDataStore().getLocalBucketById(bucketId);
>if (bucket == null || !bucket.getBucketAdvisor().isPrimary()) {
>  event.setPossibleDuplicate(true);
> //I think the debug log should be placed here?
>}
> }
> if (isDebugEnabled) {
>   logger.debug( "Bucket id: {} is no longer primary on this node. The event 
> {} will be dispatched from this node with possibleDuplicate set to true.", 
> bucketId, event);
> }
> {noformat}



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

[GitHub] geode pull request #505: [GEODE-2890]: Corrected debug log location in Abstr...

[ameybarve15]

GitHub user ameybarve15 opened a pull request:

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

[GEODE-2890]: Corrected debug log location in 
AbstractGatewaySenderEventProcessor.processQueue().

Corrected debug log location in 
AbstractGatewaySenderEventProcessor.processQueue().

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

$ git pull https://github.com/ameybarve15/incubator-geode feature/GEODE-2890

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

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


commit a787737f9ad6656e7da382b35c49ecf622900bf0
Author: Amey Barve 
Date:   2017-05-10T09:17:30Z

GEODE-2890: Corrected debug log location in
AbstractGatewaySenderEventProcessor.processQueue().




---
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-2853) Change of locator list request interval

[ASF GitHub Bot (JIRA)]

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

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

Github user masaki-yamakawa commented on the issue:

https://github.com/apache/geode/pull/483
  
Thanks @bschuchardt @kirklund for review.
Is this PR OK to merge?
If it is possible to merge, I do not have the merge permission, so I would 
appreciate if you could please merge it.


> 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 issue #483: GEODE-2853: Change of locator list request interval

[masaki-yamakawa]

Github user masaki-yamakawa commented on the issue:

https://github.com/apache/geode/pull/483
  
Thanks @bschuchardt @kirklund for review.
Is this PR OK to merge?
If it is possible to merge, I do not have the merge permission, so I would 
appreciate if you could please merge 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-2812) Add API to get list of live locators

[ASF GitHub Bot (JIRA)]

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

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

Github user masaki-yamakawa commented on the issue:

https://github.com/apache/geode/pull/475
  
Thanks @bschuchardt @kirklund for review.
Is this PR OK to merge?
If it is possible to merge, I do not have the merge permission, so I would 
appreciate if you could please merge it.


> 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-254) Remove deprecated Region.keys and Region.entries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-254:
--

GitHub user davinash opened a pull request:

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

GEODE-254: Removed deprecated Region.keys and Region.entries

Addressing review comment from 
https://github.com/apache/geode/pull/488
- removed method entries
- IndexMaintenanceJUnitTest#testIndexMaintenanceWithIndexOnMethodEntries is 
no longer applicable so removed the same.
- Other than GMSMembershipManagerJUnitTest all tests are passing
- This also fixed ConsoleDistributionManagerDUnitTest#testApplications, 
which was failing due to my previous fix.

@dschneider-pivotal , @kirklund  Please review.

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

$ git pull https://github.com/davinash/geode feature/GEODE-254.2

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

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


commit bba87157d39cefcc977ce9207842f0316cbb6729
Author: adongre 
Date:   2017-05-09T19:04:14Z

GEODE-254: Addressing review comments from PR #488
Replacing all inststance of entries with entrySet

GEODE-254: Fixing the Test Failures
 - Removed test testIndexMaintenanceWithIndexOnMethodEntries since this is 
no more applicable.

GEODE-254: Spotless fixing.




> Remove deprecated Region.keys and Region.entries
> 
>
> Key: GEODE-254
> URL: https://issues.apache.org/jira/browse/GEODE-254
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Region.keys and Region.entries. Any calls can be simply 
> changed to Region.keySet and Region.entrySet so this should be an easy change.
> A large number of tests call the deprecated methods.



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

[GitHub] geode pull request #504: GEODE-254: Removed deprecated Region.keys and Regio...

[davinash]

GitHub user davinash opened a pull request:

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

GEODE-254: Removed deprecated Region.keys and Region.entries

Addressing review comment from 
https://github.com/apache/geode/pull/488
- removed method entries
- IndexMaintenanceJUnitTest#testIndexMaintenanceWithIndexOnMethodEntries is 
no longer applicable so removed the same.
- Other than GMSMembershipManagerJUnitTest all tests are passing
- This also fixed ConsoleDistributionManagerDUnitTest#testApplications, 
which was failing due to my previous fix.

@dschneider-pivotal , @kirklund  Please review.

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

$ git pull https://github.com/davinash/geode feature/GEODE-254.2

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

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


commit bba87157d39cefcc977ce9207842f0316cbb6729
Author: adongre 
Date:   2017-05-09T19:04:14Z

GEODE-254: Addressing review comments from PR #488
Replacing all inststance of entries with entrySet

GEODE-254: Fixing the Test Failures
 - Removed test testIndexMaintenanceWithIndexOnMethodEntries since this is 
no more applicable.

GEODE-254: Spotless fixing.




---
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-2866) Bytes.java is not used in product, Only used in BytesJUnitTest, should be removed

[Prasad Subhash Indulkar (JIRA)]

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

Prasad Subhash Indulkar resolved GEODE-2866.

   Resolution: Fixed
Fix Version/s: 1.2.0

> Bytes.java is not used in product, Only used in BytesJUnitTest, should be 
> removed
> -
>
> Key: GEODE-2866
> URL: https://issues.apache.org/jira/browse/GEODE-2866
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Avinash Dongre
>Assignee: Prasad Subhash Indulkar
> Fix For: 1.2.0
>
>
> Bytes.java is not used only used in BytesJUnitTest, should be removed
> FYI [~bschuchardt]



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

[jira] [Updated] (GEODE-2908) Swagger UI Tags seems broken in Latest

[Avinash Dongre (JIRA)]

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

Avinash Dongre updated GEODE-2908:
--
Attachment: Before.png

> Swagger UI Tags seems broken in Latest
> --
>
> Key: GEODE-2908
> URL: https://issues.apache.org/jira/browse/GEODE-2908
> Project: Geode
>  Issue Type: Bug
>Reporter: Avinash Dongre
> Attachments: Before.png
>
>
> Swagger UI Tags seems broken in Latest



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

[jira] [Created] (GEODE-2908) Swagger UI Tags seems broken in Latest

[Avinash Dongre (JIRA)]

Avinash Dongre created GEODE-2908:
-

 Summary: Swagger UI Tags seems broken in Latest
 Key: GEODE-2908
 URL: https://issues.apache.org/jira/browse/GEODE-2908
 Project: Geode
  Issue Type: Bug
Reporter: Avinash Dongre


Swagger UI Tags seems broken in Latest



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

[jira] [Commented] (GEODE-2866) Bytes.java is not used in product, Only used in BytesJUnitTest, should be removed

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-2866:


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

GEODE-2866: Removing the unused files and the corresponding test.
This closes #497

Signed-off-by: adongre 


> Bytes.java is not used in product, Only used in BytesJUnitTest, should be 
> removed
> -
>
> Key: GEODE-2866
> URL: https://issues.apache.org/jira/browse/GEODE-2866
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Avinash Dongre
>Assignee: Prasad Subhash Indulkar
>
> Bytes.java is not used only used in BytesJUnitTest, should be removed
> FYI [~bschuchardt]



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

[jira] [Commented] (GEODE-2866) Bytes.java is not used in product, Only used in BytesJUnitTest, should be removed

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Bytes.java is not used in product, Only used in BytesJUnitTest, should be 
> removed
> -
>
> Key: GEODE-2866
> URL: https://issues.apache.org/jira/browse/GEODE-2866
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Avinash Dongre
>Assignee: Prasad Subhash Indulkar
>
> Bytes.java is not used only used in BytesJUnitTest, should be removed
> FYI [~bschuchardt]



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

[GitHub] geode pull request #497: GEODE-2866: Removing the unused files and the corre...

[asfgit]

Github user asfgit closed the pull request at:

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


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