[jira] [Commented] (GEODE-4973) Add docker-compose to ci pipeline image

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4973:


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

Merge pull request #1702 from nreich/feature/GEODE-4973

GEODE-4973: Add docker-compose to pipeline docker image

> Add docker-compose to ci pipeline image
> ---
>
> Key: GEODE-4973
> URL: https://issues.apache.org/jira/browse/GEODE-4973
> Project: Geode
>  Issue Type: Improvement
>  Components: ci
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> To enable tests that spin up (potentially multiple) docker containers, add 
> docker-compose to the items installed in the ci image.



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

[jira] [Commented] (GEODE-4973) Add docker-compose to ci pipeline image

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4973:


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

GEODE-4973: Add docker-compose to pipeline docker image


> Add docker-compose to ci pipeline image
> ---
>
> Key: GEODE-4973
> URL: https://issues.apache.org/jira/browse/GEODE-4973
> Project: Geode
>  Issue Type: Improvement
>  Components: ci
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> To enable tests that spin up (potentially multiple) docker containers, add 
> docker-compose to the items installed in the ci image.



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

[jira] [Commented] (GEODE-4973) Add docker-compose to ci pipeline image

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4973:


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

Merge pull request #1702 from nreich/feature/GEODE-4973

GEODE-4973: Add docker-compose to pipeline docker image

> Add docker-compose to ci pipeline image
> ---
>
> Key: GEODE-4973
> URL: https://issues.apache.org/jira/browse/GEODE-4973
> Project: Geode
>  Issue Type: Improvement
>  Components: ci
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> To enable tests that spin up (potentially multiple) docker containers, add 
> docker-compose to the items installed in the ci image.



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

[jira] [Updated] (GEODE-3237) Loading cluster configuration from a dir that does not have complete CC will throw NPE

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-3237:
--
Description: 
We should handle the error more gracefully and informatively. Currently if user 
did the following:

gfsh> start locator --name=locator
 gfsh> shutdown --include-lcoator=true
 gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true

the console message says "Cluster configuration service has been started, but 
its not running yet",
 and there is an NPE in the log:
 [error 2017/07/18 10:22:38.357 PDT locator  
tid=0x41] null
 java.lang.NullPointerException
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
 at 
org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at 
org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
 at 
org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
 at java.lang.Thread.run(Thread.java:745)

The error message should be saying: You have 
-load-cluster-configuration-from-dir=true but have not specified 
-cluster-config-dir with a directory to the cluster config file.

  was:
We should handle the error more gracefully and informatively. Currently if user 
did the following:

gfsh> start locator --name=locator
 gfsh> shutdown --include-lcoator=true
 gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true

the console message says "Cluster configuration service has been started, but 
its not running yet",
 and there is an NPE in the log:
 [error 2017/07/18 10:22:38.357 PDT locator  
tid=0x41] null
 java.lang.NullPointerException
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
 at 
org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at 
org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
 at 
org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
 at java.lang.Thread.run(Thread.java:745)

The error message should be saying: You have 
--load-cluster-configuration-from-dir=true but have not specified 
--cluster-config-dir with a directory to the cluster config file.


> Loading cluster configuration from a dir that does not have complete CC will 
> throw NPE
> --
>
> Key: GEODE-3237
> URL: https://issues.apache.org/jira/browse/GEODE-3237
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jinmei Liao
>Priority: Major
>
> We should handle the error more gracefully and informatively. Currently if 
> user did the following:
> gfsh> start locator --name=locator
>  gfsh> shutdown --include-lcoator=true
>  gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true
> the console message says "Cluster configuration service has been started, but 
> its not running yet",
>  and there is an NPE in the log:
>  [error 2017/07/18 10:22:38.357 PDT locator  
> tid=0x41] null
>  java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
>  at 
> org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
>  at java.lang.Thread.run(Thread.java:745)
> The error message 

[jira] [Commented] (GEODE-4913) gfsh start server cmd is not recognizing local properties and cache.xml, instead using default

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4913:


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

