[jira] [Commented] (GEODE-1957) CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1957:


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

GEODE-1957: mark test as flaky


> CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion
> 
>
> Key: GEODE-1957
> URL: https://issues.apache.org/jira/browse/GEODE-1957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Bruce Schuchardt
>  Labels: ci, flaky
>
> This test failed in a CI run with SHA 7254cf3fb0ceb2255650d96f2b0ed615118ef700
> {noformat}
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
> testCloseOpenRegion FAILED
> java.lang.AssertionError: Failed on entry 40 expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
> {noformat}



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

[jira] [Updated] (GEODE-1957) CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-1957:

Labels: ci flaky  (was: ci)

> CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion
> 
>
> Key: GEODE-1957
> URL: https://issues.apache.org/jira/browse/GEODE-1957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Bruce Schuchardt
>  Labels: ci, flaky
>
> This test failed in a CI run with SHA 7254cf3fb0ceb2255650d96f2b0ed615118ef700
> {noformat}
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
> testCloseOpenRegion FAILED
> java.lang.AssertionError: Failed on entry 40 expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
> {noformat}



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

[jira] [Updated] (GEODE-1933) CI Failure: ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-1933:

Labels: ci flaky  (was: ci)

> CI Failure: 
> ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy
> 
>
> Key: GEODE-1933
> URL: https://issues.apache.org/jira/browse/GEODE-1933
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Reporter: Eric Shu
>  Labels: ci, flaky
>
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest$70.call in 
> VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:320)
>   at 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.doFailoverWork(ClientServerTransactionDUnitTest.java:1910)
>   at 
> org.apache.geode.internal.cache.ClientServerTransactionDUnitTest.testFailoverWithP2PMessagingAndCachingProxy(ClientServerTransactionDUnitTest.java:1835)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> 

[jira] [Commented] (GEODE-1891) Potential region inconsistency with bulk operations and non-replicant regions

[Darrel Schneider (JIRA)]

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

Darrel Schneider commented on GEODE-1891:
-

When this issue is fixed this unit test should be reenabled: 
DistributedAckRegionCCEDUnitTest.testClearOnNonReplicateWithConcurrentEvents()

> Potential region inconsistency with bulk operations and non-replicant regions
> -
>
> Key: GEODE-1891
> URL: https://issues.apache.org/jira/browse/GEODE-1891
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Scott Jewell
>
> There is a possible region inconsistency when performing bulk operations with 
> non-replicant regions.
> The LocalRegion.lockRVVForBulkOp and unlockRVVForBulkOp methods
> only take cache modification lock if region attribute withReplication() is 
> true.



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

[jira] [Commented] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



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

[jira] [Commented] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1907:


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

GEODE-1907: QueryDataFunction now adds LIMIT clause if space is missing after 
FROM clause

This closes #249


> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



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

[jira] [Updated] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1793:

Fix Version/s: (was: 1.0.0-incubating)

> Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
> ---
>
> Key: GEODE-1793
> URL: https://issues.apache.org/jira/browse/GEODE-1793
> Project: Geode
>  Issue Type: Bug
>  Components: locator
>Reporter: Udo Kohlmeyer
>Priority: Minor
>
> This test fails due to something not cleaning itself properly. Undetermined 
> what the problem is, but it will run perfectly by itself everytime, but once 
> run inside of the TestClass it fails



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

[jira] [Updated] (GEODE-1570) developer REST API should be secured

[Swapnil Bawaskar (JIRA)]

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

Swapnil Bawaskar updated GEODE-1570:

Fix Version/s: 1.0.0-incubating

> developer REST API should be secured
> 
>
> Key: GEODE-1570
> URL: https://issues.apache.org/jira/browse/GEODE-1570
> Project: Geode
>  Issue Type: Sub-task
>  Components: rest (dev), security
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating
>
>
> The developer REST API should require authentication when security is 
> enabled. For authorization, the implementation should use the new 
> Resource:Operation permissions API that is used by JMX.



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

[jira] [Updated] (GEODE-1948) Open geode.properties if gemfire.properties is not found

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller updated GEODE-1948:
---
Labels: branding configuration docs  (was: branding configuration)

> Open geode.properties if gemfire.properties is not found
> 
>
> Key: GEODE-1948
> URL: https://issues.apache.org/jira/browse/GEODE-1948
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>  Labels: branding, configuration, docs
> Fix For: 1.0.0-incubating
>
>
> geode.properties should be the new default filename.  If gemfire.properties 
> is specified on startup and cannot be located, fall back to geode.properties 
> and try to open that file before presenting an error.



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

