[jira] [Updated] (GEODE-4942) Secondary Gateway Sender queue after GII might leave some event un-drained

[ASF GitHub Bot (JIRA)]

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

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

> Secondary Gateway Sender queue after GII might leave some event un-drained
> --
>
> Key: GEODE-4942
> URL: https://issues.apache.org/jira/browse/GEODE-4942
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
>
> We found this problem in #49196. It has been fixed several times. I just 
> reproduced another scenario via 
> ParallelGatewaySenderOperationsDUnitTest.
> testParallelPropagationSenderStartAfterStop_Scenario2.
> The test did not check the drain of secondary queue, if added the checking. 
> sometime it will fail with some event stay in secondary queue forever. 



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

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

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg commented on GEODE-4959:
-

I think the best solution, as far as stability and consistency with other 
commands, would be to add a {{--skip-if-exists}} option to this command.  If a 
gateway receiver does exist but the option is provided, the output table will 
note that that state.  If it is not provided, then an exception will be thrown 
to gfsh.


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



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

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

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg reassigned GEODE-4959:
---

Assignee: Patrick Rhomberg

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



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

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

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4959:
--
Component/s: docs

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



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

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

[ASF GitHub Bot (JIRA)]

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

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

> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
>




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

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

[Jinmei Liao (JIRA)]

Jinmei Liao created GEODE-5000:
--

 Summary: When initializing a client cache, we don't need to 
request/apply cluster configuration
 Key: GEODE-5000
 URL: https://issues.apache.org/jira/browse/GEODE-5000
 Project: Geode
  Issue Type: Bug
Reporter: Jinmei Liao






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

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

[Jinmei Liao (JIRA)]

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

Jinmei Liao updated GEODE-5000:
---
Affects Version/s: 1.4.0

> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Priority: Major
>




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

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

[Jinmei Liao (JIRA)]

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

Jinmei Liao reassigned GEODE-5000:
--

Assignee: Jinmei Liao

> When initializing a client cache, we don't need to request/apply cluster 
> configuration
> --
>
> Key: GEODE-5000
> URL: https://issues.apache.org/jira/browse/GEODE-5000
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>




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

[jira] [Updated] (GEODE-4518) make DSCODE an enum

[ASF GitHub Bot (JIRA)]

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

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

> make DSCODE an enum
> ---
>
> Key: GEODE-4518
> URL: https://issues.apache.org/jira/browse/GEODE-4518
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: Starter, pull-request-available
>
> From DSCODE:
> {color:#629755}/**
> {color}{color:#629755} * An interface that contains a bunch of static final 
> values used for the implementation of
> {color}{color:#629755} * {{color}{color:#629755}@link 
> {color}{color:#629755}DataSerializer}. It is basically an Enum and could be 
> changed to one once we drop 1.4. The
> {color}{color:#629755} * allowed range of these codes is -128..127 inclusive 
> (i.e. byte).
> {color}{color:#629755} *
> {color}{color:#629755} * {color}{color:#629755}@since 
> {color}{color:#629755}GemFire 5.7{color}
> {color:#33}Since we no longer support Java 4, let's make this an 
> enum.{color}



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

[jira] [Updated] (GEODE-4999) support for tcserver requires specific tomcat 8 and 85 directories

[ASF GitHub Bot (JIRA)]

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

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

> support for tcserver requires specific tomcat 8 and 85 directories
> --
>
> Key: GEODE-4999
> URL: https://issues.apache.org/jira/browse/GEODE-4999
> Project: Geode
>  Issue Type: Bug
>  Components: http session
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>
> currently we support tomcat 7 and tomcat 8 along with tcserver.  For tcserver 
> to move to geode, it requires specific tomcat 85 directories to be created.  
> Currently tomcat 8 modules do support 8.5 and above but tcserver requires 
> explicit artifacts to be created



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

[jira] [Updated] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Kenneth Howe (JIRA)]

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

Kenneth Howe updated GEODE-3003:

Fix Version/s: 1.5.0

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, membership
>Reporter: Anton Mironenko
>Assignee: Kenneth Howe
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: 20170522-geode-klyazma.zip, 20170522-geode-vyazma.zip, 
> 20170608-host1-locator0.zip, 20170608-host2-locator0.zip, geode-host1.zip, 
> geode-host2.zip, readme.txt
>
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-3) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on host1, then on host2. See 
> that this cluster start is successful.
> 3) kill locator and server processes first on host1, then on host2
>   kill [locator-PID] [server-PID]
> 4) run 
>   ./start-locator.sh; ./start-server.sh 
> on host1, then on host2. Make sure the interval between this command run on 
> two hosts is less than 1 second!
> 5) see via gfsh that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with the error 
>   "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data.".



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

[jira] [Resolved] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Kenneth Howe (JIRA)]

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

Kenneth Howe resolved GEODE-3003.
-
Resolution: Fixed

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, membership
>Reporter: Anton Mironenko
>Assignee: Kenneth Howe
>Priority: Major
> Attachments: 20170522-geode-klyazma.zip, 20170522-geode-vyazma.zip, 
> 20170608-host1-locator0.zip, 20170608-host2-locator0.zip, geode-host1.zip, 
> geode-host2.zip, readme.txt
>
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-3) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on host1, then on host2. See 
> that this cluster start is successful.
> 3) kill locator and server processes first on host1, then on host2
>   kill [locator-PID] [server-PID]
> 4) run 
>   ./start-locator.sh; ./start-server.sh 
> on host1, then on host2. Make sure the interval between this command run on 
> two hosts is less than 1 second!
> 5) see via gfsh that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with the error 
>   "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data.".



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

