date:20170906

[jira] [Resolved] (GEODE-3568) User can set a LuceneSerializer through the Java API

2017-09-06 Thread xiaojian zhou (JIRA)


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

xiaojian zhou resolved GEODE-3568.
--
   Resolution: Fixed
Fix Version/s: 1.3.0

> User can set a LuceneSerializer through the  Java API
> -
>
> Key: GEODE-3568
> URL: https://issues.apache.org/jira/browse/GEODE-3568
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
> Fix For: 1.3.0
>
>
> Need a java API to specify user's LuceneSerializer. The documents returned by 
> the LuceneSerializer are stored in the index.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3568) User can set a LuceneSerializer through the Java API

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3568:


Commit 51b13ab96d95af6d72ea2921ce575e8f4ecc97d7 in geode's branch 
refs/heads/develop from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=51b13ab ]

GEODE-3568: User can set a LuceneSerializer through the Java API

This closes #760


> User can set a LuceneSerializer through the  Java API
> -
>
> Key: GEODE-3568
> URL: https://issues.apache.org/jira/browse/GEODE-3568
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>
> Need a java API to specify user's LuceneSerializer. The documents returned by 
> the LuceneSerializer are stored in the index.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3082) Client Health Monitor should be able to manage new protocol client connections

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3082:


Commit e7ca79659a80134a780b426aedc843551b276a84 in geode's branch 
refs/heads/feature/GEODE-3082 from [~amurmann]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e7ca796 ]

GEODE-3082 Integrated GenericProtocolServerConnection with ClientHealthMonitor.

1. Now GenericProtocolServerConnection creates ClientProxyMembershipId.
2. added test where CHM closes the connection.
3. added test where CHM doesn't close the connection

Signed-off-by: Hitesh Khamesra 


> Client Health Monitor should be able to manage new protocol client connections
> --
>
> Key: GEODE-3082
> URL: https://issues.apache.org/jira/browse/GEODE-3082
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>
> As a user of a Geode grid, I need the Client Health Monitor to effectively 
> manage my client connections, perhaps removing unresponsive clients 
> (depending on my config).  
> Ensure new protocol connections are managed correctly by Client Health 
> Monitor.
> Specifically:
> {{ClientHealthMonitor}} keeps track of {{ServerConnection}}s, makes sure that 
> they are healthy, and sometimes kills them. Make sure that 
> {{NewClientServerConnection}} registers correctly with 
> {{ClientHealthMonitor}} and unregisters correctly when we shutdown. Make sure 
> that we let it manage us correctly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3517) Variable-ize product version and name in client user guide

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3517:


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

GEODE-3517 Variable-ize product version and name in client user guide


> Variable-ize product version and name in client user guide
> --
>
> Key: GEODE-3517
> URL: https://issues.apache.org/jira/browse/GEODE-3517
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
> Fix For: 1.3.0
>
>
> Same as main task, but apply the change to the geode-native docs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3568) User can set a LuceneSerializer through the Java API

2017-09-06 Thread xiaojian zhou (JIRA)

xiaojian zhou created GEODE-3568:


 Summary: User can set a LuceneSerializer through the  Java API
 Key: GEODE-3568
 URL: https://issues.apache.org/jira/browse/GEODE-3568
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: xiaojian zhou


Need a java API to specify user's LuceneSerializer. The documents returned by 
the LuceneSerializer are stored in the index.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEODE-3568) User can set a LuceneSerializer through the Java API

2017-09-06 Thread xiaojian zhou (JIRA)


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

xiaojian zhou reassigned GEODE-3568:


Assignee: xiaojian zhou

> User can set a LuceneSerializer through the  Java API
> -
>
> Key: GEODE-3568
> URL: https://issues.apache.org/jira/browse/GEODE-3568
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>
> Need a java API to specify user's LuceneSerializer. The documents returned by 
> the LuceneSerializer are stored in the index.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

2017-09-06 Thread Udo Kohlmeyer (JIRA)


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

Udo Kohlmeyer updated GEODE-3567:
-
Description: 
When running the following steps, ends up causing the `export config` command 
to list multiple `` entries to be created in the exported 
`cache.xml`