[jira] [Resolved] (GEODE-1948) Open geode.properties if gemfire.properties is not found

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-1948.
-
Resolution: Fixed

> Open geode.properties if gemfire.properties is not found
> 
>
> Key: GEODE-1948
> URL: https://issues.apache.org/jira/browse/GEODE-1948
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>  Labels: branding, configuration
> Fix For: 1.0.0-incubating
>
>
> geode.properties should be the new default filename.  If gemfire.properties 
> is specified on startup and cannot be located, fall back to geode.properties 
> and try to open that file before presenting an error.



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

[jira] [Updated] (GEODE-1957) CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-1957:

Description: 
This test failed in a CI run with SHA 7254cf3fb0ceb2255650d96f2b0ed615118ef700

{noformat}
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
testCloseOpenRegion FAILED
java.lang.AssertionError: Failed on entry 40 expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
{noformat}


  was:
This test failed in a CI run with SHA 

{noformat}
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
testCloseOpenRegion FAILED
java.lang.AssertionError: Failed on entry 40 expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
{noformat}



> CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion
> 
>
> Key: GEODE-1957
> URL: https://issues.apache.org/jira/browse/GEODE-1957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Bruce Schuchardt
>  Labels: ci
>
> This test failed in a CI run with SHA 7254cf3fb0ceb2255650d96f2b0ed615118ef700
> {noformat}
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
> testCloseOpenRegion FAILED
> java.lang.AssertionError: Failed on entry 40 expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
> {noformat}



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

[jira] [Updated] (GEODE-1957) CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-1957:

Labels: ci  (was: )

> CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion
> 
>
> Key: GEODE-1957
> URL: https://issues.apache.org/jira/browse/GEODE-1957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Bruce Schuchardt
>  Labels: ci
>
> This test failed in a CI run with SHA 
> {noformat}
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
> testCloseOpenRegion FAILED
> java.lang.AssertionError: Failed on entry 40 expected: but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
> at 
> org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
> {noformat}



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

[jira] [Created] (GEODE-1957) CI failure: DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-1957:
---

 Summary: CI failure: 
DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion
 Key: GEODE-1957
 URL: https://issues.apache.org/jira/browse/GEODE-1957
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Bruce Schuchardt


This test failed in a CI run with SHA 

{noformat}
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest > 
testCloseOpenRegion FAILED
java.lang.AssertionError: Failed on entry 40 expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.checkEntriesInMemory(DiskRegionAsyncRecoveryJUnitTest.java:456)
at 
org.apache.geode.internal.cache.DiskRegionAsyncRecoveryJUnitTest.testCloseOpenRegion(DiskRegionAsyncRecoveryJUnitTest.java:382)
{noformat}




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

[jira] [Updated] (GEODE-209) CI failure: FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-209:
---
Summary: CI failure: 
FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
  (was: 
FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
 is not stable)

> CI failure: 
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
> 
>
> Key: GEODE-209
> URL: https://issues.apache.org/jira/browse/GEODE-209
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Ashvin
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: ci
> Fix For: 1.0.0-incubating.M1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
>   at 
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
>   public void subTearDown() throws Exception {
> this.process.waitFor();
> assertFalse(this.process.isAlive());
>   }
> {code}
> Fix to GEODE-127 may have caused this issue.



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

[jira] [Updated] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-209:
---
Labels: ci  (was: )

> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  is not stable
> --
>
> Key: GEODE-209
> URL: https://issues.apache.org/jira/browse/GEODE-209
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Ashvin
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: ci
> Fix For: 1.0.0-incubating.M1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
>   at 
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
>   public void subTearDown() throws Exception {
> this.process.waitFor();
> assertFalse(this.process.isAlive());
>   }
> {code}
> Fix to GEODE-127 may have caused this issue.



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

[jira] [Commented] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt commented on GEODE-209:


This test is still failing periodically in CI runs

SHA: 44427d4e9e68285001363527c2c063128e6e763c
{noformat}
org.apache.geode.test.process.MainLauncher 
org.apache.geode.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest
at 
org.apache.geode.test.process.ProcessStreamReader.start(ProcessStreamReader.java:52)
at 
org.apache.geode.test.process.ProcessOutputReader.start(ProcessOutputReader.java:44)
at 
org.apache.geode.test.process.ProcessWrapper.start(ProcessWrapper.java:323)
at 
org.apache.geode.test.process.ProcessWrapper.access$000(ProcessWrapper.java:41)
{noformat}

