[jira] [Commented] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/277
  
@upthewaterspout I think you closed PR "227" instead of "277".


> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Commented] (GEODE-1871) Update Dockerfile for Geode 1.0.0

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

Github user metatype commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/275#discussion_r85631878
  
--- Diff: docker/Dockerfile ---
@@ -14,25 +14,34 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-FROM geode/base:0.1
-MAINTAINER Geode Community 
+FROM centos:7
+MAINTAINER Apache Geode Community 
 
 LABEL Vendor="Apache Geode (incubating)"
-LABEL version=unstable
+LABEL version=1.0.0
 
 # download JDK 8
-# ENV  JAVA_HOME /jdk1.8.0_51
+ENVJAVA_HOME /jdk1.8.0_111
 
-RUNgit clone -b develop 
https://github.com/apache/incubator-geode.git \
+RUNyum install -y wget which tar git \
+   && wget --no-cookies --no-check-certificate --header "Cookie: 
gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; 
oraclelicense=accept-securebackup-cookie" 
"http://download.oracle.com/otn-pub/java/jdk/8u111-b14/jdk-8u111-linux-x64.tar.gz;
 \
--- End diff --

What about just doing `yum install java-1.8.0-openjdk` and avoid any legal 
issues with redistributing the oracle jdk?


> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for 1.0.0



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

[jira] [Commented] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/277
  
Thanks for your contribution!


> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Resolved] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread Dan Smith (JIRA) 

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

Dan Smith resolved GEODE-1098.
--
Resolution: Fixed

> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Commented] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1098:


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

GEODE-1098: Fix gfsh.bat error with default Java installation

Paths to JAR dependencies quoted to prevent spaces from causing error

This closes #227


> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Commented] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

Github user upthewaterspout commented on the issue:

https://github.com/apache/incubator-geode/pull/277
  
+1 Looks good to me. I'll merge this. Thanks!

The travis failure appears to be code checked in on develop with formatting 
changes. I'm looking into that, but it's not related to this change.


> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Commented] (GEODE-2012) Test rolling stat archive after closing a resource instance

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2012:


Commit 765a55a0e6d5155c352c6c199e660cfb1a5b4f6d in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=765a55a ]

Revert "GEODE-2012: always write stat types to archive"

This reverts commit 3ff33be200484ff4c8614a0d97e3612e1ca85ac4.


> Test rolling stat archive after closing a resource instance
> ---
>
> Key: GEODE-2012
> URL: https://issues.apache.org/jira/browse/GEODE-2012
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Need to test this scenario:
> 1) create resource instance of new type
> 2) sample so that resource instance and type are written to gfs
> 3) close resource instance so no instances exist of that type
> 4) sample
> 5) roll gfs archive
> 6) sample
> 7) create new resource instance of same type
> 8) sample
> 9) verify that resource instance and type were both written to gfs



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

[jira] [Commented] (GEODE-2017) Removal of nonSingleHopsCount stat in client

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2017:


Commit e9b509580de948145e145b8f54d50aeaa7d0867f in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e9b5095 ]

GEODE-2017: Fixed formatting


> Removal of nonSingleHopsCount stat in client
> 
>
> Key: GEODE-2017
> URL: https://issues.apache.org/jira/browse/GEODE-2017
> Project: Geode
>  Issue Type: Bug
>  Components: client/server, native client
>Reporter: Udo Kohlmeyer
>Assignee: Udo Kohlmeyer
>
> Currently, the nonSingleHopsCount stat in the client is defined as "Total 
> number of times client request observed more than one hop during operation." 
> From this definition, this stat should track every time a client operation 
> requires more than one hop. Currently, this stat is only incremented when 
> "singleHop" is enabled on the pool. If this is correct then 
> metaDataRefreshCount will track the same metric, as the client will 
> automatically refresh when more than one hop is required for a prSingleHop 
> enabled pool.
> If the nonSingleHopsCount metric where to track every non-one hop operation, 
> regardless of the "singleHop" flag on the pool, then the implementation of 
> this stat would need to change.
> Otherwise we remove this stat and only track all nonSingleHop operation with 
> the metaDataRefresh count.



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