{code}
start locator --name=locator --enable-cluster-configuration=true 
--J=-Dgemfire.hostname-for-clients=bob
start server --name=server --use-cluster-configuration=true --server-port=0 
--hostname-for-clients=bob3
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export cluster-configuration --zip-file-name=./backup1.zip
export config --dir=./serversBack1
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack2
create disk-store --name=diskstore1 --dir=./ds1
create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
export cluster-configuration --zip-file-name=./backup2.zip
export config --dir=./serversBack3
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack4
{code}
Extract from serversBack4 exported cache.xml
{code}
http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://geode.apache.org/schema/cache; 
xsi:schemaLocation="http://geode.apache.org/schema/cache 
http://geode.apache.org/schema/cache/cache-1.0.xsd; version="1.0" 
is-server="true">
  
  
{code}

  was:
When running the following steps, ends up causing the `export config` command 
to list multiple `` entries to be created in the exported 
`cache.xml`

{code}
start locator --name=locator --enable-cluster-configuration=true 
--J=-Dgemfire.hostname-for-clients=bob
start server --name=server --use-cluster-configuration=true --server-port=0 
--hostname-for-clients=bob3
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export cluster-configuration --zip-file-name=./backup1.zip
export config --dir=./serversBack1
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack2
create disk-store --name=diskstore1 --dir=./ds1
create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
export cluster-configuration --zip-file-name=./backup2.zip
export config --dir=./serversBack3
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack4
{code}
{code}
http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://geode.apache.org/schema/cache; 
xsi:schemaLocation="http://geode.apache.org/schema/cache 
http://geode.apache.org/schema/cache/cache-1.0.xsd; version="1.0" 
is-server="true">
  
  
{code}


> Exporting configuration from GFSH causes multiple cacheservers to be listed
> ---
>
> Key: GEODE-3567
> URL: https://issues.apache.org/jira/browse/GEODE-3567
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.2.0
>Reporter: Udo Kohlmeyer
>
> When running the following steps, ends up causing the `export config` command 
> to list multiple `` entries to be created in the exported 
> `cache.xml`
> {code}
> start locator --name=locator --enable-cluster-configuration=true 
> --J=-Dgemfire.hostname-for-clients=bob
> start server --name=server --use-cluster-configuration=true --server-port=0 
> --hostname-for-clients=bob3
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export cluster-configuration --zip-file-name=./backup1.zip
> export config --dir=./serversBack1
> stop server --name=server2
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export config --dir=./serversBack2
> create disk-store --name=diskstore1 --dir=./ds1
> create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
> --disk-store=diskstore1
> create region --name=TestRegion

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

2017-09-06 Thread Udo Kohlmeyer (JIRA)


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

Udo Kohlmeyer updated GEODE-3567:
-
Description: 
When running the following steps, ends up causing the `export config` command 
to list multiple `` entries to be created in the exported 
`cache.xml`

{code}
start locator --name=locator --enable-cluster-configuration=true 
--J=-Dgemfire.hostname-for-clients=bob
start server --name=server --use-cluster-configuration=true --server-port=0 
--hostname-for-clients=bob3
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export cluster-configuration --zip-file-name=./backup1.zip
export config --dir=./serversBack1
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack2
create disk-store --name=diskstore1 --dir=./ds1
create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
export cluster-configuration --zip-file-name=./backup2.zip
export config --dir=./serversBack3
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack4
{code}
{code}
http://www.w3.org/2001/XMLSchema-instance; 
xmlns="http://geode.apache.org/schema/cache; 
xsi:schemaLocation="http://geode.apache.org/schema/cache 
http://geode.apache.org/schema/cache/cache-1.0.xsd; version="1.0" 
is-server="true">
  
  
{code}

  was:
When running the following steps, ends up causing the `export config` command 
to list multiple `` entries to be created in the exported 
`cache.xml`

{code}
start locator --name=locator --enable-cluster-configuration=true 
--J=-Dgemfire.hostname-for-clients=bob
start server --name=server --use-cluster-configuration=true --server-port=0 
--hostname-for-clients=bob3
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export cluster-configuration --zip-file-name=./backup1.zip
export config --dir=./serversBack1
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack2
create disk-store --name=diskstore1 --dir=./ds1
create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
export cluster-configuration --zip-file-name=./backup2.zip
export config --dir=./serversBack3
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack4
{code}