SHA: 44427d4e9e68285001363527c2c063128e6e763c
{noformat}
org.apache.geode.test.process.MainLauncher 
org.apache.geode.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest
at 
org.apache.geode.test.process.ProcessStreamReader.start(ProcessStreamReader.java:52)
at 
org.apache.geode.test.process.ProcessOutputReader.start(ProcessOutputReader.java:44)
at 
org.apache.geode.test.process.ProcessWrapper.start(ProcessWrapper.java:323)
at 
org.apache.geode.test.process.ProcessWrapper.access$000(ProcessWrapper.java:41)
at 
org.apache.geode.test.process.ProcessWrapper$1.run(ProcessWrapper.java:253)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Stream closed
at 
java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:283)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:161)
at java.io.BufferedReader.readLine(BufferedReader.java:324)
at java.io.BufferedReader.readLine(BufferedReader.java:389)
at 
org.apache.geode.test.process.ProcessStreamReader.run(ProcessStreamReader.java:60)
{noformat}

> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  is not stable
> --
>
> Key: GEODE-209
> URL: https://issues.apache.org/jira/browse/GEODE-209
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Ashvin
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: ci
> Fix For: 1.0.0-incubating.M1
>
>
> FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
>  failed 5 times in the last 30 runs. It is failing in the tearDown phase.
> {quote}
> java.lang.AssertionError
>   at org.junit.Assert.fail(Assert.java:86)
>   at org.junit.Assert.assertTrue(Assert.java:41)
>   at org.junit.Assert.assertFalse(Assert.java:64)
>   at org.junit.Assert.assertFalse(Assert.java:74)
>   at 
> com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
>   at 
> com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {quote}
> {code}
>   public void subTearDown() throws Exception {
> this.process.waitFor();
> assertFalse(this.process.isAlive());
>   }
> {code}
> Fix to GEODE-127 may have caused this issue.



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

[jira] [Commented] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

[ASF GitHub Bot (JIRA)]

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/249
  
+1 pulling in now


> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1548:


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

GEODE-1548: Specifying --J=-Dgemfire.jmx-manager-hostname-for-clients now 
automatically sets -Djava.rmi.server.hostname

 * This closes #248


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/248
  
+1


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/248#discussion_r81409537
  
--- Diff: 
geode-core/src/test/java/org/apache/geode/management/internal/security/JavaRmiServerNameJunitTest.java
 ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.management.internal.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.internal.AvailablePort;
+import org.apache.geode.test.junit.categories.UnitTest;
+
+@Category(UnitTest.class)
--- End diff --

Thanks for clarifying that distinction.  I pushed another commit with this 
change.


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/248#discussion_r81408700
  
--- Diff: 
geode-core/src/test/java/org/apache/geode/management/internal/security/JavaRmiServerNameJunitTest.java
 ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.management.internal.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.internal.AvailablePort;
+import org.apache.geode.test.junit.categories.UnitTest;
+
+@Category(UnitTest.class)
--- End diff --

Oh got it, I missed the previous comment around @IntegrationTest.


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/248#discussion_r81408523
  
--- Diff: 
geode-core/src/test/java/org/apache/geode/management/internal/security/JavaRmiServerNameJunitTest.java
 ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.management.internal.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.internal.AvailablePort;
+import org.apache.geode.test.junit.categories.UnitTest;
+
+@Category(UnitTest.class)
--- End diff --

Isn't the convention to use *JUnitTest for unit tests?


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/249#discussion_r81404596
  
--- Diff: 
geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java
 ---
