[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/207
  
this seems to have some conflict with the current develop branch. Please 
rebase again.


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



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

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/201
  
I think it's probably safe to get the storage team involved to review this 
PR.


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



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

[jira] [Resolved] (GEODE-1600) DUnitLauncher should not use AvailablePort to pick the locator port

2016-07-14 Thread nabarun (JIRA) 

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

nabarun resolved GEODE-1600.

Resolution: Fixed

> DUnitLauncher should not use AvailablePort to pick the locator port
> ---
>
> Key: GEODE-1600
> URL: https://issues.apache.org/jira/browse/GEODE-1600
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> In a recent dunit precheckin run, I saw a number of tests fail with the below 
> errors
> {noformat}
> 11:38:15 com.gemstone.gemfire.disttx.DistTXDebugDUnitTest > classMethod FAILED
> 11:38:15 java.lang.RuntimeException: Unable to launch dunit VMS
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.lang.RuntimeException: Failed to start locator
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Failed to create server socket 
> on  null[29,649]
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Address already in use
> 11:38:17 
> 11:38:17 com.gemstone.gemfire.disttx.DistTXRestrictionsDUnitTest > 
> testPersistentRestriction FAILED
> 11:38:17 com.gemstone.gemfire.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> 11:38:18 
> 11:38:18 com.gemstone.gemfire.disttx.PRDistTXDUnitTest > 
> testColocationPartitionedRegion FAILED
> 11:38:18 com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.execute.PRTransactionDUnitTest$12.call in 
> VM 0 running on Host zambia.gemstone.com with 4 VMs
> 11:38:18 
> 11:38:18 Caused by:
> 11:38:18 com.gemstone.gemfire.GemFireConfigException: Unable to join 
> the distributed system.  Operation either timed out, was stopped or Locator 
> does not exist.
> {noformat}
> It looks like the issue is that the locator failed to start because the port 
> it was starting on was already used.
> We should refactor the launcher code to call Locator.startLocatorAndDS with a 
> port of 0 and let it pick an open port. That way we should no longer have a 
> chance of port conflicts when launching dunit.



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

[jira] [Resolved] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message

2016-07-14 Thread Kevin Duling (JIRA) 

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

Kevin Duling resolved GEODE-746.

Resolution: Fixed

> When starting a locator using --bind-address, gfsh prints incorrect connect 
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1 
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like 
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
> -Dgemfire.load-cluster-configuration-from-dir=false 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the 
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind 
> address.



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

[jira] [Comment Edited] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message

2016-07-14 Thread Kevin Duling (JIRA) 

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

Kevin Duling edited comment on GEODE-746 at 7/14/16 10:45 PM:
--

Grace and I tracked the first part of this down to a problem in 
{{LauncherLifecycleCommands}}:
{{String locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
  locatorHostName = bindAddr.getCanonicalHostName();
} else {
  locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());
}
{code}

This resolved the problem.  The system will now connect: {{gfsh start locator 
--name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is 
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
-Dgemfire.load-cluster-configuration-from-dir=false 
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: 
/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar

Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099]

Cluster configuration service is up and running.
{noformat}

The successfully connected message appears to be showing the wrong IP address.  
Looking at netstat, we can see that the listener is correctly bound to the IP 
address specified:
{noformat}
$ netstat -an | grep 19991
tcp4   0  0  192.168.1.187.19991*.*LISTEN 
{noformat}
The "successfully connected" hostname reports a different NIC: {{ping 
pdx2-office-dhcp9.eng.vmware.com}}
{noformat}
PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes
{noformat}
Both NICs exist on this machine: {{nestat -rn}}
{noformat}
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use   Netif Expire
default10.118.33.253  UGSc  3600 en4
default192.168.1.253  UGScI  350 en0
{noformat}

Tracing this down, the address is coming from this line in 
{{ShellCommands.connectToLocator(String host, int port, int timeout, 
Map props)}}

{code}
JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host, 
port, timeout, props);  
// locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099, 
ssl=false, ex=null]”
// host: “192.168.1.187”
// port: 19991
// timeout: 15000
// props: size = 0
{code}