> Exporting configuration from GFSH causes multiple cacheservers to be listed
> ---
>
> Key: GEODE-3567
> URL: https://issues.apache.org/jira/browse/GEODE-3567
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.2.0
>Reporter: Udo Kohlmeyer
>
> When running the following steps, ends up causing the `export config` command 
> to list multiple `` entries to be created in the exported 
> `cache.xml`
> {code}
> start locator --name=locator --enable-cluster-configuration=true 
> --J=-Dgemfire.hostname-for-clients=bob
> start server --name=server --use-cluster-configuration=true --server-port=0 
> --hostname-for-clients=bob3
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export cluster-configuration --zip-file-name=./backup1.zip
> export config --dir=./serversBack1
> stop server --name=server2
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export config --dir=./serversBack2
> create disk-store --name=diskstore1 --dir=./ds1
> create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
> --disk-store=diskstore1
> create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
> --disk-store=diskstore1
> create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
> export cluster-configuration --zip-file-name=./backup2.zip
> export config --dir=./serversBack3
> stop server --name=server2
> start server --name=server2

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

2017-09-06 Thread Udo Kohlmeyer (JIRA)


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

Udo Kohlmeyer updated GEODE-3567:
-
Affects Version/s: 1.0.0-incubating
   1.1.0
   1.2.0

> Exporting configuration from GFSH causes multiple cacheservers to be listed
> ---
>
> Key: GEODE-3567
> URL: https://issues.apache.org/jira/browse/GEODE-3567
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Affects Versions: 1.0.0-incubating, 1.1.0, 1.2.0
>Reporter: Udo Kohlmeyer
>
> When running the following steps, ends up causing the `export config` command 
> to list multiple `` entries to be created in the exported 
> `cache.xml`
> {code}
> start locator --name=locator --enable-cluster-configuration=true 
> --J=-Dgemfire.hostname-for-clients=bob
> start server --name=server --use-cluster-configuration=true --server-port=0 
> --hostname-for-clients=bob3
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export cluster-configuration --zip-file-name=./backup1.zip
> export config --dir=./serversBack1
> stop server --name=server2
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export config --dir=./serversBack2
> create disk-store --name=diskstore1 --dir=./ds1
> create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
> --disk-store=diskstore1
> create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
> --disk-store=diskstore1
> create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
> export cluster-configuration --zip-file-name=./backup2.zip
> export config --dir=./serversBack3
> stop server --name=server2
> start server --name=server2 --use-cluster-configuration=true --server-port=0 
> --group=serverGROUP2 --hostname-for-clients=bob2
> export config --dir=./serversBack4
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

2017-09-06 Thread Udo Kohlmeyer (JIRA)

Udo Kohlmeyer created GEODE-3567:


 Summary: Exporting configuration from GFSH causes multiple 
cacheservers to be listed
 Key: GEODE-3567
 URL: https://issues.apache.org/jira/browse/GEODE-3567
 Project: Geode
  Issue Type: Bug
  Components: configuration, gfsh
Reporter: Udo Kohlmeyer


When running the following steps, ends up causing the `export config` command 
to list multiple `` entries to be created in the exported 
`cache.xml`

{code}
start locator --name=locator --enable-cluster-configuration=true 
--J=-Dgemfire.hostname-for-clients=bob
start server --name=server --use-cluster-configuration=true --server-port=0 
--hostname-for-clients=bob3
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export cluster-configuration --zip-file-name=./backup1.zip
export config --dir=./serversBack1
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack2
create disk-store --name=diskstore1 --dir=./ds1
create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW 
--disk-store=diskstore1
create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2
export cluster-configuration --zip-file-name=./backup2.zip
export config --dir=./serversBack3
stop server --name=server2
start server --name=server2 --use-cluster-configuration=true --server-port=0 
--group=serverGROUP2 --hostname-for-clients=bob2
export config --dir=./serversBack4
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEODE-3509) Update Gradle Docker Plugin To Work With Gradle 3.X

2017-09-06 Thread Mark Bretl (JIRA)


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

Mark Bretl resolved GEODE-3509.
---
Resolution: Duplicate