@@ -360,31 +373,36 @@ public static Object queryData(final String query,
 for (String regionPath : regionsInQuery) {
   DistributedRegionMXBean regionMBean = 
service.getDistributedRegionMXBean(regionPath);
   if (regionMBean == null) {
-return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__REGIONS_NOT_FOUND.toLocalizedString(regionPath)).toString();
+return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__REGIONS_NOT_FOUND.toLocalizedString(regionPath))
+  .toString();
   } else {
 Set associatedMembers = 
DataCommands.getRegionAssociatedMembers(regionPath, cache, true);
 
 if (inputMembers != null && inputMembers.size() > 0) {
   if (!associatedMembers.containsAll(inputMembers)) {
-return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__REGIONS_NOT_FOUND_ON_MEMBERS.toLocalizedString(regionPath))
-  .toString();
+return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__REGIONS_NOT_FOUND_ON_MEMBERS
+  .toLocalizedString(regionPath)).toString();
   }
 }
   }
 
 }
   } else {
-return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__INVALID_QUERY.toLocalizedString("Region
 mentioned in query probably missing /")).toString();
+return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__INVALID_QUERY.toLocalizedString("Region
 mentioned in query probably missing /"))
+  .toString();
   }
 
   // Validate
   if (regionsInQuery.size() > 1 && inputMembers == null) {
 for (String regionPath : regionsInQuery) {
   DistributedRegionMXBean regionMBean = 
service.getDistributedRegionMXBean(regionPath);
 
-  if 
(regionMBean.getRegionType().equals(DataPolicy.PARTITION.toString()) || 
-  
regionMBean.getRegionType().equals(DataPolicy.PERSISTENT_PARTITION.toString())) 
{
-return new 
JsonisedErroMessage(ManagementStrings.QUERY__MSG__JOIN_OP_EX.toLocalizedString()).toString();
+  if (regionMBean.getRegionType()
--- End diff --

I updated the formatters in etc/ including etc/intellijIdeaCodeStyle.xml to 
prevent these whacky linefeeds. Please update and rerun the formatter. The 
changes look good and I'll pull it in as soon as you've reformatted. Thanks!


> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/248#discussion_r81402893
  
--- Diff: 
geode-core/src/test/java/org/apache/geode/management/internal/security/JavaRmiServerNameJunitTest.java
 ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.management.internal.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.internal.AvailablePort;
+import org.apache.geode.test.junit.categories.UnitTest;
+
+@Category(UnitTest.class)
--- End diff --

The test name is ok but I'd probably make it 
JavaRmiServerNameIntegrationTest.java


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1548) jmx-manager-hostname-for-clients not honored

[ASF GitHub Bot (JIRA)]

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

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

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

https://github.com/apache/incubator-geode/pull/248#discussion_r81402616
  
--- Diff: 
geode-core/src/test/java/org/apache/geode/management/internal/security/JavaRmiServerNameJunitTest.java
 ---
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.management.internal.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.internal.AvailablePort;
+import org.apache.geode.test.junit.categories.UnitTest;
+
+@Category(UnitTest.class)
--- End diff --

Since this test is testing more than one class (it's creating a Cache and 
using networking resources), it should have @Category(IntegrationTest.class).


> jmx-manager-hostname-for-clients not honored
> 
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Jared Stewart
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}} 
> is not being honored resulting in not being able to connect to gfsh from 
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator 
> --J=-Dgemfire.jmx-manager-hostname-for-clients= 
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following 
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to : 
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed 
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root 
> exception is java.rmi.ConnectIOException: error during JRMP connection 
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not 
> using the {{jmx-manager-hostname-for-clients}} property provided.



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

[jira] [Commented] (GEODE-1952) Merge documentation to develop branch

[Dan Smith (JIRA)]

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

Dan Smith commented on GEODE-1952:
--

Regarding whether the files need headers, this link seems to suggest that they 
are needed - http://www.apache.org/legal/src-headers.html

{noformat}
Does this policy apply to documentation files included in a release?

Yes.
{noformat}

> Merge documentation to develop branch
> -
>
> Key: GEODE-1952
> URL: https://issues.apache.org/jira/browse/GEODE-1952
> Project: Geode
>  Issue Type: New Feature
>  Components: docs
>Reporter: Anthony Baker
>
> The staging/docs-grant1 branch [1] contains the source current used to build 
> the documentation site [2] for geode.  In order to merge this source init the 
> develop branch, we need to:
> 1) Review the files and determine if there are any licensing or dependency 
> considerations.  Update the LICENSE and NOTICE files as necessary.
> 2) Update the source headers and replace with the Apache source header as 
> needed.  Since these are documentation files, determine if a source header is 
> required.
> 3) Improve the build process to make it simpler for contributors and users. 
> This includes writing up build instructions.  We will need to create a 
> top-level directory (geode-docs?) to hold the files.
> 4) Include the documentation in the source distributions created by the build.
> 5) Incorporate other suggestions from the community.
> Once the branch has been merged, we should host the documentation site on 
> geode.apache.org.
> [1] 
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tree;h=refs/heads/staging/docs-grant1;hb=refs/heads/staging/docs-grant1
> [2] http://geode.docs.pivotal.io



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