So the confusion here now is that this is the JMX address, not the locator 
address.  The formatting of this message lends one to believe it's supposed to 
be the locator.  Yet, if you look at the original response from the system, it 
correctly reports the Locator's address:
{noformat}
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is 
currently online.
{noformat}

I've added JMX to the "successfully connected" message to reduce confusion.




was (Author: kduling):
Grace and I tracked the first part of this down to a problem in 
{{LauncherLifecycleCommands}}:
{{String locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
  locatorHostName = bindAddr.getCanonicalHostName();
} else {
  locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());
}
{code}

This improved things a little.  The system will now connect: {{gfsh start 
locator --name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is 
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
-Dgemfire.load-cluster-configuration-from-dir=false

[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for peer authentication

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user gracemeilen closed the pull request at:

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


> Enable use of SecurityManager for peer authentication
> -
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, 
> the peer-to-peer authentication should also be able to use SecurityManager so 
> that the users could truly have one callback for all authentication.



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

[jira] [Closed] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread Anthony Baker (JIRA) 

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

Anthony Baker closed GEODE-1664.

Assignee: Anthony Baker

> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Resolved] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread Anthony Baker (JIRA) 

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

Anthony Baker resolved GEODE-1664.
--
Resolution: Fixed

> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Commented] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1664:


Commit 3c5c62fb51e7023aa84419f46355283dacf7251a in incubator-geode's branch 
refs/heads/release/1.0.0-incubating.M3 from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=3c5c62f ]

GEODE-1664: Remove jopt-simple from src LICENSE

The jopt-simple source dependency was replaced by a binary
dependency.


> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Commented] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1664:


Commit 7c9d3a6b175ffa2ea1f447ebe00cf21344154564 in incubator-geode's branch 
refs/heads/release/1.0.0-incubating.M3 from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7c9d3a6 ]

GEODE-1664: Add AOP Alliance to LICENSE


> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Commented] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1664:


Commit cc89b76b5559e582f4583acce02b54bc81554511 in incubator-geode's branch 
refs/heads/release/1.0.0-incubating.M3 from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cc89b76 ]

GEODE-1664: Update SLF4J version in LICENSE


> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Commented] (GEODE-1665) geode-examples bundles gradle wrapper

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1665:


Commit 1fdcdb2840dd7c646f3f6ddc53e5b388c5b59c9b in incubator-geode's branch 
refs/heads/release/1.0.0-incubating.M3 from [~amb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1fdcdb2 ]

GEODE-1665: Remove bundled jar from source distribution

Modified the geode-example to remove the bundled gradle wrapper
jar from the source distribution.


> geode-examples bundles gradle wrapper
> -
>
> Key: GEODE-1665
> URL: https://issues.apache.org/jira/browse/GEODE-1665
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The geode-examples project bundles the gradle wrapper.  This is not allowed 
> as it includes a binary file.
> 1) Remove the wrapper jar.
> 2) Update rat excludes.



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

[jira] [Commented] (GEODE-1644) ClassCastException is thrown with in queries against a map index

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1644:


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

GEODE-1644: ClassCastException is thrown with in queries against a map index


> ClassCastException is thrown with in queries against a map index
> 
>
> Key: GEODE-1644
> URL: https://issues.apache.org/jira/browse/GEODE-1644
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>
> When a query with an in clause is used and queries against a map index, a 
> ClassCastException is thrown.  A map index expects an array where the first 
> key is the index key and the second value is the map index key.



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

[jira] [Commented] (GEODE-11) Lucene Integration

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-11:
--

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

This closes #205

GEODE-11: Adding stats option to list lucene index gfsh command

Added an option to display lucene index stats in the list lucene index command. 
Added junit and dunit tests to verify the same.

GEODE-11: Added describe lucene index gfsh command