GEODE-4913: gfsh start server cmd is not recognizing local properties… (#1687)

… and cache.xml, instead using default

  * Reverted having a default cluster xml, having a default xml
in the cluster config caused a default cache server to be
launched, which caused the sighted issue.

  * Instead cluster config is initialized only when needed.


> gfsh start server cmd is not recognizing local properties and cache.xml, 
> instead using default
> --
>
> Key: GEODE-4913
> URL: https://issues.apache.org/jira/browse/GEODE-4913
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Affects Versions: 1.5.0, 1.6.0
>Reporter: Diane Hardman
>Priority: Critical
>  Labels: pull-request-available
> Attachments: geode-script_10-31-2016.tgz
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The attached tarfile contains scripts to start up 2 clusters and connect them 
> with a WAN gateway.
>  The script for starting the servers for the first cluster (ln) fail because 
> the default 40404 port is being used for each server. Instead, the start 
> server command should be using the local cache.xml files found under 
> config/gemfire-XX-hub.xml which contain:
> 
> This should force gfsh to choose the next available port, rather than the 
> default 40404.
> It appears that the default cache.xml is being used. This problem does not 
> exist with Geode 1.4.0.



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

[jira] [Updated] (GEODE-3237) Loading cluster configuration from a dir that does not have complete CC will throw NPE

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-3237:
--
Component/s: gfsh
 configuration

> Loading cluster configuration from a dir that does not have complete CC will 
> throw NPE
> --
>
> Key: GEODE-3237
> URL: https://issues.apache.org/jira/browse/GEODE-3237
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jinmei Liao
>Priority: Major
>
> We should handle the error more gracefully and informatively. Currently if 
> user did the following:
> gfsh> start locator --name=locator
>  gfsh> shutdown --include-lcoator=true
>  gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true
> the console message says "Cluster configuration service has been started, but 
> its not running yet",
>  and there is an NPE in the log:
>  [error 2017/07/18 10:22:38.357 PDT locator  
> tid=0x41] null
>  java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
>  at 
> org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
>  at java.lang.Thread.run(Thread.java:745)
> The error message should be saying: You have 
> --load-cluster-configuration-from-dir=true but have not specified 
> --cluster-config-dir with a directory to the cluster config file.



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

[jira] [Updated] (GEODE-3237) Loading cluster configuration from a dir that does not have complete CC will throw NPE

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-3237:
--
Description: 
We should handle the error more gracefully and informatively. Currently if user 
did the following:

gfsh> start locator --name=locator
 gfsh> shutdown --include-lcoator=true
 gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true

the console message says "Cluster configuration service has been started, but 
its not running yet",
 and there is an NPE in the log:
 [error 2017/07/18 10:22:38.357 PDT locator  
tid=0x41] null
 java.lang.NullPointerException
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
 at 
org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
 at 
org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at 
org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
 at 
org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
 at java.lang.Thread.run(Thread.java:745)

The error message should be saying: You have 
--load-cluster-configuration-from-dir=true but have not specified 
--cluster-config-dir with a directory to the cluster config file.

  was:
We should handle the error more gracefully and informatively. Currently if user 
did the following:

gfsh> start locator --name=locator
gfsh> shutdown --include-lcoator=true
gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true

the console message says "Cluster configuration service has been started, but 
its not running yet",
 and there is an NPE in the log:
[error 2017/07/18 10:22:38.357 PDT locator  
tid=0x41] null
java.lang.NullPointerException
at 
org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
at 
org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
at 
org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at 
org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
at 
org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
at java.lang.Thread.run(Thread.java:745)

the message should be saying: the CC can't be started, because the directory 
did not contain valid CC information.


> Loading cluster configuration from a dir that does not have complete CC will 
> throw NPE
> --
>
> Key: GEODE-3237
> URL: https://issues.apache.org/jira/browse/GEODE-3237
> Project: Geode
>  Issue Type: Bug
>Reporter: Jinmei Liao
>Priority: Major
>
> We should handle the error more gracefully and informatively. Currently if 
> user did the following:
> gfsh> start locator --name=locator
>  gfsh> shutdown --include-lcoator=true
>  gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true
> the console message says "Cluster configuration service has been started, but 
> its not running yet",
>  and there is an NPE in the log:
>  [error 2017/07/18 10:22:38.357 PDT locator  
> tid=0x41] null
>  java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
>  at 
> org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
>  at java.lang.Thread.run(Thread.java:745)
> The error message should be saying: You have 
> 

[jira] [Commented] (GEODE-4799) Remove static member variables from Apache.Geode.Client.Serializable

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4799:


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

GEODE-4799: Adding nuget to packer (#255)

Signed-off-by: Ryan McMahon 

> Remove static member variables from Apache.Geode.Client.Serializable
> 
>
> Key: GEODE-4799
> URL: https://issues.apache.org/jira/browse/GEODE-4799
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Michael Martell
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently this class contains a bunch of static member variables. These need 
> to be converted to instance variables.
> This change will allow each cache instance to have its own custom serializer 
> without needing to use a chained serializer.



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

[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4218:
--
Description: 
Currently if you start a locator with:
 load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty.

Since we cannot remove the option -load-cluster-configuration-from-dir since 
this will break backward compatibility for existing customers who are using 
this, we can make this option optional (not required) when you specify 
-cluster-config-dir=.

Also, we need to return an error if you specify 
load-cluster-configuration-from-dir=true but don't provide 
--cluster-config-dir=. See GEODE-3237.

 

 

  was:
Currently if you start a locator with:
 load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty.

Since we cannot remove the option --load-cluster-configuration-from-dir since 
this will break backward compatibility for existing customers who are using 
this, we can make this option optional (not required) when you specify 
--cluster-config-dir=.

 

Also, we need to return an error if you specify 
load-cluster-configuration-from-dir=true but don't provide 
--cluster-config-dir=.

 

 


> load-cluster-configuration-from-dir is no longer required when setting 
> --cluster-config-dir
> ---
>
> Key: GEODE-4218
> URL: https://issues.apache.org/jira/browse/GEODE-4218
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, management
>Reporter: Jinmei Liao
>Priority: Major
>
> Currently if you start a locator with:
>  load-cluster-configuration-from-dir=true
> you would usually need to specify a "cluster-configuration-dir" to go with 
> it, if you don't, it will default to the locator's working dir which is 
> usually empty, and when this happens, it will override the entire cluster's 
> configuration to be empty.
> Since we cannot remove the option -load-cluster-configuration-from-dir since 
> this will break backward compatibility for existing customers who are using 
> this, we can make this option optional (not required) when you specify 
> -cluster-config-dir=.
> Also, we need to return an error if you specify 
> load-cluster-configuration-from-dir=true but don't provide 
> --cluster-config-dir=. See GEODE-3237.
>  
>  



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

[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4218:
--
Description: 
Currently if you start a locator with:
 load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty.

Since we cannot remove the option --load-cluster-configuration-from-dir since 
this will break backward compatibility for existing customers who are using 
this, we can make this option optional (not required) when you specify 
--cluster-config-dir=.

 

Also, we need to return an error if you specify 
load-cluster-configuration-from-dir=true but don't provide 
--cluster-config-dir=.

 

 

  was:
Currently if you start a locator with:
 load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty.

 

 


> load-cluster-configuration-from-dir is no longer required when setting 
> --cluster-config-dir
> ---
>
> Key: GEODE-4218
> URL: https://issues.apache.org/jira/browse/GEODE-4218
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, management
>Reporter: Jinmei Liao
>Priority: Major
>
> Currently if you start a locator with:
>  load-cluster-configuration-from-dir=true
> you would usually need to specify a "cluster-configuration-dir" to go with 
> it, if you don't, it will default to the locator's working dir which is 
> usually empty, and when this happens, it will override the entire cluster's 
> configuration to be empty.
> Since we cannot remove the option --load-cluster-configuration-from-dir since 
> this will break backward compatibility for existing customers who are using 
> this, we can make this option optional (not required) when you specify 
> --cluster-config-dir=.
>  
> Also, we need to return an error if you specify 
> load-cluster-configuration-from-dir=true but don't provide 
> --cluster-config-dir=.
>  
>  



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

[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir is no longer required when setting --cluster-config-dir

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4218:
--
Summary: load-cluster-configuration-from-dir is no longer required when 
setting --cluster-config-dir  (was: load-cluster-configuration-from-dir should 
specify the directory instead of just a boolean value)

> load-cluster-configuration-from-dir is no longer required when setting 
> --cluster-config-dir
> ---
>
> Key: GEODE-4218
> URL: https://issues.apache.org/jira/browse/GEODE-4218
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, management
>Reporter: Jinmei Liao
>Priority: Major
>
> Currently if you start a locator with:
>  load-cluster-configuration-from-dir=true
> you would usually need to specify a "cluster-configuration-dir" to go with 
> it, if you don't, it will default to the locator's working dir which is 
> usually empty, and when this happens, it will override the entire cluster's 
> configuration to be empty.
>  
>  



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

[jira] [Updated] (GEODE-4218) load-cluster-configuration-from-dir should specify the directory instead of just a boolean value

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4218:
--
Description: 
Currently if you start a locator with:
 load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty.

 

 

  was:
Currently if you start a locator with:
load-cluster-configuration-from-dir=true

you would usually need to specify a "cluster-configuration-dir" to go with it, 
if you don't, it will default to the locator's working dir which is usually 
empty, and when this happens, it will override the entire cluster's 
configuration to be empty


> load-cluster-configuration-from-dir should specify the directory instead of 
> just a boolean value
> 
>
> Key: GEODE-4218
> URL: https://issues.apache.org/jira/browse/GEODE-4218
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, management
>Reporter: Jinmei Liao
>Priority: Major
>
> Currently if you start a locator with:
>  load-cluster-configuration-from-dir=true
> you would usually need to specify a "cluster-configuration-dir" to go with 
> it, if you don't, it will default to the locator's working dir which is 
> usually empty, and when this happens, it will override the entire cluster's 
> configuration to be empty.
>  
>  



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

[jira] [Updated] (GEODE-4799) Remove static member variables from Apache.Geode.Client.Serializable

[ASF GitHub Bot (JIRA)]

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

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

> Remove static member variables from Apache.Geode.Client.Serializable
> 
>
> Key: GEODE-4799
> URL: https://issues.apache.org/jira/browse/GEODE-4799
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Michael Martell
>Priority: Major
>  Labels: pull-request-available
>
> Currently this class contains a bunch of static member variables. These need 
> to be converted to instance variables.
> This change will allow each cache instance to have its own custom serializer 
> without needing to use a chained serializer.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 7be2a7e215a85c9d48ec293c024b54d719946008 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7be2a7e ]

GEODE-4876: Cleanup CacheRule tests use of VM and javadocs

* rename CacheRuleTest as CacheRuleBuilderDistributedTest
* write new CacheRuleDistributedTest
* fix javadocs of CacheRule


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 4296f218aa9122e910ce6db45a1b7fd0664b9366 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4296f21 ]

GEODE-4876: Update SharedErrorCollectorDistributedTest use of VM and NetworkUtil

* rename SharedErrorCollectorTest as SharedErrorCollectorDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 5271b6b970e2239a4e46e3bc43fb41250c7b39e4 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5271b6b ]

GEODE-4876: Update DistributedDisconnectRuleDistributedTest use of VM and 
NetworkUtil

* rename DistributedDisconnectRuleTest as 
DistributedDisconnectRuleDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit da4044ec9af30cca84f8eb51354efe381cfc307b in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=da4044e ]

GEODE-4876: Update DistributedDisconnectRuleAsClassRuleDistributedTest use of VM

* renamed from DistributedDisconnectRuleAsClassRuleTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 99bb4f0fc411f529cd219d8f2f2787f541e0f884 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=99bb4f0 ]

GEODE-4876: Update AcceptorImplClientQueueDistributedTest use of VM and 
NetworkUtil

* rename AcceptorImplClientQueueDUnitTest as 
AcceptorImplClientQueueDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-3926) Lucene Query should throw an exception while lucene index is being built on existing region

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3926:


Commit 6ea3f648e7abf2bf77a53e8df1bf761ed17e8d5e in geode's branch 
refs/heads/feature/GEODE-3926_3 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6ea3f64 ]

GEODE-3926 Initial commit to add LuceneIndexCreationInProgressException


> Lucene Query should throw an exception while lucene index is being built on 
> existing region
> ---
>
> Key: GEODE-3926
> URL: https://issues.apache.org/jira/browse/GEODE-3926
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> When GEODE-3928 is complete, we will have a process to index existing data in 
> a region when a lucene index is added. That process may take some time. While 
> indexing is going on queries should not block for a long period of time or 
> return incorrect results. Instead the query should throw an exception 
> indicating that the index does not exist/is not built yet.
> Acceptance:
> Queries executed while indexing is going on throw an exception, rather than 
> blocking or returning incorrect results.
> Implementation Details:
> GEODE-3928 is about modifying computeRepository to actually do the indexing. 
> Queries also call compute repository, so they will block until 
> computeRepository is done.
> To avoid blocking, we can make  computeRepo to return an IndexRepository in 
> an "building" state. That index repo could contain an asynchronous task that 
> is actually indexing the data. Until the asynchronous task is complete, the 
> IndexRepostory could throw exceptions from query operations. This has the 
> advantage of making sure that whenever computeRepository is called, we always 
> at least start or make sure there is a task running to index the data.



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

[jira] [Commented] (GEODE-4970) CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4970:


Commit a2cc50346fe0bb3f03ddf7c9c8a2494118b4a131 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a2cc503 ]

GEODE-4970: Disable PartitionedRegionQueryDUnitTest

Mark PartitionedRegionQueryDUnitTest with @Ignore to prevent this test
from hanging during precheckin. I'll merge a followup commit to reenable
the test after I overhaul it.


> CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may 
> hang
> 
>
> Key: GEODE-4970
> URL: https://issues.apache.org/jira/browse/GEODE-4970
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> We should disable this test until we can commit a fix.
> {noformat}
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-connectors/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:20:34.241 +
> Ended @ 2018-03-27 00:22:53.324 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-core/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:23:14.674 +
> 2018-03-27 01:03:05.285 +  
> org.apache.geode.internal.cache.PartitionedRegionQueryDUnitTest 
> tesRangeIndexWithPdxObjects
> Ended @ 2018-03-27 02:55:00.443 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-assembly/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:30:39.754 +
> Ended @ 2018-03-27 00:20:28.529 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/extensions/geode-modules-tomcat8/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:28:30.596 +
> Ended @ 2018-03-26 23:30:03.751 +
> {noformat}



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit b6b4ac2de7f48d3b45298c872bda6f9453c59409 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b6b4ac2 ]

GEODE-4876: Update DistributedTestRuleDistributedTest use of VM and NetworkUtil

* rename DistributedTestRuleTest as DistributedTestRuleDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 40795fedf572fb7658edee94f15d20b170ad0408 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=40795fe ]

GEODE-4876: Update SharedCountersRuleDistributedTest use of VM and NetworkUtil

* rename SharedCountersRuleTest as SharedCountersRuleDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Updated] (GEODE-4972) Move VersionManager into geode-old-versions module

[ASF GitHub Bot (JIRA)]

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

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

> Move VersionManager into geode-old-versions module
> --
>
> Key: GEODE-4972
> URL: https://issues.apache.org/jira/browse/GEODE-4972
> Project: Geode
>  Issue Type: Task
>  Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>
> This is a precursor to GEODE-4971



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

[jira] [Assigned] (GEODE-3993) Re-evaluate the Cache.createDataInput/Output API

[Blake Bender (JIRA)]

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

Blake Bender reassigned GEODE-3993:
---

Assignee: Blake Bender

> Re-evaluate the Cache.createDataInput/Output API
> 
>
> Key: GEODE-3993
> URL: https://issues.apache.org/jira/browse/GEODE-3993
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Blake Bender
>Priority: Major
>
> Having the factory on Cache is convenient for end users but produces 
> DataInput/Output objects that are not usable for internal use because it 
> relies on access to the Pool. If a User's use of the DataInput/Output also 
> needs Pool then it will be broken.  Internally we turn around and call an 
> internal API to add the Pool to the DataInput/Output. This all seems really 
> dirty, can we do better?



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

[jira] [Commented] (GEODE-3926) Lucene Query should throw an exception while lucene index is being built on existing region

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3926:


Commit 3b1af0dca04e2ef7bd11c68ef87b9c9cfa005867 in geode's branch 
refs/heads/feature/GEODE-3926_3 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3b1af0d ]

GEODE-3926 Initial commit to add LuceneIndexCreationInProgressException


> Lucene Query should throw an exception while lucene index is being built on 
> existing region
> ---
>
> Key: GEODE-3926
> URL: https://issues.apache.org/jira/browse/GEODE-3926
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Udo Kohlmeyer
>Priority: Major
>
> When GEODE-3928 is complete, we will have a process to index existing data in 
> a region when a lucene index is added. That process may take some time. While 
> indexing is going on queries should not block for a long period of time or 
> return incorrect results. Instead the query should throw an exception 
> indicating that the index does not exist/is not built yet.
> Acceptance:
> Queries executed while indexing is going on throw an exception, rather than 
> blocking or returning incorrect results.
> Implementation Details:
> GEODE-3928 is about modifying computeRepository to actually do the indexing. 
> Queries also call compute repository, so they will block until 
> computeRepository is done.
> To avoid blocking, we can make  computeRepo to return an IndexRepository in 
> an "building" state. That index repo could contain an asynchronous task that 
> is actually indexing the data. Until the asynchronous task is complete, the 
> IndexRepostory could throw exceptions from query operations. This has the 
> advantage of making sure that whenever computeRepository is called, we always 
> at least start or make sure there is a task running to index the data.



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

[jira] [Commented] (GEODE-4945) InternalGfshCommand should not have to implement CommandMarker directly

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4945:


Commit 7b9ac98824322bc14e29258643dce6ac2ddf743e in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7b9ac98 ]

GEODE-4945: InternalGfshCommand should not have to implement CommandM… (#1684)

* Correct class scanning for user gfsh commands


> InternalGfshCommand should not have to implement CommandMarker directly
> ---
>
> Key: GEODE-4945
> URL: https://issues.apache.org/jira/browse/GEODE-4945
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> InternalGfshCommand should only need to implement GfshCommand (as GfshCommand 
> already implements CommandMarker)



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

[jira] [Commented] (GEODE-4520) Remove singleton calls from product code in org.apache.geode.management.internal.configuration.callbacks

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4520:


Commit dde0ae7a69df9c9352f6e28f21b37e21e4210140 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dde0ae7 ]

GEODE-4520: Remove singleton CacheFactory.getAnyInstance() from 
o.a.g.management.internal.configuration.callbacks.



> Remove singleton calls from product code in 
> org.apache.geode.management.internal.configuration.callbacks
> 
>
> Key: GEODE-4520
> URL: https://issues.apache.org/jira/browse/GEODE-4520
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> These product classes in 
> org.apache.geode.management.internal.configuration.callbacks invoke singleton 
> getters.
> CacheFactory.getAnyInstance():
> * ConfigurationChangeListener



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

[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4822:


Commit 6f025bc79d4b612f9b73c4321791e910d62fb124 in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6f025bc ]

Revert "GEODE-4822 The second server instance startup error: Could not create 
an instance of PartitionRegionConfig"

This reverts commit d8ec1ead880566c0f911f2cd304b634717ee6836.


> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.internal.cache.PartitionRegionConfig .
>   at Remote Member 

[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4822:


Commit 4cd33db63df0f5e969e5fd70bf75ab18b561701c in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4cd33db ]

Revert "GEODE-4822 The second server instance startup error: Could not create 
an instance of PartitionRegionConfig"

This reverts commit a5118f634c6d7a97e7f6da9726b4c08c85b51dd0.


> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.internal.cache.PartitionRegionConfig .
>   at Remote Member 

[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4822:


Commit d044ce0ca5bb6742af96bb1c504e329572d686fa in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d044ce0 ]

GEODE-4822 The second server instance startup error: Could not create an 
instance of PartitionRegionConfig

Fixed deserialization issue in a streaming result collector.


> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.internal.cache.PartitionRegionConfig .
>   at Remote Member 

[jira] [Commented] (GEODE-4922) JDBC connector does not handle java.util.Date

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4922:


Commit 1307696270a571b94a24bc4dace9bc2ab1bc104a in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1307696 ]

GEODE-4922: handle Date conversion (#1686)

When writing a java.util.Date the column type will be used 
to convert it to a java.sql.Date, java.sql.Time, or java.sql.Timestamp.
When reading a pdx DATE field, the column type will be used to
decide if getDate, getTime, or getTimestamp is called.
When reading a pdx OBJECT field, if getObject returns an instance of
java.sql.Date, java.sql.Time, or java.sql.Timestamp then it will be
converted to java.util.Date and that will be stored in the pdx field.

> JDBC connector does not handle java.util.Date
> -
>
> Key: GEODE-4922
> URL: https://issues.apache.org/jira/browse/GEODE-4922
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Pdx types can have java.util.Date fields or object fields that contain 
> java.util.Date.
> When these are written that java.util.Date may cause a failure from the jdbc 
> driver if it does not support java.util.Date. Jdbc drivers must support 
> java.sql.Date, java.sql.Time, and java.sql.Timestamp but may not support 
> java.util.Date.
> The JDBC connector should convert java.util.Date to one of the java.sql 
> interfaces using the data type of the column to determine which one to 
> convert it to.
> When reading from jdbc back into geode if the pdx field is java.util.Date 
> then we should convert the java.sql.* instance to java.util.Date. It is also 
> possible we should do this conversion if the pdx field is of type object.
>  



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

[jira] [Commented] (GEODE-4782) Categorize Gfsh tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4782:


Commit f1410195ede68f06188480694ff130768159742f in geode's branch 
refs/heads/feature/GEODE-3926_3 from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f141019 ]