[jira] [Commented] (GEODE-1793) Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt commented on GEODE-1793:
-

this ticket describes the test as Flaky but the test has not been annotated as 
being flaky and so is still being run with regular unit tests

> Flaky: LocatorDUnitTest.testStartTwoLocatorsOneWithSSLAndTheOtherNonSSL
> ---
>
> Key: GEODE-1793
> URL: https://issues.apache.org/jira/browse/GEODE-1793
> Project: Geode
>  Issue Type: Bug
>  Components: locator
>Reporter: Udo Kohlmeyer
>Priority: Minor
> Fix For: 1.0.0-incubating
>
>
> This test fails due to something not cleaning itself properly. Undetermined 
> what the problem is, but it will run perfectly by itself everytime, but once 
> run inside of the TestClass it fails



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

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

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-1956:
---

 Summary: CI failure: 
LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate
 Key: GEODE-1956
 URL: https://issues.apache.org/jira/browse/GEODE-1956
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: Bruce Schuchardt


org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest$$Lambda$50/1718051859.run
 in VM 0 running on Host cc2-rh6.gemstone.com with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:389)
at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
at org.apache.geode.test.dunit.VM.invoke(VM.java:293)
at 
org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenCloseCacheHappensOnIndexUpdate(LuceneQueriesPeerPRRedundancyDUnitTest.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 

[jira] [Created] (GEODE-1955) JMX suspect string causes tests to fail

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-1955:
---

 Summary: JMX suspect string causes tests to fail
 Key: GEODE-1955
 URL: https://issues.apache.org/jira/browse/GEODE-1955
 Project: Geode
  Issue Type: Bug
  Components: jmx
Reporter: Bruce Schuchardt


This suspect string is causing periodic failures in a number of unit tests:

Error Message

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 283

[fatal 2016/09/29 12:12:03.891 PDT  tid=0x18d] (tid=397 
msgId=39) No longer connected to cc6-co6.gemstone.com[27162].





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

[jira] [Resolved] (GEODE-1949) geode-rebalancer is not part of the binary distribution

[Dan Smith (JIRA)]

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

Dan Smith resolved GEODE-1949.
--
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> geode-rebalancer is not part of the binary distribution
> ---
>
> Key: GEODE-1949
> URL: https://issues.apache.org/jira/browse/GEODE-1949
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating
>
>
> The geode-rebalancer jar is not part of the binary distribution. That means 
> that users that want to use the rebalancer must download it and it's 
> dependencies from maven and add them to the server's classpath.
> I think the main reason not to include the rebalancer in the server's 
> classpath is the dependency on quartz. But looking at the code, it looks like 
> the only usage of quartz is a one line validation that doesn't need to be 
> there. We should remove the dependency on quartz and include the rebalancer 
> in the geode server's classpath by default.



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

[jira] [Updated] (GEODE-1955) JMX suspect string causes tests to fail

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-1955:

Labels: ci  (was: )

> JMX suspect string causes tests to fail
> ---
>
> Key: GEODE-1955
> URL: https://issues.apache.org/jira/browse/GEODE-1955
> Project: Geode
>  Issue Type: Bug
>  Components: jmx
>Reporter: Bruce Schuchardt
>  Labels: ci
>
> This suspect string is causing periodic failures in a number of unit tests:
> Error Message
> 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 283
> [fatal 2016/09/29 12:12:03.891 PDT  tid=0x18d] 
> (tid=397 msgId=39) No longer connected to cc6-co6.gemstone.com[27162].



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

[jira] [Commented] (GEODE-1949) geode-rebalancer is not part of the binary distribution

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1949:


Commit 22afc3bd740241e53444dec2fd30ea39fa15c5dc in incubator-geode's branch 
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=22afc3b ]

GEODE-1949: Remove the dependency on quartz from the rebalancer

The geode-rebalancer does not need to depend on quartz, it is using
spring-expression for all of the cron heavy lifting.


> geode-rebalancer is not part of the binary distribution
> ---
>
> Key: GEODE-1949
> URL: https://issues.apache.org/jira/browse/GEODE-1949
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> The geode-rebalancer jar is not part of the binary distribution. That means 
> that users that want to use the rebalancer must download it and it's 
> dependencies from maven and add them to the server's classpath.
> I think the main reason not to include the rebalancer in the server's 
> classpath is the dependency on quartz. But looking at the code, it looks like 
> the only usage of quartz is a one line validation that doesn't need to be 
> there. We should remove the dependency on quartz and include the rebalancer 
> in the geode server's classpath by default.



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