[jira] [Commented] (GEODE-2012) Test rolling stat archive after closing a resource instance

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2012:


Commit 3ff33be200484ff4c8614a0d97e3612e1ca85ac4 in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3ff33be ]

GEODE-2012: always write stat types to archive

* write additional tests for stat archive rolling
* expose bug GEODE-2012 in StatTypesAreRolledOverRegressionTest
* fix failure in StatTypesAreRolledOverRegressionTest


> Test rolling stat archive after closing a resource instance
> ---
>
> Key: GEODE-2012
> URL: https://issues.apache.org/jira/browse/GEODE-2012
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Need to test this scenario:
> 1) create resource instance of new type
> 2) sample so that resource instance and type are written to gfs
> 3) close resource instance so no instances exist of that type
> 4) sample
> 5) roll gfs archive
> 6) sample
> 7) create new resource instance of same type
> 8) sample
> 9) verify that resource instance and type were both written to gfs



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

[jira] [Commented] (GEODE-2027) Gateway events being processed by the ParallelQueueRemovalMessage in the secondary at the time of GII may not be removed from the queue successfully

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2027:


Commit b10a171e11990a566ed42560a903668908131390 in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~barry.oglesby]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b10a171 ]

GEODE-2027: ParallelQueueRemovalMessage processing removes events from the 
region and temp queue