Added describe lucene index gfsh command that takes the index name and region 
as arguments and displays information about the lucene index (fields, analyzers 
and stats). Also added junit and dunit tests for the same.

Signed-off-by: Gester Zhou 


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Commented] (GEODE-11) Lucene Integration

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-11:
--

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

This closes #205

GEODE-11: Adding stats option to list lucene index gfsh command

Added an option to display lucene index stats in the list lucene index command. 
Added junit and dunit tests to verify the same.

GEODE-11: Added describe lucene index gfsh command

Added describe lucene index gfsh command that takes the index name and region 
as arguments and displays information about the lucene index (fields, analyzers 
and stats). Also added junit and dunit tests for the same.

Signed-off-by: Gester Zhou 


> Lucene Integration
> --
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
>  Issue Type: New Feature
>  Components: querying
>Reporter: Dan Smith
>Assignee: xiaojian zhou
>
> This is a feature that has been under development for GemFire but was not 
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text 
> searches on data stored in Geode. 



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

[jira] [Updated] (GEODE-1665) geode-examples bundles gradle wrapper

2016-07-14 Thread Anthony Baker (JIRA) 

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

Anthony Baker updated GEODE-1665:
-
Fix Version/s: 1.0.0-incubating.M3

> geode-examples bundles gradle wrapper
> -
>
> Key: GEODE-1665
> URL: https://issues.apache.org/jira/browse/GEODE-1665
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The geode-examples project bundles the gradle wrapper.  This is not allowed 
> as it includes a binary file.
> 1) Remove the wrapper jar.
> 2) Update rat excludes.



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

[jira] [Created] (GEODE-1665) geode-examples bundles gradle wrapper

2016-07-14 Thread Anthony Baker (JIRA) 
Anthony Baker created GEODE-1665:


 Summary: geode-examples bundles gradle wrapper
 Key: GEODE-1665
 URL: https://issues.apache.org/jira/browse/GEODE-1665
 Project: Geode
  Issue Type: Bug
  Components: build
Reporter: Anthony Baker


The geode-examples project bundles the gradle wrapper.  This is not allowed as 
it includes a binary file.

1) Remove the wrapper jar.
2) Update rat excludes.



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

[jira] [Created] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread Anthony Baker (JIRA) 
Anthony Baker created GEODE-1664:


 Summary: Fix M3 license issues
 Key: GEODE-1664
 URL: https://issues.apache.org/jira/browse/GEODE-1664
 Project: Geode
  Issue Type: Bug
Reporter: Anthony Baker


The following binary LICENSE changes are need for the M3 release:

1) Add aopalliance 1.0 (public domain)
2) Update slf4j version to 1.7.21
3) Move jopt-simple declaration from src LICENSE to here




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

[jira] [Updated] (GEODE-1664) Fix M3 license issues

2016-07-14 Thread Anthony Baker (JIRA) 

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

Anthony Baker updated GEODE-1664:
-
Fix Version/s: 1.0.0-incubating.M3

> Fix M3 license issues
> -
>
> Key: GEODE-1664
> URL: https://issues.apache.org/jira/browse/GEODE-1664
> Project: Geode
>  Issue Type: Bug
>Reporter: Anthony Baker
> Fix For: 1.0.0-incubating.M3
>
>
> The following binary LICENSE changes are need for the M3 release:
> 1) Add aopalliance 1.0 (public domain)
> 2) Update slf4j version to 1.7.21
> 3) Move jopt-simple declaration from src LICENSE to here



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

[jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message

2016-07-14 Thread Kevin Duling (JIRA) 

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

Kevin Duling commented on GEODE-746:


Grace and I tracked the first part of this down to a problem in 
{{LauncherLifecycleCommands}}:
{{String locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
  locatorHostName = bindAddr.getCanonicalHostName();
} else {
  locatorHostName = 
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), 
getLocalHost());
}
{code}