Feature/geode 4782 (#1682)

* GEODE-4782: Add GfshTest annotation to test classes



> Categorize Gfsh tests
> -
>
> Key: GEODE-4782
> URL: https://issues.apache.org/jira/browse/GEODE-4782
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add Category annotation for gfsh integration and distributed tests.



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

[jira] [Updated] (GEODE-4973) Add docker-compose to ci pipeline image

[ASF GitHub Bot (JIRA)]

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

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

> Add docker-compose to ci pipeline image
> ---
>
> Key: GEODE-4973
> URL: https://issues.apache.org/jira/browse/GEODE-4973
> Project: Geode
>  Issue Type: Improvement
>  Components: ci
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>
> To enable tests that spin up (potentially multiple) docker containers, add 
> docker-compose to the items installed in the ci image.



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

[jira] [Resolved] (GEODE-4946) Cleanup compiler warnings with MSVC

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett resolved GEODE-4946.
-
Resolution: Fixed

> Cleanup compiler warnings with MSVC
> ---
>
> Key: GEODE-4946
> URL: https://issues.apache.org/jira/browse/GEODE-4946
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Too many warnings slow down compilation and hide real issues in the log noise.



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

[jira] [Assigned] (GEODE-4967) Cleanup compiler warnings with Clang

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett reassigned GEODE-4967:
---

Assignee: Jacob S. Barrett

> Cleanup compiler warnings with Clang
> 
>
> Key: GEODE-4967
> URL: https://issues.apache.org/jira/browse/GEODE-4967
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>
> Too many compiler warnings makes for lots of noise when compiling. Warnings 
> lead to errors. Make all warnings errors.



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

[jira] [Commented] (GEODE-3993) Re-evaluate the Cache.createDataInput/Output API

[Blake Bender (JIRA)]

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

Blake Bender commented on GEODE-3993:
-

So perhaps the most offensive issue here is that, wherever we create a DI/DO 
internally, we call createDataInput/Output then _immediately_ call setPoolName. 
 If we simply add the pool name as a parameter to 
CacheImpl::createDataInput/Output, then in Cache::createDataInput/Output we 
passed the name of the first pool from the pool manager, the user could call 
the cache method and create without a pool name, and we could remove the 
setPoolName method from DataInput/DataOutput altogether.

> Re-evaluate the Cache.createDataInput/Output API
> 
>
> Key: GEODE-3993
> URL: https://issues.apache.org/jira/browse/GEODE-3993
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>
> Having the factory on Cache is convenient for end users but produces 
> DataInput/Output objects that are not usable for internal use because it 
> relies on access to the Pool. If a User's use of the DataInput/Output also 
> needs Pool then it will be broken.  Internally we turn around and call an 
> internal API to add the Pool to the DataInput/Output. This all seems really 
> dirty, can we do better?



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

[jira] [Assigned] (GEODE-4973) Add docker-compose to ci pipeline image

[Nick Reich (JIRA)]

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

Nick Reich reassigned GEODE-4973:
-

Assignee: Nick Reich

> Add docker-compose to ci pipeline image
> ---
>
> Key: GEODE-4973
> URL: https://issues.apache.org/jira/browse/GEODE-4973
> Project: Geode
>  Issue Type: Improvement
>  Components: ci
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>
> To enable tests that spin up (potentially multiple) docker containers, add 
> docker-compose to the items installed in the ci image.



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

[jira] [Created] (GEODE-4973) Add docker-compose to ci pipeline image

[Nick Reich (JIRA)]

Nick Reich created GEODE-4973:
-

 Summary: Add docker-compose to ci pipeline image
 Key: GEODE-4973
 URL: https://issues.apache.org/jira/browse/GEODE-4973
 Project: Geode
  Issue Type: Improvement
  Components: ci
Reporter: Nick Reich


To enable tests that spin up (potentially multiple) docker containers, add 
docker-compose to the items installed in the ci image.



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

[jira] [Commented] (GEODE-4970) CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4970:


Commit a2cc50346fe0bb3f03ddf7c9c8a2494118b4a131 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a2cc503 ]

GEODE-4970: Disable PartitionedRegionQueryDUnitTest

Mark PartitionedRegionQueryDUnitTest with @Ignore to prevent this test
from hanging during precheckin. I'll merge a followup commit to reenable
the test after I overhaul it.


> CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may 
> hang
> 
>
> Key: GEODE-4970
> URL: https://issues.apache.org/jira/browse/GEODE-4970
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> We should disable this test until we can commit a fix.
> {noformat}
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-connectors/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:20:34.241 +
> Ended @ 2018-03-27 00:22:53.324 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-core/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:23:14.674 +
> 2018-03-27 01:03:05.285 +  
> org.apache.geode.internal.cache.PartitionedRegionQueryDUnitTest 
> tesRangeIndexWithPdxObjects
> Ended @ 2018-03-27 02:55:00.443 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-assembly/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:30:39.754 +
> Ended @ 2018-03-27 00:20:28.529 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/extensions/geode-modules-tomcat8/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:28:30.596 +
> Ended @ 2018-03-26 23:30:03.751 +
> {noformat}



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

[jira] [Assigned] (GEODE-4971) Allow GfshRule to launch a cluster with a different Geode version

[Jens Deppe (JIRA)]

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

Jens Deppe reassigned GEODE-4971:
-

Assignee: Jens Deppe

> Allow GfshRule to launch a cluster with a different Geode version
> -
>
> Key: GEODE-4971
> URL: https://issues.apache.org/jira/browse/GEODE-4971
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> We should be able to use {{VersionManager}} to start a cluster with an older 
> Geode version.



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

[jira] [Assigned] (GEODE-4972) Move VersionManager into geode-old-versions module

[Jens Deppe (JIRA)]

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

Jens Deppe reassigned GEODE-4972:
-

Assignee: Jens Deppe

> Move VersionManager into geode-old-versions module
> --
>
> Key: GEODE-4972
> URL: https://issues.apache.org/jira/browse/GEODE-4972
> Project: Geode
>  Issue Type: Task
>  Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> This is a precursor to GEODE-4971



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

[jira] [Commented] (GEODE-4970) CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang

[Kirk Lund (JIRA)]

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

Kirk Lund commented on GEODE-4970:
--

After studying the test, I think we should just do thorough cleanup and run the 
test over-and-over to see if there's a race in the test or product that can 
cause this test to hang.

> CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may 
> hang
> 
>
> Key: GEODE-4970
> URL: https://issues.apache.org/jira/browse/GEODE-4970
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> We should disable this test until we can commit a fix.
> {noformat}
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-connectors/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:20:34.241 +
> Ended @ 2018-03-27 00:22:53.324 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-core/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:23:14.674 +
> 2018-03-27 01:03:05.285 +  
> org.apache.geode.internal.cache.PartitionedRegionQueryDUnitTest 
> tesRangeIndexWithPdxObjects
> Ended @ 2018-03-27 02:55:00.443 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-assembly/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:30:39.754 +
> Ended @ 2018-03-27 00:20:28.529 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/extensions/geode-modules-tomcat8/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:28:30.596 +
> Ended @ 2018-03-26 23:30:03.751 +
> {noformat}



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

[jira] [Created] (GEODE-4971) Allow GfshRule to launch a cluster with a different Geode version

[Jens Deppe (JIRA)]

Jens Deppe created GEODE-4971:
-

 Summary: Allow GfshRule to launch a cluster with a different Geode 
version
 Key: GEODE-4971
 URL: https://issues.apache.org/jira/browse/GEODE-4971
 Project: Geode
  Issue Type: Task
  Components: gfsh
Reporter: Jens Deppe


We should be able to use {{VersionManager}} to start a cluster with an older 
Geode version.



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

[jira] [Assigned] (GEODE-4970) CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-4970:


Assignee: Kirk Lund

> CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may 
> hang
> 
>
> Key: GEODE-4970
> URL: https://issues.apache.org/jira/browse/GEODE-4970
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> We should disable this test until we can commit a fix.
> {noformat}
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-connectors/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:20:34.241 +
> Ended @ 2018-03-27 00:22:53.324 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-core/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-27 00:23:14.674 +
> 2018-03-27 01:03:05.285 +  
> org.apache.geode.internal.cache.PartitionedRegionQueryDUnitTest 
> tesRangeIndexWithPdxObjects
> Ended @ 2018-03-27 02:55:00.443 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/geode-assembly/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:30:39.754 +
> Ended @ 2018-03-27 00:20:28.529 +
> Checking progress file: 
> /tmp/build/ae3c03f4/built-geode/test/extensions/geode-modules-tomcat8/build/distributedTest/distributedTest-progress.txt
> Started @ 2018-03-26 23:28:30.596 +
> Ended @ 2018-03-26 23:30:03.751 +
> {noformat}



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

[jira] [Created] (GEODE-4970) CI failure: PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-4970:


 Summary: CI failure: 
PartitionedRegionQueryDUnitTest.tesRangeIndexWithPdxObjects may hang
 Key: GEODE-4970
 URL: https://issues.apache.org/jira/browse/GEODE-4970
 Project: Geode
  Issue Type: Bug
  Components: tests
Reporter: Kirk Lund


We should disable this test until we can commit a fix.
{noformat}
Checking progress file: 
/tmp/build/ae3c03f4/built-geode/test/geode-connectors/build/distributedTest/distributedTest-progress.txt
Started @ 2018-03-27 00:20:34.241 +
Ended @ 2018-03-27 00:22:53.324 +
Checking progress file: 
/tmp/build/ae3c03f4/built-geode/test/geode-core/build/distributedTest/distributedTest-progress.txt
Started @ 2018-03-27 00:23:14.674 +
2018-03-27 01:03:05.285 +  
org.apache.geode.internal.cache.PartitionedRegionQueryDUnitTest 
tesRangeIndexWithPdxObjects
Ended @ 2018-03-27 02:55:00.443 +
Checking progress file: 
/tmp/build/ae3c03f4/built-geode/test/geode-assembly/build/distributedTest/distributedTest-progress.txt
Started @ 2018-03-26 23:30:39.754 +
Ended @ 2018-03-27 00:20:28.529 +
Checking progress file: 
/tmp/build/ae3c03f4/built-geode/test/extensions/geode-modules-tomcat8/build/distributedTest/distributedTest-progress.txt
Started @ 2018-03-26 23:28:30.596 +
Ended @ 2018-03-26 23:30:03.751 +
{noformat}



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