[jira] [Commented] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Kenneth Howe (JIRA)]

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

Kenneth Howe commented on GEODE-3003:
-

I reproduced the problem in Geode v1.1.0 using the steps noted above. Then 
using the same steps verified that it is fixed in Geode v1.5.0.

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, membership
>Reporter: Anton Mironenko
>Assignee: Kenneth Howe
>Priority: Major
> Attachments: 20170522-geode-klyazma.zip, 20170522-geode-vyazma.zip, 
> 20170608-host1-locator0.zip, 20170608-host2-locator0.zip, geode-host1.zip, 
> geode-host2.zip, readme.txt
>
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-3) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on host1, then on host2. See 
> that this cluster start is successful.
> 3) kill locator and server processes first on host1, then on host2
>   kill [locator-PID] [server-PID]
> 4) run 
>   ./start-locator.sh; ./start-server.sh 
> on host1, then on host2. Make sure the interval between this command run on 
> two hosts is less than 1 second!
> 5) see via gfsh that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with the error 
>   "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data.".



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

[jira] [Assigned] (GEODE-4518) make DSCODE an enum

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4518:


Assignee: Michael Dodge

> make DSCODE an enum
> ---
>
> Key: GEODE-4518
> URL: https://issues.apache.org/jira/browse/GEODE-4518
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: Starter
>
> From DSCODE:
> {color:#629755}/**
> {color}{color:#629755} * An interface that contains a bunch of static final 
> values used for the implementation of
> {color}{color:#629755} * {{color}{color:#629755}@link 
> {color}{color:#629755}DataSerializer}. It is basically an Enum and could be 
> changed to one once we drop 1.4. The
> {color}{color:#629755} * allowed range of these codes is -128..127 inclusive 
> (i.e. byte).
> {color}{color:#629755} *
> {color}{color:#629755} * {color}{color:#629755}@since 
> {color}{color:#629755}GemFire 5.7{color}
> {color:#33}Since we no longer support Java 4, let's make this an 
> enum.{color}



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

[jira] [Resolved] (GEODE-4644) Remove static ClientSideHandshake.deltaEnabledOnServer

[Michael Dodge (JIRA)]

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

Michael Dodge resolved GEODE-4644.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Remove static ClientSideHandshake.deltaEnabledOnServer
> --
>
> Key: GEODE-4644
> URL: https://issues.apache.org/jira/browse/GEODE-4644
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This static is used by the cache



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

[jira] [Commented] (GEODE-4644) Remove static ClientSideHandshake.deltaEnabledOnServer

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4644:


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

GEODE-4644: Move static to member of distributed system. (#1734)



> Remove static ClientSideHandshake.deltaEnabledOnServer
> --
>
> Key: GEODE-4644
> URL: https://issues.apache.org/jira/browse/GEODE-4644
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This static is used by the cache



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

[jira] [Assigned] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Kenneth Howe (JIRA)]

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

Kenneth Howe reassigned GEODE-3003:
---

Assignee: Kenneth Howe  (was: Jinmei Liao)

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, membership
>Reporter: Anton Mironenko
>Assignee: Kenneth Howe
>Priority: Major
> Attachments: 20170522-geode-klyazma.zip, 20170522-geode-vyazma.zip, 
> 20170608-host1-locator0.zip, 20170608-host2-locator0.zip, geode-host1.zip, 
> geode-host2.zip, readme.txt
>
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-3) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on host1, then on host2. See 
> that this cluster start is successful.
> 3) kill locator and server processes first on host1, then on host2
>   kill [locator-PID] [server-PID]
> 4) run 
>   ./start-locator.sh; ./start-server.sh 
> on host1, then on host2. Make sure the interval between this command run on 
> two hosts is less than 1 second!
> 5) see via gfsh that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with the error 
>   "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data.".



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

[jira] [Commented] (GEODE-4456) Remove singleton calls from all tests in org.apache.geode.internal.cache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4456:


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

GEODE-4456: Remove singleton calls from all tests in 
org.apache.geode.internal.cache

* removed InternalDistributedSystem.getConnectedInstance call from 
TombstoneCreationJUnitTest
* Also the cache is now created in a @Before method and uses non-deprecated 
methods to create it.
* removed InternalDistributedSystem.getConnectedInstance call from 
ClientServerTransactionDUnitTest
* removed getAnyInstance calls in GridAdvisorDUnitTest


> Remove singleton calls from all tests in org.apache.geode.internal.cache
> 
>
> Key: GEODE-4456
> URL: https://issues.apache.org/jira/browse/GEODE-4456
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions, tests, transactions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> These tests in org.apache.geode.internal.cache invoke singleton getters.
> CacheFactory.getAnyInstance():
> * Bug37241DUnitTest
> * CommitFunction
> * GridAdvisorDUnitTest
> * NestedTransactionFunction
> * RollbackFunction
> * SingleHopStatsDUnitTest
> * UpdateVersionDUnitTest
> CacheFactory.getExisting(DistributedSystem):
> * PartitionedRegionTestHelper
> GemFireCacheImpl.getInstance():
> * DiskRegRecoveryJUnitTest
> * FixedPRSinglehopDUnitTest
> * NetSearchMessagingDUnitTest
> * RemoteCQTransactionDUnitTest
> * RemoteTransactionDUnitTest
> * SystemFailureDUnitTest
> GemFireCacheImpl.setInstanceForTests(GemFireCacheImpl):
> * ColocationHelperTest
> InternalDistributedSystem.getAnyInstance():
> * ClientServerTransactionDUnitTest
> * GridAdvisorDUnitTest
> InternalDistributedSystem.getConnectedInstance():
> * ClientServerTransactionDUnitTest
> * TombstoneCreationJUnitTest



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

[jira] [Created] (GEODE-4999) support for tcserver requires specific tomcat 8 and 85 directories

[Jason Huynh (JIRA)]

Jason Huynh created GEODE-4999:
--

 Summary: support for tcserver requires specific tomcat 8 and 85 
directories
 Key: GEODE-4999
 URL: https://issues.apache.org/jira/browse/GEODE-4999
 Project: Geode
  Issue Type: Bug
  Components: http session
Reporter: Jason Huynh


currently we support tomcat 7 and tomcat 8 along with tcserver.  For tcserver 
to move to geode, it requires specific tomcat 85 directories to be created.  
Currently tomcat 8 modules do support 8.5 and above but tcserver requires 
explicit artifacts to be created



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

[jira] [Assigned] (GEODE-4999) support for tcserver requires specific tomcat 8 and 85 directories

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-4999:
--

Assignee: Jason Huynh

> support for tcserver requires specific tomcat 8 and 85 directories
> --
>
> Key: GEODE-4999
> URL: https://issues.apache.org/jira/browse/GEODE-4999
> Project: Geode
>  Issue Type: Bug
>  Components: http session
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> currently we support tomcat 7 and tomcat 8 along with tcserver.  For tcserver 
> to move to geode, it requires specific tomcat 85 directories to be created.  
> Currently tomcat 8 modules do support 8.5 and above but tcserver requires 
> explicit artifacts to be created



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

[jira] [Created] (GEODE-4998) Document how to use Geode to preload data into a region

[Karen Smoler Miller (JIRA)]

Karen Smoler Miller created GEODE-4998:
--

 Summary: Document how to use Geode to preload data into a region
 Key: GEODE-4998
 URL: https://issues.apache.org/jira/browse/GEODE-4998
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Describe what it means to preload a Geode region.

Describe the code/interface (cache loader)  that a developer must implement.

Document how to configure and/or deploy the cache loader.



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

[jira] [Created] (GEODE-4997) Document how to use Geode as an inline cache

[Karen Smoler Miller (JIRA)]

Karen Smoler Miller created GEODE-4997:
--

 Summary: Document how to use Geode as an inline cache
 Key: GEODE-4997
 URL: https://issues.apache.org/jira/browse/GEODE-4997
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Describe what an inline cache is and how a Geode region together with deployed 
code on a server can form an inline cache.

Describe the code/interface that a developer must implement.

Document how to configure and/or deploy the code.



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

[jira] [Resolved] (GEODE-4984) Add new subsection in docs: use cases

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller resolved GEODE-4984.

   Resolution: Fixed
Fix Version/s: 1.6.0

> Add new subsection in docs: use cases
> -
>
> Key: GEODE-4984
> URL: https://issues.apache.org/jira/browse/GEODE-4984
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Our documentation is missing a place to present, discuss, and describe the 
> implementation of various design patterns.  For example, how would a 
> developer use Geode to implement an inline cache? How would a developer use 
> Geode to pre-load a set of region entries?  There are also a large number of 
> design patterns that increase fault tolerance by working over WAN.
> Introduce a new manual section called Use Cases, and add introductory 
> sentences an placeholders where we can fill in more details (over time).



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

[jira] [Resolved] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

[Fred Krone (JIRA)]

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

Fred Krone resolved GEODE-4833.
---
Resolution: Fixed

> JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
> 
>
> Key: GEODE-4833
> URL: https://issues.apache.org/jira/browse/GEODE-4833
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method 
> PreparedStatement.setObject with a value of "null" if the pdx field contains 
> "null".
> This will work with jdbc drivers that support sending "non-typed Null" to the 
> backend database.
> But some drivers do not support this and these puts will fail with a 
> SQLException.
> For portability the jdbc connector should be changed to not pass "null" to 
> setObject without a type.
>  



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

[jira] [Commented] (GEODE-4984) Add new subsection in docs: use cases

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4984:


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

GEODE-4984 Add new Use Cases section to docs (#1733)

- add the start of a subsection on using Geode as an inline cache

> Add new subsection in docs: use cases
> -
>
> Key: GEODE-4984
> URL: https://issues.apache.org/jira/browse/GEODE-4984
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Our documentation is missing a place to present, discuss, and describe the 
> implementation of various design patterns.  For example, how would a 
> developer use Geode to implement an inline cache? How would a developer use 
> Geode to pre-load a set of region entries?  There are also a large number of 
> design patterns that increase fault tolerance by working over WAN.
> Introduce a new manual section called Use Cases, and add introductory 
> sentences an placeholders where we can fill in more details (over time).



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

[jira] [Created] (GEODE-4996) NullPointerException during HAEventWrapper serialization

[Barry Oglesby (JIRA)]

Barry Oglesby created GEODE-4996:


 Summary: NullPointerException during HAEventWrapper serialization
 Key: GEODE-4996
 URL: https://issues.apache.org/jira/browse/GEODE-4996
 Project: Geode
  Issue Type: Improvement
  Components: client queues
Reporter: Barry Oglesby


HAEventWrapper toData can throw NPE during HARegion GII.
{noformat}
java.lang.NullPointerException
at 
org.apache.geode.internal.cache.tier.sockets.HAEventWrapper.toData(HAEventWrapper.java:287)
at 
org.apache.geode.internal.InternalDataSerializer.invokeToData(InternalDataSerializer.java:2425)
at 
org.apache.geode.internal.InternalDataSerializer.writeDSFID(InternalDataSerializer.java:1533)
at 
org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2193)
at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2936)
at org.apache.geode.internal.util.BlobHelper.serializeTo(BlobHelper.java:66)
at 
org.apache.geode.internal.cache.entries.AbstractRegionEntry.fillInValue(AbstractRegionEntry.java:411)
at 
org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.chunkEntries(InitialImageOperation.java:1982)
at 
org.apache.geode.internal.cache.InitialImageOperation$RequestImageMessage.process(InitialImageOperation.java:1750)
at 
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
at 
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at 
org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1118)
at 
org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
at 
org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:830)
at java.lang.Thread.run(Thread.java:748)

{noformat}



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

[jira] [Updated] (GEODE-4995) ClusterStartupRule is inefficient when shutting down the cluster

[ASF GitHub Bot (JIRA)]

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

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

> ClusterStartupRule is inefficient when shutting down the cluster
> 
>
> Key: GEODE-4995
> URL: https://issues.apache.org/jira/browse/GEODE-4995
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>
> ClusterStartupRule is often used to create a locator and some number of 
> servers, ignoring the locator started by DUnitLauncher.  This is inefficient 
> but it's probably intentional and can be avoided by configuring the servers 
> to use the DUnitLauncher's locator.
> However, when shutting down the cluster it is managing ClusterStartupRule 
> shuts down the VMs in order starting with vm0.  If vm0 happens to be the 
> membership coordinator this causes membership to create a new coordinator in 
> vm1 and causes distributed lock grantor state to also fail over to vm1.  Then 
> vm1 is shut down, causing services to fail over to vm2. Etc.
> ClusterStartupRule should be modified to shut down non-locator VMs first and 
> then shut down locator VMs.



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

[jira] [Commented] (GEODE-4983) PluckStacks is no longer detecting idle executors and weeding them out

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4983:


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

GEODE-4983 PluckStacks is no longer detecting idle executors and weeding them 
out

fixing the sort order of thread dumps


> PluckStacks is no longer detecting idle executors and weeding them out
> --
>
> Key: GEODE-4983
> URL: https://issues.apache.org/jira/browse/GEODE-4983
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> The PluckStacks utility is supposed to detect idle threads in stack dumps and 
> ignore them but it is no longer doing so.  It failed with java 8 build 161.



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

[jira] [Assigned] (GEODE-4849) Internal REST endpoints in geode-core can be obfuscated by those in geode-web-api

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4849:


Assignee: Michael Dodge

> Internal REST endpoints in geode-core can be obfuscated by those in 
> geode-web-api
> -
>
> Key: GEODE-4849
> URL: https://issues.apache.org/jira/browse/GEODE-4849
> Project: Geode
>  Issue Type: Bug
>  Components: rest (dev)
>Reporter: Patrick Rhomberg
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> For instance, a GET to {{http://localhost:8080/geode/v1/version}} is 
> returning 
> {noformat}
> {
> "cause": "The Region identified by name (version) could not be found!"
> }
> {noformat}
> because it is matching the endpoint in {{PdxBasedCrudController}}:
> {noformat}
>   @RequestMapping(method = RequestMethod.GET, value = "/{region}",
>   produces = MediaType.APPLICATION_JSON_UTF8_VALUE)
> {noformat}
> rather than the intended endpoint in {{ShellCommandsController}}:
> {noformat}
>   @RequestMapping(method = RequestMethod.GET, value = "/version")
> {noformat}
> Similar errors exist for {{/mbean}}, {{/regions}}, {{/indexes}}, and 
> {{/management}}.



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

[jira] [Resolved] (GEODE-4911) Remove DataSerializer.TRACE_SERIALIZABLE

[Michael Dodge (JIRA)]

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

Michael Dodge resolved GEODE-4911.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

Marked it as deprecated for removal in the next major release.

> Remove DataSerializer.TRACE_SERIALIZABLE
> 
>
> Key: GEODE-4911
> URL: https://issues.apache.org/jira/browse/GEODE-4911
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available, starter
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> This is a boolean that's set from a system property. Since it's never used, 
> we should probably delete it.



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

[jira] [Assigned] (GEODE-3860) DistributionLocatorId is in the AnalyzeSerializablesJUnitTest excludedClasses file but should not be

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-3860:


Assignee: (was: Michael Dodge)

> DistributionLocatorId is in the AnalyzeSerializablesJUnitTest excludedClasses 
> file but should not be
> 
>
> Key: GEODE-3860
> URL: https://issues.apache.org/jira/browse/GEODE-3860
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Priority: Major
>
> This class is serialized in WAN location service messages and needs to be in 
> sanctionedSerializables.txt, not in the excludedClasses.txt file.  This needs 
> to be done to track changes in its serialized form that could break backward 
> compatibility.



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

[jira] [Updated] (GEODE-4989) CQ reply message fromData method deserializes query results

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-4989:

Fix Version/s: (was: 1.5.0)
   1.6.0

> CQ reply message fromData method deserializes query results
> ---
>
> Key: GEODE-4989
> URL: https://issues.apache.org/jira/browse/GEODE-4989
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Recent changes in DataSerializableFixedID serialization have left CQ reply 
> message handling in a bad state.  When results are read they are deserialized 
> into POJOs and this can cause queries to hang if the domain classes aren't 
> available in the server.  Even if they are it will hit performance because 
> the objects are completely deserialized and then have to be re-serialized to 
> be sent to clients.
> If the classes aren't available an exception like this will be thrown:
> {noformat}
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage
>  .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2703)
>   at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3543)
>   at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1827)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1688)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.cache.query.internal.CqEntry .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2862)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readUserObject(InternalDataSerializer.java:2817)
>   at 
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage.fromData(StreamingOperation.java:559)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 8 more
> Caused by: org.apache.geode.pdx.PdxSerializationException: Could not create 
> an instance of a class util.PdxVersionedQueryObject
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:239)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.basicGetObject(PdxReaderImpl.java:687)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.getObject(PdxReaderImpl.java:682)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readPdxSerializable(InternalDataSerializer.java:3226)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:3031)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.cache.query.internal.CqEntry.fromData(CqEntry.java:95)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 14 more
> Caused by: java.lang.ClassNotFoundException: util.PdxVersionedQueryObject
>   at 
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
>   at 
> org.apache.geode.internal.InternalDataSerializer.getCachedClass(InternalDataSerializer.java:3870)
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:235)
>   ... 21 more
> {noformat}



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