> Update Gradle Docker Plugin To Work With Gradle 3.X
> ---
>
> Key: GEODE-3509
> URL: https://issues.apache.org/jira/browse/GEODE-3509
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Mark Bretl
>
> After updating the Gradle wrapper to 3.5.1, the Docker plugin now fails with 
> the error:
> Could not find matching constructor for: 
> org.gradle.process.internal.worker.DefaultWorkerProcessFactory(org.gradle.api.logging.LogLevel,
>  com.pedjak.gradle.plugins.dockerizedtest.DockerizedTestPlugin$MessageServer, 
> org.gradle.api.internal.DefaultClassPathRegistry, 
> org.gradle.internal.id.LongIdGenerator, java.io.File, 
> org.gradle.api.internal.file.TmpDirTemporaryFileProvider, 
> com.sun.proxy.$Proxy73)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEODE-3516) TXManagerImpl.tryResume call may add itself again into the waiting thread queue

2017-09-06 Thread Eric Shu (JIRA)


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

Eric Shu resolved GEODE-3516.
-
   Resolution: Fixed
Fix Version/s: 1.3.0

> TXManagerImpl.tryResume call may add itself again into the waiting thread 
> queue
> ---
>
> Key: GEODE-3516
> URL: https://issues.apache.org/jira/browse/GEODE-3516
> Project: Geode
>  Issue Type: Bug
>  Components: transactions
>Affects Versions: 1.1.0, 1.2.0, 1.3.0
>Reporter: Eric Shu
>Assignee: Eric Shu
> Fix For: 1.3.0
>
>
> Need to avoid adding tryResume thread again into the thread queue when it is 
> spuriously returned from LockSupport.parkNanos call.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3385) Change GetAllRequest to return list of errors

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3385:


Commit 501bd79a8bc161649df4e3113c27b0093faab45d in geode's branch 
refs/heads/feature/GEODE-3557 from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=501bd79 ]

GEODE-3385: Change GetAllRequest to return list of errors.

Also:
* Rename `KeyedErrorResponse` to `KeyedError`.
* move `ErrorResponse` to `clientProtocol.proto`.
* Check for null `value` in `ProtobufUtilities.createEntry`.
  If we find a null, we don't set the value; previously this resulted in
NPE.

Signed-off-by: Galen O'Sullivan 


> Change GetAllRequest to return list of errors
> -
>
> Key: GEODE-3385
> URL: https://issues.apache.org/jira/browse/GEODE-3385
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Galen O'Sullivan
>Assignee: Galen O'Sullivan
> Fix For: 1.3.0
>
>
> GetAllRequest currently returns a list of successful keys or an error (if 
> getting any key threw an exception). We should instead return a list of 
> errors, similar to PutAllRequest.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3557) Classes that have access to a DM should be changed to ask it for the InternalCache instead of calling GemFIreCacheImpl.getInstance

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3557:


Commit 06c4830dc0a7b73339b30089a435bbe010c05e5b in geode's branch 
refs/heads/feature/GEODE-3557 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=06c4830 ]

Merge branch 'develop' into feature/GEODE-3557


> Classes that have access to a DM should be changed to ask it for the 
> InternalCache instead of calling GemFIreCacheImpl.getInstance
> --
>
> Key: GEODE-3557
> URL: https://issues.apache.org/jira/browse/GEODE-3557
> Project: Geode
>  Issue Type: Improvement
>  Components: core
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> A large number of classes call GemFireCacheImpl.getInstance that have access 
> to a DM instance.
> The DM should be changed to remember the InternalCache associated with it and 
> these classes can then ask it for the cache instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (GEODE-3249) Validate internal client/server messages

2017-09-06 Thread Brian Baynes (JIRA)


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

Brian Baynes updated GEODE-3249:

Comment: was deleted

(was: Change to 3249 internal messaging -- going to make this messaging change 
"opt-in", so that the default is no change in behavior.  With the next major 
release, we'll make "on" the default.

Docs will also need updating on this change in approach.)

> Validate internal client/server messages
> 
>
> Key: GEODE-3249
> URL: https://issues.apache.org/jira/browse/GEODE-3249
> Project: Geode
>  Issue Type: Bug
>  Components: docs, messaging
>Reporter: Anthony Baker
>Assignee: Bruce Schuchardt
> Fix For: 1.3.0, 1.2.1
>
>
> Some message types can not be invoked directly by an end user.  For 
> validation purposes, we should treat these messages the same way we treat 
> normal messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3556:


Commit 6d32e28727136ce72ecff0017f7f6079757b819f in geode's branch 
refs/heads/feature/GEODE-3557 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6d32e28 ]

GEODE-3556: Update gradle docker plugin to 0.5.4

- Note that this feature only works on Linux


> Update gradle docker plugin
> ---
>
> Key: GEODE-3556
> URL: https://issues.apache.org/jira/browse/GEODE-3556
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jens Deppe
>
> Since gradle has been updated to 3.5.1, the docker gradle plugin does not 
> work any more. We need to update the plugin to 0.5.4 and fix the associated 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3316) Fix the order of rolling members in RollingUpgrade related tests

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3316:


Commit 841d4e9031d3336c6c4d4f541088a46ddd7faae2 in geode's branch 
refs/heads/feature/GEODE-3557 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=841d4e9 ]

GEODE-3316: Modified tests to roll locator and server


> Fix the order of rolling members in RollingUpgrade related tests
> 
>
> Key: GEODE-3316
> URL: https://issues.apache.org/jira/browse/GEODE-3316
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: nabarun
>Assignee: nabarun
>
> In test classes like RollingUpgrade2DUnit and WANRollingUpgrade, there are 
> tests with clusters which have new version servers connected to an older 
> version locator.
> These tests should be refactored so that everything starts at an older 
> version, then follows the following order of upgrade.
> 1. Locators are rolled first to the current version
> 2. Then the servers are upgraded to current version
> 3. And at last the clients are upgraded.
> Queries/ data verification must done in between these steps to confirm that 
> the data integrity is maintained while upgrades are happening



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3556:


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

Merge branch 'feature/GEODE-3556' into develop


> Update gradle docker plugin
> ---
>
> Key: GEODE-3556
> URL: https://issues.apache.org/jira/browse/GEODE-3556
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jens Deppe
>
> Since gradle has been updated to 3.5.1, the docker gradle plugin does not 
> work any more. We need to update the plugin to 0.5.4 and fix the associated 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEODE-3274) CI failure: org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest > testRMAndTimeoutSetOnServer FAILED

2017-09-06 Thread Shelley Lynn Hughes-Godfrey (JIRA)


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

Shelley Lynn Hughes-Godfrey reassigned GEODE-3274:
--

Assignee: Shelley Lynn Hughes-Godfrey

> CI failure: 
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest > 
> testRMAndTimeoutSetOnServer FAILED
> 
>
> Key: GEODE-3274
> URL: https://issues.apache.org/jira/browse/GEODE-3274
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Affects Versions: 1.3.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>
> {noformat}
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest > 
> testRMAndTimeoutSetOnServer FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.fail(Assert.java:95)
> at 
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doTestCriticalHeapAndQueryTimeout(ResourceManagerWithQueryMonitorDUnitTest.java:738)
> at 
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.doCriticalMemoryHitTestOnServer(ResourceManagerWithQueryMonitorDUnitTest.java:645)
> at 
> org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest.testRMAndTimeoutSetOnServer(ResourceManagerWithQueryMonitorDUnitTest.java:195)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEODE-3331) CI failure: org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > testWANPDX_RR_SerialSender3Sites FAILED

2017-09-06 Thread Shelley Lynn Hughes-Godfrey (JIRA)


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

Shelley Lynn Hughes-Godfrey reassigned GEODE-3331:
--

Assignee: Shelley Lynn Hughes-Godfrey

> CI failure: org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > 
> testWANPDX_RR_SerialSender3Sites FAILED
> -
>
> Key: GEODE-3331
> URL: https://issues.apache.org/jira/browse/GEODE-3331
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Affects Versions: 1.3.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>
> Possibly related to GEODE-1319 with data inconsistency in a WAN PDX test
> {noformat}
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > 
> testWANPDX_RR_SerialSender3Sites FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest$$Lambda$150/528892289.run
>  in VM 4 running on Host f244c02ee98a with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:302)
> at 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest.testWANPDX_RR_SerialSender3Sites(PDXNewWanDUnitTest.java:312)
> Caused by:
> java.lang.AssertionError: expected: myEnum=TWO]> but was:
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at 
> org.apache.geode.internal.cache.wan.WANTestBase.validateRegionSize_PDX(WANTestBase.java:2825)
> at 
> org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest.lambda$testWANPDX_RR_SerialSender3Sites$bb17a952$21(PDXNewWanDUnitTest.java:312)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEODE-3566) Moving a bucket during rebalancing does not update overflow stats