[jira] [Commented] (GEODE-1949) geode-rebalancer is not part of the binary distribution

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1949:


Commit 0a6e1a5339243b069a04d8010a869bfd1f4172c1 in incubator-geode's branch 
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0a6e1a5 ]

GEODE-1949: Adding geode-rebalancer to the binary distribution


> geode-rebalancer is not part of the binary distribution
> ---
>
> Key: GEODE-1949
> URL: https://issues.apache.org/jira/browse/GEODE-1949
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> The geode-rebalancer jar is not part of the binary distribution. That means 
> that users that want to use the rebalancer must download it and it's 
> dependencies from maven and add them to the server's classpath.
> I think the main reason not to include the rebalancer in the server's 
> classpath is the dependency on quartz. But looking at the code, it looks like 
> the only usage of quartz is a one line validation that doesn't need to be 
> there. We should remove the dependency on quartz and include the rebalancer 
> in the geode server's classpath by default.



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

[jira] [Updated] (GEODE-1954) CI Failure: IndexCommandsDUnitTest.testCreateDestroyUpdatesSharedConfig

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-1954:

Summary: CI Failure: 
IndexCommandsDUnitTest.testCreateDestroyUpdatesSharedConfig  (was: CI Failure: 
org.apache.geode.management.internal.cli.commands.IndexCommandsDUnitTest.testCreateDestroyUpdatesSharedConfig)

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

[jira] [Updated] (GEODE-1953) CI Failure: CacheServerMBeanAuthorizationJUnitTest.classMethod

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-1953:

Labels: ci  (was: )

> CI Failure: CacheServerMBeanAuthorizationJUnitTest.classMethod
> --
>
> Key: GEODE-1953
> URL: https://issues.apache.org/jira/browse/GEODE-1953
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Bruce Schuchardt
>  Labels: ci
>
> Error Message
> java.net.BindException: Failed to create server socket on  null[40,404]
> Stacktrace
> java.net.BindException: Failed to create server socket on  null[40,404]
>   at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:759)
>   at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:725)
>   at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:694)
>   at 
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:457)
>   at 
> org.apache.geode.internal.cache.CacheServerImpl.start(CacheServerImpl.java:323)
>   at 
> org.apache.geode.management.internal.security.JsonAuthorizationCacheStartRule.before(JsonAuthorizationCacheStartRule.java:71)
>   at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Address already in use
>   at java.net.PlainSocketImpl.socketBind(Native Method)
>   at 
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
>   at java.net.ServerSocket.bind(ServerSocket.java:375)
>   at 
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:757)
>   ... 34 more



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

[jira] [Commented] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

[ASF GitHub Bot (JIRA)]

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

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

GitHub user jaredjstewart opened a pull request:

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

GEODE-1907: QueryDataFunction now adds LIMIT clause if space is missi…

…ng after FROM clause

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

$ git pull https://github.com/jaredjstewart/incubator-geode 
feature/GEODE-1907

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

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


commit 6fb64a7b671af3054a38610c245f51ab9c30c342
Author: Jared Stewart 
Date:   2016-09-29T19:47:15Z

GEODE-1907: QueryDataFunction now adds LIMIT clause if space is missing 
after FROM clause




> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



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

[jira] [Created] (GEODE-1953) CI Failure: CacheServerMBeanAuthorizationJUnitTest.classMethod

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-1953:
---

 Summary: CI Failure: 
CacheServerMBeanAuthorizationJUnitTest.classMethod
 Key: GEODE-1953
 URL: https://issues.apache.org/jira/browse/GEODE-1953
 Project: Geode
  Issue Type: Bug
  Components: management
Reporter: Bruce Schuchardt


Error Message

java.net.BindException: Failed to create server socket on  null[40,404]

Stacktrace

java.net.BindException: Failed to create server socket on  null[40,404]
at 
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:759)
at 
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:725)
at 
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:694)
at 
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:457)
at 
org.apache.geode.internal.cache.CacheServerImpl.start(CacheServerImpl.java:323)
at 
org.apache.geode.management.internal.security.JsonAuthorizationCacheStartRule.before(JsonAuthorizationCacheStartRule.java:71)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at 
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at 
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:757)
... 34 more




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