This improved things a little.  The system will now connect: {{gfsh start 
locator --name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is 
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
-Dgemfire.load-cluster-configuration-from-dir=false 
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2 
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path: 
/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar

Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099]

Cluster configuration service is up and running.
{noformat}

But now the successfully connected message is showing the wrong IP address.  
Looking at netstat, we can see that the listener is correctly bound to the IP 
address specified:
{noformat}
$ netstat -an | grep 19991
tcp4   0  0  192.168.1.187.19991*.*LISTEN 
{noformat}
Yet the hostname actually resolves to a different NIC: {{ping 
pdx2-office-dhcp9.eng.vmware.com}}
{noformat}
PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes
{noformat}
Both NICs exist on this machine, just one is being erroneously reported: 
{{nestat -rn}}
{noformat}
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use   Netif Expire
default10.118.33.253  UGSc  3600 en4
default192.168.1.253  UGScI  350 en0
{noformat}

Tracing this down, it appears to be an incorrect response from the locator in 
{{ShellCommands.connectToLocator(String host, int port, int timeout, 
Map props)}}

{code}
JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host, 
port, timeout, props);  
// locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099, 
ssl=false, ex=null]”
// host: “192.168.1.187”
// port: 19991
// timeout: 15000
// props: size = 0
{code}


> When starting a locator using --bind-address, gfsh prints incorrect connect 
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
>  Issue Type: Improvement
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1 
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like 
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true 
> -Dgemfire.load-cluster-configuration-from-dir=false 
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true 
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: 
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the 
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind 
> address.



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

[jira] [Commented] (GEODE-1612) CI failure: WanAutoDiscoveryDUnitTest.test_RingTopology

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user nabarunnag opened a pull request:

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

GEODE-1612: Gets a list of random ports at once

* Getting a random port for each locator one by one led to different 
locators getting assigned the same port number
* By getting a list of available ports at one shot reduces the 
possiblity of locators being assigned the same port number
* This will not solve the problem of locators being assigned a port 
which is in use.
* We can't pass 0 as the locator port parameter because we need the 
ring topology before the locators are started.

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

$ git pull https://github.com/nabarunnag/incubator-geode feature/GEODE-1612

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

https://github.com/apache/incubator-geode/pull/204.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 #204


commit 2528e3ba2e19cef10f42eeb9916614d5790f2245
Author: nabarun 
Date:   2016-07-13T18:49:45Z

GEODE-1612: Gets a list of random ports at once

* Getting a random port for each locator one by one led to different 
locators getting assigned the same port number
* By getting a list of available ports at one shot reduces the 
possiblity of locators being assigned the same port number
* This will not solve the problem of locators being assigned a port 
which is in use.
* We can't pass 0 as the locator port parameter because we need the 
ring topology before the locators are started.




> CI failure: WanAutoDiscoveryDUnitTest.test_RingTopology
> ---
>
> Key: GEODE-1612
> URL: https://issues.apache.org/jira/browse/GEODE-1612
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Dan Smith
>  Labels: ci
>
> Revision: 7ad9cc9451212f1c8a0acba3ec78a9eb562d3780 
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest$$Lambda$2185/1936764995.call
>  in VM 0 running on Host doomtwo.gemstone.com with 8 VMs
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
>   at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:320)
>   at 
> com.gemstone.gemfire.internal.cache.wan.misc.WanAutoDiscoveryDUnitTest.test_RingTopology(WanAutoDiscoveryDUnitTest.java:339)
>   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
>   at 
>

[jira] [Commented] (GEODE-1600) DUnitLauncher should not use AvailablePort to pick the locator port

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1600:


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

GEODE-1600: startLocatorAndDS takes 0 as port number parameter

* Use of getAvailableTCP port led to race conditions which led to 
locators being assigned ports in use.
* Use of 0 now assignes a port number to the locator after the server 
is started.
* Code modification to accept 0 as a valid port number until a real 
port number is assigned after the server is started.