2017-09-06 Thread Lynn Gallinat (JIRA)


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

Lynn Gallinat reassigned GEODE-3566:


Assignee: Lynn Gallinat

> Moving a bucket during rebalancing does not update overflow stats
> -
>
> Key: GEODE-3566
> URL: https://issues.apache.org/jira/browse/GEODE-3566
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Lynn Gallinat
>Assignee: Lynn Gallinat
>
> When a bucket is moved from one member to another due to rebalancing, the 
> member that loses the bucket does not update overflow stats, specifically 
> numEntriesInVM and numOverflowOnDisk. The member that receives the bucket is 
> fine because it updates stats when the getInitialImage brings the data in for 
> the new bucket.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3566) Moving a bucket during rebalancing does not update overflow stats

2017-09-06 Thread Lynn Gallinat (JIRA)

Lynn Gallinat created GEODE-3566:


 Summary: Moving a bucket during rebalancing does not update 
overflow stats
 Key: GEODE-3566
 URL: https://issues.apache.org/jira/browse/GEODE-3566
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Lynn Gallinat


When a bucket is moved from one member to another due to rebalancing, the 
member that loses the bucket does not update overflow stats, specifically 
numEntriesInVM and numOverflowOnDisk. The member that receives the bucket is 
fine because it updates stats when the getInitialImage brings the data in for 
the new bucket.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3565) Remove default Server/Locator with Pool

2017-09-06 Thread David Kimura (JIRA)

David Kimura created GEODE-3565:
---

 Summary: Remove default Server/Locator with Pool
 Key: GEODE-3565
 URL: https://issues.apache.org/jira/browse/GEODE-3565
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: David Kimura


PoolFactory has hidden behavior where if user doesn't specify a server or 
locator it will create a default pool connecting to a default endpoint.  GSS 
doesn't think anybody is using this hidden behavior so we should probably 
remove it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3277) Gfsh commands throw NumberFormatException when given wrong port number

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3277:


Commit 0469ca9d20b3811685865834beb26f5e681f5d86 in geode's branch 
refs/heads/feature/GEODE-3277 from [~khowe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0469ca9 ]

GEODE-3277: Fix error path constructors of Launcher inner State classess

Updated tests for changes in the error constructors for ServerState and
LocatorState.

Minor spelling corrections.

This reintroduces changes that were reverted due to merge conflicts with
the previous state of the develop branch


> Gfsh commands throw NumberFormatException when given wrong port number
> --
>
> Key: GEODE-3277
> URL: https://issues.apache.org/jira/browse/GEODE-3277
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Kenneth Howe
>Assignee: Kenneth Howe
> Fix For: 1.3.0
>
>
> The {{status locator}} and {{status server}} commands internally throw 
> NumberFormatException, and print the message "null" on the console if the 
> port specified with the {{--port=}} option is not the correct port.
> The expected response should like:
> {code}
> Locator in  on 127.0.0.1[12346] is currently not responding.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3316) Fix the order of rolling members in RollingUpgrade related tests

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3316:


Commit 841d4e9031d3336c6c4d4f541088a46ddd7faae2 in geode's branch 
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=841d4e9 ]

GEODE-3316: Modified tests to roll locator and server


> Fix the order of rolling members in RollingUpgrade related tests
> 
>
> Key: GEODE-3316
> URL: https://issues.apache.org/jira/browse/GEODE-3316
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: nabarun
>Assignee: nabarun
>
> In test classes like RollingUpgrade2DUnit and WANRollingUpgrade, there are 
> tests with clusters which have new version servers connected to an older 
> version locator.
> These tests should be refactored so that everything starts at an older 
> version, then follows the following order of upgrade.
> 1. Locators are rolled first to the current version
> 2. Then the servers are upgraded to current version
> 3. And at last the clients are upgraded.
> Queries/ data verification must done in between these steps to confirm that 
> the data integrity is maintained while upgrades are happening



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (GEODE-3554) Fix startup freeze at callback to CacheFactory.getAnyInstance()

