[jira] [Updated] (GEODE-5095) Fix output for create gateway-receiver (port number)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-5095:
--
Labels: pull-request-available  (was: )

> Fix output for create gateway-receiver (port number)
> 
>
> Key: GEODE-5095
> URL: https://issues.apache.org/jira/browse/GEODE-5095
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
>
> The gfsh command "create gateway-receiver" has the following output:
> {code:java}
> gfsh>create gateway-receiver
> Member | Status
> -- | 
> --
> s1 | GatewayReceiver created on member "s1" and will listen on the port 
> "5,383"
>  {code}
>  
> The port number should not have comma in it.
> {code:java}
> GatewayReceiver created on member "s1" and will listen on the port 
> "5383"{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5070) Support --member option for describe & list jdbc connector commands

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5070:


Commit a881a790da13c698a38a735d471df0871b552a7b in geode's branch 
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a881a79 ]

GEODE-5070: Support --member option for describe & list jdbc connecto… (#1798)

When cluster configuration service is disabled user
have to provide --member option in-order to describe
and list connections and mappings.

> Support --member option for describe & list jdbc connector commands
> ---
>
> Key: GEODE-5070
> URL: https://issues.apache.org/jira/browse/GEODE-5070
> Project: Geode
>  Issue Type: New Feature
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When cluster configuration service is disabled user have to provide --member 
> option in-order to describe and list connections and mappings. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5078) InternalCache should have a getApplicationRegion method

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-5078:
--
Labels: pull-request-available  (was: )

> InternalCache should have a getApplicationRegion method
> ---
>
> Key: GEODE-5078
> URL: https://issues.apache.org/jira/browse/GEODE-5078
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>
> To help servers not provide access to secret/internal regions to clients; 
> InternalCache should have a method named getApplicationRegion which behaves 
> just like getRegion except that if the given name finds a secret/internal 
> region then it will throw an exception.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4410:


Commit 91f3626a24ae46dd95014b8abd9278fe8edccbc8 in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=91f3626 ]

Revert "GEODE-4410: Prevent future unused paramters from MSVC."

This reverts commit 4e09a7cb59bc1512d02c8af80b1ea8ada9900e1d.


> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4410:


Commit 4e09a7cb59bc1512d02c8af80b1ea8ada9900e1d in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=4e09a7c ]

GEODE-4410: Prevent future unused paramters from MSVC.


> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5081) ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property when configuring the DEFAULT Pool

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5081:


Commit b9bb961aa28074aa5643550c684614df33b1f613 in geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9bb961 ]

GEODE-5081 ClientCacheFactory is missing the 
setPoolSubscriptionTimeoutMultiplier()

Added the missing method & a test for it

This closes #1804


> ClientCacheFactory is missing the poolSubscriptionTimeoutMultiplier property 
> when configuring the DEFAULT Pool
> --
>
> Key: GEODE-5081
> URL: https://issues.apache.org/jira/browse/GEODE-5081
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: John Blum
>Assignee: Bruce Schuchardt
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Apache Geode 1.4 introduced the new {{subscriptionTimeoutMultiplier}} 
> configuration property when 
> [configuring|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/PoolFactory.html#setSubscriptionTimeoutMultiplier-int-]
>  a _Pool_ with the {{o.a.g.cache.client.PoolFactory}} class.  The 
> configuration setting for {{subscriptionTimeoutMultiplier}} could be queried 
> using the {{o.a.g.cache.client.Pool's}} [property 
> accessor|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/Pool.html#getSubscriptionTimeoutMultiplier--].
> However, this same _Pool_ configuration property was not properly added to 
> the 
> [{{o.a.g.cache.client.ClientCacheFactory}}|http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/client/ClientCacheFactory.html]
>  when configuring the "DEFAULT" _Pool_, i.e. there is no 
> {{setPoolSubscriptionTimeoutMultiplier(:int)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4410:


Commit 737077a5ed47ecbbc0798bc8397f95697c227c44 in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=737077a ]

GEODE-4410: Fixes .NET compile with removed cache parameter.


> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4842) Remove Cache parameter from PoolFactory::Create in clicache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4842:


Commit 6cbb1c0d800463f44411691b6787b5d2dd6c847a in geode-native's branch 
refs/heads/revert-279-feature/GEODE-4842-redo from [~eburghardt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=6cbb1c0 ]

Revert "GEODE-4842: Rebase with develop (#279)"

This reverts commit 805b8b7c5b5baab06ebbb1a6d5587e857e43017c.


> Remove Cache parameter from PoolFactory::Create in clicache
> ---
>
> Key: GEODE-4842
> URL: https://issues.apache.org/jira/browse/GEODE-4842
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> PoolFactory::Create in clicache takes a Cache parameter which is _completely 
> unused_. This parameter should simply be removed from the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5099) BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged should not include the jars in extensions directory

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5099:


Commit a8941fb088b59c4bf51cf8d64e85821e989047b5 in geode's branch 
refs/heads/exclude-extensions-in-jar-check from Bradford Boyle
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a8941fb ]

Omit extensions in check of bundled jars

[GEODE-5099]

Signed-off-by Jianxia Chen 


> BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged should not include the 
> jars in extensions directory
> 
>
> Key: GEODE-5099
> URL: https://issues.apache.org/jira/browse/GEODE-5099
> Project: Geode
>  Issue Type: Bug
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently the test BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged 
> includes all jars in GEODE_HOME including extensions directory. The jars in 
> the extensions directory should be excluded from this check.
> For extensions directory, please see GEODE-4923.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4716:


Commit d3e6280bc96e3b5b598cee7a92641a88fc6ceb6c in geode's branch 
refs/heads/exclude-extensions-in-jar-check from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d3e6280 ]

GEODE-4716 Document new stats and missing gateway sender/receiver MXBean (#1813)

- found and fixed a subnav typo for a link to the MXBean doc
- corrected a bad Object Name for the AsyncEventQueueMXBean

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-5099) BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged should not include the jars in extensions directory

[Jianxia Chen (JIRA)]

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

Jianxia Chen reassigned GEODE-5099:
---

Assignee: Jianxia Chen

> BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged should not include the 
> jars in extensions directory
> 
>
> Key: GEODE-5099
> URL: https://issues.apache.org/jira/browse/GEODE-5099
> Project: Geode
>  Issue Type: Bug
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently the test BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged 
> includes all jars in GEODE_HOME including extensions directory. The jars in 
> the extensions directory should be excluded from this check.
> For extensions directory, please see GEODE-4923.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5099) BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged should not include the jars in extensions directory

[Jianxia Chen (JIRA)]

Jianxia Chen created GEODE-5099:
---

 Summary: BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged 