> DUnitLauncher should not use AvailablePort to pick the locator port
> ---
>
> Key: GEODE-1600
> URL: https://issues.apache.org/jira/browse/GEODE-1600
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> In a recent dunit precheckin run, I saw a number of tests fail with the below 
> errors
> {noformat}
> 11:38:15 com.gemstone.gemfire.disttx.DistTXDebugDUnitTest > classMethod FAILED
> 11:38:15 java.lang.RuntimeException: Unable to launch dunit VMS
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.lang.RuntimeException: Failed to start locator
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Failed to create server socket 
> on  null[29,649]
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Address already in use
> 11:38:17 
> 11:38:17 com.gemstone.gemfire.disttx.DistTXRestrictionsDUnitTest > 
> testPersistentRestriction FAILED
> 11:38:17 com.gemstone.gemfire.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> 11:38:18 
> 11:38:18 com.gemstone.gemfire.disttx.PRDistTXDUnitTest > 
> testColocationPartitionedRegion FAILED
> 11:38:18 com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.execute.PRTransactionDUnitTest$12.call in 
> VM 0 running on Host zambia.gemstone.com with 4 VMs
> 11:38:18 
> 11:38:18 Caused by:
> 11:38:18 com.gemstone.gemfire.GemFireConfigException: Unable to join 
> the distributed system.  Operation either timed out, was stopped or Locator 
> does not exist.
> {noformat}
> It looks like the issue is that the locator failed to start because the port 
> it was starting on was already used.
> We should refactor the launcher code to call Locator.startLocatorAndDS with a 
> port of 0 and let it pick an open port. That way we should no longer have a 
> chance of port conflicts when launching dunit.



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

[jira] [Commented] (GEODE-1600) DUnitLauncher should not use AvailablePort to pick the locator port

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> DUnitLauncher should not use AvailablePort to pick the locator port
> ---
>
> Key: GEODE-1600
> URL: https://issues.apache.org/jira/browse/GEODE-1600
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> In a recent dunit precheckin run, I saw a number of tests fail with the below 
> errors
> {noformat}
> 11:38:15 com.gemstone.gemfire.disttx.DistTXDebugDUnitTest > classMethod FAILED
> 11:38:15 java.lang.RuntimeException: Unable to launch dunit VMS
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.lang.RuntimeException: Failed to start locator
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Failed to create server socket 
> on  null[29,649]
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Address already in use
> 11:38:17 
> 11:38:17 com.gemstone.gemfire.disttx.DistTXRestrictionsDUnitTest > 
> testPersistentRestriction FAILED
> 11:38:17 com.gemstone.gemfire.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> 11:38:18 
> 11:38:18 com.gemstone.gemfire.disttx.PRDistTXDUnitTest > 
> testColocationPartitionedRegion FAILED
> 11:38:18 com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.execute.PRTransactionDUnitTest$12.call in 
> VM 0 running on Host zambia.gemstone.com with 4 VMs
> 11:38:18 
> 11:38:18 Caused by:
> 11:38:18 com.gemstone.gemfire.GemFireConfigException: Unable to join 
> the distributed system.  Operation either timed out, was stopped or Locator 
> does not exist.
> {noformat}
> It looks like the issue is that the locator failed to start because the port 
> it was starting on was already used.
> We should refactor the launcher code to call Locator.startLocatorAndDS with a 
> port of 0 and let it pick an open port. That way we should no longer have a 
> chance of port conflicts when launching dunit.



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

[jira] [Commented] (GEODE-1600) DUnitLauncher should not use AvailablePort to pick the locator port

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1600:


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

GEODE-1600: startLocatorAndDS takes 0 as port number parameter

* Use of getAvailableTCP port led to race conditions which led to 
locators being assigned ports in use.
* Use of 0 now assignes a port number to the locator after the server 
is started.
* Code modification to accept 0 as a valid port number until a real 
port number is assigned after the server is started.
This closes #202