> Gateway events being processed by the ParallelQueueRemovalMessage in the 
> secondary at the time of GII may not be removed from the queue successfully
> 
>
> Key: GEODE-2027
> URL: https://issues.apache.org/jira/browse/GEODE-2027
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>
> This is the same as Trac ticket 49196.
> I see two cases that cause this issue (so far). In both cases the member is 
> starting and GIIing the bucket region, and the entry in question is included 
> in the GII response.
> In case one:
> - the bucket region is not found in the {{ParallelGatewaySenderQueue.put}} 
> path, so the event is added to the temp queue
> - the bucket region is found in the {{ParallelQueueRemovalMessage.process}} 
> path and contains the key so it is removed from it
> - the event is added back into the bucket region from the temp queue
> The event is added to the temp queue:
> {noformat}
> [warning 2016/10/20 01:25:07.715 UTC bridgegemfire_1_1_ip-10-32-109-74_25707 
>  ip-10-32-109-74(bridgegemfire_1_2_ip-10-32-109-74_25713:25713):1026 
> unshared ordered uid=75 dom #1 port=57564> tid=0x82] XXX 
> ParallelGatewaySenderQueue.put adding to tempQueue brq=null; key=33283; 
> value=SenderEventImpl[id=EventID[threadID=0x10007|5;sequenceID=177;bucketId=7];action=2;operation=DESTROY;region=/testRegion1;key=Object_2934;value=;valueIsObject=1;numberOfParts=8;callbackArgument=GatewaySenderEventCallbackArgument
>  
> [originalCallbackArg=null;originatingSenderId=1;recipientGatewayReceivers=[2]];possibleDuplicate=false;creationTime=1476926707714;shadowKey=
>  33283;timeStamp=1476926707709;acked=false;dispatched=false]
> {noformat}
> The event exists in the bucket region and is removed:
> {noformat}
> [warning 2016/10/20 01:25:10.265 UTC bridgegemfire_1_1_ip-10-32-109-74_25707 
>  tid=0x63] XXX 
> ParallelQueueRemovalMessage.process bucket is not initialized but contains 
> key destroying from bucket 
> name=/__PR/_B__sender__bridgeds__1__to__bridgeds__2__PARALLEL__GATEWAY__SENDER__QUEUE_7;
>  key=33283
> {noformat}
> The event is loaded from the temp queue into the bucket region:
> {noformat}
> [warning 2016/10/20 01:25:10.432 UTC bridgegemfire_1_1_ip-10-32-109-74_25707 
>  tid=0x4f] XXX 
> AbstractBucketRegionQueue.loadEventsFromTempQueue 
> _B__sender__bridgeds__1__to__bridgeds__2__PARALLEL__GATEWAY__SENDER__QUEUE_7 
> adding to queue key=33283 -> 
> SenderEventImpl[id=EventID[threadID=0x10007|5;sequenceID=177;bucketId=7];action=2;operation=DESTROY;region=/testRegion1;key=Object_2934;value=;valueIsObject=1;numberOfParts=8;callbackArgument=GatewaySenderEventCallbackArgument
>  
> [originalCallbackArg=null;originatingSenderId=1;recipientGatewayReceivers=[2]];possibleDuplicate=true;creationTime=1476926707714;shadowKey=
>  33283;timeStamp=1476926707709;acked=false;dispatched=false]
> {noformat}
> The bucket region contains the key right before it is available for use:
> {noformat}
> [warning 2016/10/20 01:25:10.790 UTC bridgegemfire_1_1_ip-10-32-109-74_25707 
>  tid=0x4f] XXX 
> BucketRegionQueue.cleanUpDestroyedTokensAndMarkGIIComplete 
> _B__sender__bridgeds__1__to__bridgeds__2__PARALLEL__GATEWAY__SENDER__QUEUE_7 
> keySet4=[33283, 33079, 34591, 35071, 35119, 34879, 34447, 34891, 34843, 
> 35083, 33295, 34387, 34339, 32743, 35131, 35095, 35059, 34603, 34471, 34567, 
> 34375, 32983, 32875, 34399, 34867, 34831, 34759, 34675, 35107, 35047, 34723, 
> 34495, 34507, 34459, 34699, 34735]
> {noformat}
> In case two:
> - the bucket region is not found in the {{ParallelGatewaySenderQueue.put}} 
> path, so the event is added to the temp queue
> - the bucket region is found in the {{ParallelQueueRemovalMessage.process}} 
> path, but doesn't contain the key so it is removed from the temp queue
> - the event is removed from the temp queue but is also in the bucket region
> The event is added to the temp queue:
> {noformat}
> [warning 2016/10/19 22:55:27.743 UTC bridgegemfire_1_1_ip-10-32-109-74_24670 
>  ip-10-32-109-74(bridgegemfire_1_3_ip-10-32-109-74_24716:24716):1028 
> unshared ordered uid=62 dom #1 port=56962> tid=0x68] XXX 
> ParallelGatewaySenderQueue.put adding to tempQueue brq=null; key=31555; 
>

[jira] [Commented] (GEODE-1912) gfsh does not validate start server command

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1912:


Commit fa88520b658dbf8ec74a83a63190bca8dc2bcff5 in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=fa88520 ]

GEODE-1912: make ServerStarter and LocatorStarter as regular rules so that it's 
easier to use them in a RuleChain


> gfsh does not validate start server command
> ---
>
> Key: GEODE-1912
> URL: https://issues.apache.org/jira/browse/GEODE-1912
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Minor
>
> When I tried to start a server from gfsh I accidently used {{--locator}} 
> (singular) rather than -{{-locators}}. gfsh did not throw an error and 
> started the server without connecting to the locator.
> We should throw an error for unrecognized command options in gfsh.



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

[jira] [Commented] (GEODE-1983) Swagger is broken with integrated security

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1983:


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

GEODE-1983: Swagger is broken with integrated security

* this closes #273


> Swagger is broken with integrated security
> --
>
> Key: GEODE-1983
> URL: https://issues.apache.org/jira/browse/GEODE-1983
> Project: Geode
>  Issue Type: Bug
>  Components: rest (dev), security
>Reporter: Diane Hardman
>Assignee: Kevin Duling
> Fix For: 1.1.0-incubating
>
>
> Swagger UI does not work with latest integrated security. After configuring 
> security manager and attempting up to open up Swagger UI we get a prompt for 
> username and password. Entering credentials does not bring up the UI, instead 
> asking for credentials again.



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

[jira] [Commented] (GEODE-2012) Test rolling stat archive after closing a resource instance

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2012:


Commit 3ff33be200484ff4c8614a0d97e3612e1ca85ac4 in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3ff33be ]