should not include the jars in extensions directory
 Key: GEODE-5099
 URL: https://issues.apache.org/jira/browse/GEODE-5099
 Project: Geode
  Issue Type: Bug
Reporter: Jianxia Chen
 Fix For: 1.6.0


Currently the test BundledJarsJUnitTest#verifyBundledJarsHaveNotChanged 
includes all jars in GEODE_HOME including extensions directory. The jars in the 
extensions directory should be excluded from this check.

For extensions directory, please see GEODE-4923.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5098) Integrate OWASP Dependency Check for known vulnerabilities

[Praveendra Singh (JIRA)]

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

Praveendra Singh commented on GEODE-5098:
-

this is something we should leverage in all Apache Open Source systems.

> Integrate OWASP Dependency Check for known vulnerabilities
> --
>
> Key: GEODE-5098
> URL: https://issues.apache.org/jira/browse/GEODE-5098
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Praveendra Singh
>Priority: Major
>
> Given the sensitivity of the Geode system, we would like to avoid any 
> vulnerable dependencies sneaking into the final product. One way to be little 
> defensive is to leverage OWASP Dependency-Check. There are paid services 
> (e.g. Veracode) in the market however OWASP tool gives results which are very 
> close to the commercial services.
> h2. OWASP Dependency-Check
> Dependency-Check is a utility that identifies project dependencies and checks 
> if there are any known, publicly disclosed, vulnerabilities.
>  
> ref: [https://www.owasp.org/index.php/OWASP_Dependency_Check]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5098) Integrate OWASP Dependency Check for known vulnerabilities

[Praveendra Singh (JIRA)]

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

Praveendra Singh updated GEODE-5098:

Fix Version/s: (was: 1.7.0)

> Integrate OWASP Dependency Check for known vulnerabilities
> --
>
> Key: GEODE-5098
> URL: https://issues.apache.org/jira/browse/GEODE-5098
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Praveendra Singh
>Priority: Major
>
> Given the sensitivity of the Geode system, we would like to avoid any 
> vulnerable dependencies sneaking into the final product. One way to be little 
> defensive is to leverage OWASP Dependency-Check. There are paid services 
> (e.g. Veracode) in the market however OWASP tool gives results which are very 
> close to the commercial services.
> h2. OWASP Dependency-Check
> Dependency-Check is a utility that identifies project dependencies and checks 
> if there are any known, publicly disclosed, vulnerabilities.
>  
> ref: [https://www.owasp.org/index.php/OWASP_Dependency_Check]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5098) Integrate OWASP Dependency Check for known vulnerabilities

[Praveendra Singh (JIRA)]

Praveendra Singh created GEODE-5098:
---

 Summary: Integrate OWASP Dependency Check for known vulnerabilities
 Key: GEODE-5098
 URL: https://issues.apache.org/jira/browse/GEODE-5098
 Project: Geode
  Issue Type: Improvement
  Components: build
Reporter: Praveendra Singh
 Fix For: 1.7.0


Given the sensitivity of the Geode system, we would like to avoid any 
vulnerable dependencies sneaking into the final product. One way to be little 
defensive is to leverage OWASP Dependency-Check. There are paid services (e.g. 
Veracode) in the market however OWASP tool gives results which are very close 
to the commercial services.
h2. OWASP Dependency-Check

Dependency-Check is a utility that identifies project dependencies and checks 
if there are any known, publicly disclosed, vulnerabilities.

 

ref: [https://www.owasp.org/index.php/OWASP_Dependency_Check]

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller resolved GEODE-4716.

Resolution: Fixed

Documentation update cherry-picked to release/1.6.0 branch.

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4716:


Commit 02824613c7fd4210b17310f42e642137f762dc4c in geode's branch 
refs/heads/release/1.6.0 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0282461 ]

GEODE-4716 Document new stats and missing gateway sender/receiver MXBean (#1813)

- found and fixed a subnav typo for a link to the MXBean doc
- corrected a bad Object Name for the AsyncEventQueueMXBean

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5097) CI Failure: AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners

[Barry Oglesby (JIRA)]

Barry Oglesby created GEODE-5097:


 Summary: CI Failure: 
AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners
 Key: GEODE-5097
 URL: https://issues.apache.org/jira/browse/GEODE-5097
 Project: Geode
  Issue Type: Improvement
Reporter: Barry Oglesby


Occurred in FlakyTest 434:

https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/434

{noformat}
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest > 
testAsyncStatsTwoListeners FAILED
 org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest$$Lambda$79/2036409943.run
 in VM 2 running on Host 5f4c74fb-2dca-48a0-4b2c-156d54846ff4 with 5 VMs
 at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
 at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
 at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
 at 
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners(AsyncEventQueueStatsDUnitTest.java:139)

Caused by:
 org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
expression in org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase that 
uses int, intorg.apache.geode.cache.asyncqueue.internal.AsyncEventQueueStats 
Expected queue entries: 1000 but actual entries: 999 expected:<1000> but 
was:<999> within 120 seconds.
 at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
 at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
 at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
 at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
 at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
 at 
org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase.checkAsyncEventQueueStats(AsyncEventQueueTestBase.java:735)
 at org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUni
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5097) CI Failure: AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners

[Barry Oglesby (JIRA)]

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

Barry Oglesby updated GEODE-5097:
-
Issue Type: Bug  (was: Improvement)

> CI Failure: AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners
> 
>
> Key: GEODE-5097
> URL: https://issues.apache.org/jira/browse/GEODE-5097
> Project: Geode
>  Issue Type: Bug
>Reporter: Barry Oglesby
>Priority: Major
>
> Occurred in FlakyTest 434:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/434
> {noformat}
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest 
> > testAsyncStatsTwoListeners FAILED
>  org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest$$Lambda$79/2036409943.run
>  in VM 2 running on Host 5f4c74fb-2dca-48a0-4b2c-156d54846ff4 with 5 VMs
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
>  at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
>  at 
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners(AsyncEventQueueStatsDUnitTest.java:139)
> Caused by:
>  org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda 
> expression in org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase 
> that uses int, 
> intorg.apache.geode.cache.asyncqueue.internal.AsyncEventQueueStats Expected 
> queue entries: 1000 but actual entries: 999 expected:<1000> but was:<999> 
> within 120 seconds.
>  at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
>  at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
>  at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
>  at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
>  at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
>  at 
> org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase.checkAsyncEventQueueStats(AsyncEventQueueTestBase.java:735)
>  at org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUni
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4716:


Commit d3e6280bc96e3b5b598cee7a92641a88fc6ceb6c in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d3e6280 ]

GEODE-4716 Document new stats and missing gateway sender/receiver MXBean (#1813)

- found and fixed a subnav typo for a link to the MXBean doc
- corrected a bad Object Name for the AsyncEventQueueMXBean

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-577) CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally

[Barry Oglesby (JIRA)]

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

Barry Oglesby commented on GEODE-577:
-

Reproduced in 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/429:
{noformat}
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest > 
testQueryExecutionLocally FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 
0fb6c9e9-3a24-4963-76ab-3fc91bfbb78a with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:336)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:480)

Caused by:
java.lang.AssertionError: The query should have been canceled by the 
QueryMonitor. Query: SELECT ID FROM /root/exampleRegion p WHERE p.ID > 100
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQuery(QueryMonitorDUnitTest.java:360)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQueriesAgainstQueryService(QueryMonitorDUnitTest.java:351)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQueriesOnServer(QueryMonitorDUnitTest.java:342)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryExecutionLocally$bb17a952$6(QueryMonitorDUnitTest.java:480)
{noformat}

> CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
> ---
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Barry Oglesby
>Priority: Major
>  Labels: CI, Flaky
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1 
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1 
> running on Host latvia.gemstone.com with 4 VMs
>   at dunit.VM.invoke(VM.java:369)
>   at dunit.VM.invoke(VM.java:312)
>   at dunit.VM.invoke(VM.java:266)
>   at 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
>   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:105)
>   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:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor124.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 

[jira] [Assigned] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene are concurrently created

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer reassigned GEODE-5096:


Assignee: Udo Kohlmeyer

> AddCacheServerProfile should throw an error when conflicting Lucene are 
> concurrently created
> 
>
> Key: GEODE-5096
> URL: https://issues.apache.org/jira/browse/GEODE-5096
> Project: Geode
>  Issue Type: New Feature
>  Components: lucene
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> When two servers concurrently define a LuceneIndex, the addCacheServerProfile 
> should throw an error to avoid conflicting indexes being defined.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene indexes are concurrently created

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer updated GEODE-5096:
-
Summary: AddCacheServerProfile should throw an error when conflicting 
Lucene indexes are concurrently created  (was: AddCacheServerProfile should 
throw an error when conflicting Lucene are concurrently created)

> AddCacheServerProfile should throw an error when conflicting Lucene indexes 
> are concurrently created
> 
>
> Key: GEODE-5096
> URL: https://issues.apache.org/jira/browse/GEODE-5096
> Project: Geode
>  Issue Type: New Feature
>  Components: lucene
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> When two servers concurrently define a LuceneIndex, the addCacheServerProfile 
> should throw an error to avoid conflicting indexes being defined.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4410) DistributedSystem has public method to get internal class StatisticsManager

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4410:


Commit a0c770b752b4088d259a522f8d829f9b209509be in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=a0c770b ]

GEODE-4410: Fixes unused parameter in DistributedSystem::connect


> DistributedSystem has public method to get internal class StatisticsManager
> ---
>
> Key: GEODE-4410
> URL: https://issues.apache.org/jira/browse/GEODE-4410
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene are concurrently created

[Udo Kohlmeyer (JIRA)]

Udo Kohlmeyer created GEODE-5096:


 Summary: AddCacheServerProfile should throw an error when 
conflicting Lucene are concurrently created
 Key: GEODE-5096
 URL: https://issues.apache.org/jira/browse/GEODE-5096
 Project: Geode
  Issue Type: New Feature
  Components: lucene
Reporter: Udo Kohlmeyer


When two servers concurrently define a LuceneIndex, the addCacheServerProfile 
should throw an error to avoid conflicting indexes being defined.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn edited comment on GEODE-4959 at 4/17/18 8:49 PM:


When calling command
{code:java}
create gateway-receiver{code}
on a cluster but one member in the cluster already has a gateway receiver, the 
command will create a gateway receiver on the other members in the cluster, but 
will not persist the gateway receivers in the cluster. In this case we need to 
display a warning that the gateway receivers will not be persisted in cluster 
config.
{code:java}
gfsh>create gateway-receiver --member=s1
This change is not persisted in the cluster configuration, either because the 
cluster configuration service is not running or the command is operating on 
targeted members.
Member | Status
-- | 
--
s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,071"

gfsh>create gateway-receiver
Member | Status
-- | 
-
s1 | ERROR: java.lang.IllegalStateException: A Gateway Receiver already 
exists on this member.
s2 | GatewayReceiver created on member "s2" and will listen on the port 
"5,138"

This change is not persisted in the cluster configuration, because an error 
occurred during execution.
{code}


was (Author: bpruijn):
When calling command
{code:java}
create gateway-receiver{code}
on a cluster but one member in the cluster already has a gateway receiver, the 
command will create a gateway receiver on the other members in the cluster, but 
will not persist the gateway receivers in the cluster. In this case we need to 
display a warning that the gateway receivers will not be persisted in cluster 
config.
{code:java}
gfsh>create gateway-receiver --member=s1
This change is not persisted in the cluster configuration, either because the 
cluster configuration service is not running or the command is operating on 
targeted members.
Member | Status
-- | 
--
s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,071"

gfsh>create gateway-receiver
This change is not persisted in the cluster configuration, because a gateway 
receiver already existed on a member before running this command.
Member | Status
-- | 
-
s1 | ERROR: java.lang.IllegalStateException: A Gateway Receiver already 
exists on this member.
s2 | GatewayReceiver created on member "s2" and will listen on the port 
"5,138"
{code}

> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> 

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5094:


Commit a03bba213a6b5932a9da9c0a4848c94fd485bbfb in geode's branch 
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a03bba2 ]

added flaky category to test method for GEODE-5094


> ProxyJUnitTest fails intermittently in testExpiration
> -
>
> Key: GEODE-5094
> URL: https://issues.apache.org/jira/browse/GEODE-5094
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Darrel Schneider
>Priority: Major
>  Labels: flaky
>
> {noformat}
> org.apache.geode.cache.ProxyJUnitTest > testExpiration FAILED
> org.apache.geode.cache.RegionDestroyedException: 
> org.apache.geode.internal.cache.DistributedRegion[path='/rEMPTY';scope=DISTRIBUTED_NO_ACK';dataPolicy=EMPTY;
>  concurrencyChecksEnabled]
> at 
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at 
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1356)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1314)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1299)
> at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at 
> org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1106)
> {noformat}
> The test is scheduling a region to be destroyed if it is not used for 500 
> miliseconds. It then starting doing gets which will keep using the region. 
> But it is possible for the gets to lose the cpu and be prevented from using 
> the region and it then expiring. That is what is happening in this test.
> This test as currently written is flaky and needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5095) Fix output for create gateway-receiver (port number)

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-5095:
--
Description: 
The gfsh command "create gateway-receiver" has the following output:
{code:java}
gfsh>create gateway-receiver

Member | Status

-- | 
--

s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,383"
 {code}
 