2017-09-06 Thread Fred Krone (JIRA)


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

Fred Krone updated GEODE-3554:
--
Description: 
As long as the product continues to invoke user plug-in callbacks during 
startup (and with the main thread), we probably need to document a warning not 
to use CacheFactory.getAnyInstance() as the API call is common in plug-ins and 
this will freeze startup.

A better fix could be to make changes to cache initialization that would 
prevent this deadlock.



  was:
As long as the product continues to invoke user plug-in callbacks during 
startup (and with the main thread), we probably need to document a warning not 
to use CacheFactory.getAnyInstance() as the API call is common in plug-ins and 
this will freeze startup.




> Fix startup freeze at callback to CacheFactory.getAnyInstance()  
> -
>
> Key: GEODE-3554
> URL: https://issues.apache.org/jira/browse/GEODE-3554
> Project: Geode
>  Issue Type: Improvement
>  Components: core
>Reporter: Fred Krone
>
> As long as the product continues to invoke user plug-in callbacks during 
> startup (and with the main thread), we probably need to document a warning 
> not to use CacheFactory.getAnyInstance() as the API call is common in 
> plug-ins and this will freeze startup.
> A better fix could be to make changes to cache initialization that would 
> prevent this deadlock.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEODE-3561) GetAllServers should return public IPs

2017-09-06 Thread Udo Kohlmeyer (JIRA)


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

Udo Kohlmeyer resolved GEODE-3561.
--
Resolution: Cannot Reproduce

This seems to have a been a momentary issue. Works with 
6575b31708d007e6e1126772a06b72b157893ad5

> GetAllServers should return public IPs
> --
>
> Key: GEODE-3561
> URL: https://issues.apache.org/jira/browse/GEODE-3561
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Udo Kohlmeyer
>
> GetAllServers seems to be returning private IP addresses instead of the 
> configured public IPs (hostname-for-clients).  
> Use both Java API and gfsh to configure and test -- GetAllServers should 
> return the configured public IPs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (GEODE-3561) GetAllServers should return public IPs

2017-09-06 Thread Udo Kohlmeyer (JIRA)


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

Udo Kohlmeyer reassigned GEODE-3561:


Assignee: Udo Kohlmeyer

> GetAllServers should return public IPs
> --
>
> Key: GEODE-3561
> URL: https://issues.apache.org/jira/browse/GEODE-3561
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Udo Kohlmeyer
>
> GetAllServers seems to be returning private IP addresses instead of the 
> configured public IPs (hostname-for-clients).  
> Use both Java API and gfsh to configure and test -- GetAllServers should 
> return the configured public IPs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3564) testThinClientListenerCallbackArgTest fails on SPARC

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3564:


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

GEODE-3564: Re-enable testThinClientListenerCallbackArgTest on SPARC.


> testThinClientListenerCallbackArgTest fails on SPARC
> 
>
> Key: GEODE-3564
> URL: https://issues.apache.org/jira/browse/GEODE-3564
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Test testThinClientListenerCallbackArgTest failed on SPARC.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3564) testThinClientListenerCallbackArgTest fails on SPARC

2017-09-06 Thread Jacob S. Barrett (JIRA)

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

 Summary: testThinClientListenerCallbackArgTest fails on SPARC
 Key: GEODE-3564
 URL: https://issues.apache.org/jira/browse/GEODE-3564
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


Test testThinClientListenerCallbackArgTest failed on SPARC.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (GEODE-3563) SSL socket handling problems in TCPConduit run

2017-09-06 Thread Vahram Aharonyan (JIRA)

Vahram Aharonyan created GEODE-3563:
---

 Summary: SSL socket handling problems in TCPConduit run
 Key: GEODE-3563
 URL: https://issues.apache.org/jira/browse/GEODE-3563
 Project: Geode
  Issue Type: Bug
  Components: client/server
Reporter: Vahram Aharonyan
 Fix For: 1.2.1


Here are two cases that seems to problematic in TCPConduit.run flow:

1. TCPConduit.run() has no action performed for the case when SSLException is 
thrown from sslSocket.startHandshake(), as a result the socket remains open. 
Catch block from the end of  configureServerSSLSocket() will just report a 
fatal error(even it seem that this portion is going to be removed in 1.2.1 
according to GEODE-3393) and re-throw the exception.