GEODE-2012: always write stat types to archive

* write additional tests for stat archive rolling
* expose bug GEODE-2012 in StatTypesAreRolledOverRegressionTest
* fix failure in StatTypesAreRolledOverRegressionTest


> Test rolling stat archive after closing a resource instance
> ---
>
> Key: GEODE-2012
> URL: https://issues.apache.org/jira/browse/GEODE-2012
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Need to test this scenario:
> 1) create resource instance of new type
> 2) sample so that resource instance and type are written to gfs
> 3) close resource instance so no instances exist of that type
> 4) sample
> 5) roll gfs archive
> 6) sample
> 7) create new resource instance of same type
> 8) sample
> 9) verify that resource instance and type were both written to gfs



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

[jira] [Commented] (GEODE-2043) severe Internal product error log message possible when async disk configured on persistent region

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2043:


Commit 2ef50b24de1457ab91729f22a3c2ff4a8a07557b in incubator-geode's branch 
refs/heads/feature/GEM-983 from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=2ef50b2 ]

GEODE-2043: change makeTombstone to handle exception

Now if makeTombstone has an exception but had already changed
the region entry value to a TOMBSTONE, it will now change
the value to REMOVE_PHASE2 instead of leaving it as a TOMBSTONE.


> severe Internal product error log message possible when async disk configured 
> on persistent region
> --
>
> Key: GEODE-2043
> URL: https://issues.apache.org/jira/browse/GEODE-2043
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.1.0-incubating
>
>
> It is possible to see a log message like this:
> [severe 2016/10/22 07:18:14.665 UTC gemfire3_client-10_8522  reader for client-10(gemfire1_client-10_8469:8469):1028 shared 
> ordered uid=10 port=50942> tid=0x66] Internal product error: attempt to 
> directly remove a versioned tombstone from region entry map
> java.lang.Exception: stack trace
> at 
> org.apache.geode.internal.cache.AbstractRegionMap.removeEntry(AbstractRegionMap.java:261)
> This log message can be safely ignored. It happens if async disk is 
> configured on a persistent geode region. If an entry on that region is being 
> destroyed and the region is being closed or destroyed at the same time, then 
> this message may be logged.



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

[jira] [Commented] (GEODE-1098) gfsh.bat error with default Java installation

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user mmurdoch opened a pull request:

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

GEODE-1098: Fix gfsh.bat error with default Java installation

Paths to JAR dependencies quoted to prevent spaces from causing error

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

$ git pull https://github.com/mmurdoch/incubator-geode feature/GEODE-1098

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

https://github.com/apache/incubator-geode/pull/277.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #277






> gfsh.bat error with default Java installation
> -
>
> Key: GEODE-1098
> URL: https://issues.apache.org/jira/browse/GEODE-1098
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating
>Reporter: Karen Smoler Miller
> Fix For: 1.1.0-incubating
>
>
> The Windows gfsh.bat script issues an error when invoked from the command 
> line, and the JAVA_HOME variable has a path name component that contains a 
> space. JAVA_HOME is used when no GF_JAVA variable is defined.
> The default Java installation on Windows places itself into {{C:\Program 
> Files\Java\...}}, therefore there will be a space in the {{Program Files}} 
> portion of the path name.
> The error message looks similar to: 
> {{'"C:Program' is not recognized as an internal or external command, operable 
> program, or batch file.}}



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

[jira] [Resolved] (GEODE-2043) severe Internal product error log message possible when async disk configured on persistent region