[jira] [Updated] (GEODE-4929) PR Accessor with Overflow should not create DiskStore

[ASF GitHub Bot (JIRA)]

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

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

> PR Accessor with Overflow should not create DiskStore
> -
>
> Key: GEODE-4929
> URL: https://issues.apache.org/jira/browse/GEODE-4929
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>  Labels: pull-request-available
>
> While renaming Bug42055DUnitTest as 
> BucketRegionSizeWithOverflowRegressionTest, I found that the test had never 
> been "completed" so I finished writing it according to the summary and 
> description of the original TRAC bug.
> Javadocs on the test say:
> {noformat}
> Test that the bucket size does not go negative when we fault out and in a 
> delta object.
> {noformat}
> ...but the original bug doesn't seem to be specific to delta, so I recommend 
> writing another test to cover what this javadoc describes.
> The summary of TRAC #42055 is:
> {noformat}
> a pr accessor configured for OverflowToDisk fails during creation because of 
> disk
> {noformat}
> I interpret the bug as saying:
> {noformat}
> PR accessor configured for OverflowToDisk should not create a diskstore.
> {noformat}
> Unfortunately, the test shows that the Accessor does in fact create a 
> diskstore. I'm marking the test with {{\@Ignore("GEODE-4929")}} until we can 
> fix this bug or determine that the assertion is invalid.



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

[jira] [Closed] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda closed GEODE-4880.
--

> Ignore Pulse UI acceptance tests that are flaky
> ---
>
> Key: GEODE-4880
> URL: https://issues.apache.org/jira/browse/GEODE-4880
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Closed] (GEODE-4807) Pulse UI tests using locator/cluster rule.

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda closed GEODE-4807.
--

> Pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4807) Pulse UI tests using locator/cluster rule.

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda resolved GEODE-4807.

Resolution: Fixed

> Pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda resolved GEODE-4880.

Resolution: Fixed

> Ignore Pulse UI acceptance tests that are flaky
> ---
>
> Key: GEODE-4880
> URL: https://issues.apache.org/jira/browse/GEODE-4880
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Closed] (GEODE-4898) Fix field names in DestroyJndiBindingCommand

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda closed GEODE-4898.
--

> Fix field names in DestroyJndiBindingCommand
> 
>
> Key: GEODE-4898
> URL: https://issues.apache.org/jira/browse/GEODE-4898
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Field names in DestroyJndiBindingCommand uses CREATE_BINDING.



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

[jira] [Resolved] (GEODE-4898) Fix field names in DestroyJndiBindingCommand

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda resolved GEODE-4898.

Resolution: Fixed

> Fix field names in DestroyJndiBindingCommand
> 
>
> Key: GEODE-4898
> URL: https://issues.apache.org/jira/browse/GEODE-4898
> Project: Geode
>  Issue Type: Task
>  Components: gfsh
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Field names in DestroyJndiBindingCommand uses CREATE_BINDING.



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

[jira] [Resolved] (GEODE-4941) Increase UITests timeout to 2h

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda resolved GEODE-4941.

Resolution: Fixed

> Increase UITests timeout to 2h
> --
>
> Key: GEODE-4941
> URL: https://issues.apache.org/jira/browse/GEODE-4941
> Project: Geode
>  Issue Type: Task
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some of the runs timed out after 1hr. Lets increase it to 2h.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 99bb4f0fc411f529cd219d8f2f2787f541e0f884 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=99bb4f0 ]

GEODE-4876: Update AcceptorImplClientQueueDistributedTest use of VM and 
NetworkUtil

* rename AcceptorImplClientQueueDUnitTest as 
AcceptorImplClientQueueDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 5271b6b970e2239a4e46e3bc43fb41250c7b39e4 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5271b6b ]

GEODE-4876: Update DistributedDisconnectRuleDistributedTest use of VM and 
NetworkUtil

* rename DistributedDisconnectRuleTest as 
DistributedDisconnectRuleDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 4296f218aa9122e910ce6db45a1b7fd0664b9366 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4296f21 ]

GEODE-4876: Update SharedErrorCollectorDistributedTest use of VM and NetworkUtil

* rename SharedErrorCollectorTest as SharedErrorCollectorDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 7be2a7e215a85c9d48ec293c024b54d719946008 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7be2a7e ]

GEODE-4876: Cleanup CacheRule tests use of VM and javadocs

* rename CacheRuleTest as CacheRuleBuilderDistributedTest
* write new CacheRuleDistributedTest
* fix javadocs of CacheRule


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit cb6cd2d295cb007615d479df9ab02211f72c3304 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cb6cd2d ]

GEODE-4876: Update PRCustomPartitioningDistributedTest use of VM and NetworkUtil

* rename PRCustomPartitioningDUnitTest as PRCustomPartitioningDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 40795fedf572fb7658edee94f15d20b170ad0408 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=40795fe ]

GEODE-4876: Update SharedCountersRuleDistributedTest use of VM and NetworkUtil

* rename SharedCountersRuleTest as SharedCountersRuleDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit da4044ec9af30cca84f8eb51354efe381cfc307b in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=da4044e ]

GEODE-4876: Update DistributedDisconnectRuleAsClassRuleDistributedTest use of VM

* renamed from DistributedDisconnectRuleAsClassRuleTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit 46e98fb5e1be80c0ac6568848565c15519631d98 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=46e98fb ]

GEODE-4876: Update FunctionExecutionWithExceptionDistributedTest use of VM and 
NetworkUtil

* rename FunctionExecution_ExceptionDUnitTest as 
FunctionExecutionWithExceptionDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Commented] (GEODE-4876) Add static VM APIs from Host to VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4876:


Commit b069c1fa0121b4ce6a1ffbe206be699d89ade41f in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b069c1f ]

GEODE-4876: Update RegionListenerDistributedTest use of VM and NetworkUtil

* rename RegionListenerDUnitTest as RegionListenerDistributedTest


> Add static VM APIs from Host to VM
> --
>
> Key: GEODE-4876
> URL: https://issues.apache.org/jira/browse/GEODE-4876
> Project: Geode
>  Issue Type: Improvement
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM.
> Change tests that use DistributedTestRule to invoke methods on VM instead of 
> Host.



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

[jira] [Resolved] (GEODE-4829) Categorize the AEQ tests

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-4829.
-

I reopened this by mistake - dyslexia strikes again

> Categorize the AEQ tests
> 
>
> Key: GEODE-4829
> URL: https://issues.apache.org/jira/browse/GEODE-4829
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4928) DistributedLockService doesn't work as expected while the dlock grantor is initialized

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-4928.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> DistributedLockService doesn't work as expected while the dlock grantor is 
> initialized
> --
>
> Key: GEODE-4928
> URL: https://issues.apache.org/jira/browse/GEODE-4928
> Project: Geode
>  Issue Type: Bug
>  Components: distributed lock service
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> I wrote a function that obtained a dlock and then performed a transaction.  
> It always operates on the same dlock key and the same keys in my region.  
> That protects against getting a commit conflict exception BUT this sometimes 
> fails if the JVM holding the lock crashes.  One of the functions appears to 
> get the dlock okay but then its transaction fails when it goes to commit.



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

[jira] [Commented] (GEODE-4928) DistributedLockService doesn't work as expected while the dlock grantor is initialized

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4928:


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

GEODE-4928 DistributedLockService doesn't work as expected while the dlock 
grantor is initialized

Wait for background transaction cleanup when there is a failure.


> DistributedLockService doesn't work as expected while the dlock grantor is 
> initialized
> --
>
> Key: GEODE-4928
> URL: https://issues.apache.org/jira/browse/GEODE-4928
> Project: Geode
>  Issue Type: Bug
>  Components: distributed lock service
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> I wrote a function that obtained a dlock and then performed a transaction.  
> It always operates on the same dlock key and the same keys in my region.  
> That protects against getting a commit conflict exception BUT this sometimes 
> fails if the JVM holding the lock crashes.  One of the functions appears to 
> get the dlock okay but then its transaction fails when it goes to commit.



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

[jira] [Assigned] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME

[Michael Oleske (JIRA)]

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

Michael Oleske reassigned GEODE-4637:
-

Assignee: (was: Michael Oleske)