The port number should not have comma in it.
{code:java}
GatewayReceiver created on member "s1" and will listen on the port "5383"{code}

  was:
The gfsh command "create gateway-receiver" has the following output:
{code:java}
gfsh>create gateway-receiver

Member | Status

-- | 
--

s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,383"
 {code}
 

The port number should not have comma in it.


> Fix output for create gateway-receiver (port number)
> 
>
> Key: GEODE-5095
> URL: https://issues.apache.org/jira/browse/GEODE-5095
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> The gfsh command "create gateway-receiver" has the following output:
> {code:java}
> gfsh>create gateway-receiver
> Member | Status
> -- | 
> --
> s1 | GatewayReceiver created on member "s1" and will listen on the port 
> "5,383"
>  {code}
>  
> The port number should not have comma in it.
> {code:java}
> GatewayReceiver created on member "s1" and will listen on the port 
> "5383"{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5095) Fix output for create gateway-receiver (port number)

[Barbara Pruijn (JIRA)]

Barbara Pruijn created GEODE-5095:
-

 Summary: Fix output for create gateway-receiver (port number)
 Key: GEODE-5095
 URL: https://issues.apache.org/jira/browse/GEODE-5095
 Project: Geode
  Issue Type: Bug
  Components: gfsh
Reporter: Barbara Pruijn


The gfsh command "create gateway-receiver" has the following output:
{code:java}
gfsh>create gateway-receiver

Member | Status

-- | 
--

s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,383"
 {code}
 

The port number should not have comma in it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5018) Cache should wrap CacheImpl (fully honor the pimpl model)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5018:


Commit fc413448d12c63a1588a2f0300159ea7b570acd0 in geode-native's branch 
refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=fc41344 ]

GEODE-5018: Fixing PIMPL pattern for Cache (#278)

* Moving type registry out and using forward decl
* Using initializer list in Cache constructor


> Cache should wrap CacheImpl (fully honor the pimpl model)
> -
>
> Key: GEODE-5018
> URL: https://issues.apache.org/jira/browse/GEODE-5018
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Ernest Burghardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> CacheImpl should own TypeRegistry etc... i.e. fix anything not honoring the 
> pimpl model...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

[Darrel Schneider (JIRA)]

Darrel Schneider created GEODE-5094:
---

 Summary: ProxyJUnitTest fails intermittently in testExpiration
 Key: GEODE-5094
 URL: https://issues.apache.org/jira/browse/GEODE-5094
 Project: Geode
  Issue Type: Bug
  Components: expiration
Reporter: Darrel Schneider


{noformat}
org.apache.geode.cache.ProxyJUnitTest > testExpiration FAILED
org.apache.geode.cache.RegionDestroyedException: 
org.apache.geode.internal.cache.DistributedRegion[path='/rEMPTY';scope=DISTRIBUTED_NO_ACK';dataPolicy=EMPTY;
 concurrencyChecksEnabled]
at 
org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
at 
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1356)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1314)
at 
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1299)
at 
org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
at 
org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1106)
{noformat}
The test is scheduling a region to be destroyed if it is not used for 500 
miliseconds. It then starting doing gets which will keep using the region. But 
it is possible for the gets to lose the cpu and be prevented from using the 
region and it then expiring. That is what is happening in this test.

This test as currently written is flaky and needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-5094:

Labels: flaky  (was: )

> ProxyJUnitTest fails intermittently in testExpiration
> -
>
> Key: GEODE-5094
> URL: https://issues.apache.org/jira/browse/GEODE-5094
> Project: Geode
>  Issue Type: Bug
>  Components: expiration
>Reporter: Darrel Schneider
>Priority: Major
>  Labels: flaky
>
> {noformat}
> org.apache.geode.cache.ProxyJUnitTest > testExpiration FAILED
> org.apache.geode.cache.RegionDestroyedException: 
> org.apache.geode.internal.cache.DistributedRegion[path='/rEMPTY';scope=DISTRIBUTED_NO_ACK';dataPolicy=EMPTY;
>  concurrencyChecksEnabled]
> at 
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at 
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1356)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1314)
> at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1299)
> at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at 
> org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1106)
> {noformat}
> The test is scheduling a region to be destroyed if it is not used for 500 
> miliseconds. It then starting doing gets which will keep using the region. 
> But it is possible for the gets to lose the cpu and be prevented from using 
> the region and it then expiring. That is what is happening in this test.
> This test as currently written is flaky and needs to be rewritten.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4957:


Commit 33f8f5fadbe5655a31f2607dd121fc97e1a373f3 in geode's branch 
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=33f8f5f ]

Revert "GEODE-4957: fix race in concurrent create on region (#1750)" (#1812)

This reverts commit 65b52f28f4e11b9f5ec82b0e457fc0292132e5da.

> The key used in a putIfAbsent call that returns null may not be the one in 
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null 
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no 
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9 
> creates the RegionEntry. You can see that because not only is oldRe=null for 
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are 
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0 
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); 
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=1682369152; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=342592289; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4957:

Fix Version/s: (was: 1.6.0)

> The key used in a putIfAbsent call that returns null may not be the one in 
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null 
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no 
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9 
> creates the RegionEntry. You can see that because not only is oldRe=null for 
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are 
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0 
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); 
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=1682369152; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=342592289; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[Darrel Schneider (JIRA)]

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

Darrel Schneider edited comment on GEODE-4957 at 4/17/18 6:56 PM:
--

The fix caused a problem with persistence so that fix will be reverted and this 
issue reopened.


was (Author: dschneider):
The fix caused a problem with persistence

> The key used in a putIfAbsent call that returns null may not be the one in 
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null 
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no 
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9 
> creates the RegionEntry. You can see that because not only is oldRe=null for 
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are 
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0 
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); 
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=1682369152; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=342592289; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[Darrel Schneider (JIRA)]

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

Darrel Schneider reopened GEODE-4957:
-

The fix caused a problem with persistence

> The key used in a putIfAbsent call that returns null may not be the one in 
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Barry Oglesby
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null 
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no 
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9 
> creates the RegionEntry. You can see that because not only is oldRe=null for 
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are 
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0 
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); 
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=1682369152; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=342592289; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller reopened GEODE-4624:

  Assignee: Karen Smoler Miller  (was: xiaojian zhou)

Reopening ticket, as the documentation has not yet been done.

> Add a new stat for AyncEventQueue/GatewaySender to track the processing of 
> queueRemovals
> 
>
> Key: GEODE-4624
> URL: https://issues.apache.org/jira/browse/GEODE-4624
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Affects Versions: 1.5.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.7.0
>
>
> We currently track the number of events queues, queue size and 
> eventsDistributed ... but we don't track the number of events removed via 
> queue removal. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-4959:
---