2016-10-28 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider resolved GEODE-2043.
-
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> severe Internal product error log message possible when async disk configured 
> on persistent region
> --
>
> Key: GEODE-2043
> URL: https://issues.apache.org/jira/browse/GEODE-2043
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.1.0-incubating
>
>
> It is possible to see a log message like this:
> [severe 2016/10/22 07:18:14.665 UTC gemfire3_client-10_8522  reader for client-10(gemfire1_client-10_8469:8469):1028 shared 
> ordered uid=10 port=50942> tid=0x66] Internal product error: attempt to 
> directly remove a versioned tombstone from region entry map
> java.lang.Exception: stack trace
> at 
> org.apache.geode.internal.cache.AbstractRegionMap.removeEntry(AbstractRegionMap.java:261)
> This log message can be safely ignored. It happens if async disk is 
> configured on a persistent geode region. If an entry on that region is being 
> destroyed and the region is being closed or destroyed at the same time, then 
> this message may be logged.



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

[jira] [Assigned] (GEODE-2043) severe Internal product error log message possible when async disk configured on persistent region

2016-10-28 Thread Darrel Schneider (JIRA) 

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

Darrel Schneider reassigned GEODE-2043:
---

Assignee: Darrel Schneider

> severe Internal product error log message possible when async disk configured 
> on persistent region
> --
>
> Key: GEODE-2043
> URL: https://issues.apache.org/jira/browse/GEODE-2043
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
> Fix For: 1.1.0-incubating
>
>
> It is possible to see a log message like this:
> [severe 2016/10/22 07:18:14.665 UTC gemfire3_client-10_8522  reader for client-10(gemfire1_client-10_8469:8469):1028 shared 
> ordered uid=10 port=50942> tid=0x66] Internal product error: attempt to 
> directly remove a versioned tombstone from region entry map
> java.lang.Exception: stack trace
> at 
> org.apache.geode.internal.cache.AbstractRegionMap.removeEntry(AbstractRegionMap.java:261)
> This log message can be safely ignored. It happens if async disk is 
> configured on a persistent geode region. If an entry on that region is being 
> destroyed and the region is being closed or destroyed at the same time, then 
> this message may be logged.



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

[jira] [Commented] (GEODE-2043) severe Internal product error log message possible when async disk configured on persistent region

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2043:


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

GEODE-2043: change makeTombstone to handle exception

Now if makeTombstone has an exception but had already changed
the region entry value to a TOMBSTONE, it will now change
the value to REMOVE_PHASE2 instead of leaving it as a TOMBSTONE.


> severe Internal product error log message possible when async disk configured 
> on persistent region
> --
>
> Key: GEODE-2043
> URL: https://issues.apache.org/jira/browse/GEODE-2043
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Darrel Schneider
>
> It is possible to see a log message like this:
> [severe 2016/10/22 07:18:14.665 UTC gemfire3_client-10_8522  reader for client-10(gemfire1_client-10_8469:8469):1028 shared 
> ordered uid=10 port=50942> tid=0x66] Internal product error: attempt to 
> directly remove a versioned tombstone from region entry map
> java.lang.Exception: stack trace
> at 
> org.apache.geode.internal.cache.AbstractRegionMap.removeEntry(AbstractRegionMap.java:261)
> This log message can be safely ignored. It happens if async disk is 
> configured on a persistent geode region. If an entry on that region is being 
> destroyed and the region is being closed or destroyed at the same time, then 
> this message may be logged.



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

[jira] [Resolved] (GEODE-1993) value returned through /region/key rest service needs to be post processed

2016-10-28 Thread Kevin Duling (JIRA) 

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

Kevin Duling resolved GEODE-1993.
-
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> value returned through /region/key rest service needs to be post processed
> --
>
> Key: GEODE-1993
> URL: https://issues.apache.org/jira/browse/GEODE-1993
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
> Fix For: 1.1.0-incubating
>
>
> The new rest security did not use post processor before returning the value 
> back to the client.



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

[jira] [Updated] (GEODE-1993) value returned through /region/key rest service needs to be post processed

2016-10-28 Thread Kevin Duling (JIRA) 

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

Kevin Duling updated GEODE-1993:

Assignee: Kevin Duling

> value returned through /region/key rest service needs to be post processed
> --
>
> Key: GEODE-1993
> URL: https://issues.apache.org/jira/browse/GEODE-1993
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Jinmei Liao
>Assignee: Kevin Duling
>
> The new rest security did not use post processor before returning the value 
> back to the client.



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