> Geode Native uses GEODE rather than GEODE_HOME
> --
>
> Key: GEODE-4637
> URL: https://issues.apache.org/jira/browse/GEODE-4637
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The java side of things uses {{GEODE_HOME}} environment variable to point to 
> the Geode install directory containing the /bin.
> [https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]
> Geode Native uses the environment variable GEODE. 
>  [https://github.com/apache/geode-native/blob/develop/BUILDING.md]
> This is confusing. It would be best if we standardize on {{GEODE_HOME}}.
>  
> This does not mean changing the FindGeode.cmake module's {{GEODE_ROOT}} 
> configuration variable. The only change should be in which environment 
> variable is used to search for Geode if the {{GEODE_ROOT}} is not explicitly 
> set.



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

[jira] [Commented] (GEODE-4946) Cleanup compiler warnings with MSVC

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4946:


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

GEODE-4946: Treat warnings as error on MSVC (#252)

- Removes LTCG warning on Release builds.
- Fixes compiler warnings on MSVC.


> Cleanup compiler warnings with MSVC
> ---
>
> Key: GEODE-4946
> URL: https://issues.apache.org/jira/browse/GEODE-4946
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> Too many warnings slow down compilation and hide real issues in the log noise.



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

[jira] [Updated] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett updated GEODE-4637:

Description: 
The java side of things uses {{GEODE_HOME}} environment variable to point to 
the Geode install directory containing the /bin.

[https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]

Geode Native uses the environment variable GEODE. 
 [https://github.com/apache/geode-native/blob/develop/BUILDING.md]

This is confusing. It would be best if we standardize on {{GEODE_HOME}}.

 

This does not mean changing the FindGeode.cmake module's {{GEODE_ROOT}} 
configuration variable. The only change should be in which environment variable 
is used to search for Geode if the {{GEODE_ROOT}} is not explicitly set.

  was:
The java side of things uses GEODE_HOME to point to the Geode install directory 
containing the /bin.

[https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]

Geode Native uses the env variable GEODE. 
 [https://github.com/apache/geode-native/blob/develop/BUILDING.md]

This is confusing. It would be best if we standardize on GEODE_HOME.

 

This does not mean changing the FindGeode.cmake module's `GEODE_ROOT` 
configuration variable. The only change should be in which environment variable 
is used to search for Geode if the `GEODE_ROOT` is not explicitly set.


> Geode Native uses GEODE rather than GEODE_HOME
> --
>
> Key: GEODE-4637
> URL: https://issues.apache.org/jira/browse/GEODE-4637
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The java side of things uses {{GEODE_HOME}} environment variable to point to 
> the Geode install directory containing the /bin.
> [https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]
> Geode Native uses the environment variable GEODE. 
>  [https://github.com/apache/geode-native/blob/develop/BUILDING.md]
> This is confusing. It would be best if we standardize on {{GEODE_HOME}}.
>  
> This does not mean changing the FindGeode.cmake module's {{GEODE_ROOT}} 
> configuration variable. The only change should be in which environment 
> variable is used to search for Geode if the {{GEODE_ROOT}} is not explicitly 
> set.



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

[jira] [Updated] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett updated GEODE-4637:

Description: 
The java side of things uses GEODE_HOME to point to the Geode install directory 
containing the /bin.

[https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]

Geode Native uses the env variable GEODE. 
 [https://github.com/apache/geode-native/blob/develop/BUILDING.md]

This is confusing. It would be best if we standardize on GEODE_HOME.

 

This does not mean changing the FindGeode.cmake module's `GEODE_ROOT` 
configuration variable. The only change should be in which environment variable 
is used to search for Geode if the `GEODE_ROOT` is not explicitly set.

  was:
The java side of things uses GEODE_HOME to point to the Geode install directory 
containing the /bin.

https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle

Geode Native uses the env variable GEODE.  
https://github.com/apache/geode-native/blob/develop/BUILDING.md

This is confusing.  It would be best if we standardize on GEODE_HOME.



> Geode Native uses GEODE rather than GEODE_HOME
> --
>
> Key: GEODE-4637
> URL: https://issues.apache.org/jira/browse/GEODE-4637
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The java side of things uses GEODE_HOME to point to the Geode install 
> directory containing the /bin.
> [https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle]
> Geode Native uses the env variable GEODE. 
>  [https://github.com/apache/geode-native/blob/develop/BUILDING.md]
> This is confusing. It would be best if we standardize on GEODE_HOME.
>  
> This does not mean changing the FindGeode.cmake module's `GEODE_ROOT` 
> configuration variable. The only change should be in which environment 
> variable is used to search for Geode if the `GEODE_ROOT` is not explicitly 
> set.



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

[jira] [Updated] (GEODE-4909) Add dunit test coverage for lucene reindex with security

[ASF GitHub Bot (JIRA)]

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

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

> Add dunit test coverage for lucene reindex with security
> 
>
> Key: GEODE-4909
> URL: https://issues.apache.org/jira/browse/GEODE-4909
> Project: Geode
>  Issue Type: Test
>  Components: lucene
>Affects Versions: 1.6.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
>  Labels: pull-request-available
>
> Add new dunit tests:
> - LuceneClientSecurityWithRegionCreatedBeforeReindexDUnitTest 
> - LuceneCommandSecurityWithRegionCreatedBeforeReindexDUnitTest



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

[jira] [Assigned] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME

[Michael Oleske (JIRA)]

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

Michael Oleske reassigned GEODE-4637:
-

Assignee: Michael Oleske

> Geode Native uses GEODE rather than GEODE_HOME
> --
>
> Key: GEODE-4637
> URL: https://issues.apache.org/jira/browse/GEODE-4637
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>
> The java side of things uses GEODE_HOME to point to the Geode install 
> directory containing the /bin.
> https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle
> Geode Native uses the env variable GEODE.  
> https://github.com/apache/geode-native/blob/develop/BUILDING.md
> This is confusing.  It would be best if we standardize on GEODE_HOME.



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

[jira] [Updated] (GEODE-4637) Geode Native uses GEODE rather than GEODE_HOME

[ASF GitHub Bot (JIRA)]

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

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

> Geode Native uses GEODE rather than GEODE_HOME
> --
>
> Key: GEODE-4637
> URL: https://issues.apache.org/jira/browse/GEODE-4637
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>
> The java side of things uses GEODE_HOME to point to the Geode install 
> directory containing the /bin.
> https://github.com/apache/geode-examples/blob/5b413a34e30790a6631332cfa1f4b485a487abcb/build.gradle
> Geode Native uses the env variable GEODE.  
> https://github.com/apache/geode-native/blob/develop/BUILDING.md
> This is confusing.  It would be best if we standardize on GEODE_HOME.



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

[jira] [Updated] (GEODE-4963) ConnectCommandDUnitTest is broken since GfshCommand was made 'public'

[Shelley Lynn Hughes-Godfrey (JIRA)]

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

Shelley Lynn Hughes-Godfrey updated GEODE-4963:
---
Description: 
The failure looks like this:

{noformat}
org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest > 
useCurrentGfshToConnectToOlderLocator FAILED
java.lang.AssertionError: 
Expecting:
 <"_ __
   / _/ __/ __/ // /
  / /  __/ /___  /_  / _  / 
 / /__/ / /  _/ / // /  
/__/_/  /__/_//_/1.6.0-SNAPSHOT

Monitor and Manage Apache Geode
Connecting to Manager at [host=localhost, port=28823] ..
Could not connect to : [host=localhost, port=28823]. Failed to retrieve 
RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is: 
java.net.ConnectException: Connection refused (Connection refused)]

">
to contain:
 <"Cannot use a"> 
at 
org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:79)
at 
org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandDUnitTest.java:46)
{noformat}

> ConnectCommandDUnitTest is broken since GfshCommand was made 'public'
> -
>
> Key: GEODE-4963
> URL: https://issues.apache.org/jira/browse/GEODE-4963
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: ci
>
> The failure looks like this:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest > 
> useCurrentGfshToConnectToOlderLocator FAILED
> java.lang.AssertionError: 
> Expecting:
>  <"_ __
>/ _/ __/ __/ // /
>   / /  __/ /___  /_  / _  / 
>  / /__/ / /  _/ / // /  
> /__/_/  /__/_//_/1.6.0-SNAPSHOT
> 
> Monitor and Manage Apache Geode
> Connecting to Manager at [host=localhost, port=28823] ..
> Could not connect to : [host=localhost, port=28823]. Failed to retrieve 
> RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is 
> java.rmi.ConnectException: Connection refused to host: localhost; nested 
> exception is: 
>   java.net.ConnectException: Connection refused (Connection refused)]
> ">
> to contain:
>  <"Cannot use a"> 
> at 
> org.apache.geode.test.junit.assertions.CommandResultAssert.containsOutput(CommandResultAssert.java:79)
> at 
> org.apache.geode.management.internal.cli.commands.ConnectCommandDUnitTest.useCurrentGfshToConnectToOlderLocator(ConnectCommandDUnitTest.java:46)
> {noformat}



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

[jira] [Updated] (GEODE-4963) ConnectCommandDUnitTest is broken since GfshCommand was made 'public'

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4963:
--
Labels: ci  (was: )

> ConnectCommandDUnitTest is broken since GfshCommand was made 'public'
> -
>
> Key: GEODE-4963
> URL: https://issues.apache.org/jira/browse/GEODE-4963
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>  Labels: ci
>




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

[jira] [Updated] (GEODE-4930) Add @Disabled annotation to be applied to GfshCommand classes.

[ASF GitHub Bot (JIRA)]

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

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

> Add @Disabled annotation to be applied to GfshCommand classes.
> --
>
> Key: GEODE-4930
> URL: https://issues.apache.org/jira/browse/GEODE-4930
> Project: Geode
>  Issue Type: Sub-task
>  Components: gfsh
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>




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

[jira] [Resolved] (GEODE-1320) gfsh function execution does not report errors correctly

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-1320.
---
Resolution: Won't Do

> gfsh function execution does not report errors correctly
> 
>
> Key: GEODE-1320
> URL: https://issues.apache.org/jira/browse/GEODE-1320
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
>
> I have a locator and a server and am trying to execute a simple function 
> using a {{ResultCollector}} as follows:
> {noformat}
> gfsh> execute function --id=basic-function --region=FOO -\
> -result-collector=io.pivotal.gemfire.ToUpperResultCollector
> {noformat}
> The result is simply:
> {noformat}
> io.pivotal.gemfire.ToUpperResultCollector
> {noformat}
> This occurs if my collector class is not on the classpath of the locator. in 
> {{FunctionCommands.executeFunction}} the collector is trying to be 
> instantiated but a {{ClassNotFoundException}} is generated and does not make 
> it back to the client.
> Here is the code for the collector:
> {code:java}
> public class ToUpperResultCollector implements ResultCollector {
>   private List results = new ArrayList<>();
>   private CountDownLatch latch = new CountDownLatch(1);
>   @Override
>   public Object getResult() throws FunctionException {
> try {
>   latch.await();
> } catch (InterruptedException e) {
>   throw new FunctionException("Interrupted waiting for results", e);
> }
> return results;
>   }
>   @Override
>   public Object getResult(long timeout, TimeUnit unit) throws 
> FunctionException, InterruptedException {
> latch.await(timeout, unit);
> return results;
>   }
>   @Override
>   public void addResult(DistributedMember memberID, Object 
> resultOfSingleExecution) {
> results.add(resultOfSingleExecution.toString().toUpperCase());
>   }
>   @Override
>   public void endResults() {
> latch.countDown();
>   }
>   @Override
>   public void clearResults() {
> results.clear();
> latch = new CountDownLatch(1);
>   }
> }
> {code}



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

[jira] [Resolved] (GEODE-2115) Some GFSH commands may report success even for failures

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-2115.
---
Resolution: Won't Do

> Some GFSH commands may report success even for failures
> ---
>
> Key: GEODE-2115
> URL: https://issues.apache.org/jira/browse/GEODE-2115
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Jared Stewart
>Priority: Major
>
> GFSH commands with potentially broken error handling:
> * MiscellaneousCommands.exportLogs
> Command implementation (ie MiscellaneousCommands) may ignore errors returned 
> from Function via sendException or lastResult. Function implementation (ie 
> LogFileFunction) may fail to invoke sendException for caught exceptions.
> Functions under `org.apache.geode.management.internal.cli.functions` should 
> use `ResultSend::sendException` to return full stack trace of caught 
> exceptions.
> Command implementations should read exceptions returned from functions 
> without discarding the info.



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

[jira] [Commented] (GEODE-2315) Improve cluster config: starting a second locator which joins a locator with cluster configuration should inherit the first locator's security settings.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-2315:
---

[~jinmeiliao] Has this been fixed? Can this be closed?

> Improve cluster config: starting a second locator which joins a locator with 
> cluster configuration should inherit the first locator's security settings.
> 
>
> Key: GEODE-2315
> URL: https://issues.apache.org/jira/browse/GEODE-2315
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Jinmei Liao
>Priority: Major
>




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

[jira] [Commented] (GEODE-4969) PDX Type registry throws CacheClosedException causing random test failures

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4969:


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

GEODE-4969 PDX Type registry throws CacheClosedException causing random test 
failures

bullet proofing yet another test against this TypeRegistry problem


> PDX Type registry throws CacheClosedException causing random test failures
> --
>
> Key: GEODE-4969
> URL: https://issues.apache.org/jira/browse/GEODE-4969
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Priority: Major
>
> The type registry throws a CacheClosedException if a cache ever existed in a 
> JVM and has been closed.  This is causing unit tests that do not create a 
> cache to fail:
> org.apache.geode.internal.HeapDataOutputStreamJUnitTest > 
> testWriteJavaSerializeNoCopy FAILED 
> org.apache.geode.cache.CacheClosedException: Could not PDX serialize because 
> the cache was closed at 
> org.apache.geode.pdx.internal.TypeRegistry.getPdxSerializer(TypeRegistry.java:366)
>  at 
> org.apache.geode.internal.InternalDataSerializer.writeUserObject(InternalDataSerializer.java:1661)
>  at 
> org.apache.geode.internal.InternalDataSerializer.writeWellKnownObject(InternalDataSerializer.java:1562)
>  at 
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2226)
>  at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936) at 
> org.apache.geode.internal.HeapDataOutputStreamJUnitTest.testWriteJavaSerializeNoCopy(HeapDataOutputStreamJUnitTest.java:148)
>  
> Tests have to be modified to invoke TypeRegistry.init() to get around this 
> problem but they shouldn't have to.



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

[jira] [Resolved] (GEODE-2211) OQL query shows partial results when data is inserted through REST POST api.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-2211.
---
Resolution: Won't Do

> OQL query shows partial results when data is inserted through REST POST api.
> 
>
> Key: GEODE-2211
> URL: https://issues.apache.org/jira/browse/GEODE-2211
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Amey Barve
>Priority: Major
>  Labels: gfsh
>
> Steps to Reproduce the Issue
> Start a locator
> Configure pdx
> Start server1 with Developer Rest Enabled.
> Start server2
> Create Geode Region PARTIONED_PERSISTENENT
> Using Swagger UI enter some Key and Values in the Region.
> using mash run query "Select * /Region"
> Executing - query --query="Select * from /test"
> Result : true
> startCount : 0
> endCount   : 20
> Rows   : 4
>  1   |  3   |deserializedForReading | 
> stringForm | DSFID |  serializedValue   | sizeInBytes | serialized | 
> valueSizeInBytes | value
>  |  | - | 
> -- | - | -- | --- | 
> -- |  | --
> A| C| org.apache.geode.pdx.internal.PdxInstanceImpl | 
> PDX[2,__GEMFIRE_JSON]{2=B} | -65   | org.json.JSONArray | 37  | true  
>  | 25   | org.json.JSONArray
> null | null | org.apache.geode.pdx.internal.PdxInstanceImpl | 
> PDX[4,__GEMFIRE_JSON]{4=D} | -65   | org.json.JSONArray | 37  | true  
>  | 25   | org.json.JSONArray
> null | null | null  | null
>| null  | null   | null| null   | null 
> | null
> null | null | null  | null
>| null  | null   | null| null   | null 
> | null
> NEXT_STEP_NAME : END
> It only shows first 2 entries and other as null.
> The below script reproduces the issue:
> #!/usr/bin/env bash
> GEODE_HOME=./geode-assembly/build/install/apache-geode
> $GEODE_HOME/bin/gfsh -e "start locator --name=l1 --port=10339" \
> -e "configure pdx --read-serialized=true --disk-store" \
> -e "start server --name=s1 --server-port=40408 
> --J=-Dgemfire.start-dev-rest-api=true --J=-Dgemfire.http-service-port=8080 
> --J=-Dgemfire.http-service-bind-address=localhost" \
> -e "start server --name=s2 --server-port=40409 " \
> -e "create region --name=test --type=PARTITION_PERSISTENT"
> tput setaf 3; echo "Inserting the values in persisten region test"
> `curl -s -H 'Content-Type: application/json' -H 'Accept: application/json' -X 
> POST -d '{"1":"A"}' http://localhost:8080/gemfire-api/v1/test?key=1`
> `curl -s -H 'Content-Type: application/json' -H 'Accept: application/json' -X 
> POST -d '{"2":"B"}' http://localhost:8080/gemfire-api/v1/test?key=2`
> `curl -s -H 'Content-Type: application/json' -H 'Accept: application/json' -X 
> POST -d '{"3":"C"}' http://localhost:8080/gemfire-api/v1/test?key=3`
> `curl -s -H 'Content-Type: application/json' -H 'Accept: application/json' -X 
> POST -d '{"4":"D"}' http://localhost:8080/gemfire-api/v1/test?key=4`
> tput setaf 3; echo "The values inserted into the region test are as"
> echo `curl -X GET http://localhost:8080/gemfire-api/v1/test?limit=50 
> 2>/dev/null`
> $GEODE_HOME/bin/gfsh -e "connect --locator=localhost[10339]" \
>  -e "query --query=\"Select * from /test\"" 
>  -e "stop server --name=s1 " \
>  -e "stop server --name=s2 " \
>  -e "stop locator --name=l1 "



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

[jira] [Resolved] (GEODE-1865) Change DistributionConfigImpl to store Ciphers and Protocols as String[] rather than just plain String

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-1865.
---
Resolution: Won't Do

> Change DistributionConfigImpl to store Ciphers and Protocols as String[] 
> rather than just plain String
> --
>
> Key: GEODE-1865
> URL: https://issues.apache.org/jira/browse/GEODE-1865
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration
>Reporter: Udo Kohlmeyer
>Priority: Major
>
> Currently *-ciphers and *-protocols are stored as Strings. Given that these 
> settings are multi-valued it would make more sense to store them as String[].



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

[jira] [Resolved] (GEODE-1950) Start locator hangs forever on AWS when specifying -Djava.rmi.server.hostname

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-1950.
---
Resolution: Won't Do

> Start locator hangs forever on AWS when specifying -Djava.rmi.server.hostname 
> --
>
> Key: GEODE-1950
> URL: https://issues.apache.org/jira/browse/GEODE-1950
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Jared Stewart
>Priority: Major
> Attachments: gfshThreadDump.txt, locatorThreadDump.txt
>
>
> If you spin up an AWS instance, specify 
> {{--J=-Djava.rmi.server.hostname=}}, and don't open incoming tcp 
> connections for the JMX port in the AWS security group for that instance, the 
> start locator command hangs indefinitely.  
> {code}
> gfsh>start locator --name=l1 --J=-Djava.rmi.server.hostname=
> {code}



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

[jira] [Resolved] (GEODE-1815) ConfigurationProperties javadocs need to be more descriptive in a number of cases

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-1815.
---
Resolution: Won't Do

> ConfigurationProperties javadocs need to be more descriptive in a number of 
> cases
> -
>
> Key: GEODE-1815
> URL: https://issues.apache.org/jira/browse/GEODE-1815
> Project: Geode
>  Issue Type: Bug
>  Components: security
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: javadocs
>
> There are a number of new SECURITY properties in ConfigurationProperties that 
> have a "geode 1.0" tag that have inadequate javadocs.  This is the primary 
> location for documenting distribution config properties, so they need to have 
> a good description like all of the other properties.
> This is one such property:
> {noformat}
>   /**
>* The static String definition of the "security-manager"
>* property
>* @since Geode 1.0
>*/
>   String SECURITY_MANAGER = SECURITY_PREFIX + "manager";
> {noformat}
> this is a properly documented property:
> {noformat}
>   /**
>* The static String definition of the "remote-locators" property
>* 
>* Description: A list of locators (host and port) that a cluster
>* will use in order to connect to a remote site in a multi-site (WAN)
>* configuration. This attribute's value is a possibly comma separated list.
>* For each remote locator, provide a hostname and/or address
>* (separated by '@', if you use both), followed by a port number in 
> brackets.
>* Examples:
>* remote-locators=address1[port1],address2[port2]
>* 
>* remote-locators=hostName1@address1[port1],hostName2@address2[port2]
>* 
>* remote-locators=hostName1[port1],hostName2[port2]
>* 
>* Default: ""
>*/
>   String REMOTE_LOCATORS = "remote-locators";
> {noformat}



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

[jira] [Created] (GEODE-4969) PDX Type registry throws CacheClosedException causing random test failures

[Bruce Schuchardt (JIRA)]

Bruce Schuchardt created GEODE-4969:
---

 Summary: PDX Type registry throws CacheClosedException causing 
random test failures
 Key: GEODE-4969
 URL: https://issues.apache.org/jira/browse/GEODE-4969
 Project: Geode
  Issue Type: Bug
  Components: serialization
Reporter: Bruce Schuchardt


The type registry throws a CacheClosedException if a cache ever existed in a 
JVM and has been closed.  This is causing unit tests that do not create a cache 
to fail:

org.apache.geode.internal.HeapDataOutputStreamJUnitTest > 
testWriteJavaSerializeNoCopy FAILED 
org.apache.geode.cache.CacheClosedException: Could not PDX serialize because 
the cache was closed at 
org.apache.geode.pdx.internal.TypeRegistry.getPdxSerializer(TypeRegistry.java:366)
 at 
org.apache.geode.internal.InternalDataSerializer.writeUserObject(InternalDataSerializer.java:1661)
 at 
org.apache.geode.internal.InternalDataSerializer.writeWellKnownObject(InternalDataSerializer.java:1562)
 at 
org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2226)
 at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936) at 