> DUnitLauncher should not use AvailablePort to pick the locator port
> ---
>
> Key: GEODE-1600
> URL: https://issues.apache.org/jira/browse/GEODE-1600
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> In a recent dunit precheckin run, I saw a number of tests fail with the below 
> errors
> {noformat}
> 11:38:15 com.gemstone.gemfire.disttx.DistTXDebugDUnitTest > classMethod FAILED
> 11:38:15 java.lang.RuntimeException: Unable to launch dunit VMS
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.lang.RuntimeException: Failed to start locator
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Failed to create server socket 
> on  null[29,649]
> 11:38:15 
> 11:38:15 Caused by:
> 11:38:15 java.net.BindException: Address already in use
> 11:38:17 
> 11:38:17 com.gemstone.gemfire.disttx.DistTXRestrictionsDUnitTest > 
> testPersistentRestriction FAILED
> 11:38:17 com.gemstone.gemfire.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> 11:38:18 
> 11:38:18 com.gemstone.gemfire.disttx.PRDistTXDUnitTest > 
> testColocationPartitionedRegion FAILED
> 11:38:18 com.gemstone.gemfire.test.dunit.RMIException: While invoking 
> com.gemstone.gemfire.internal.cache.execute.PRTransactionDUnitTest$12.call in 
> VM 0 running on Host zambia.gemstone.com with 4 VMs
> 11:38:18 
> 11:38:18 Caused by:
> 11:38:18 com.gemstone.gemfire.GemFireConfigException: Unable to join 
> the distributed system.  Operation either timed out, was stopped or Locator 
> does not exist.
> {noformat}
> It looks like the issue is that the locator failed to start because the port 
> it was starting on was already used.
> We should refactor the launcher code to call Locator.startLocatorAndDS with a 
> port of 0 and let it pick an open port. That way we should no longer have a 
> chance of port conflicts when launching dunit.



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

[jira] [Commented] (GEODE-1617) Regions can be created with a variety of characters that are unsupported

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user kirklund commented on the issue:

https://github.com/apache/incubator-geode/pull/201
  
I'm running this change through precheckin.


> Regions can be created with a variety of characters that are unsupported
> 
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
>  and this 
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
>  on the dev forums and [geode 
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
>  region names may only consist of alphanumeric characters, an underscore, and 
> a hyphen.  These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while 
> others cannot be located.



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

[jira] [Commented] (GEODE-1660) geode-core:compileTestJava generates compile warnings

2016-07-14 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> geode-core:compileTestJava generates compile warnings
> -
>
> Key: GEODE-1660
> URL: https://issues.apache.org/jira/browse/GEODE-1660
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> :geode-core:compileTestJava
> /Users/klund/dev/gemfire/open/geode-core/src/test/java/com/gemstone/gemfire/internal/logging/log4j/LogWriterAppenderJUnitTest.java:188:
>  warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
> LogEvent event = 
> Log4jLogEvent.newBuilder().setLevel(Level.INFO).setLoggerFqcn("NAME").setLoggerName("NAME").setMessage(new
>  ParameterizedMessage("LOGEVENT MESSAGE", null)).build();
>   
>   
>  ^
>   cast to Object for a varargs call
>   cast to Object[] for a non-varargs call and to suppress this warning
> /Users/klund/dev/gemfire/open/geode-core/src/test/java/com/gemstone/gemfire/security/templates/LdapUserAuthenticator.java:89:
>  warning: LdapCtxFactory is internal proprietary API and may be removed in a 
> future release
> env.put(Context.INITIAL_CONTEXT_FACTORY, 
> com.sun.jndi.ldap.LdapCtxFactory.class.getName());
>   ^
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for detail



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

[jira] [Commented] (GEODE-1654) Fix javadoc warnings

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1654:


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

GEODE-1654: Fix Javadoc warnings


> Fix javadoc warnings
> 
>
> Key: GEODE-1654
> URL: https://issues.apache.org/jira/browse/GEODE-1654
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.0.0-incubating.M3
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>Priority: Trivial
>
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/cache/tier/sockets/HandShake.java:1797:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:172:
>  warning - @return tag has no arguments.
> * 
> geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java:360:
>  warning - @return tag has no arguments.



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

[jira] [Commented] (GEODE-1656) Fix compilation warnings

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1656:


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

GEODE-1656: fix compilation warnings with @SuppressWarnings annotations


> Fix compilation warnings
> 
>
> Key: GEODE-1656
> URL: https://issues.apache.org/jira/browse/GEODE-1656
> Project: Geode
>  Issue Type: Bug
>  Components: general
>Reporter: Grace Meilen
>Assignee: Grace Meilen
>
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/internal/filter/SessionReplicationIntegrationJUnitTest.java
>  uses unchecked or unsafe operations.
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session/src/main/java/com/gemstone/gemfire/modules/session/installer/JarClassLoader.java
>  uses or overrides a deprecated API.
> * Note: 
> /Users/gmeilen/Desktop/open/extensions/geode-modules-session-internal/src/main/java/com/gemstone/gemfire/modules/session/internal/filter/GemfireHttpSession.java
>  uses or overrides a deprecated API.



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

[jira] [Commented] (GEODE-1660) geode-core:compileTestJava generates compile warnings

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1660:


Commit 5b2898761ee4153284e784fff89985f8e7e4 in incubator-geode's branch 
refs/heads/develop from gmeilen
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=5b28987 ]