When calling command
{code:java}
create gateway-receiver{code}
on a cluster but one member in the cluster already has a gateway receiver, the 
command will create a gateway receiver on the other members in the cluster, but 
will not persist the gateway receivers in the cluster. In this case we need to 
display a warning that the gateway receivers will not be persisted in cluster 
config.
{code:java}
gfsh>create gateway-receiver --member=s1
This change is not persisted in the cluster configuration, either because the 
cluster configuration service is not running or the command is operating on 
targeted members.
Member | Status
-- | 
--
s1 | GatewayReceiver created on member "s1" and will listen on the port 
"5,071"

gfsh>create gateway-receiver
This change is not persisted in the cluster configuration, because a gateway 
receiver already existed on a member before running this command.
Member | Status
-- | 
-
s1 | ERROR: java.lang.IllegalStateException: A Gateway Receiver already 
exists on this member.
s2 | GatewayReceiver created on member "s2" and will listen on the port 
"5,138"
{code}

> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> -
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver 
> already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with 
> GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with 
> --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, 
> it could happen that some one could end up a cluster with multiple gwr 
> created in cluster configuration and could prevent them to upgrade to 1.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5077) Categorize refactored/newly added OQL tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5077:


Commit 49991b35e47614230379a40b2a3376b73990ff37 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=49991b3 ]

GEODE-5077: Categorized newly added oql tests (#1797)



> Categorize refactored/newly added OQL tests
> ---
>
> Key: GEODE-5077
> URL: https://issues.apache.org/jira/browse/GEODE-5077
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Following a refactor these tests were added and it would be nice to add the 
> OQLIndexTest or OQLQueryTest to the categories.
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexAndPdxDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithOrderByDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithPdxDuringRebalanceRegressionTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRWithIndexAfterRebalanceRegressionTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5088) Remove getContentAsString from CommandResult

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5088:


Commit 4d8ae7117b4e1c40793dea252014bd12e6951cad in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d8ae71 ]

GEODE-5088: Remove getContentAsString from CommandResult (#1809)



> Remove getContentAsString from CommandResult
> 
>
> Key: GEODE-5088
> URL: https://issues.apache.org/jira/browse/GEODE-5088
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This allows for more specific response interrogation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4955:


Commit cb5fb79d0efbf21ec0ba32be6ba0e5733b17fff9 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cb5fb79 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  Add 
removal to spotless (#1781)

* Remove trivial javadoc stubs as part of spotless.
* Remove empty javadoc and comment blocks as part of spotless.
* Apply spotless to JDBC's ConnectionService.

> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4959:


Commit 4dff0cde9c3abca2dad03897c055e9c443a81b60 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4dff0cd ]

GEODE-4959: Add --if-not-exists option to create gateway receiver com… (#1770)

* GEODE-4959: Add --if-not-exists option to create gateway receiver command.
* Command will now raise an error if a gateway receiver cannot be created on 
every member
* This error will *not* be raised if a gateway receiver already exists on a 
given member.
* Cleanup test class.
* Add setStatus to CommandResult


> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> -
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver 
> already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with 
> GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with 
> --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, 
> it could happen that some one could end up a cluster with multiple gwr 
> created in cluster configuration and could prevent them to upgrade to 1.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4986) Refactor GMSEncrypt

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4986:


Commit d1a5ecf767961ff023cd6e1c5418e4e23abfd75c in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1a5ecf ]

GEODE-4986: refactoring GMS encryption (#1715)

GEODE-4986: refactoring GMS encryption


> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4954:


Commit cb5fb79d0efbf21ec0ba32be6ba0e5733b17fff9 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cb5fb79 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  Add 
removal to spotless (#1781)

* Remove trivial javadoc stubs as part of spotless.
* Remove empty javadoc and comment blocks as part of spotless.
* Apply spotless to JDBC's ConnectionService.

> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5048) Availability Indicator for "list jndi-bindings", "list jdbc-connections" and "list jdbc-mappings" are wrong

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5048:


Commit 575659c13d57d253c654f74e90761a4ac3a1b2fc in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=575659c ]

GEODE-5048: add missing availability indicators for certain commands (#1800)



> Availability Indicator for "list jndi-bindings", "list jdbc-connections" and 
> "list jdbc-mappings" are wrong
> ---
>
> Key: GEODE-5048
> URL: https://issues.apache.org/jira/browse/GEODE-5048
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> those commands, when not connected to a locator, should be listed as "not 
> available" in gfsh help, but they are listed as "available".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4959:


Commit 4dff0cde9c3abca2dad03897c055e9c443a81b60 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4dff0cd ]

GEODE-4959: Add --if-not-exists option to create gateway receiver com… (#1770)

* GEODE-4959: Add --if-not-exists option to create gateway receiver command.
* Command will now raise an error if a gateway receiver cannot be created on 
every member
* This error will *not* be raised if a gateway receiver already exists on a 
given member.
* Cleanup test class.
* Add setStatus to CommandResult


> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> -
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver 
> already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with 
> GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with 
> --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, 
> it could happen that some one could end up a cluster with multiple gwr 
> created in cluster configuration and could prevent them to upgrade to 1.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4858:


Commit 828e0c232a3e5e717ea3bcb1c00d127ac380e934 in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=828e0c2 ]

GEODE-4858: add test for custom cache elements not properly registered (#1806)



> refactor internal commands to use the public ClusterConfigService
> -
>
> Key: GEODE-4858
> URL: https://issues.apache.org/jira/browse/GEODE-4858
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> # except the ones that would need to access the internal cluster 
> configuration regions, like importClusterConfigCommand, 
> exportClusterConfigCommand or deploy
>  # use the configuration object as much as possible to pass parameters to the 
> functions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4986) Refactor GMSEncrypt

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4986:


Commit d1a5ecf767961ff023cd6e1c5418e4e23abfd75c in geode's branch 
refs/heads/feature/GEODE-Lucene-Udo from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1a5ecf ]

GEODE-4986: refactoring GMS encryption (#1715)

GEODE-4986: refactoring GMS encryption


> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5077) Categorize refactored/newly added OQL tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5077:


Commit 49991b35e47614230379a40b2a3376b73990ff37 in geode's branch 
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=49991b3 ]

GEODE-5077: Categorized newly added oql tests (#1797)



> Categorize refactored/newly added OQL tests
> ---
>
> Key: GEODE-5077
> URL: https://issues.apache.org/jira/browse/GEODE-5077
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Following a refactor these tests were added and it would be nice to add the 
> OQLIndexTest or OQLQueryTest to the categories.
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexAndPdxDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithIndexDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithOrderByDistributedTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRQueryWithPdxDuringRebalanceRegressionTest.java
> geode-core/src/test/java/org/apache/geode/internal/cache/PRWithIndexAfterRebalanceRegressionTest.java



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5064) Remove unused code and if clause that does not get thrown

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-5064:
---
Fix Version/s: (was: 1.6.0)
   1.7.0

