[jira] [Commented] (GEODE-1209) Support/Propagating eviction and expiration operation with AsycEventQueue.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1209:


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

GEODE-1209: Changes to ignoreEvictionAndExpiration AEQ attribute based on the 
new proposal
(changing ignoreEvictionAndExpiration to forwardExpirationDestroy).

GEODE-1209 was proposed to add new attribute ignoreEvictionAndExpiration to 
AsyncEventQueue.
As mentioned in the ticket due to product issue a new proposal was made to 
change the
functionality, to only forward expiration-destroy operation.

The changes made here replaces ignoreEvictionAndExpiration attribute to 
forwardExiprationDestroy.


> Support/Propagating eviction and expiration operation with AsycEventQueue.
> --
>
> Key: GEODE-1209
> URL: https://issues.apache.org/jira/browse/GEODE-1209
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
>
> The AsyncEventQueue works as a write-behind cache event handler to 
> synchronize region updates with other source...Currently it does not support 
> distribution of eviction or expiration operationThis makes the external 
> source to be out of sync with data that has been removed/invalidated through 
> eviction and expiration.
> This ticket is to add/support eviction and expiration operation with 
> AsyncEventQueue, so that all the operations are propagated to 
> AsyncEventQueueListener and the usage of those events are left to underlying 
> implementation/applications(like WAN, Lucene, plug-able storage, etc).
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/events/implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling



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

[jira] [Commented] (GEODE-1209) Support/Propagating eviction and expiration operation with AsycEventQueue.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1209:


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

GEODE-1209: Changes to ignoreEvictionAndExpiration AEQ attribute based on the 
new proposal
(changing ignoreEvictionAndExpiration to forwardExpirationDestroy).

GEODE-1209 was proposed to add new attribute ignoreEvictionAndExpiration to 
AsyncEventQueue.
As mentioned in the ticket due to product issue a new proposal was made to 
change the
functionality, to only forward expiration-destroy operation.

The changes made here replaces ignoreEvictionAndExpiration attribute to 
forwardExiprationDestroy.


> Support/Propagating eviction and expiration operation with AsycEventQueue.
> --
>
> Key: GEODE-1209
> URL: https://issues.apache.org/jira/browse/GEODE-1209
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Reporter: Anilkumar Gingade
>Assignee: Anilkumar Gingade
>
> The AsyncEventQueue works as a write-behind cache event handler to 
> synchronize region updates with other source...Currently it does not support 
> distribution of eviction or expiration operationThis makes the external 
> source to be out of sync with data that has been removed/invalidated through 
> eviction and expiration.
> This ticket is to add/support eviction and expiration operation with 
> AsyncEventQueue, so that all the operations are propagated to 
> AsyncEventQueueListener and the usage of those events are left to underlying 
> implementation/applications(like WAN, Lucene, plug-able storage, etc).
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/events/implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling



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

[jira] [Created] (GEODE-1558) LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance failed on flushing the queue

[Aparna Dharmakkan (JIRA)]

Aparna Dharmakkan created GEODE-1558:


 Summary: 
LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance failed on 
flushing the queue
 Key: GEODE-1558
 URL: https://issues.apache.org/jira/browse/GEODE-1558
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: Aparna Dharmakkan


The error was:

{noformat}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
com.gemstone.gemfire.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsAfterRebalance(LuceneQueriesPRBase.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
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.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
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 

[jira] [Commented] (GEODE-11) Lucene Integration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-11:
--

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

GEODE-11: Removed ParseException from LuceneQueryFactory.create, added 
LuceneQueryException

Adding a new exception to wrap lucene exceptions called LuceneQueryException. 
Removed lucene exceptions from the public API.


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Commented] (GEODE-1372) Geode UDP communications are not secure when SSL is configured

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1372:


Commit e96c57528aa0775b90a255fdc4c8519104af7154 in incubator-geode's branch 
refs/heads/feature/GEODE-1372 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e96c575 ]

GEODE-1372 added time stats for udp encryption-de. added test for it


> Geode UDP communications are not secure when SSL is configured
> --
>
> Key: GEODE-1372
> URL: https://issues.apache.org/jira/browse/GEODE-1372
> Project: Geode
>  Issue Type: New Feature
>  Components: membership
>Reporter: Bruce Schuchardt
>Assignee: Hitesh Khamesra
>
> Gemfire servers use UDP requests to communicate membership views, suspect 
> processing and other information. When gemfire SSL is enabled, only the TCP 
> requests are encrypted and UDP requests are not.



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

[jira] [Commented] (GEODE-1556) Create unit test for GFSH hostname

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1556:


Commit 28d2ce069681f3fc246b4f9405869ed51d1007ff in incubator-geode's branch 
refs/heads/develop from gmeilen
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=28d2ce0 ]

GEODE-1556: refactor and create unit tests for GFSH hostname

* extract hostname methods to HostName class
* create HostNameTest
* This closes #165 [kl...@apache.org]


> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Commented] (GEODE-1556) Create unit test for GFSH hostname

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Assigned] (GEODE-1349) "java.lang.InternalError: Memory Pool not found" on client

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-1349:


Assignee: Kirk Lund

> "java.lang.InternalError: Memory Pool not found" on client
> --
>
> Key: GEODE-1349
> URL: https://issues.apache.org/jira/browse/GEODE-1349
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>
> In a client based gemfire services they got this repeating exception and 
> cache failure: 
> Caused by: java.lang.InternalError: Memory Pool not found 
> at sun.management.MemoryPoolImpl.getUsage0(Native Method) 
> at sun.management.MemoryPoolImpl.getUsage(MemoryPoolImpl.java:96) 
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refreshMemoryPools(VMStats50.java:502)
>  
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refresh(VMStats50.java:631) 
> at 
> com.gemstone.gemfire.internal.HostStatSampler.sampleSpecialStats(HostStatSampler.java:501)
>  
> at 
> com.gemstone.gemfire.internal.HostStatSampler.run(HostStatSampler.java:195) 
> Unfortunately the logs have rolled and of not much use anymore. 
> In the code in VMStats50.refreshMemoryPools there is a check for if 
> (!mp.isValid()) ... But there is still a time window between the 
> MemoryPoolMXBean.isValid() call and the MemoryPoolMXBean.getUsage() call 
> where the JVM could have gotten rid of the pool. In addition, 
> MemoryPoolMXBean.getUsage() returns null by JVM contract and it doesn't seem 
> the code checks for null return value. 
> There is no check for null value GemFire 8.x. either. 
> Can this and similar code paths be reviewed please? 
> It has happened once and after restart the issue was gone. When this happened 
> it caused a service outage for the customer.



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

[jira] [Resolved] (GEODE-1459) "java.lang.InternalError: Memory Pool not found" on client

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-1459.
--
Resolution: Duplicate

> "java.lang.InternalError: Memory Pool not found" on client
> --
>
> Key: GEODE-1459
> URL: https://issues.apache.org/jira/browse/GEODE-1459
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Swapnil Bawaskar
>Assignee: Kirk Lund
>
> "Memory Pool not found" exception is thrown with the below stack trace:
> {noformat}
> Caused by: java.lang.InternalError: Memory Pool not found 
> at sun.management.MemoryPoolImpl.getUsage0(Native Method) 
> at sun.management.MemoryPoolImpl.getUsage(MemoryPoolImpl.java:96) 
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refreshMemoryPools(VMStats50.java:502)
>  
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refresh(VMStats50.java:631) 
> at 
> com.gemstone.gemfire.internal.HostStatSampler.sampleSpecialStats(HostStatSampler.java:501)
>  
> at 
> com.gemstone.gemfire.internal.HostStatSampler.run(HostStatSampler.java:195) 
> {noformat}



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

[jira] [Assigned] (GEODE-1459) "java.lang.InternalError: Memory Pool not found" on client

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-1459:


Assignee: Kirk Lund