[jira] [Commented] (GEODE-1993) value returned through /region/key rest service needs to be post processed

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user kjduling opened a pull request:

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

GEODE-1993: postprocess region/key

Add post processing to the GET {region}/{key..key} endpoint
precheckin running

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

$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-1993

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

https://github.com/apache/incubator-geode/pull/276.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #276


commit 41559682c95f844018fa285f35a1adf2f7fcf0ba
Author: Kevin Duling 
Date:   2016-10-28T20:27:56Z

GEODE-1993: postprocess region/key




> value returned through /region/key rest service needs to be post processed
> --
>
> Key: GEODE-1993
> URL: https://issues.apache.org/jira/browse/GEODE-1993
> Project: Geode
>  Issue Type: New Feature
>  Components: management
>Reporter: Jinmei Liao
>
> The new rest security did not use post processor before returning the value 
> back to the client.



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

[jira] [Created] (GEODE-2045) Improve documentation of region shortcuts

2016-10-28 Thread Karen Smoler Miller (JIRA) 
Karen Smoler Miller created GEODE-2045:
--

 Summary: Improve documentation of region shortcuts
 Key: GEODE-2045
 URL: https://issues.apache.org/jira/browse/GEODE-2045
 Project: Geode
  Issue Type: Bug
Reporter: Karen Smoler Miller


The description of a bunch of region shortcuts for partitioned regions says 
that they have local scope, and they don't. While fixing this, also fix the 
links to those descriptions (since they do not error out, but they also do not 
work correctly), and remove many of the links that clutter each description.



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

[jira] [Resolved] (GEODE-502) CI Failure: TestSuite$1.warning

2016-10-28 Thread nabarun (JIRA) 

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

nabarun resolved GEODE-502.
---
   Resolution: Fixed
Fix Version/s: 1.0.0-incubating

> CI Failure: TestSuite$1.warning
> ---
>
> Key: GEODE-502
> URL: https://issues.apache.org/jira/browse/GEODE-502
> Project: Geode
>  Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>  Labels: CI
> Fix For: 1.0.0-incubating
>
> Attachments: Test results - Class 
> org.apache.geode.modules.session.Tomcat8SessionsDUnitTest.html
>
>
> I saw this in a internal CI run. The first test fails with the below error 
> about VMs not launching in 30 seconds. Then later tests fail with a cause of 
> "Log writer has already been created"
> This is actually a failure to launch the dunit framework, which is why it's 
> misreporting the test name as "TestSuite$1.warning"; the failure happens 
> during the constructor of the test case. 
> {noformat}
> junit.framework.AssertionFailedError: Exception in constructor: 
> testPutGetTimeout (java.lang.RuntimeException: Unable to launch dunit VMS
>   at dunit.standalone.DUnitLauncher.launchIfNeeded(DUnitLauncher.java:130)
>   at dunit.DistributedTestCase.(DistributedTestCase.java:416)
>   at 
> com.gemstone.gemfire.cache30.CacheTestCase.(CacheTestCase.java:89)
>   at 
> com.gemstone.gemfire.cache30.RegionTestCase.(RegionTestCase.java:110)
>   at 
> com.gemstone.gemfire.cache30.MultiVMRegionTestCase.(MultiVMRegionTestCase.java:160)
>   at 
> com.gemstone.gemfire.cache30.GlobalRegionDUnitTest.(GlobalRegionDUnitTest.java:39)
>   at 
> com.gemstone.gemfire.cache30.GlobalRegionCompressionDUnitTest.(GlobalRegionCompressionDUnitTest.java:34)
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>   at junit.framework.TestSuite.createTest(TestSuite.java:65)
>   at junit.framework.TestSuite.addTestMethod(TestSuite.java:307)
>   at junit.framework.TestSuite.addTestsFromTestCase(TestSuite.java:150)
>   at junit.framework.TestSuite.(TestSuite.java:129)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.(JUnit38ClassRunner.java:74)
>   at 
> org.junit.internal.builders.JUnit3Builder.runnerForClass(JUnit3Builder.java:11)
>   at 
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>   at 
> org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>   at 
> org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
>   at 
> org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:88)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
>