[jira] [Updated] (GEODE-4644) Remove static ClientSideHandshake.deltaEnabledOnServer

[ASF GitHub Bot (JIRA)]

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

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

> Remove static ClientSideHandshake.deltaEnabledOnServer
> --
>
> Key: GEODE-4644
> URL: https://issues.apache.org/jira/browse/GEODE-4644
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>
> This static is used by the cache



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

[jira] [Updated] (GEODE-4984) Add new subsection in docs: use cases

[ASF GitHub Bot (JIRA)]

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

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

> Add new subsection in docs: use cases
> -
>
> Key: GEODE-4984
> URL: https://issues.apache.org/jira/browse/GEODE-4984
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
>
> Our documentation is missing a place to present, discuss, and describe the 
> implementation of various design patterns.  For example, how would a 
> developer use Geode to implement an inline cache? How would a developer use 
> Geode to pre-load a set of region entries?  There are also a large number of 
> design patterns that increase fault tolerance by working over WAN.
> Introduce a new manual section called Use Cases, and add introductory 
> sentences an placeholders where we can fill in more details (over time).



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

[jira] [Resolved] (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 resolved GEODE-4970.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> 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
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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-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=16425896#comment-16425896
 ] 

ASF subversion and git services commented on GEODE-4970:


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

GEODE-4970: Overhaul and split up PartitionedRegionQueryDUnitTest (#1718)

Rename:
* PartitionedRegionQueryDUnitTest -> PRQueryDistributedTest

Extract the following tests from PRQueryDistributedTest:
* PRQueryWithIndexAndPdxDistributedTest
* PRQueryWithIndexDistributedTest
* PRQueryWithOrderByDistributedTest
* PRQueryWithPdxDuringRebalanceRegressionTest
* PRWithIndexAfterRebalanceRegressionTest

Introduce and use:
* InternalClientCache interface
* ClientCacheRule

> 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
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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-4893) import cluster configuration command shuts down the existing servers

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4893:


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