> Remove unused code and if clause that does not get thrown
> -
>
> Key: GEODE-5064
> URL: https://issues.apache.org/jira/browse/GEODE-5064
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There appears to be an exception that should be thrown, but upon futher 
> inspection, this clause can never be hit because the boolean it checks is 
> never set to true;
>  
> In LocalRegion:
> logger.info("Failed to create index {} on region {} with exception: {}",
>  icd.getIndexName(), this.getFullPath(), ex);
> // Check if the region index creation is from cache.xml, in that case throw 
> exception.
> // Other case is when bucket regions are created dynamically, in that case 
> ignore the
> // exception.
> if (internalRegionArgs.getDeclarativeIndexCreation()) {
>  throw new 
> InternalGemFireError(LocalizedStrings.GemFireCache_INDEX_CREATION_EXCEPTION_1
>  .toLocalizedString(icd.getIndexName(), this.getFullPath()), ex);
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-5093) Update packer script for dev image to use Dependencies instead of Depends

[Michael Oleske (JIRA)]

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

Michael Oleske reassigned GEODE-5093:
-

Assignee: Ryan McMahon

> Update packer script for dev image to use Dependencies instead of Depends
> -
>
> Key: GEODE-5093
> URL: https://issues.apache.org/jira/browse/GEODE-5093
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Michael Oleske
>Assignee: Ryan McMahon
>Priority: Major
>
>  
> **We should** replace Depends
> **Because** Dependencies repo is a much improved version of Depends.
> **Notes** The install is just a zipfile that needs to be downloaded and 
> unzipped and is at [https://github.com/lucasg/Dependencies]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-5093) Update packer script for dev image to use Dependencies instead of Depends

[Michael Oleske (JIRA)]

Michael Oleske created GEODE-5093:
-

 Summary: Update packer script for dev image to use Dependencies 
instead of Depends
 Key: GEODE-5093
 URL: https://issues.apache.org/jira/browse/GEODE-5093
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Michael Oleske


 

**We should** replace Depends
**Because** Dependencies repo is a much improved version of Depends.

**Notes** The install is just a zipfile that needs to be downloaded and 
unzipped and is at [https://github.com/lucasg/Dependencies]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4624) Add a new stat for AyncEventQueue/GatewaySender to track the processing of queueRemovals

[xiaojian zhou (JIRA)]

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

xiaojian zhou updated GEODE-4624:
-
Fix Version/s: (was: 1.6.0)
   1.7.0

> Add a new stat for AyncEventQueue/GatewaySender to track the processing of 
> queueRemovals
> 
>
> Key: GEODE-4624
> URL: https://issues.apache.org/jira/browse/GEODE-4624
> Project: Geode
>  Issue Type: Bug
>  Components: docs, wan
>Affects Versions: 1.5.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: xiaojian zhou
>Priority: Major
> Fix For: 1.7.0
>
>
> We currently track the number of events queues, queue size and 
> eventsDistributed ... but we don't track the number of events removed via 
> queue removal. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5090) Create a DUnitTest where a Lucene query is executed but we lose all copies of a bucket

[nabarun (JIRA)]

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

nabarun commented on GEODE-5090:


With the current implementation the query is not retried, which is we want
{noformat}
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.cache.lucene.LuceneQueriesAccessorBase$$Lambda$33/1899223686.call
 in VM 3 running on Host 10.118.19.39 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:371)
at 
org.apache.geode.cache.lucene.LuceneQueriesAccessorBase.executeTextSearch(LuceneQueriesAccessorBase.java:86)
at 
org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.executeQueryAndValidateNoHang(LuceneQueriesReindexDUnitTest.java:105)
at 
org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.luceneQueryExecutedWithReindexWhenAllBucketsAreLostShouldNotCauseAHang(LuceneQueriesReindexDUnitTest.java:100)
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 
junitparams.internal.InvokeParameterisedMethod.evaluate(InvokeParameterisedMethod.java:234)
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 
junitparams.internal.ParameterisedTestMethodRunner.runMethodInvoker(ParameterisedTestMethodRunner.java:47)
at 
junitparams.internal.ParameterisedTestMethodRunner.runTestMethod(ParameterisedTestMethodRunner.java:40)
at 
junitparams.internal.ParameterisedTestClassRunner.runParameterisedTest(ParameterisedTestClassRunner.java:146)
at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:446)
at junitparams.JUnitParamsRunner.runChild(JUnitParamsRunner.java:393)
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.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at 
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.apache.geode.cache.PartitionedRegionStorageException: Unable to 
find any members to host a bucket in the partitioned region. Advise you to 
start enough data store nodes.
Partitioned Region name = /region
   Redundancy level set to 0
. Number of available data stores: 0
   . Number successfully allocated = 0
. Data stores: []
. Data stores successfully allocated: []
. Equivalent members: [10.118.19.39(80639):32771, 
10.118.19.39(80641):32772, 10.118.19.39(80637:locator):32769, 
10.118.19.39(80638):32770]

at 
org.apache.geode.internal.cache.PRHARedundancyProvider.insufficientStores(PRHARedundancyProvider.java:306)
at 
org.apache.geode.internal.cache.PRHARedundancyProvider.createBucketOnDataStore(PRHARedundancyProvider.java:478)
at 
org.apache.geode.internal.cache.PartitionedRegion.createBucket(PartitionedRegion.java:3334)
at 
org.apache.geode.internal.cache.partitioned.RegionAdvisor$BucketSet$BucketSetIterator.next(RegionAdvisor.java:1420)
at 
org.apache.geode.internal.cache.PartitionedRegion.executeOnAllBuckets(PartitionedRegion.java:3848)
at 
org.apache.geode.internal.cache.PartitionedRegion.executeFunction(PartitionedRegion.java:3424)
at 

[jira] [Resolved] (GEODE-5048) Availability Indicator for "list jndi-bindings", "list jdbc-connections" and "list jdbc-mappings" are wrong

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-5048.
---
Resolution: Fixed

> Availability Indicator for "list jndi-bindings", "list jdbc-connections" and 
> "list jdbc-mappings" are wrong
> ---
>
> Key: GEODE-5048
> URL: https://issues.apache.org/jira/browse/GEODE-5048
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> those commands, when not connected to a locator, should be listed as "not 
> available" in gfsh help, but they are listed as "available".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (GEODE-4172) GEODE-4172 : [CI failure] org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest - testMatchingCQsWithMultipleServers

[Jason Huynh (JIRA)]

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

Jason Huynh reopened GEODE-4172:


I've seen this test fail again recently and am reopening for someone to make 
sure it's not a product issue and rather still a test issue.