GEODE-1660: fix compilation warnings

This closes #200


> geode-core:compileTestJava generates compile warnings
> -
>
> Key: GEODE-1660
> URL: https://issues.apache.org/jira/browse/GEODE-1660
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: Kirk Lund
>Assignee: Grace Meilen
>
> :geode-core:compileTestJava
> /Users/klund/dev/gemfire/open/geode-core/src/test/java/com/gemstone/gemfire/internal/logging/log4j/LogWriterAppenderJUnitTest.java:188:
>  warning: non-varargs call of varargs method with inexact argument type for 
> last parameter;
> LogEvent event = 
> Log4jLogEvent.newBuilder().setLevel(Level.INFO).setLoggerFqcn("NAME").setLoggerName("NAME").setMessage(new
>  ParameterizedMessage("LOGEVENT MESSAGE", null)).build();
>   
>   
>  ^
>   cast to Object for a varargs call
>   cast to Object[] for a non-varargs call and to suppress this warning
> /Users/klund/dev/gemfire/open/geode-core/src/test/java/com/gemstone/gemfire/security/templates/LdapUserAuthenticator.java:89:
>  warning: LdapCtxFactory is internal proprietary API and may be removed in a 
> future release
> env.put(Context.INITIAL_CONTEXT_FACTORY, 
> com.sun.jndi.ldap.LdapCtxFactory.class.getName());
>   ^
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for detail



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

[jira] [Commented] (GEODE-1571) Client security should be able to use Resource:Operation permissions

2016-07-14 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1571:


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

GEODE-1571: fix permission needed for remove data command


> Client security should be able to use Resource:Operation permissions
> 
>
> Key: GEODE-1571
> URL: https://issues.apache.org/jira/browse/GEODE-1571
> Project: Geode
>  Issue Type: Sub-task
>  Components: security
>Reporter: Swapnil Bawaskar
>
> While providing role based access control for JMX and CLI, noun-verby 
> permission of the form of RESOURCE:OPERATION[:REGION] have been introduced. 
> Please refer to the wiki for more details: 
> https://cwiki.apache.org/confluence/display/GEODE/How+to+secure+JMX+and+GFSH
> We now need to provide a new interface so that client-server security can 
> also use these noun-verby permissions.
> To make Geode security "integrated", users will only have to provide an 
> implementation of this new interface and it will work for JMX, gfsh and 
> client-server.
> {{com.gemstone.gemfire.security.AccessControl}} should be deprecated once we 
> have this new interface.



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