GEODE-4893: add test to make sure the callbacks will be loaded correctly (#1729)



> import cluster configuration command shuts down the existing servers
> 
>
> Key: GEODE-4893
> URL: https://issues.apache.org/jira/browse/GEODE-4893
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, docs, gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> `import cluster-configuration --zip-file-name=...` in a cluster which has 
> locator and servers (Server has no application regions defined yet). the 
> server is shutdown without any message in the logs as to why the server was 
> shutdown. Gfsh says import was successful.
> On manual restart of the server I can see that the config was actually 
> imported successfully.
>  
> We had added the feature that user can do an {{import cluster-configuration 
> --zip-file-name=...}} without shutting down the vanilla servers, and the 
> servers cache would just bounce. We should
>  # make sure the server's cache is completely empty. i.e. not just without 
> regions, should not have any other entities like async event queue, disk 
> stores etc.
>  # make sure after the import, the servers are not shut down.
> We have ClusterConfigImportDUnitTest.testImportWithRunningServer to test this 
> scenaio, in the Dunit environment, the servers are not shut down after the 
> import. We will need to write a similar acceptance tests to expose the 
> problem.



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

[jira] [Assigned] (GEODE-4644) Remove static ClientSideHandshake.deltaEnabledOnServer

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4644:


Assignee: Michael Dodge

> Remove static ClientSideHandshake.deltaEnabledOnServer
> --
>
> Key: GEODE-4644
> URL: https://issues.apache.org/jira/browse/GEODE-4644
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>
> This static is used by the cache



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

[jira] [Resolved] (GEODE-4989) CQ reply message fromData method deserializes query results

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-4989.
-
   Resolution: Fixed
Fix Version/s: 1.5.0

> CQ reply message fromData method deserializes query results
> ---
>
> Key: GEODE-4989
> URL: https://issues.apache.org/jira/browse/GEODE-4989
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Recent changes in DataSerializableFixedID serialization have left CQ reply 
> message handling in a bad state.  When results are read they are deserialized 
> into POJOs and this can cause queries to hang if the domain classes aren't 
> available in the server.  Even if they are it will hit performance because 
> the objects are completely deserialized and then have to be re-serialized to 
> be sent to clients.
> If the classes aren't available an exception like this will be thrown:
> {noformat}
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage
>  .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2703)
>   at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3543)
>   at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1827)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1688)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.cache.query.internal.CqEntry .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2862)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readUserObject(InternalDataSerializer.java:2817)
>   at 
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage.fromData(StreamingOperation.java:559)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 8 more
> Caused by: org.apache.geode.pdx.PdxSerializationException: Could not create 
> an instance of a class util.PdxVersionedQueryObject
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:239)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.basicGetObject(PdxReaderImpl.java:687)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.getObject(PdxReaderImpl.java:682)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readPdxSerializable(InternalDataSerializer.java:3226)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:3031)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.cache.query.internal.CqEntry.fromData(CqEntry.java:95)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 14 more
> Caused by: java.lang.ClassNotFoundException: util.PdxVersionedQueryObject
>   at 
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
>   at 
> org.apache.geode.internal.InternalDataSerializer.getCachedClass(InternalDataSerializer.java:3870)
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:235)
>   ... 21 more
> {noformat}



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