> GEODE-4172 : [CI failure] 
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest - 
> testMatchingCQsWithMultipleServers
> -
>
> Key: GEODE-4172
> URL: https://issues.apache.org/jira/browse/GEODE-4172
> Project: Geode
>  Issue Type: Bug
>  Components: cq
>Reporter: nabarun
>Priority: Major
>
> Stacktrace
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest$10.run in VM 1 
> running on Host 3580a85a1bde with 4 VMs
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
>   at 
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest.validateMatchingCqs(CqPerfUsingPoolDUnitTest.java:952)
>   at 
> org.apache.geode.cache.query.cq.dunit.CqPerfUsingPoolDUnitTest.testMatchingCQsWithMultipleServers(CqPerfUsingPoolDUnitTest.java:804)
>   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:114)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> 

[jira] [Assigned] (GEODE-4842) Remove Cache parameter from PoolFactory::Create in clicache

[Michael Oleske (JIRA)]

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

Michael Oleske reassigned GEODE-4842:
-

Assignee: Ryan McMahon

> Remove Cache parameter from PoolFactory::Create in clicache
> ---
>
> Key: GEODE-4842
> URL: https://issues.apache.org/jira/browse/GEODE-4842
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> PoolFactory::Create in clicache takes a Cache parameter which is _completely 
> unused_. This parameter should simply be removed from the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4986) Refactor GMSEncrypt

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4986:


Commit d1a5ecf767961ff023cd6e1c5418e4e23abfd75c in geode's branch 
refs/heads/develop from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1a5ecf ]

GEODE-4986: refactoring GMS encryption (#1715)

GEODE-4986: refactoring GMS encryption


> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4986) Refactor GMSEncrypt

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4986:


Commit d1a5ecf767961ff023cd6e1c5418e4e23abfd75c in geode's branch 
refs/heads/develop from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d1a5ecf ]

GEODE-4986: refactoring GMS encryption (#1715)

GEODE-4986: refactoring GMS encryption


> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4986) Refactor GMSEncrypt

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4986:
--
Labels: pull-request-available  (was: )

> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4986) Refactor GMSEncrypt

[Brian Rowe (JIRA)]

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

Brian Rowe resolved GEODE-4986.
---
   Resolution: Fixed
Fix Version/s: 1.6.0

> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg resolved GEODE-4955.
-
Resolution: Fixed

> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg resolved GEODE-4954.
-
Resolution: Fixed

> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4955) Improve spotless -- Remove empty javadocs and block comments

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4955:


Commit cb5fb79d0efbf21ec0ba32be6ba0e5733b17fff9 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cb5fb79 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  Add 
removal to spotless (#1781)

* Remove trivial javadoc stubs as part of spotless.
* Remove empty javadoc and comment blocks as part of spotless.
* Apply spotless to JDBC's ConnectionService.

> Improve spotless -- Remove empty javadocs and block comments
> 
>
> Key: GEODE-4955
> URL: https://issues.apache.org/jira/browse/GEODE-4955
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> This should be executed after GEODE-4654, since the removal of javadoc stubs 
> may yield a now-empty javadoc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4954) Improve spotless -- remove trivial javadoc stubs

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4954:


Commit cb5fb79d0efbf21ec0ba32be6ba0e5733b17fff9 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cb5fb79 ]

GEODE-4954, GEODE-4955: Remove trivial javadoc stubs and empty blocks:  Add 
removal to spotless (#1781)

* Remove trivial javadoc stubs as part of spotless.
* Remove empty javadoc and comment blocks as part of spotless.
* Apply spotless to JDBC's ConnectionService.

> Improve spotless -- remove trivial javadoc stubs
> 
>
> Key: GEODE-4954
> URL: https://issues.apache.org/jira/browse/GEODE-4954
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> For instance, the block
> {noformat}
> @param myparam
> @param secondParam
> @throws Exception
> {noformat}
> is entirely implicit by the method's signature, which is included in the 
> javadoc itself.  Javadoc stubs that do not include description of a given 
> term is trivial, redundant, and should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4959:


Commit 4dff0cde9c3abca2dad03897c055e9c443a81b60 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4dff0cd ]

GEODE-4959: Add --if-not-exists option to create gateway receiver com… (#1770)

* GEODE-4959: Add --if-not-exists option to create gateway receiver command.
* Command will now raise an error if a gateway receiver cannot be created on 
every member
* This error will *not* be raised if a gateway receiver already exists on a 
given member.
* Cleanup test class.
* Add setStatus to CommandResult


> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> -
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver 
> already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with 
> GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with 
> --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, 
> it could happen that some one could end up a cluster with multiple gwr 
> created in cluster configuration and could prevent them to upgrade to 1.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4959) Attempt to create multiple gw receivers results an error on gfsh console.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4959:


Commit 4dff0cde9c3abca2dad03897c055e9c443a81b60 in geode's branch 
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4dff0cd ]

GEODE-4959: Add --if-not-exists option to create gateway receiver com… (#1770)

* GEODE-4959: Add --if-not-exists option to create gateway receiver command.
* Command will now raise an error if a gateway receiver cannot be created on 
every member
* This error will *not* be raised if a gateway receiver already exists on a 
given member.
* Cleanup test class.
* Add setStatus to CommandResult


> Attempt to create multiple gw receivers results an error on gfsh console.
> -
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh
>Reporter: Sai Boorlagadda
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per 
> node in the xsd. So when user attempts to create multiple gwr show a better 
> error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet
>  on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] 
> -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true 
> -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> ---
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and 
> will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --- | 
> -
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver 
> already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with 
> GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with 
> --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, 
> it could happen that some one could end up a cluster with multiple gwr 
> created in cluster configuration and could prevent them to upgrade to 1.4.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5085:


Commit 2c28e0a4b894611e0c61a742030e0eb1d377e462 in geode's branch 
refs/heads/feature/GEODE-5085 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2c28e0a ]

GEODE-5085 authentication failure when auto-reconnecting

Reverting getSecurityProps() to return the converted internal form of
property values.  The security service expects these to be in this form
and not the external form.  My change caused a handful of security tests
to fail.

Added toSecurityProperties() in Config.java and converted
InternalDistributedSystem.reconnect() to use this and toProperties()
to get the external form of properties in order to build the new
DistributionConfig to feed the reconnecting system.


> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
>   

[jira] [Created] (GEODE-5092) TSSDataOutput class should be using modern memory management, and have a meaningful name

[Blake Bender (JIRA)]

Blake Bender created GEODE-5092:
---

 Summary: TSSDataOutput class should be using modern memory 
management, and have a meaningful name
 Key: GEODE-5092
 URL: https://issues.apache.org/jira/browse/GEODE-5092
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Blake Bender