[jira] [Commented] (GEODE-2012) Test rolling stat archive after closing a resource instance

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2012:


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

Revert "GEODE-2012: always write stat types to archive"

This reverts commit 3ff33be200484ff4c8614a0d97e3612e1ca85ac4.


> Test rolling stat archive after closing a resource instance
> ---
>
> Key: GEODE-2012
> URL: https://issues.apache.org/jira/browse/GEODE-2012
> Project: Geode
>  Issue Type: Bug
>  Components: statistics
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>
> Need to test this scenario:
> 1) create resource instance of new type
> 2) sample so that resource instance and type are written to gfs
> 3) close resource instance so no instances exist of that type
> 4) sample
> 5) roll gfs archive
> 6) sample
> 7) create new resource instance of same type
> 8) sample
> 9) verify that resource instance and type were both written to gfs



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

[jira] [Resolved] (GEODE-17) Provide Integrated Security

2016-10-28 Thread Jinmei Liao (JIRA) 

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

Jinmei Liao resolved GEODE-17.
--
Resolution: Fixed

> Provide Integrated Security
> ---
>
> Key: GEODE-17
> URL: https://issues.apache.org/jira/browse/GEODE-17
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server, docs, security
>Reporter: Tushar Khairnar
>Assignee: Jens Deppe
>  Labels: security
>
> Integrated Security: Purpose of integrated security feature is to provide 
> uniform authentication and authorization capabilities for all Geode clients. 
> Geode distributed systems has different clients, some perform cache/region 
> operations, some perform management operations. In order to authenticate and 
> authorize these actions we need single consistent framework or interface. 
> Such interface should allow configuration of access levels from single place 
> and/or repository. 
> The key requirements being met here are
>  - Authentication of all clients from single plugin
>  - Authorization of cache/data operations (through cache-client and REST) and 
> managements (GFSH/JMX) operations from single plugin
>  - Extend existing Client-Server security framework



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

[jira] [Commented] (GEODE-1912) gfsh does not validate start server command

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1912:


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

GEODE-1912: make ServerStarter and LocatorStarter as regular rules so that it's 
easier to use them in a RuleChain


> gfsh does not validate start server command
> ---
>
> Key: GEODE-1912
> URL: https://issues.apache.org/jira/browse/GEODE-1912
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Minor
>
> When I tried to start a server from gfsh I accidently used {{--locator}} 
> (singular) rather than -{{-locators}}. gfsh did not throw an error and 
> started the server without connecting to the locator.
> We should throw an error for unrecognized command options in gfsh.



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

[jira] [Commented] (GEODE-2030) Geode Security framework needs to support easier integration in SDG

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-2030:


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

GEODE-2030: security support for SDG


> Geode Security framework needs to support easier integration in SDG
> ---
>
> Key: GEODE-2030
> URL: https://issues.apache.org/jira/browse/GEODE-2030
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Reporter: Jinmei Liao
>
> While using gemfire properties to configure security is doable in SDG, they 
> would prefer an object based injection model to configure security. Here are 
> the two things they would need:
> 1. directly inject a Gemfire SecurityManager object into CacheFactory.
> 2. directly configure Shiro Security using their xml based configuration.



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

[jira] [Commented] (GEODE-1983) Swagger is broken with integrated security

2016-10-28 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1983:


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

GEODE-1983: Swagger is broken with integrated security

* this closes #273


> Swagger is broken with integrated security
> --
>
> Key: GEODE-1983
> URL: https://issues.apache.org/jira/browse/GEODE-1983
> Project: Geode
>  Issue Type: Bug
>  Components: rest (dev), security
>Reporter: Diane Hardman
>Assignee: Kevin Duling
> Fix For: 1.1.0-incubating
>
>
> Swagger UI does not work with latest integrated security. After configuring 
> security manager and attempting up to open up Swagger UI we get a prompt for 
> username and password. Entering credentials does not bring up the UI, instead 
> asking for credentials again.



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