[jira] [Commented] (GEODE-4989) CQ reply message fromData method deserializes query results

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4989:


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

GEODE-4989 CQ reply message fromData method deserializes query results

CqEntry was using DataSerializer.readObject() to read the entry's value
instead of InternalDataSerializer.readUserObject().  The latter is needed
to respect the setting of pdx-read-serialized in the query service's
StreamingReplyMessage.

This closes #1719


> CQ reply message fromData method deserializes query results
> ---
>
> Key: GEODE-4989
> URL: https://issues.apache.org/jira/browse/GEODE-4989
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Recent changes in DataSerializableFixedID serialization have left CQ reply 
> message handling in a bad state.  When results are read they are deserialized 
> into POJOs and this can cause queries to hang if the domain classes aren't 
> available in the server.  Even if they are it will hit performance because 
> the objects are completely deserialized and then have to be re-serialized to 
> be sent to clients.
> If the classes aren't available an exception like this will be thrown:
> {noformat}
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage
>  .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2703)
>   at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3543)
>   at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1827)
>   at org.apache.geode.internal.tcp.Connection.run(Connection.java:1688)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.cache.query.internal.CqEntry .
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2505)
>   at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2862)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readUserObject(InternalDataSerializer.java:2817)
>   at 
> org.apache.geode.distributed.internal.streaming.StreamingOperation$StreamingReplyMessage.fromData(StreamingOperation.java:559)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 8 more
> Caused by: org.apache.geode.pdx.PdxSerializationException: Could not create 
> an instance of a class util.PdxVersionedQueryObject
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:239)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.basicGetObject(PdxReaderImpl.java:687)
>   at 
> org.apache.geode.pdx.internal.PdxReaderImpl.getObject(PdxReaderImpl.java:682)
>   at 
> org.apache.geode.internal.InternalDataSerializer.readPdxSerializable(InternalDataSerializer.java:3226)
>   at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:3031)
>   at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
>   at 
> org.apache.geode.cache.query.internal.CqEntry.fromData(CqEntry.java:95)
>   at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2494)
>   ... 14 more
> Caused by: java.lang.ClassNotFoundException: util.PdxVersionedQueryObject
>   at 
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
>   at 
> org.apache.geode.internal.InternalDataSerializer.getCachedClass(InternalDataSerializer.java:3870)
>   at org.apache.geode.pdx.internal.PdxType.getPdxClass(PdxType.java:235)
>   ... 21 more
> 