> "java.lang.InternalError: Memory Pool not found" on client
> --
>
> Key: GEODE-1459
> URL: https://issues.apache.org/jira/browse/GEODE-1459
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Swapnil Bawaskar
>Assignee: Kirk Lund
>
> "Memory Pool not found" exception is thrown with the below stack trace:
> {noformat}
> Caused by: java.lang.InternalError: Memory Pool not found 
> at sun.management.MemoryPoolImpl.getUsage0(Native Method) 
> at sun.management.MemoryPoolImpl.getUsage(MemoryPoolImpl.java:96) 
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refreshMemoryPools(VMStats50.java:502)
>  
> at 
> com.gemstone.gemfire.internal.stats50.VMStats50.refresh(VMStats50.java:631) 
> at 
> com.gemstone.gemfire.internal.HostStatSampler.sampleSpecialStats(HostStatSampler.java:501)
>  
> at 
> com.gemstone.gemfire.internal.HostStatSampler.run(HostStatSampler.java:195) 
> {noformat}



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

[jira] [Commented] (GEODE-1556) Create unit test for GFSH hostname

[ASF GitHub Bot (JIRA)]

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

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

GitHub user gracemeilen opened a pull request:

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

GEODE-1556: refactor and create unit tests for GFSH hostname

* extract hostname methods to HostName class
* create HostNameTest

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

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

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

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


commit 1aee7634dd0964c0f6651c35f21d02fd47c9a286
Author: gmeilen 
Date:   2016-06-16T22:33:53Z

GEODE-1556: refactor and create unit tests for GFSH hostname

* extract hostname methods to HostName class
* create HostNameTest




> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Commented] (GEODE-1556) Create unit test for GFSH hostname

[ASF GitHub Bot (JIRA)]

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

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

Github user gracemeilen closed the pull request at:

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


> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Commented] (GEODE-1556) Create unit test for GFSH hostname

[ASF GitHub Bot (JIRA)]

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

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

GitHub user gracemeilen opened a pull request:

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

GEODE-1556 refactor and create unit test for GFSH hostname

* extract hostname methods to HostName class
* create HostNameTest

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

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

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

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


commit 6dedec632750b106214375249e5b442f2c00f58c
Author: gmeilen 
Date:   2016-06-16T22:12:27Z

GEODE-1556 refactor and create unit test for GFSH hostname

* extract hostname methods to HostName class
* create HostNameTest




> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Resolved] (GEODE-1543) Not using the the correct log level when exceptions are thrown while creating indexes.

[nabarun (JIRA)]

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

nabarun resolved GEODE-1543.

Resolution: Fixed

> Not using the the correct log level when exceptions are thrown while creating 
> indexes.
> --
>
> Key: GEODE-1543
> URL: https://issues.apache.org/jira/browse/GEODE-1543
> Project: Geode
>  Issue Type: Bug
>Reporter: nabarun
>
> When two or more peers join the cluster concurrently, only the first one that 
> joins will distribute the index creation while reading its cache.xml file, 
> the rest will create the index locally due to the distributed message and log 
> an error afterwards, while trying to create the index from its own cache.xml 
> file. This error message is currently being registered under "ERROR" log 
> level, and it should be registered under "WARNING", or even not be registered 
> at all since this "exception" is expected during startup (we could easily 
> cache the indexes created locally by other distributed members)
> {noformat}
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Index creation message got the pr Partitioned Region 
> @57fd91c9 [path='/ClientSessionRegionPosSrv'; dataPolicy=PARTITION; 
> gatewayEnabled=false; prId=1; isDestroyed=false; isClosed=false; 
> retryTimeout=360; serialNumber=7; partition 
> attributes=PartitionAttributes@1828508781[redundantCopies=1;localMaxMemory=5;totalMaxMemory=2147483647;totalNumBuckets=47;partitionResolver=null;colocatedWith=null;recoveryDelay=30;startupRecoveryDelay=6;FixedPartitionAttributes=null;partitionListeners=null];
>  on VM 10.69.252.112(host1-server2:21655):34609]
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] 
> LocalRegion.createOQLIndexes on region /ClientSessionRegionPosSrv
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Processing index creation message on this remote 
> partitioned region vm for indexes: ClientSessionRegionPosSrv.byUser 
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Started creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Indexfrom caluse=/ClientSessionRegionPosSrv, 
> Remote Request: true
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] QueryService 
> Index creation process for {}ClientSessionRegionPosSrv.byUser
> [fine 2016/05/12 09:37:01.750 BST host1-server2  Processor1> tid=0x44] Completed creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Remote Request: true
> [fine 2016/05/12 09:37:01.751 BST host1-server2  Processor1> tid=0x44] Multi Index creation completed on remote host and has 
> sent the reply to the originating vm.
> [fine 2016/05/12 09:37:01.769 BST host1-server2  tid=0x1] Started 
> creating index with Index Name :ClientSessionRegionPosSrv.byUser On 
> PartitionedRegion /ClientSessionRegionPosSrv, Indexfrom 
> caluse=/ClientSessionRegionPosSrv, Remote Request: false
> [error 2016/05/12 09:37:01.770 BST host1-server2  tid=0x1] Failed to 
> create index ClientSessionRegionPosSrv.byUser on region 
> /ClientSessionRegionPosSrv with exception: 
> com.gemstone.gemfire.cache.query.IndexNameConflictException: Index named ' 
> ClientSessionRegionPosSrv.byUser ' already exists.
> {noformat}



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

[jira] [Commented] (GEODE-420) locator ssl configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-420:
---

Commit f941188b3a8c4e69a1ae4bcdda6340ff4f01b358 in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f941188 ]

GEODE-420: Added tests to cover the ssl-enabled-components.
cleaned up code using AbstractDistributionConfig.checkAttributes to not require 
the method to return a value.
Added a validation step at the end of the initialization to validate the 
properties once all properties are set.


> locator ssl configuration
> -
>
> Key: GEODE-420
> URL: https://issues.apache.org/jira/browse/GEODE-420
> Project: Geode
>  Issue Type: New Feature
>  Components: locator
>Reporter: Darrel Schneider
>Assignee: Bruce Schuchardt
>
> We currently allow separate SSL configuration for cluster, server, gateway, 
> jmx-manager, and http-service.
> The "server" attributes configure the ssl connections from clients to a cache 
> server.
> The "gateway" attributes configure the ssl connections between a gateway 
> sender and receiver.
> The "jmx-manager" attributes configure the ssl connections between an admin 
> client (for example gfsh) and the jmx-manager.
> The "http-service" attributes configure the ssl connections between REST 
> clients and the http-service.
> The "cluster" attributes configure the ssl connections between the members of 
> a distributed system (peer-to-peer connections) AND to the locators.
> Using "cluster" for the connections to a locator can be a problem.
> Say you trust all your members of a distributed system since they are running 
> on your private network. So no need for ssl on the p2p connections.
> So you disable cluster-ssl. These means that your peers are locators are all 
> using unsecure connections.
> But some of these members are hosting a cache server and have clients 
> connecting to them. So you configure "server" ssl for the client to server 
> connections. But for your clients to find you servers they need to talk to 
> the locator. Since the clients are coming from the outside world you want 
> them to use SSL. So you configure "server" ssl on them for when they connect 
> to the cache server and "cluster" SSL on them for when they connect to the 
> locator. But your locators are configured with "cluster" SSL disabled so that 
> the p2p connects on the internal network will not be SSL.
> So you are either forced to have you client to locator connections to be 
> unsecure or you need to secure all the cluster connections forcing the peers 
> to also use SSL.
> I think we should introduce "locator" SSL configuration options that would 
> allow you to have just the locator and server using SSL and the "cluster" to 
> have SSL disabled.
> Something else to consider would be for the locator to be able to use SSL for 
> clients but non-SSL for locator-to-locator and peers-to-locator connections. 
> I think this would be more complicated because we would need to have 
> different ports that the locator listens on (one for clients and one for 
> locators and members).
>  



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

[jira] [Commented] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1521:


Commit f5093debbed715615ff773a14e1ed3d4d690ccc5 in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f5093de ]

GEODE-1521 - APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

Change to search for " count(" instead of "count(*)" because 'count' can accept 
more options than simply a star.

* This closes #155 [kl...@apache.org]


> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().  
> Specifically, one can do:  {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect.  Instead, the search 
> to apply the limt should look for {{" count("}}



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

[jira] [Commented] (GEODE-1543) Not using the the correct log level when exceptions are thrown while creating indexes.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1543:


Commit 8994be0564bb0622a4b9b99c4db10b714ebb8b76 in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8994be0 ]

GEODE-1543: Change the log level from error to info