2. configureServerSSLSocket call is performed without setting socket timeout 
before that. This can bring to run thread blocking case if read initiated from 
the SSL handshake flow will not return. Linking to similar issues observed with 
other acceptors previously: GEODE-2898, GEODE-3023.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3556:


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

GEODE-3556: Add support for setting the user inside docker containers


> Update gradle docker plugin
> ---
>
> Key: GEODE-3556
> URL: https://issues.apache.org/jira/browse/GEODE-3556
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jens Deppe
>
> Since gradle has been updated to 3.5.1, the docker gradle plugin does not 
> work any more. We need to update the plugin to 0.5.4 and fix the associated 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

2017-09-06 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on GEODE-3556:


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

GEODE-3556: Update gradle docker plugin to 0.5.4

- Note that this feature only works on Linux


> Update gradle docker plugin
> ---
>
> Key: GEODE-3556
> URL: https://issues.apache.org/jira/browse/GEODE-3556
> Project: Geode
>  Issue Type: Improvement
>  Components: build
>Reporter: Jens Deppe
>
> Since gradle has been updated to 3.5.1, the docker gradle plugin does not 
> work any more. We need to update the plugin to 0.5.4 and fix the associated 
> configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (GEODE-3568) User can set a LuceneSerializer through the Java API

[jira] [Commented] (GEODE-3568) User can set a LuceneSerializer through the Java API

[jira] [Commented] (GEODE-3082) Client Health Monitor should be able to manage new protocol client connections

[jira] [Commented] (GEODE-3517) Variable-ize product version and name in client user guide

[jira] [Created] (GEODE-3568) User can set a LuceneSerializer through the Java API

[jira] [Assigned] (GEODE-3568) User can set a LuceneSerializer through the Java API

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

[jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

[jira] [Created] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed

[jira] [Resolved] (GEODE-3509) Update Gradle Docker Plugin To Work With Gradle 3.X

[jira] [Resolved] (GEODE-3516) TXManagerImpl.tryResume call may add itself again into the waiting thread queue

[jira] [Commented] (GEODE-3385) Change GetAllRequest to return list of errors

[jira] [Commented] (GEODE-3557) Classes that have access to a DM should be changed to ask it for the InternalCache instead of calling GemFIreCacheImpl.getInstance

[jira] [Issue Comment Deleted] (GEODE-3249) Validate internal client/server messages

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

[jira] [Commented] (GEODE-3316) Fix the order of rolling members in RollingUpgrade related tests

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

[jira] [Assigned] (GEODE-3274) CI failure: org.apache.geode.cache.query.dunit.ResourceManagerWithQueryMonitorDUnitTest > testRMAndTimeoutSetOnServer FAILED

[jira] [Assigned] (GEODE-3331) CI failure: org.apache.geode.internal.cache.wan.misc.PDXNewWanDUnitTest > testWANPDX_RR_SerialSender3Sites FAILED

[jira] [Assigned] (GEODE-3566) Moving a bucket during rebalancing does not update overflow stats

[jira] [Created] (GEODE-3566) Moving a bucket during rebalancing does not update overflow stats

[jira] [Created] (GEODE-3565) Remove default Server/Locator with Pool

[jira] [Commented] (GEODE-3277) Gfsh commands throw NumberFormatException when given wrong port number

[jira] [Commented] (GEODE-3316) Fix the order of rolling members in RollingUpgrade related tests

[jira] [Updated] (GEODE-3554) Fix startup freeze at callback to CacheFactory.getAnyInstance()

[jira] [Resolved] (GEODE-3561) GetAllServers should return public IPs

[jira] [Assigned] (GEODE-3561) GetAllServers should return public IPs

[jira] [Commented] (GEODE-3564) testThinClientListenerCallbackArgTest fails on SPARC

[jira] [Created] (GEODE-3564) testThinClientListenerCallbackArgTest fails on SPARC

[jira] [Created] (GEODE-3563) SSL socket handling problems in TCPConduit run

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

[jira] [Commented] (GEODE-3556) Update gradle docker plugin

33 matches

Site Navigation

Mail list logo

Footer information