[jira] [Resolved] (GEODE-1884) Users should be able to parse the output of gfsh start command

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-1884.
---
Resolution: Duplicate

> Users should be able to parse the output of gfsh start command
> --
>
> Key: GEODE-1884
> URL: https://issues.apache.org/jira/browse/GEODE-1884
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>
> Geode servers can be started on a ephemeral port and the output does contain 
> the port number on which the server has started to listen, but the output is 
> not parseable for integration tests; example:
> {noformat}
> gfsh>start server --name=serv1 --server-port=0
> Starting a Geode Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1...
> ..
> Server in 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1
>  on 192.168.0.21[57851] as serv1 is currently online.
> Process ID: 19039
> Uptime: 3 seconds
> GemFire Version: 1.0.0-incubating-SNAPSHOT
> Java Version: 1.8.0_45
> Log File: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/serv1/serv1.log
> JVM Arguments: -Dgemfire.default.locators=192.168.0.21[10334] 
> -Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080 
> -Dgemfire.start-dev-rest-api=false -XX:OnOutOfMemoryError=kill -KILL %p 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/sbawaskar/acceptance/incubator-geode/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> {noformat}
> The output of the above command needs to presented as a json so that it can 
> be parsed. We need an additional {{--output-format}} option to the start 
> server command:
> {noformat}
> gfsh start server --server-port=0 --output-format=json
> {noformat}
> which should result in the above output be returned as a json. The bind 
> address and the port should be available as separate elements in the json 
> output.



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

[jira] [Updated] (GEODE-4857) make a public ClusterConfigurationService to retrive/perisist configuration objects

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4857:
--
Fix Version/s: 1.6.0

> make a public ClusterConfigurationService to retrive/perisist configuration 
> objects
> ---
>
> Key: GEODE-4857
> URL: https://issues.apache.org/jira/browse/GEODE-4857
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> # have InternalClusterConfigurationService implement this interface
>  # All the internal commands should still be able to access the 
> InternalClusterConfigService.
>  # Refer to the wiki for the apis: 
> [https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration]
>  # Mark this interface @experimental



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

[jira] [Resolved] (GEODE-4857) make a public ClusterConfigurationService to retrive/perisist configuration objects

[Barbara Pruijn (JIRA)]

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

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

> make a public ClusterConfigurationService to retrive/perisist configuration 
> objects
> ---
>
> Key: GEODE-4857
> URL: https://issues.apache.org/jira/browse/GEODE-4857
> Project: Geode
>  Issue Type: Sub-task
>  Components: configuration
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> # have InternalClusterConfigurationService implement this interface
>  # All the internal commands should still be able to access the 
> InternalClusterConfigService.
>  # Refer to the wiki for the apis: 
> [https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration]
>  # Mark this interface @experimental



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

[jira] [Created] (GEODE-4994) Cleanup compiler warnings with GCC

[Jacob S. Barrett (JIRA)]

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

 Summary: Cleanup compiler warnings with GCC
 Key: GEODE-4994
 URL: https://issues.apache.org/jira/browse/GEODE-4994
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett






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