* When multiple peers join the cluster conncurrently, only the first one 
that joins will distribute the index creation and other will try to create the 
index locally because of the distributed message and then log an error 
afterwards.
* This is an expected behaviour and hence should not be logged as error but 
rather as a info.

This closes #156


> Not using the the correct log level when exceptions are thrown while creating 
> indexes.
> --
>
> Key: GEODE-1543
> URL: https://issues.apache.org/jira/browse/GEODE-1543
> Project: Geode
>  Issue Type: Bug
>Reporter: nabarun
>
> When two or more peers join the cluster concurrently, only the first one that 
> joins will distribute the index creation while reading its cache.xml file, 
> the rest will create the index locally due to the distributed message and log 
> an error afterwards, while trying to create the index from its own cache.xml 
> file. This error message is currently being registered under "ERROR" log 
> level, and it should be registered under "WARNING", or even not be registered 
> at all since this "exception" is expected during startup (we could easily 
> cache the indexes created locally by other distributed members)
> {noformat}
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Index creation message got the pr Partitioned Region 
> @57fd91c9 [path='/ClientSessionRegionPosSrv'; dataPolicy=PARTITION; 
> gatewayEnabled=false; prId=1; isDestroyed=false; isClosed=false; 
> retryTimeout=360; serialNumber=7; partition 
> attributes=PartitionAttributes@1828508781[redundantCopies=1;localMaxMemory=5;totalMaxMemory=2147483647;totalNumBuckets=47;partitionResolver=null;colocatedWith=null;recoveryDelay=30;startupRecoveryDelay=6;FixedPartitionAttributes=null;partitionListeners=null];
>  on VM 10.69.252.112(host1-server2:21655):34609]
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] 
> LocalRegion.createOQLIndexes on region /ClientSessionRegionPosSrv
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Processing index creation message on this remote 
> partitioned region vm for indexes: ClientSessionRegionPosSrv.byUser 
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Started creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Indexfrom caluse=/ClientSessionRegionPosSrv, 
> Remote Request: true
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] QueryService 
> Index creation process for {}ClientSessionRegionPosSrv.byUser
> [fine 2016/05/12 09:37:01.750 BST host1-server2  Processor1> tid=0x44] Completed creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Remote Request: true
> [fine 2016/05/12 09:37:01.751 BST host1-server2  Processor1> tid=0x44] Multi Index creation completed on remote host and has 
> sent the reply to the originating vm.
> [fine 2016/05/12 09:37:01.769 BST host1-server2  tid=0x1] Started 
> creating index with Index Name :ClientSessionRegionPosSrv.byUser On 
> PartitionedRegion /ClientSessionRegionPosSrv, Indexfrom 
> caluse=/ClientSessionRegionPosSrv, Remote Request: false
> [error 2016/05/12 09:37:01.770 BST host1-server2  tid=0x1] Failed to 
> create index ClientSessionRegionPosSrv.byUser on region 
> /ClientSessionRegionPosSrv with exception: 
> com.gemstone.gemfire.cache.query.IndexNameConflictException: Index named ' 
> ClientSessionRegionPosSrv.byUser ' already exists.
> {noformat}



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

[jira] [Commented] (GEODE-1544) Fail to initiate final check when network partition occurs

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1544:


Commit f9c426e3f9c64897529337737c34f9a7b517c2cc in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~jchen21]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f9c426e ]

GEODE-1544: Fail to initiate final check when network partition occurs

Currently, suspect request is only sent to a limited number of members,
when there are more than 4 members in the distributed system. It is
possible that the recipients of suspect request is unreachable due to
network partition. This fix makes sure that the recipients of suspect
request are not the suspect members. So that suspect request will be
processed.


> Fail to initiate final check when network partition occurs
> --
>
> Key: GEODE-1544
> URL: https://issues.apache.org/jira/browse/GEODE-1544
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M3
>
>
> When network partition occurs, something keeps the losing side of a network 
> partition from initiating any final checks on members no longer reachable. 



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

[jira] [Commented] (GEODE-11) Lucene Integration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-11:
--

Commit fae0f90fa1652d30b1e1fe90eb2e1baa2f2e835c in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=fae0f90 ]

GEODE-11: Support indexing values that are Strings or Numbers

Adding support to index values that are strings or numbers, by providing
a special field name LuceneIndex.REGION_VALUE_FIELD that indicates the
entire value should be indexed.


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Commented] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-68:
--

Commit a10f83e1d942c14c5af0e298e097fa9b87508241 in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=a10f83e ]

GEODE-68: GFSH SYS_HOST_NAME variable should report hostname if available

* This closes #157 [kl...@apache.org]


> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
>  Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.  
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- | 
> --
> APP_COLLECTION_LIMIT   | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS   | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE   | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME   | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER  | basic
> SYS_CLASSPATH  | 
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME  | wmarkito
> SYS_JAVA_VERSION   | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR  |
> SYS_USER   | wmarkito
> SYS_USER_HOME  | /Users/wmarkito
> {code}



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

[jira] [Commented] (GEODE-1374) Run tests labeled 'flaky' in a separate build task

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1374:


Commit e516b86baf894c08c5b2b080a1d25a25572a8bbd in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e516b86 ]

GEODE-1374: Run flaky tests in a separate gradle task

Add a new test task specifically for running tests annotated with
@FlakyTest.  This allows us to isolate tests that exhibit
intermittent failures.  Other changes include:

- Exclude flaky tests from test, integrationTest, uiTest, and
  distributedTest tasks
- Cleanup how tests are found using the minimum set of
  include/exclude categories


> Run tests labeled 'flaky' in a separate build task
> --
>
> Key: GEODE-1374
> URL: https://issues.apache.org/jira/browse/GEODE-1374
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>
> We have a number of tests that have been annotated with the @FlakyTest 
> category.  These tests exhibit intermittent failures.  We should exclude 
> these tests from the normal test tasks and create a special task to run these 
> separately.  This will help to isolate test failures so we can focus and 
> prioritize test fixes.



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

[jira] [Commented] (GEODE-835) Replace joptsimple source with a binary dependency

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-835:
---

Commit 921bec11d89866e3332fd3e7ce2ac2f9e8526eb1 in incubator-geode's branch 
refs/heads/feature/GEODE-420 from [~gmeilen]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=921bec1 ]

GEODE-835: replace geode-joptsimple with jopt-simple dependency

* remove geode-joptsimple module
* add dependency on jopt-simple 5.0.1
* wrap value of --J option with quotes
* create tests OptionJFormatterTest, CommentSkipHelperTest, 
GfshParserIntegrationTest
* invalid arguments are silently ignored
* This closes #162 [kl...@apache.org]


> Replace joptsimple source with a binary dependency
> --
>
> Key: GEODE-835
> URL: https://issues.apache.org/jira/browse/GEODE-835
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh
>Reporter: Anthony Baker
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
> Attachments: joptsimple.patch
>
>
> The gemfire-jopsimple folder contains modified source code from the 
> joptsimple library.  We should replace this with a binary dependency.



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

[jira] [Commented] (GEODE-11) Lucene Integration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-11:
-

GitHub user aparnard opened a pull request:

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

GEODE-11 Creating a new LuceneQueryException and removing ParseException 
from the API

Adding a new exception to wrap lucene exceptions called 
LuceneQueryException. Removed lucene exceptions from the public API.

Added LuceneQueryException to the search method.

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

$ git pull https://github.com/aparnard/incubator-geode 
feature/GEODE-11-LuceneQueryException

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

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


commit 2ac5edb0917683b820647f45aa3c60899093ac1a
Author: Aparna Dharmakkan 
Date:   2016-06-16T18:20:13Z

GEODE-11: Removed ParseException from LuceneQueryFactory.create, added 
LuceneQueryException

Adding a new exception to wrap lucene exceptions called 
LuceneQueryException. Removed lucene exceptions from the public API.

commit 678858d63fcd089f341bc95c2f0026e46b8dbe13
Author: Aparna Dharmakkan 
Date:   2016-06-16T21:12:42Z

GEODE-11: Added LuceneQueryException to search signature

Search will now throw a LuceneQueryException if a query cannot be parsed.




> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Resolved] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-1521.
-
Resolution: Fixed

Delivered

> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().  
> Specifically, one can do:  {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect.  Instead, the search 
> to apply the limt should look for {{" count("}}



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

[jira] [Resolved] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-68.
---
Resolution: Fixed

Delivered

> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
>  Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.  
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- | 
> --
> APP_COLLECTION_LIMIT   | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS   | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE   | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME   | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER  | basic
> SYS_CLASSPATH  | 
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME  | wmarkito
> SYS_JAVA_VERSION   | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR  |
> SYS_USER   | wmarkito
> SYS_USER_HOME  | /Users/wmarkito
> {code}



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

[jira] [Resolved] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH

[Kevin Duling (JIRA)]

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

Kevin Duling resolved GEODE-744.

Resolution: Fixed

> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from 
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the 
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and, 
> afterwards, executes two queries, one using lower case and other using upper 
> case. You can see from the console that ouput is different, one returns the 
> actual size (1500) and the other one returns the default APP_FETCH_SIZE 
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner 
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to 
> compare strings without using the actual word case. Is not enough to add more 
> "or" to the comparison like we are currently doing with since keywords like 
> "Count" or "coUn" will still break the functionallity. We should compare 
> everything using lower case or upper case, it doesn't matter which one, or at 
> least make sure that gfsh converts the query to upper/lower case before 
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT")  query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}



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

[jira] [Commented] (GEODE-1549) Incorrect "Help" hyperlink in pulse

[ASF GitHub Bot (JIRA)]

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

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

Github user jinmeiliao commented on the issue:

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


> Incorrect "Help" hyperlink in pulse
> ---
>
> Key: GEODE-1549
> URL: https://issues.apache.org/jira/browse/GEODE-1549
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Srikanth Manvi
>Assignee: Srikanth Manvi
>Priority: Minor
>
> When we click on "Help" link on the top right corner in pulse we get 
> PageNotFound



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

[jira] [Commented] (GEODE-1549) Incorrect "Help" hyperlink in pulse

[ASF GitHub Bot (JIRA)]

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

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

Github user sboorlagadda commented on the issue:

https://github.com/apache/incubator-geode/pull/161
  
@smanvi-pivotal The PR gets updated automatically when you push the new 
commit on your feature branch.


> Incorrect "Help" hyperlink in pulse
> ---
>
> Key: GEODE-1549
> URL: https://issues.apache.org/jira/browse/GEODE-1549
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Srikanth Manvi
>Assignee: Srikanth Manvi
>Priority: Minor
>
> When we click on "Help" link on the top right corner in pulse we get 
> PageNotFound



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

[jira] [Created] (GEODE-1557) LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance fails with suspect string error

[Aparna Dharmakkan (JIRA)]

Aparna Dharmakkan created GEODE-1557:


 Summary: 
LuceneQueriesPeerPRDUnitTest.returnCorrectResultsAfterRebalance fails with 
suspect string error
 Key: GEODE-1557
 URL: https://issues.apache.org/jira/browse/GEODE-1557
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: Aparna Dharmakkan


This test failed with the following error

{noformat}
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 61460
[error 2016/06/16 12:02:33.844 PDT  tid=1453] Unable to save to 
lucene index
com.gemstone.gemfire.internal.cache.BucketNotFoundException: User bucket was 
not found for region Partitioned Region @149884aa [path='/region'; 
dataPolicy=PARTITION; prId=92; isDestroyed=false; isClosed=false; 
retryTimeout=360; serialNumber=10558; partition 
attributes=PartitionAttributes@1660363202[redundantCopies=0;localMaxMemory=409;totalMaxMemory=2147483647;totalNumBuckets=113;partitionResolver=null;colocatedWith=null;recoveryDelay=-1;startupRecoveryDelay=0;FixedPartitionAttributes=null;partitionListeners=null];
 on VM 192.168.1.17(10580):1025]key 1 callbackarg null
at 
com.gemstone.gemfire.cache.lucene.internal.PartitionedRepositoryManager.getRepository(PartitionedRepositoryManager.java:102)
at 
com.gemstone.gemfire.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:72)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:168)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:87)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:613)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1058)
---
{noformat}

It looks like this test is doing a rebalance, so it may be expected that 
buckets are not found when writing to the lucent index. The system should 
probably not log an error just because a bucket has moved.



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

[jira] [Commented] (GEODE-1549) Incorrect "Help" hyperlink in pulse

[ASF GitHub Bot (JIRA)]

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

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

Github user smanvi-pivotal commented on the issue:

https://github.com/apache/incubator-geode/pull/161
  
Thanks for pointing out @sboorlagadda and @kirklund. Will make the change. 
Was not aware that there was separate documentation for Geode.



> Incorrect "Help" hyperlink in pulse
> ---
>
> Key: GEODE-1549
> URL: https://issues.apache.org/jira/browse/GEODE-1549
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Srikanth Manvi
>Assignee: Srikanth Manvi
>Priority: Minor
>
> When we click on "Help" link on the top right corner in pulse we get 
> PageNotFound



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

[jira] [Commented] (GEODE-1549) Incorrect "Help" hyperlink in pulse

[ASF GitHub Bot (JIRA)]

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

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

Github user sboorlagadda commented on the issue:

https://github.com/apache/incubator-geode/pull/161
  