[jira] [Resolved] (GEODE-1959) Prompt for username and password when adding a member

2016-10-28 Thread Kevin Duling (JIRA) 

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

Kevin Duling resolved GEODE-1959.
-
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> Prompt for username and password when adding a member
> -
>
> Key: GEODE-1959
> URL: https://issues.apache.org/jira/browse/GEODE-1959
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Diane Hardman
>Assignee: Kevin Duling
> Fix For: 1.1.0-incubating
>
> Attachments: gemfire.properties, security.json
>
>
> When you have SecurityManager configured as part of starting a locator, the 
> administrator currently needs to have either AuthInitialize implemented or 
> have stored credentials (in plain text) in geode.properties file. In the case 
> where neither AuthInitialize is implemented NOR are there any credentials 
> stored in geode.properties, then the administrator should be prompted for 
> username and password when attempting to start another member in the 
> distributed system.



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

[jira] [Resolved] (GEODE-2014) Upgrade Swagger libraries

2016-10-28 Thread Kevin Duling (JIRA) 

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

Kevin Duling resolved GEODE-2014.
-
   Resolution: Fixed
Fix Version/s: 1.1.0-incubating

> Upgrade Swagger libraries
> -
>
> Key: GEODE-2014
> URL: https://issues.apache.org/jira/browse/GEODE-2014
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, rest (dev)
>Affects Versions: 1.0.0-incubating
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.1.0-incubating
>
>
> Upgrade swagger and swagger-springmvc



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

[jira] [Assigned] (GEODE-1896) unable to specify a PartitionResolver in gfsh

2016-10-28 Thread Avinash (JIRA) 

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

Avinash reassigned GEODE-1896:
--

Assignee: Avinash

> unable to specify a PartitionResolver in gfsh
> -
>
> Key: GEODE-1896
> URL: https://issues.apache.org/jira/browse/GEODE-1896
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Avinash
>
> While creating a region in gfsh, users should be able to provide a 
> PartitionResolver, something like:
> {noformat}
> gfsh>create region --name=myRegion --type=PARTITION 
> --partition-resolver=com.mycompany.MyCustomPartitionResolver
> {noformat}



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

[jira] [Updated] (GEODE-1871) Update Dockerfile for Geode 1.0.0

2016-10-28 Thread William Markito Oliveira (JIRA) 

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

William Markito Oliveira updated GEODE-1871:

Summary: Update Dockerfile for Geode 1.0.0  (was: Update Dockerfile for 
Geode M3)

> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for M3.



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

[jira] [Updated] (GEODE-1871) Update Dockerfile for Geode 1.0.0

2016-10-28 Thread William Markito Oliveira (JIRA) 

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

William Markito Oliveira updated GEODE-1871:

Description: Need to update Dockerfile under incubator-geode/docker for 
1.0.0  (was: Need to update Dockerfile under incubator-geode/docker for M3.)

> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for 1.0.0



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

[jira] [Commented] (GEODE-1871) Update Dockerfile for Geode 1.0.0

2016-10-28 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user markito opened a pull request:

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

[GEODE-1871] - Updating and cleaning up Dockerfile for Geode 1.0.0

Removed unused files. Updated JDK version and Docker tag for 1.0.0. 

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

$ git pull https://github.com/markito/incubator-geode feature/GEODE-1871

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

https://github.com/apache/incubator-geode/pull/275.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #275


commit b566a46e8349612386c91c5d135636ac334218ad
Author: William Markito 
Date:   2016-10-28T06:11:39Z

Updating and cleaning up Dockerfile for 1.0.0




> Update Dockerfile for Geode 1.0.0
> -
>
> Key: GEODE-1871
> URL: https://issues.apache.org/jira/browse/GEODE-1871
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: William Markito Oliveira
>
> Need to update Dockerfile under incubator-geode/docker for 1.0.0



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