[jira] [Resolved] (GEODE-4850) Restore default rpath behavior for CMake builds.

[Jacob S. Barrett (JIRA)]

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

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

> Restore default rpath behavior for CMake builds.
> 
>
> Key: GEODE-4850
> URL: https://issues.apache.org/jira/browse/GEODE-4850
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4906) Improve compile times using PCH

[Jacob S. Barrett (JIRA)]

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

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

> Improve compile times using PCH
> ---
>
> Key: GEODE-4906
> URL: https://issues.apache.org/jira/browse/GEODE-4906
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Reduce compile times by using precompiled headers (PCH).
>  



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

[jira] [Resolved] (GEODE-4918) dotnet examples build broken in develop branch

[Jacob S. Barrett (JIRA)]

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

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

> dotnet examples build broken in develop branch
> --
>
> Key: GEODE-4918
> URL: https://issues.apache.org/jira/browse/GEODE-4918
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Blake Bender
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> The CMakeLists.txt files in the dotnet examples do not have the .net target 
> version set to 4.5.2, and are refusing to link against the currently built 
> Apache.Geode.dll which is built against that version.  



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

[jira] [Resolved] (GEODE-4921) New integration test framework

[Jacob S. Barrett (JIRA)]

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

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

> New integration test framework 
> ---
>
> Key: GEODE-4921
> URL: https://issues.apache.org/jira/browse/GEODE-4921
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Should be a single process test suite. Should be debuggable from most IDEs. 
> Should be based on common testing framework. 



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

[jira] [Commented] (GEODE-4911) Remove DataSerializer.TRACE_SERIALIZABLE

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4911:


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

GEODE-4911: Deprecate DataSerializer.TRACE_SERIALIZABLE. (#1722)



> Remove DataSerializer.TRACE_SERIALIZABLE
> 
>
> Key: GEODE-4911
> URL: https://issues.apache.org/jira/browse/GEODE-4911
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Galen O'Sullivan
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available, starter
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> This is a boolean that's set from a system property. Since it's never used, 
> we should probably delete it.



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

[jira] [Resolved] (GEODE-4912) Change DistributedSystem::create to return value type

[Jacob S. Barrett (JIRA)]

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

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

> Change DistributedSystem::create to return value type
> -
>
> Key: GEODE-4912
> URL: https://issues.apache.org/jira/browse/GEODE-4912
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Blake Bender
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4916) Default MSVC++ project can't link agains our library.

[Jacob S. Barrett (JIRA)]

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

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