@smanvi-pivotal  Shouldn`t we refer geode docs rather than gemfire? 
Eg: 
http://**geode.**docs.pivotal.io/**docs**/tools_modules/pulse/chapter_overview.html


> Incorrect "Help" hyperlink in pulse
> ---
>
> Key: GEODE-1549
> URL: https://issues.apache.org/jira/browse/GEODE-1549
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Srikanth Manvi
>Assignee: Srikanth Manvi
>Priority: Minor
>
> When we click on "Help" link on the top right corner in pulse we get 
> PageNotFound



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

[jira] [Commented] (GEODE-1549) Incorrect "Help" hyperlink in pulse

[ASF GitHub Bot (JIRA)]

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/161
  
Changes look good. I'll pull this in to commit!


> Incorrect "Help" hyperlink in pulse
> ---
>
> Key: GEODE-1549
> URL: https://issues.apache.org/jira/browse/GEODE-1549
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Srikanth Manvi
>Assignee: Srikanth Manvi
>Priority: Minor
>
> When we click on "Help" link on the top right corner in pulse we get 
> PageNotFound



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

[jira] [Commented] (GEODE-1374) Run tests labeled 'flaky' in a separate build task

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1374:


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

GEODE-1374: Run flaky tests in a separate gradle task

Add a new test task specifically for running tests annotated with
@FlakyTest.  This allows us to isolate tests that exhibit
intermittent failures.  Other changes include:

- Exclude flaky tests from test, integrationTest, uiTest, and
  distributedTest tasks
- Cleanup how tests are found using the minimum set of
  include/exclude categories


> Run tests labeled 'flaky' in a separate build task
> --
>
> Key: GEODE-1374
> URL: https://issues.apache.org/jira/browse/GEODE-1374
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>
> We have a number of tests that have been annotated with the @FlakyTest 
> category.  These tests exhibit intermittent failures.  We should exclude 
> these tests from the normal test tasks and create a special task to run these 
> separately.  This will help to isolate test failures so we can focus and 
> prioritize test fixes.



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

[jira] [Assigned] (GEODE-1556) Create unit test for GFSH hostname

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-1556:


Assignee: Kirk Lund

> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Updated] (GEODE-1556) Create unit test for GFSH hostname

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1556:
-
Assignee: Grace Meilen  (was: Kirk Lund)

> Create unit test for GFSH hostname
> --
>
> Key: GEODE-1556
> URL: https://issues.apache.org/jira/browse/GEODE-1556
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a 
> unit test for this.



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

[jira] [Assigned] (GEODE-117) gfsh put ignores --skip-if-exists flag

[Kevin Duling (JIRA)]

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

Kevin Duling reassigned GEODE-117:
--

Assignee: Kevin Duling  (was: Srikanth Manvi)

> gfsh put ignores --skip-if-exists flag
> --
>
> Key: GEODE-117
> URL: https://issues.apache.org/jira/browse/GEODE-117
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Dan Smith
>Assignee: Kevin Duling
>  Labels: gfsh, starter
>
> Someone hit this on a forum post:
> https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21
> I looked into the code, and it looks like the flag gets lost somewhere along 
> the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, 
> but that flag is not used; the function just does a normal put.



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

[jira] [Created] (GEODE-1556) Create unit test for GFSH hostname

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-1556:


 Summary: Create unit test for GFSH hostname
 Key: GEODE-1556
 URL: https://issues.apache.org/jira/browse/GEODE-1556
 Project: Geode
  Issue Type: Test
  Components: gfsh
Reporter: Kirk Lund


Fix for GEODE-68 introduced new hostname support to GFSH. Need to create a unit 
test for this.



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

[jira] [Commented] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1521:


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

GEODE-1521 - APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

Change to search for " count(" instead of "count(*)" because 'count' can accept 
more options than simply a star.

* This closes #155 [kl...@apache.org]


> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().  
> Specifically, one can do:  {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect.  Instead, the search 
> to apply the limt should look for {{" count("}}



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

[jira] [Commented] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().  
> Specifically, one can do:  {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect.  Instead, the search 
> to apply the limt should look for {{" count("}}



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

[jira] [Commented] (GEODE-1487) CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1487:


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

GEODE-1487: annotate FlakyTests in GemfireDataCommandsDUnitTest


> CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS
> -
>
> Key: GEODE-1487
> URL: https://issues.apache.org/jira/browse/GEODE-1487
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>
> Build #482 (May 28, 2016 3:42:00 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://builds.apache.org/job/Geode-nightly/482/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testRebalanceForEntireDS/
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> asf902.gq1.ygridcore.net with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:126)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:115)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:106)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.setupTestRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1882)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1862)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.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:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   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 

[jira] [Commented] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-68:
--

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

GEODE-68: GFSH SYS_HOST_NAME variable should report hostname if available

* This closes #157 [kl...@apache.org]


> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
>  Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.  
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- | 
> --
> APP_COLLECTION_LIMIT   | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS   | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE   | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME   | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER  | basic
> SYS_CLASSPATH  | 
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME  | wmarkito
> SYS_JAVA_VERSION   | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR  |
> SYS_USER   | wmarkito
> SYS_USER_HOME  | /Users/wmarkito
> {code}



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

[jira] [Resolved] (GEODE-835) Replace joptsimple source with a binary dependency

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-835.
-
Resolution: Fixed

> Replace joptsimple source with a binary dependency
> --
>
> Key: GEODE-835
> URL: https://issues.apache.org/jira/browse/GEODE-835
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh
>Reporter: Anthony Baker
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
> Attachments: joptsimple.patch
>
>
> The gemfire-jopsimple folder contains modified source code from the 
> joptsimple library.  We should replace this with a binary dependency.



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

[jira] [Commented] (GEODE-835) Replace joptsimple source with a binary dependency

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-835:
---

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

GEODE-835: replace geode-joptsimple with jopt-simple dependency

* remove geode-joptsimple module
* add dependency on jopt-simple 5.0.1
* wrap value of --J option with quotes
* create tests OptionJFormatterTest, CommentSkipHelperTest, 
GfshParserIntegrationTest
* invalid arguments are silently ignored
* This closes #162 [kl...@apache.org]


> Replace joptsimple source with a binary dependency
> --
>
> Key: GEODE-835
> URL: https://issues.apache.org/jira/browse/GEODE-835
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh
>Reporter: Anthony Baker
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
> Attachments: joptsimple.patch
>
>
> The gemfire-jopsimple folder contains modified source code from the 
> joptsimple library.  We should replace this with a binary dependency.



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

[jira] [Commented] (GEODE-835) Replace joptsimple source with a binary dependency

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-835:
--

Github user asfgit closed the pull request at:

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


> Replace joptsimple source with a binary dependency
> --
>
> Key: GEODE-835
> URL: https://issues.apache.org/jira/browse/GEODE-835
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh
>Reporter: Anthony Baker
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
> Attachments: joptsimple.patch
>
>
> The gemfire-jopsimple folder contains modified source code from the 
> joptsimple library.  We should replace this with a binary dependency.



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

[jira] [Commented] (GEODE-835) Replace joptsimple source with a binary dependency

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on GEODE-835:
--

GitHub user gracemeilen opened a pull request:

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

GEODE-835: replace geode-joptsimple with jopt-simple dependency

GEODE-835: replace geode-joptsimple with jolt-simple dependency

* remove geode-joptsimple module
* add dependency on jopt-simple 5.0.1
* wrap value of --J option with quotes
* create tests OptionJFormatterTest, CommentSkipHelperTest, 
GfshParserIntegrationTest
* invalid arguments are silently ignored

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

$ git pull https://github.com/gracemeilen/incubator-geode develop

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

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






> Replace joptsimple source with a binary dependency
> --
>
> Key: GEODE-835
> URL: https://issues.apache.org/jira/browse/GEODE-835
> Project: Geode
>  Issue Type: Bug
>  Components: build, gfsh
>Reporter: Anthony Baker
>Assignee: Kirk Lund
> Fix For: 1.0.0-incubating.M3
>
> Attachments: joptsimple.patch
>
>
> The gemfire-jopsimple folder contains modified source code from the 
> joptsimple library.  We should replace this with a binary dependency.



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

[jira] [Resolved] (GEODE-1555) CI Failure: clientAuthnAndAuthzFailoverTest log contains NPE

[Scott Jewell (JIRA)]

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

Scott Jewell resolved GEODE-1555.
-
Resolution: Invalid

This error occurred on internal system and should be reported
on internal reporting system

> CI Failure: clientAuthnAndAuthzFailoverTest log contains NPE
> 
>
> Key: GEODE-1555
> URL: https://issues.apache.org/jira/browse/GEODE-1555
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Scott Jewell
>
> Host name: cc4-rh6
> OS name: Linux
> Architecture: amd64
> OS version: 2.6.32-122.el6.x86_64
> Java version: 1.8.0_66
> Java vm name: Java HotSpot(TM) 64-Bit Server VM
> Java vendor: Oracle Corporation
> Java home: /export/java/users/java_share/jdk/1.8.0_66/x86_64.linux/jre
>   #
>   
>   GemFire Version 9.0.0-SNAPSHOT
>   Source Date: 2016-06-14 17:23:15 -0700
>   Source Revision: 0f2bb8fa713d391b59cb5e3f8e8641194bb915e9
>   Source Repository: develop
>   
>   Build Id: build 061416
>   Build Date: 2016-06-14 22:08:22 -0700
>   Build Version: 9.0.0-SNAPSHOT build 061416 2016-06-14 22:08:22 -0700 javac 
> 1.8.0_66
>   Build JDK: Java 1.8.0_66
>   Build Platform: Linux 2.6.32-122.el6.x86_64 amd64
>   
>   #
> Test was run from 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/gemfire-test/build/resources/test/smoketest/newsmoke.bt
> Test:
> smoketest/moresmoke/clientAuthnAndAuthzFailoverTest.conf
>A=bridge
>B=writer
>C=reader
>D=query
>E=invalid
>bridgeHosts=5
>bridgeThreadsPerVM=1
>bridgeVMsPerHost=1
>invalidHosts=1
>invalidThreadsPerVM=1
>invalidVMsPerHost=1
>nPutKeyRange=200
>queryHosts=5
>queryThreadsPerVM=1
>queryVMsPerHost=1
>readerHosts=5
>readerThreadsPerVM=3
>readerVMsPerHost=1
>writerHosts=5
>writerThreadsPerVM=3
>writerVMsPerHost=1
> Run with local.conf:
> //disable lock memory for smoke test.
> hydra.GemFirePrms-lockMemory = false;
> //randomSeed extracted from test:
> hydra.Prms-randomSeed=1465990393045;
> *** Test failed with this error:
> CLIENT vm_32_thr_52_reader4_cc4-rh6_17761
> ENDTASK[1] util.LogChecker.HydraTask_checkLogs
> ERROR util.TestException: 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
>  contains java.lang.NullPointerException
> util.TestException: 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
>  contains java.lang.NullPointerException
>   at util.LogChecker.HydraTask_checkLogs(LogChecker.java:71)
>   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 hydra.MethExecutor.execute(MethExecutor.java:199)
>   at hydra.MethExecutor.execute(MethExecutor.java:163)
>   at hydra.TestTask.execute(TestTask.java:195)
>   at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)



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

[jira] [Commented] (GEODE-1555) CI Failure: clientAuthnAndAuthzFailoverTest log contains NPE

[Scott Jewell (JIRA)]

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

Scott Jewell commented on GEODE-1555:
-

Will update this ticket with location of artifacts when available.  

This occurred in build 727 
bt.smoketest/moresmoke/clientAuthnAndAuthzFailoverTest.conf

> CI Failure: clientAuthnAndAuthzFailoverTest log contains NPE
> 
>
> Key: GEODE-1555
> URL: https://issues.apache.org/jira/browse/GEODE-1555
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Scott Jewell
>
> Host name: cc4-rh6
> OS name: Linux
> Architecture: amd64
> OS version: 2.6.32-122.el6.x86_64
> Java version: 1.8.0_66
> Java vm name: Java HotSpot(TM) 64-Bit Server VM
> Java vendor: Oracle Corporation
> Java home: /export/java/users/java_share/jdk/1.8.0_66/x86_64.linux/jre
>   #
>   
>   GemFire Version 9.0.0-SNAPSHOT
>   Source Date: 2016-06-14 17:23:15 -0700
>   Source Revision: 0f2bb8fa713d391b59cb5e3f8e8641194bb915e9
>   Source Repository: develop
>   
>   Build Id: build 061416
>   Build Date: 2016-06-14 22:08:22 -0700
>   Build Version: 9.0.0-SNAPSHOT build 061416 2016-06-14 22:08:22 -0700 javac 
> 1.8.0_66
>   Build JDK: Java 1.8.0_66
>   Build Platform: Linux 2.6.32-122.el6.x86_64 amd64
>   
>   #
> Test was run from 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/gemfire-test/build/resources/test/smoketest/newsmoke.bt
> Test:
> smoketest/moresmoke/clientAuthnAndAuthzFailoverTest.conf
>A=bridge
>B=writer
>C=reader
>D=query
>E=invalid
>bridgeHosts=5
>bridgeThreadsPerVM=1
>bridgeVMsPerHost=1
>invalidHosts=1
>invalidThreadsPerVM=1
>invalidVMsPerHost=1
>nPutKeyRange=200
>queryHosts=5
>queryThreadsPerVM=1
>queryVMsPerHost=1
>readerHosts=5
>readerThreadsPerVM=3
>readerVMsPerHost=1
>writerHosts=5
>writerThreadsPerVM=3
>writerVMsPerHost=1
> Run with local.conf:
> //disable lock memory for smoke test.
> hydra.GemFirePrms-lockMemory = false;
> //randomSeed extracted from test:
> hydra.Prms-randomSeed=1465990393045;
> *** Test failed with this error:
> CLIENT vm_32_thr_52_reader4_cc4-rh6_17761
> ENDTASK[1] util.LogChecker.HydraTask_checkLogs
> ERROR util.TestException: 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
>  contains java.lang.NullPointerException
> util.TestException: 
> /cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
>  contains java.lang.NullPointerException
>   at util.LogChecker.HydraTask_checkLogs(LogChecker.java:71)
>   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 hydra.MethExecutor.execute(MethExecutor.java:199)
>   at hydra.MethExecutor.execute(MethExecutor.java:163)
>   at hydra.TestTask.execute(TestTask.java:195)
>   at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)



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

[jira] [Created] (GEODE-1555) CI Failure: clientAuthnAndAuthzFailoverTest log contains NPE

[Scott Jewell (JIRA)]

Scott Jewell created GEODE-1555:
---

 Summary: CI Failure: clientAuthnAndAuthzFailoverTest log contains 
NPE
 Key: GEODE-1555
 URL: https://issues.apache.org/jira/browse/GEODE-1555
 Project: Geode
  Issue Type: Bug
  Components: client/server
Reporter: Scott Jewell


Host name: cc4-rh6
OS name: Linux
Architecture: amd64
OS version: 2.6.32-122.el6.x86_64
Java version: 1.8.0_66
Java vm name: Java HotSpot(TM) 64-Bit Server VM
Java vendor: Oracle Corporation
Java home: /export/java/users/java_share/jdk/1.8.0_66/x86_64.linux/jre

  #
  
  GemFire Version 9.0.0-SNAPSHOT
  Source Date: 2016-06-14 17:23:15 -0700
  Source Revision: 0f2bb8fa713d391b59cb5e3f8e8641194bb915e9
  Source Repository: develop
  
  Build Id: build 061416
  Build Date: 2016-06-14 22:08:22 -0700
  Build Version: 9.0.0-SNAPSHOT build 061416 2016-06-14 22:08:22 -0700 javac 
1.8.0_66
  Build JDK: Java 1.8.0_66
  Build Platform: Linux 2.6.32-122.el6.x86_64 amd64
  
  #


Test was run from 
/cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/gemfire-test/build/resources/test/smoketest/newsmoke.bt

Test:
smoketest/moresmoke/clientAuthnAndAuthzFailoverTest.conf
   A=bridge
   B=writer
   C=reader
   D=query
   E=invalid
   bridgeHosts=5
   bridgeThreadsPerVM=1
   bridgeVMsPerHost=1
   invalidHosts=1
   invalidThreadsPerVM=1
   invalidVMsPerHost=1
   nPutKeyRange=200
   queryHosts=5
   queryThreadsPerVM=1
   queryVMsPerHost=1
   readerHosts=5
   readerThreadsPerVM=3
   readerVMsPerHost=1
   writerHosts=5
   writerThreadsPerVM=3
   writerVMsPerHost=1

Run with local.conf:
//disable lock memory for smoke test.
hydra.GemFirePrms-lockMemory = false;



//randomSeed extracted from test:
hydra.Prms-randomSeed=1465990393045;

*** Test failed with this error:
CLIENT vm_32_thr_52_reader4_cc4-rh6_17761
ENDTASK[1] util.LogChecker.HydraTask_checkLogs
ERROR util.TestException: 
/cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
 contains java.lang.NullPointerException

util.TestException: 
/cc4-rh6a/users/build/jenkins/blds/workspace/GemFire_develop_MoreSmoke/gemfire/closed/pivotalgf-assembly/build/moreSmokeTest/clientAuthnAndAuthzFailoverTest-0615-043309/bgexec15274_27208.log
 contains java.lang.NullPointerException
at util.LogChecker.HydraTask_checkLogs(LogChecker.java:71)
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 hydra.MethExecutor.execute(MethExecutor.java:199)
at hydra.MethExecutor.execute(MethExecutor.java:163)
at hydra.TestTask.execute(TestTask.java:195)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)



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

[jira] [Commented] (GEODE-1421) CI Failure: MemoryThresholdsDUnitTest.testDRLoadRejection

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1421:


Commit cdfb9401cff5b86ebcf8fb424bb36139bba36a91 in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cdfb940 ]

GEODE-1421: improve test to provide more info on failure

I ran the test 1000 times and they all passed.
Assertions are now done on the member that does
the get that should have also stored the entry
in the cache.


> CI Failure: MemoryThresholdsDUnitTest.testDRLoadRejection
> -
>
> Key: GEODE-1421
> URL: https://issues.apache.org/jira/browse/GEODE-1421
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Sai Boorlagadda
>Assignee: Darrel Schneider
>  Labels: CI
> Fix For: 1.0.0-incubating.M3
>
>
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.management.MemoryThresholdsDUnitTest$68.run in VM 
> 2 running on Host venezuela.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.management.MemoryThresholdsDUnitTest$68.run in VM 
> 2 running on Host venezuela.gemstone.com with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
>   at 
> com.gemstone.gemfire.cache.management.MemoryThresholdsDUnitTest.testDRLoadRejection(MemoryThresholdsDUnitTest.java:2019)
>   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 junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   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.GeneratedMethodAccessor369.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.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.GeneratedMethodAccessor368.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
>   at 
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
>   at 
> 

[jira] [Commented] (GEODE-1544) Fail to initiate final check when network partition occurs

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1544:


Commit 144e7d135cdd3d73d0b291a8e3c089bf320bf400 in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~jchen21]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=144e7d1 ]

GEODE-1544: Fail to initiate final check when network partition occurs

Currently, suspect request is only sent to a limited number of members,
when there are more than 4 members in the distributed system. It is
possible that the recipients of suspect request is unreachable due to
network partition. This fix makes sure that the recipients of suspect
request are not the suspect members. So that suspect request will be
processed.


> Fail to initiate final check when network partition occurs
> --
>
> Key: GEODE-1544
> URL: https://issues.apache.org/jira/browse/GEODE-1544
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M3
>
>
> When network partition occurs, something keeps the losing side of a network 
> partition from initiating any final checks on members no longer reachable. 



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

[jira] [Commented] (GEODE-11) Lucene Integration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-11:
--

Commit f59e8d0b22c7ebb4600b8cfa9c1e0b00d3925f05 in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f59e8d0 ]

GEODE-11: Support indexing values that are Strings or Numbers

Adding support to index values that are strings or numbers, by providing
a special field name LuceneIndex.REGION_VALUE_FIELD that indicates the
entire value should be indexed.


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Commented] (GEODE-1545) add a test case for query JSON object in geode-lucene

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1545:


Commit 0d5de3e3f5e69f4de683ea289ac58d36280f7d6d in incubator-geode's branch 
refs/heads/feature/GEODE-835 from zhouxh
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0d5de3e ]

GEODE-1545: fix compile problem caused by merge


> add a test case for query JSON object in geode-lucene
> -
>
> Key: GEODE-1545
> URL: https://issues.apache.org/jira/browse/GEODE-1545
> Project: Geode
>  Issue Type: Test
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>
> We did support query on JSON object, but we don't have a test yet. 



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

[jira] [Commented] (GEODE-1542) shared/unordered tcp/ip connection times out, initiating suspicion

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1542:


Commit 3de21f56a7381cea926be9fe33c8e1a1456c564d in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3de21f5 ]

GEODE-1542: Removing a bogus static import of javafx class

This class picked up a bad import of a javafx class. With openjdk this
causes compile errors.


> shared/unordered tcp/ip connection times out, initiating suspicion
> --
>
> Key: GEODE-1542
> URL: https://issues.apache.org/jira/browse/GEODE-1542
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Bruce Schuchardt
> Fix For: 1.0.0-incubating.M3
>
>
> I recently diagnosed a membership failure that was initiated when one member 
> (N) timed out its shared/unordered tcp/ip connection to another member (M).  
> Member M initiated suspect processing that lead to kicking member N out of 
> the system.  We need to either stop timing out shared/unordered connections 
> or have an orderly shutdown mechanism so that we don't initiate suspect 
> processing.
> The final-check that M performed showed something odd.  Member N never logged 
> that it processed a final check from M.  Member M logged that it had 
> connected to N and read a status byte from it.  The byte had the value 21, 
> which is not a valid response to a final check (it should be 0 or 0x7B).
> {noformat}
> Received [21, ent(clientgemfire3_ent_19225:19225):1028]
> {noformat}
> I verified that M used the correct tcp/ip port for N, so this is very odd and 
> needs to be investigated.



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

[jira] [Commented] (GEODE-1547) Add new committer to website

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1547:


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

GEODE-1547: Added Nabarun Nag to list of committers on website's Community 
page, reformatted list so columns balance


> Add new committer to website
> 
>
> Key: GEODE-1547
> URL: https://issues.apache.org/jira/browse/GEODE-1547
> Project: Geode
>  Issue Type: Improvement
>  Components: web-content
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Minor
>
> Add Nabarun Nag to the list of committers on the Geode website's Community 
> page. Build and deploy the updated site.



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

[jira] [Commented] (GEODE-1470) Upgrade log4j to 2.6

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1470:


Commit 0f2bb8fa713d391b59cb5e3f8e8641194bb915e9 in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0f2bb8f ]

GEODE-1470: Upgrade log4j to 2.6.1

* This closes #154 [kl...@apache.org]


> Upgrade log4j to 2.6
> 
>
> Key: GEODE-1470
> URL: https://issues.apache.org/jira/browse/GEODE-1470
> Project: Geode
>  Issue Type: Improvement
>  Components: logging
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> The new version of log4j (2.6) has made improvements to make it "garbage 
> free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We 
> should upgrade to this version to reap the benefits.



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

[jira] [Commented] (GEODE-1543) Not using the the correct log level when exceptions are thrown while creating indexes.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1543:


Commit 612a9d99566ac71421e5cd986c6ce6e391dedd30 in incubator-geode's branch 
refs/heads/feature/GEODE-835 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=612a9d9 ]

GEODE-1543: Change the log level from error to info

* When multiple peers join the cluster conncurrently, only the first one 
that joins will distribute the index creation and other will try to create the 
index locally because of the distributed message and then log an error 
afterwards.
* This is an expected behaviour and hence should not be logged as error but 
rather as a info.

This closes #156


> Not using the the correct log level when exceptions are thrown while creating 
> indexes.
> --
>
> Key: GEODE-1543
> URL: https://issues.apache.org/jira/browse/GEODE-1543
> Project: Geode
>  Issue Type: Bug
>Reporter: nabarun
>
> When two or more peers join the cluster concurrently, only the first one that 
> joins will distribute the index creation while reading its cache.xml file, 
> the rest will create the index locally due to the distributed message and log 
> an error afterwards, while trying to create the index from its own cache.xml 
> file. This error message is currently being registered under "ERROR" log 
> level, and it should be registered under "WARNING", or even not be registered 
> at all since this "exception" is expected during startup (we could easily 
> cache the indexes created locally by other distributed members)
> {noformat}
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Index creation message got the pr Partitioned Region 
> @57fd91c9 [path='/ClientSessionRegionPosSrv'; dataPolicy=PARTITION; 
> gatewayEnabled=false; prId=1; isDestroyed=false; isClosed=false; 
> retryTimeout=360; serialNumber=7; partition 
> attributes=PartitionAttributes@1828508781[redundantCopies=1;localMaxMemory=5;totalMaxMemory=2147483647;totalNumBuckets=47;partitionResolver=null;colocatedWith=null;recoveryDelay=30;startupRecoveryDelay=6;FixedPartitionAttributes=null;partitionListeners=null];
>  on VM 10.69.252.112(host1-server2:21655):34609]
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] 
> LocalRegion.createOQLIndexes on region /ClientSessionRegionPosSrv
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Processing index creation message on this remote 
> partitioned region vm for indexes: ClientSessionRegionPosSrv.byUser 
> [fine 2016/05/12 09:37:01.744 BST host1-server2  Processor1> tid=0x44] Started creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Indexfrom caluse=/ClientSessionRegionPosSrv, 
> Remote Request: true
> [fine 2016/05/12 09:37:01.744 BST host1-server2  tid=0x1] QueryService 
> Index creation process for {}ClientSessionRegionPosSrv.byUser
> [fine 2016/05/12 09:37:01.750 BST host1-server2  Processor1> tid=0x44] Completed creating index with Index Name 
> :ClientSessionRegionPosSrv.byUser On PartitionedRegion 
> /ClientSessionRegionPosSrv, Remote Request: true
> [fine 2016/05/12 09:37:01.751 BST host1-server2  Processor1> tid=0x44] Multi Index creation completed on remote host and has 
> sent the reply to the originating vm.
> [fine 2016/05/12 09:37:01.769 BST host1-server2  tid=0x1] Started 
> creating index with Index Name :ClientSessionRegionPosSrv.byUser On 
> PartitionedRegion /ClientSessionRegionPosSrv, Indexfrom 
> caluse=/ClientSessionRegionPosSrv, Remote Request: false
> [error 2016/05/12 09:37:01.770 BST host1-server2  tid=0x1] Failed to 
> create index ClientSessionRegionPosSrv.byUser on region 
> /ClientSessionRegionPosSrv with exception: 
> com.gemstone.gemfire.cache.query.IndexNameConflictException: Index named ' 
> ClientSessionRegionPosSrv.byUser ' already exists.
> {noformat}



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

[jira] [Commented] (GEODE-1545) add a test case for query JSON object in geode-lucene

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1545:


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

GEODE-1545: add a test case for querying JSON in geode-lucene


> add a test case for query JSON object in geode-lucene
> -
>
> Key: GEODE-1545
> URL: https://issues.apache.org/jira/browse/GEODE-1545
> Project: Geode
>  Issue Type: Test
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>
> We did support query on JSON object, but we don't have a test yet. 



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

[jira] [Commented] (GEODE-1551) CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund commented on GEODE-1551:
--

Maybe we're shutting down Jetty during an unsafe window. If so then fixing up 
how it's handled in tearDown would be one fix.

Another fix is to just ignore this exception with:
{noformat}
  @Before
  public void before() {
IgnoredException.addIgnoredException("org.eclipse.jetty.io.EofException");
  }
{noformat}


> CommandOverHttpDUnitTest
> 
>
> Key: GEODE-1551
> URL: https://issues.apache.org/jira/browse/GEODE-1551
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Scott Jewell
>Assignee: Jinmei Liao
>
> Various tests within the test suite are failing with the following error:
> Found suspect string in log4j at line 582
> [fatal 2016/06/14 21:03:21.748 PDT  tid=0x8d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)



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

[jira] [Resolved] (GEODE-1485) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-1485.
--
Resolution: Duplicate

> CI Failure: 
> gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
> -
>
> Key: GEODE-1485
> URL: https://issues.apache.org/jira/browse/GEODE-1485
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>
> Build #2718 (May 28, 2016 7:09:17 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2718/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> 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 1223
> [fatal 2016/05/28 16:52:26.927 PDT  tid=0xe2d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>

[jira] [Closed] (GEODE-1485) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund closed GEODE-1485.


> CI Failure: 
> gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
> -
>
> Key: GEODE-1485
> URL: https://issues.apache.org/jira/browse/GEODE-1485
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>
> Build #2718 (May 28, 2016 7:09:17 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2718/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> 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 1223
> [fatal 2016/05/28 16:52:26.927 PDT  tid=0xe2d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>   at 
> 

[jira] [Reopened] (GEODE-1485) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund reopened GEODE-1485:
--

> CI Failure: 
> gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
> -
>
> Key: GEODE-1485
> URL: https://issues.apache.org/jira/browse/GEODE-1485
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>
> Build #2718 (May 28, 2016 7:09:17 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2718/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> 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 1223
> [fatal 2016/05/28 16:52:26.927 PDT  tid=0xe2d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>   at 
> 

[jira] [Resolved] (GEODE-1485) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-1485.
--
Resolution: Fixed

Duplicate of GEODE-1447


> CI Failure: 
> gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
> -
>
> Key: GEODE-1485
> URL: https://issues.apache.org/jira/browse/GEODE-1485
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Udo Kohlmeyer
>
> Build #2718 (May 28, 2016 7:09:17 AM)
> Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2718/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> 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 1223
> [fatal 2016/05/28 16:52:26.927 PDT  tid=0xe2d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> 

[jira] [Updated] (GEODE-1447) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1447:
-
Summary: CI Failure: 
gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
  (was: CI Failure: 
com.gemstone.gemfire.management.internal.cli.commands.gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest)

> CI Failure: 
> gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
> -
>
> Key: GEODE-1447
> URL: https://issues.apache.org/jira/browse/GEODE-1447
> Project: Geode
>  Issue Type: Bug
>  Components: rest (admin)
>Reporter: Udo Kohlmeyer
>
> Build #2686 (May 23, 2016 3:12:32 AM)
> Revision: 617c9fd47e798c4cf0fdcae45697855760d39036
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2686/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> 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 1223
> [fatal 2016/05/23 12:53:02.457 PDT  tid=0xe32] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> 

[jira] [Updated] (GEODE-1436) CI failure: GemfireDataCommandsDUnitTest.testSimpleRemoveCommand

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1436:
-
Summary: CI failure: GemfireDataCommandsDUnitTest.testSimpleRemoveCommand  
(was: com.gemstone.gemfire.management.internal.CI failure: 
cli.commands.GemfireDataCommandsDUnitTest.testSimpleRemoveCommand)

> CI failure: GemfireDataCommandsDUnitTest.testSimpleRemoveCommand
> 
>
> Key: GEODE-1436
> URL: https://issues.apache.org/jira/browse/GEODE-1436
> Project: Geode
>  Issue Type: Bug
>  Components: rest (admin)
>Reporter: Udo Kohlmeyer
>  Labels: CI
>
> https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2673/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testSimpleRemoveCommand_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/
> Build #2673 (May 22, 2016 1:09:09 AM)
> Revision: ea19e3caeccbc01f61acd6d84734d8c136ee52a5
> 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 992
> [fatal 2016/05/22 09:12:32.474 PDT  tid=0xec2] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)
>   at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155)
>   at 
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215)
>   at 
> org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186)
>   at 
> org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
>   at 
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
>   at 
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
>   at 
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860)
>   at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:704)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
>   at 
> org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87)
>   at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>   at 
> 

[jira] [Resolved] (GEODE-1544) Fail to initiate final check when network partition occurs

[Jianxia Chen (JIRA)]

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

Jianxia Chen resolved GEODE-1544.
-
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3

> Fail to initiate final check when network partition occurs
> --
>
> Key: GEODE-1544
> URL: https://issues.apache.org/jira/browse/GEODE-1544
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M3
>
>
> When network partition occurs, something keeps the losing side of a network 
> partition from initiating any final checks on members no longer reachable. 



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

[jira] [Commented] (GEODE-1544) Fail to initiate final check when network partition occurs

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-1544:


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

GEODE-1544: Fail to initiate final check when network partition occurs

Currently, suspect request is only sent to a limited number of members,
when there are more than 4 members in the distributed system. It is
possible that the recipients of suspect request is unreachable due to
network partition. This fix makes sure that the recipients of suspect
request are not the suspect members. So that suspect request will be
processed.


> Fail to initiate final check when network partition occurs
> --
>
> Key: GEODE-1544
> URL: https://issues.apache.org/jira/browse/GEODE-1544
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>
> When network partition occurs, something keeps the losing side of a network 
> partition from initiating any final checks on members no longer reachable. 



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

[jira] [Commented] (GEODE-1551) CommandOverHttpDUnitTest

[Scott Jewell (JIRA)]

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

Scott Jewell commented on GEODE-1551:
-

This is occurring in Geode_develop_DistributedTests Build #2917 and #2922

> CommandOverHttpDUnitTest
> 
>
> Key: GEODE-1551
> URL: https://issues.apache.org/jira/browse/GEODE-1551
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Scott Jewell
>Assignee: Jinmei Liao
>
> Various tests within the test suite are failing with the following error:
> Found suspect string in log4j at line 582
> [fatal 2016/06/14 21:03:21.748 PDT  tid=0x8d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)



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

[jira] [Updated] (GEODE-1430) CI Failure: GemfireDataCommandsDUnitTest.testPutJsonKeys

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-1430:
-
Summary: CI Failure: GemfireDataCommandsDUnitTest.testPutJsonKeys  (was: CI 
Failure: emfireDataCommandsDUnitTest.testPutJsonKeys)

> CI Failure: GemfireDataCommandsDUnitTest.testPutJsonKeys
> 
>
> Key: GEODE-1430
> URL: https://issues.apache.org/jira/browse/GEODE-1430
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Sai Boorlagadda
>  Labels: CI
>
> Build # 2654
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> japan.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host 
> japan.gemstone.com with 4 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:111)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:105)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.setupForGetPutRemoveLocateEntry(GemfireDataCommandsDUnitTest.java:134)
>   at 
> com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testPutJsonKeys(GemfireDataCommandsDUnitTest.java:1342)
>   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.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.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
>   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:112)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> 

[jira] [Commented] (GEODE-1551) CommandOverHttpDUnitTest

[Jinmei Liao (JIRA)]

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

Jinmei Liao commented on GEODE-1551:


Must be an environment issue. Is it happening very frequent for you? Which 
environment are you running it on?

> CommandOverHttpDUnitTest
> 
>
> Key: GEODE-1551
> URL: https://issues.apache.org/jira/browse/GEODE-1551
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Scott Jewell
>Assignee: Jinmei Liao
>
> Various tests within the test suite are failing with the following error:
> Found suspect string in log4j at line 582
> [fatal 2016/06/14 21:03:21.748 PDT  tid=0x8d] 
> org.eclipse.jetty.io.EofException
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663)
>   at 
> org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627)
>   at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508)
>   at 
> org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668)
>   at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177)
>   at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163)
>   at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297)



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