org.apache.geode.internal.HeapDataOutputStreamJUnitTest.testWriteJavaSerializeNoCopy(HeapDataOutputStreamJUnitTest.java:148)

 

Tests have to be modified to invoke TypeRegistry.init() to get around this 
problem but they shouldn't have to.



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

[jira] [Commented] (GEODE-2262) Improve cluster config: do not allow mix of locators that has CC enabled and not enabled in one cluster.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-2262:
---

[~jinmeiliao] Has this been fixed? Can this ticket be closed?

> Improve cluster config: do not allow mix of locators that has CC enabled and 
> not enabled in one cluster.
> 
>
> Key: GEODE-2262
> URL: https://issues.apache.org/jira/browse/GEODE-2262
> Project: Geode
>  Issue Type: Sub-task
>  Components: management
>Reporter: Jinmei Liao
>Priority: Major
>
> When a locator is started with CC enabled, do not allow another locator 
> without CC to join it or vise versa.



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

[jira] [Updated] (GEODE-4968) Parameterize Find Module for Examples

[ASF GitHub Bot (JIRA)]

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

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

> Parameterize Find Module for Examples
> -
>
> Key: GEODE-4968
> URL: https://issues.apache.org/jira/browse/GEODE-4968
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ryan McMahon
>Assignee: Ryan McMahon
>Priority: Major
>  Labels: pull-request-available
>
> Adds the ability to override the product name in Find cmake script for 
> examples.



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