> Default MSVC++ project can't link agains our library.
> -
>
> Key: GEODE-4916
> URL: https://issues.apache.org/jira/browse/GEODE-4916
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Addison
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
> Attachments: Capture.PNG
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> {code:java}
> 1>-- Build started: Project: foo, Configuration: Debug x64 --
> 1>foo.obj : error LNK2001: unresolved external symbol "private: static 
> unsigned __int64 apache::geode::client::DataOutput::m_highWaterMark" 
> (?m_highWaterMark@DataOutput@client@geode@apache@@0_KA)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableBoolean" 
> (?tStr_CacheableBoolean@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableByte" 
> (?tStr_CacheableByte@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableDouble" 
> (?tStr_CacheableDouble@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableFloat" 
> (?tStr_CacheableFloat@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt16" 
> (?tStr_CacheableInt16@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt32" 
> (?tStr_CacheableInt32@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt64" 
> (?tStr_CacheableInt64@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableCharacter" 
> (?tStr_CacheableCharacter@client@geode@apache@@3QBDB)
> 1>C:\foo\foo\x64\Debug\foo.exe : fatal error LNK1120: 9 unresolved externals
> 1>Done building project "foo.vcxproj" -- FAILED.
> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped 
> =={code}



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

[jira] [Updated] (GEODE-4916) Default MSVC++ project can't link agains our library.

[Jacob S. Barrett (JIRA)]

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

Jacob S. Barrett updated GEODE-4916:

Summary: Default MSVC++ project can't link agains our library.  (was: 
Native Client cpp examples failing due to unexported symbols)

> Default MSVC++ project can't link agains our library.
> -
>
> Key: GEODE-4916
> URL: https://issues.apache.org/jira/browse/GEODE-4916
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Addison
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
> Attachments: Capture.PNG
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> {code:java}
> 1>-- Build started: Project: foo, Configuration: Debug x64 --
> 1>foo.obj : error LNK2001: unresolved external symbol "private: static 
> unsigned __int64 apache::geode::client::DataOutput::m_highWaterMark" 
> (?m_highWaterMark@DataOutput@client@geode@apache@@0_KA)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableBoolean" 
> (?tStr_CacheableBoolean@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableByte" 
> (?tStr_CacheableByte@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableDouble" 
> (?tStr_CacheableDouble@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableFloat" 
> (?tStr_CacheableFloat@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt16" 
> (?tStr_CacheableInt16@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt32" 
> (?tStr_CacheableInt32@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt64" 
> (?tStr_CacheableInt64@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableCharacter" 
> (?tStr_CacheableCharacter@client@geode@apache@@3QBDB)
> 1>C:\foo\foo\x64\Debug\foo.exe : fatal error LNK1120: 9 unresolved externals
> 1>Done building project "foo.vcxproj" -- FAILED.
> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped 
> =={code}



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

[jira] [Commented] (GEODE-4916) Native Client cpp examples failing due to unexported symbols

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4916:


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

GEODE-4916: Fixes compilation errors when including in empty VC++ project. 
(#258)

- Convert to CMake GenerateExportHeader.
- Generates platform specfic export files.
- Remove use of sprintf which caused error on Windows.
- Fixes explicit instantiation export attributes.
- Fixes default visibility.


> Native Client cpp examples failing due to unexported symbols
> 
>
> Key: GEODE-4916
> URL: https://issues.apache.org/jira/browse/GEODE-4916
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Addison
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
> Attachments: Capture.PNG
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> {code:java}
> 1>-- Build started: Project: foo, Configuration: Debug x64 --
> 1>foo.obj : error LNK2001: unresolved external symbol "private: static 
> unsigned __int64 apache::geode::client::DataOutput::m_highWaterMark" 
> (?m_highWaterMark@DataOutput@client@geode@apache@@0_KA)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableBoolean" 
> (?tStr_CacheableBoolean@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableByte" 
> (?tStr_CacheableByte@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableDouble" 
> (?tStr_CacheableDouble@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableFloat" 
> (?tStr_CacheableFloat@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt16" 
> (?tStr_CacheableInt16@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt32" 
> (?tStr_CacheableInt32@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableInt64" 
> (?tStr_CacheableInt64@client@geode@apache@@3QBDB)
> 1>foo.obj : error LNK2001: unresolved external symbol "char const * const 
> apache::geode::client::tStr_CacheableCharacter" 
> (?tStr_CacheableCharacter@client@geode@apache@@3QBDB)
> 1>C:\foo\foo\x64\Debug\foo.exe : fatal error LNK1120: 9 unresolved externals
> 1>Done building project "foo.vcxproj" -- FAILED.
> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped 
> =={code}



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

[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=16425686#comment-16425686
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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] [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=16425684#comment-16425684
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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] [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=16425682#comment-16425682
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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] [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=16425683#comment-16425683
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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] [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=16425687#comment-16425687
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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] [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=16425685#comment-16425685
 ] 

ASF subversion and git services commented on GEODE-4799:


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

Geode 4799: Removing static members from Serializable 

* Cleanup warnings

* Replace GetPdxSerializer

* PDXSerializerRegistry passes test

* PdxTypeMapper moved to TypeRegistry

* Moved PDX to LocalType maps to TypeRegistry.

* Move GetType to TypeRegistry
  Signed-off-by: Ernie Burghardt 

* Put back reference assembly recursive search
  Signed-off-by: Michael Oleske 

*  Add new project for multiple cache testing

* Attempt at test, but server fails to start

*  multi cache test running
   Signed-off-by: Jacob Barrett 

* move RegisterPdxType to TypeRegistry
  Signed-off-by: Michael Oleske 

* Temporary commit to get stuff in the shared repo

* Added a new MultiCache test and
- rolled back to a compilable state

* Made ManagedDelegatesGeneric instance based
- added test for RegisterPdxType

* Remove static from:
- NativeDelegatesGeneric
- DelegateMapGeneric
- BuiltInDelegatesGeneric

* Keeps ManagedTypeToTypeId static.

* Removed static from RegisterTypeGeneric

* Removed cache param from RegisterTypeGeneric since no longer needed

* Removed static from UnregisterTypeGeneric

* Add TypeRegistry files to MakeLists and fixed typo in file name

* Split the integration and unit tests in clicache multcache tests.

* Fixing Travis CI build.

* Remove unneeded files from unittests

* Rename test projects and remove GEODE_ROOT from top cmake file

* Undo .travis.yml change

* Rename to remove MultipleCache prefix

* Remove MultipleCache prefix and
- make test project name configurable and rename test class
- remove Serializable::Clear()
- moved statics used for object creation to TypeRegistry

* GEODE-4799: Fixing compilation issue due to namespacing
  Signed-off-by: Mike Martell 

* GEODE-4799: Removing generated file from source control
  Signed-off-by: Mike Martell 

* GEODE-4799: First set of PR feedback changes
  Signed-off-by: Ryan McMahon 

* Changes:
- test rename
- moved configurable bits to a separate file

* Added packages.config to project and add newline at the end of some files.

* Remove commented out code

* GEODE-4799: Adding missing GeodeServer.cs file

* GEODE-4799: GeodeServer.cs was in wrong location
  Signed-off-by: Mike Martell 

* GEODE-4799: Fix to use proper relative nuget packages

* Removed bad ignore line


> 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-4971) Allow GfshRule to launch a cluster with a different Geode version

[ASF GitHub Bot (JIRA)]

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

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

> 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
>  Labels: pull-request-available
>
> 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] [Updated] (GEODE-4990) Race Condition When Using Cluster Configuration Service

[ASF GitHub Bot (JIRA)]

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

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

> Race Condition When Using Cluster Configuration Service
> ---
>
> Key: GEODE-4990
> URL: https://issues.apache.org/jira/browse/GEODE-4990
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, locator
>Affects Versions: 1.4.0
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
>  Labels: pull-request-available
>
> There's a small window of time on which the locator 
> ({{enable-cluster-configuration=true}}) is receiving TCP requests from 
> starting up servers ({{use-cluster-configuration=true}}) but the cluster 
> configuration service is not yet fully loaded, because of this the servers 
> fail to startup and throw the following exception:
> {noformat}
> Exception in thread "main" org.apache.geode.cache.execute.FunctionException: 
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.getResult(FunctionStreamingResultCollector.java:232)
>   at 
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:285)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1036)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:835)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:775)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:764)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
>   at 
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
>   at 
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:844)
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:762)
>   at 
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:692)
>   at 
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:226)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The logs from the locator, when using {{log-level=fine}} show the following:
> {noformat}
> [fine 2018/04/03 15:24:40.501 IST locator1  
> tid=0x51] Exception occurred on remote member while executing Function: 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction
> java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>