This class is called TSSDataOutput because it is using ACE Thread Specific 
Storage (TSS).  As far as a name, TSS(whatever) falls into the category of 
"true but not helpful," because it doesn't tell us anything about what the 
class does.  It should probably be called something like DataOutputBufferPool, 
because that's what it is.  Also, this class is keeping a list of structures 
containing a raw byte pointer and a size, and using std::malloc and std::free 
to manage the buffer memory.  It should be using something modern - most likely 
the structs in the vector should contain a std::unique_ptr and a size, and pass 
ownership back and forth to DataOutput.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-5000) When initializing a client cache, we don't need to request/apply cluster configuration

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-5000.
---
Resolution: Fixed

> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The user running a gemfire client doesn't have write access to the local dirs 
> in the customer environment, and they get an stack trace in their logs. This 
> is caused by a client cache trying to request/apply cluster configuration.
> {noformat}
> [error 2018/02/12 17:52:13.899 EST  tid=0x12] Error 
> when attempting to deploy JAR files on load.
> java.io.IOException: Unable to write to deploy directory
> at 
> org.apache.geode.internal.JarDeployer.verifyWritableDeployDirectory(JarDeployer.java:626)
> at 
> org.apache.geode.internal.JarDeployer.loadPreviouslyDeployedJars(JarDeployer.java:74)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1242)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:794)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.createClient(GemFireCacheImpl.java:767)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.basicCreate(ClientCacheFactory.java:257)
> at 
> org.apache.geode.cache.client.ClientCacheFactory.create(ClientCacheFactory.java:207){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5048) Availability Indicator for "list jndi-bindings", "list jdbc-connections" and "list jdbc-mappings" are wrong

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5048:


Commit 575659c13d57d253c654f74e90761a4ac3a1b2fc in geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=575659c ]

GEODE-5048: add missing availability indicators for certain commands (#1800)



> Availability Indicator for "list jndi-bindings", "list jdbc-connections" and 
> "list jdbc-mappings" are wrong
> ---
>
> Key: GEODE-5048
> URL: https://issues.apache.org/jira/browse/GEODE-5048
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.7.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> those commands, when not connected to a locator, should be listed as "not 
> available" in gfsh help, but they are listed as "available".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4858:


Commit 828e0c232a3e5e717ea3bcb1c00d127ac380e934 in geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=828e0c2 ]

GEODE-4858: add test for custom cache elements not properly registered (#1806)



> refactor internal commands to use the public ClusterConfigService
> -
>
> Key: GEODE-4858
> URL: https://issues.apache.org/jira/browse/GEODE-4858
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> # except the ones that would need to access the internal cluster 
> configuration regions, like importClusterConfigCommand, 
> exportClusterConfigCommand or deploy
>  # use the configuration object as much as possible to pass parameters to the 
> functions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5088) Remove getContentAsString from CommandResult

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-5088:


Commit 4d8ae7117b4e1c40793dea252014bd12e6951cad in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d8ae71 ]

GEODE-5088: Remove getContentAsString from CommandResult (#1809)



> Remove getContentAsString from CommandResult
> 
>
> Key: GEODE-5088
> URL: https://issues.apache.org/jira/browse/GEODE-5088
> Project: Geode
>  Issue Type: Test
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This allows for more specific response interrogation



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-5090) Create a DUnitTest where a Lucene query is executed but we lose all copies of a bucket

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-5090:
--
Labels: pull-request-available  (was: )

> Create a DUnitTest where a Lucene query is executed but we lose all copies of 
> a bucket
> --
>
> Key: GEODE-5090
> URL: https://issues.apache.org/jira/browse/GEODE-5090
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>
> - DUnitTest where a Lucene query is executed but we lose all copies of a 
> bucket
> Idea:
>  * create accessor
>  * create two datastores
>  * close cache on the datastores
>  * execute the lucene query 
>  * ensure that the query doesn't hang.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-5085) authentication failure when auto-reconnecting

[Dharam Thacker (JIRA)]

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

Dharam Thacker commented on GEODE-5085:
---

Thanks Bruce!

Could we try to include this in Geode 1.6.0 as it's critical one?

It's breaking few critical apps with latest gemfire 9.4.0 as well which was 
build using Apache geode 1.5.0.

Thanks,

Dharam

> authentication failure when auto-reconnecting
> -
>
> Key: GEODE-5085
> URL: https://issues.apache.org/jira/browse/GEODE-5085
> Project: Geode
>  Issue Type: Bug
>  Components: membership, security
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I added a security manager to ReconnectDUnitTest.testReconnectWithQuorum() 
> and got a failure to authenticate during the reconnect attempt.
> {noformat}
> [vm3] [warn 2018/04/16 10:37:17.773 PDT  tid=92] Exception 
> occurred while trying to connect the system during reconnect
> [vm3] org.apache.geode.security.AuthenticationRequiredException: Failed to 
> find credentials from [10.118.20.59(16110:locator):32770]
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.attemptToJoin(GMSJoinLeave.java:452)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.join(GMSJoinLeave.java:338)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:658)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:747)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:191)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:762)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:354)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:340)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:334)
> [vm3] at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2732)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2558)
> [vm3] at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1040)
> [vm3] at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:4030)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.uncleanShutdown(GMSMembershipManager.java:1554)
> [vm3] at 
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.lambda$forceDisconnect$1(GMSMembershipManager.java:2561)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The security manager settings were added to getDistributedSystemProperties():
> {code}
>   @Override
>   public Properties getDistributedSystemProperties() {
> if (dsProperties == null) {
>   dsProperties = new Properties();
>   dsProperties.put(MAX_WAIT_TIME_RECONNECT, "2");
>   dsProperties.put(ENABLE_NETWORK_PARTITION_DETECTION, "true");
>   dsProperties.put(DISABLE_AUTO_RECONNECT, "false");
>   dsProperties.put(ENABLE_CLUSTER_CONFIGURATION, "false");
>   dsProperties.put(LOCATORS, "localHost[" + locatorPort + "]");
>   dsProperties.put(MCAST_PORT, "0");
>   dsProperties.put(MEMBER_TIMEOUT, "1000");
>   dsProperties.put(LOG_LEVEL, LogWriterUtils.getDUnitLogLevel());
>   

[jira] [Updated] (GEODE-5089) Remove recoverRepoInANewNode test

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-5089:
--
Labels: pull-request-available  (was: )

> Remove recoverRepoInANewNode test
> -
>
> Key: GEODE-5089
> URL: https://issues.apache.org/jira/browse/GEODE-5089
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>
> Remove the test recoverRepoInANewNode as this test has been commented out for 
> a year and the test execution flow will not be possible anymore because of 
> addition of the lot of countdown latches and bucket locks.
>  
> We believe that the test coverage is present in the lot of other lucene 
> rebalance tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)