[jira] [Created] (GEODE-4968) Parameterize Find Module for Examples

[Ryan McMahon (JIRA)]

Ryan McMahon created GEODE-4968:
---

 Summary: Parameterize Find Module for Examples
 Key: GEODE-4968
 URL: https://issues.apache.org/jira/browse/GEODE-4968
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Ryan McMahon


Adds the ability to override the product name in Find cmake script for examples.



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

[jira] [Assigned] (GEODE-4968) Parameterize Find Module for Examples

[Ryan McMahon (JIRA)]

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

Ryan McMahon reassigned GEODE-4968:
---

Assignee: Ryan McMahon

> Parameterize Find Module for Examples
> -
>
> Key: GEODE-4968
> URL: https://issues.apache.org/jira/browse/GEODE-4968
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ryan McMahon
>Assignee: Ryan McMahon
>Priority: Major
>
> Adds the ability to override the product name in Find cmake script for 
> examples.



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

[jira] [Created] (GEODE-4966) Add Security Permissions for JDBC gfsh commands

[Barbara Pruijn (JIRA)]

Barbara Pruijn created GEODE-4966:
-

 Summary: Add Security Permissions for JDBC gfsh commands
 Key: GEODE-4966
 URL: https://issues.apache.org/jira/browse/GEODE-4966
 Project: Geode
  Issue Type: Task
  Components: docs, regions
Reporter: Barbara Pruijn


Please make sure security permissions are documented for the jdbc commands on 
these pages:

[http://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html]
[https://cwiki.apache.org/confluence/display/GEODE/Geode+Integrated+Security]
[https://cwiki.apache.org/confluence/display/GEODE/Finer%20grained%20security]



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

[jira] [Created] (GEODE-4965) Add security permissions to documentation for JNDI binding commands

[Barbara Pruijn (JIRA)]

Barbara Pruijn created GEODE-4965:
-

 Summary: Add security permissions to documentation for JNDI 
binding commands
 Key: GEODE-4965
 URL: https://issues.apache.org/jira/browse/GEODE-4965
 Project: Geode
  Issue Type: Task
  Components: docs
Reporter: Barbara Pruijn


The following commands need to be added to the permission list on these pages:
http://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html
https://cwiki.apache.org/confluence/display/GEODE/Geode+Integrated+Security
https://cwiki.apache.org/confluence/display/GEODE/Finer%20grained%20security

create jndi-binding: CLUSTER:MANAGE
list jndi-binding: CLUSTER:READ
describe jndi-binding: CLUSTER:READ
destroy jndi-binding: CLUSTER:MANAGE





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

[jira] [Updated] (GEODE-4934) CI Failure: GfshScript timing out intermittently waiting for execution to complete

[ASF GitHub Bot (JIRA)]

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

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

> CI Failure: GfshScript timing out intermittently waiting for execution to 
> complete
> --
>
> Key: GEODE-4934
> URL: https://issues.apache.org/jira/browse/GEODE-4934
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
>Priority: Major
>  Labels: CI, pull-request-available
>
> GfshScript.awaitIfNecessary native method call to determine if the process 
> executing the script is alive hangs. This is not a hard failure, but it can 
> be reproduced with frequently running selected tests from command line. This 
> following set of tests produces failures when run on a Linux host (tested on 
> CentOS 7).
> {code}
> ./gradlew clean geode-lucene:precheckin --parallel -x rat -x javadoc -x 
> spotlessCheck{code}
> {code}
> {code:title=Typical failure stack}
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest > 
> cannotStopServerByNameWhenNotConnected FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)
> at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)
> at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:87)
> at 
> org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:35)
> {code}
> All failures show the same stack from {{at 
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)}}



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

[jira] [Created] (GEODE-4964) .NET AuthenticatedCache::CreatePdxInstanceFactory needs real Cache

[Jacob S. Barrett (JIRA)]

Jacob S. Barrett created GEODE-4964:
---

 Summary: .NET AuthenticatedCache::CreatePdxInstanceFactory needs 
real Cache
 Key: GEODE-4964
 URL: https://issues.apache.org/jira/browse/GEODE-4964
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


As a result of GEODE-4946 it was discovered that this method was attempting an 
invalid cast to Cache from AuthenticatedCache. It now passes nullptr which 
should result in a test failure but apparently there are no working tests of 
AuthenticatedCache. We need to fix this and some tests to validate correct 
behavior.



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