[jira] [Updated] (KNOX-1149) HBase High Availability Fails with Kerberos Secured Cluster

2018-01-09 Thread Rick Kellogg (JIRA) 

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

Rick Kellogg updated KNOX-1149:
---
Attachment: KNOX-1149.patch

Updated patch attached which supports Kerberos/SPNEGO challenge/response during 
ping operations.  This fix should also correct issues with other Kerberos 
protected services.  We might want to reconsider slipping this into 1.0.0 if 
someone else has some bandwidth for testing.

> HBase High Availability Fails with Kerberos Secured Cluster
> ---
>
> Key: KNOX-1149
> URL: https://issues.apache.org/jira/browse/KNOX-1149
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.13.0, 0.14.0
>Reporter: Rick Kellogg
>Assignee: Rick Kellogg
> Fix For: 1.1.0
>
> Attachments: KNOX-1149.patch
>
>
> When HBase is run on a Kerberos secured cluster, the registration of the 
> Region Servers is stored in ZooKeeper under a different path.  The 
> HBaseZookeeperURLManager class used to support high availability in Knox 
> needs to be updated to look in both locations and then ping for availability.



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

[jira] [Updated] (KNOX-1149) HBase High Availability Fails with Kerberos Secured Cluster

2018-01-09 Thread Rick Kellogg (JIRA) 

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

Rick Kellogg updated KNOX-1149:
---
Attachment: (was: KNOX-1149.patch)

> HBase High Availability Fails with Kerberos Secured Cluster
> ---
>
> Key: KNOX-1149
> URL: https://issues.apache.org/jira/browse/KNOX-1149
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.13.0, 0.14.0
>Reporter: Rick Kellogg
>Assignee: Rick Kellogg
> Fix For: 1.1.0
>
>
> When HBase is run on a Kerberos secured cluster, the registration of the 
> Region Servers is stored in ZooKeeper under a different path.  The 
> HBaseZookeeperURLManager class used to support high availability in Knox 
> needs to be updated to look in both locations and then ping for availability.



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

[jira] [Updated] (KNOX-1165) Knox - Another unnamed CacheManager already exists in the same VM.

2018-01-09 Thread Larry McCay (JIRA) 

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

Larry McCay updated KNOX-1165:
--
Fix Version/s: 1.1.0

> Knox - Another unnamed CacheManager already exists in the same VM.
> --
>
> Key: KNOX-1165
> URL: https://issues.apache.org/jira/browse/KNOX-1165
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxSSO, Server
>Affects Versions: 0.12.0
> Environment: JDK 1.8
> CentOS-6 (64bit)
>Reporter: Ernani Pereira de Mattos Junior
>Priority: Critical
>  Labels: patch
> Fix For: 1.1.0
>
>
> PROBLEM: 
> Issue is described on the note ""Error:Shiro environment initialization 
> failed" when starting KNOX"; 
>  
> ERROR env.EnvironmentLoader (EnvironmentLoader.java:initEnvironment(146)) - 
> Shiro environment initialization failed 
> org.apache.shiro.cache.CacheException: net.sf.ehcache.CacheException: Another 
> unnamed CacheManager already exists in the same VM. Please provide unique 
> names for each CacheManager in the config or do one of following: 
> After implementing the solution of creating a new ehcache.xml and reference 
> as  we still see the issue: 
> Caused by: net.sf.ehcache.CacheException: Another CacheManager with same name 
> 'knox-tp' already exists in the same VM. Please provide unique names for each 
> CacheManager in the config or do one of following:
> STEPS TO REPRODUCE: 
> When enabling the following parameters: 
>  
> main.cacheManager 
> org.apache.shiro.cache.ehcache.EhCacheManager 
>  
>  
> main.securityManager.cacheManager 
> $cacheManager 
>  
>  
> main.ldapRealm.authenticationCachingEnabled 
> true 
>  
> MORE INFO: 
> This KNOX-804 was open to solve this same issue but is not documented 
> anywhere, but we can see the coding changes in GitHub.
> -> The issue seems to be a racing condition on the Shiro lib class, in which 
> depending on the processing power of the server there are two threads within 
> the same "if" statement;
> ref: 
> https://github.com/apache/shiro/blob/master/support/ehcache/src/main/java/org/apache/shiro/cache/ehcache/EhCacheManager.java
>  
> 1. The Default constructor only builds the Object, and does not do much: 
> /** 
> * Default no argument constructor 
> */ 
> public EhCacheManager() { 
> } 
> 2. Accordingly with shiro documentation: 
> /** 
> * Initializes this instance. 
> *  
> * If a {@link #setCacheManager CacheManager} has been 
> * explicitly set (e.g. via Dependency Injection or programmatically) prior to 
> calling this 
> * method, this method does nothing. 
> *  
> * However, if no {@code CacheManager} has been set, the default Ehcache 
> singleton will be initialized, where 
> * Ehcache will look for an {@code ehcache.xml} file at the root of the 
> classpath. If one is not found, 
> * Ehcache will use its own failsafe configuration file. 
> *  
> * Because Shiro cannot use the failsafe defaults (fail-safe expunges cached 
> objects after 2 minutes, 
> * something not desirable for Shiro sessions), this class manages an internal 
> default configuration for 
> * this case. 
> * 
> * @throws org.apache.shiro.cache.CacheException 
> * if there are any CacheExceptions thrown by EhCache. 
> * @see net.sf.ehcache.CacheManager#create 
> */ 
> public final void init() throws CacheException { 
> ensureCacheManager(); 
> } 
> private net.sf.ehcache.CacheManager ensureCacheManager() { 
> ***It fails in here. 
> } 
> 2.1 This is the head of the exception: 
> The source of the existing CacheManager is: InputStreamConfigurationSource 
> [stream=java.io.BufferedInputStream@675ffd1d] 
> at 
> org.apache.shiro.cache.ehcache.EhCacheManager.ensureCacheManager(EhCacheManager.java:224)
>  
> at 
> org.apache.shiro.cache.ehcache.EhCacheManager.init(EhCacheManager.java:199) 
> at org.apache.shiro.util.LifecycleUtils.init(LifecycleUtils.java:45) 
> at org.apache.shiro.util.LifecycleUtils.init(LifecycleUtils.java:40) 
> 3. Starting from Knox-804, the KnoxCacheManager was introduced. 
> public class KnoxCacheManager extends EhCacheManager { 
> + 
> + public KnoxCacheManager() { 
> + setCacheManager(net.sf.ehcache.CacheManager.create()); 
> + } 
> +} 
> *Remember that Init() will do nothing if anything in case the setCacheManager 
> is explicitly set. 
> ref: 
> https://github.com/apache/knox/commit/f9d8e07d768459240c8665f139cc140575dc5216



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

[jira] [Commented] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319039#comment-16319039
 ] 

ASF subversion and git services commented on KNOX-1161:
---

Commit 99e6a54afb53fdd8b4311f9a5892698d2551c635 in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=99e6a54 ]

KNOX-1161 - Update hadoop dependencies to Hadoop 3 (Colm O hEigeartaigh, 
reviewed by Sandeep More)


> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Commented] (KNOX-998) Rename class packages to org.apache.knox.gateway

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319041#comment-16319041
 ] 

ASF subversion and git services commented on KNOX-998:
--

Commit 92e2ec59a5940a9e7c67ec5cd29044f811dee40a in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~moresandeep]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=92e2ec5 ]

KNOX-998 - Merge from 0.14.0 master


> Rename class packages to org.apache.knox.gateway
> 
>
> Key: KNOX-998
> URL: https://issues.apache.org/jira/browse/KNOX-998
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
>
> Update the package names in order to remove "hadoop" from the class packages 
> throughout  Apache Knox codebase. Currently, the package are some derivative 
> of "org.apache.hadoop.gateway...". The intent of this improvement is to make 
> the class packages rooted at "org.apache.knox.gateway...". We will have to 
> determine what is needed to be backward compatible for any consumers that 
> have extended our existing classes however.



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

[jira] [Commented] (KNOX-998) Rename class packages to org.apache.knox.gateway

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319040#comment-16319040
 ] 

ASF subversion and git services commented on KNOX-998:
--

Commit e5fd0622493a7e3c62811ea03ff7931c979dd87a in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~moresandeep]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=e5fd062 ]

Merge branch 'master' into KNOX-998-Package_Restructuring

# Conflicts:
#   
gateway-server/src/main/java/org/apache/knox/gateway/services/topology/impl/DefaultTopologyService.java


> Rename class packages to org.apache.knox.gateway
> 
>
> Key: KNOX-998
> URL: https://issues.apache.org/jira/browse/KNOX-998
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Server
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
>
> Update the package names in order to remove "hadoop" from the class packages 
> throughout  Apache Knox codebase. Currently, the package are some derivative 
> of "org.apache.hadoop.gateway...". The intent of this improvement is to make 
> the class packages rooted at "org.apache.knox.gateway...". We will have to 
> determine what is needed to be backward compatible for any consumers that 
> have extended our existing classes however.



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

[jira] [Commented] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319038#comment-16319038
 ] 

ASF subversion and git services commented on KNOX-1161:
---

Commit 772bc33d48dd37be5cd098992df3e50db24326f3 in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~moresandeep]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=772bc33 ]

KNOX-1161 - Update hadoop dependencies to hadoop 3


> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Commented] (KNOX-1116) Builds of src distributions result in unexpected result from gateway version API

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319037#comment-16319037
 ] 

ASF subversion and git services commented on KNOX-1116:
---

Commit 6d4756f3d6b6c16949aec2580a5b1698ea69a3eb in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=6d4756f ]

KNOX-1116 - Builds of src distributions result in unexpected result from 
gateway version API.


> Builds of src distributions result in unexpected result from gateway version 
> API
> 
>
> Key: KNOX-1116
> URL: https://issues.apache.org/jira/browse/KNOX-1116
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: KNOX-1116.patch
>
>
> When a Knox build is executed outside of a git repo (e.g., src 
> distributions), then the build.hash property in build.properties is not 
> populated with an actual value.
> This manifests as an unexpected response to the gateway version API:
> {
> "ServerVersion" : {
>"version" : "0.14.0",
>"hash" : "${buildNumber}"
> }
> This is due to the fact that the buildnumber-maven-plugin attempts to invoke 
> 'git rev-parse --verify HEAD', which fails because it's not in a git repo.
> This plugin apparently has a facility for specifying an alternate value when 
> an scm error is encountered. It would be nice if Knox could employ that 
> facility to provide a better value than ${buildNumber} in these cases.



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

[jira] [Commented] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319034#comment-16319034
 ] 

ASF subversion and git services commented on KNOX-1137:
---

Commit 7e03a9cf1714747df01c4fa4afc00615feafa8c5 in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7e03a9c ]

KNOX-1137


> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



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

[jira] [Commented] (KNOX-1043) Ambari Service Discovery Support for HA-Enabled Services

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319036#comment-16319036
 ] 

ASF subversion and git services commented on KNOX-1043:
---

Commit 348c4d7def61f6296a7cf192ed00e38a8e5c3714 in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=348c4d7 ]

KNOX-1043


> Ambari Service Discovery Support for HA-Enabled Services
> 
>
> Key: KNOX-1043
> URL: https://issues.apache.org/jira/browse/KNOX-1043
> Project: Apache Knox
>  Issue Type: Sub-task
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
>  Labels: kip-8
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1043.patch
>
>
> Make sure that Ambari ServiceDiscovery correctly supports scenarios involving 
> HA-enabled Hadoop services.



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

[jira] [Commented] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319035#comment-16319035
 ] 

ASF subversion and git services commented on KNOX-1144:
---

Commit a438bcc1e4dec613f078ecea25bb177a3904a3a7 in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~pzamp...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=a438bcc ]

KNOX-1144


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



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

[jira] [Commented] (KNOX-1141) Coverity Issues Reported For AmbariConfigurationMonitor

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319033#comment-16319033
 ] 

ASF subversion and git services commented on KNOX-1141:
---

Commit 7d42ffd065c66d810a52a90f8c2dace55f3aceed in knox's branch 
refs/heads/KNOX-998-Package_Restructuring from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=7d42ffd ]

KNOX-1141


> Coverity Issues Reported For AmbariConfigurationMonitor
> ---
>
> Key: KNOX-1141
> URL: https://issues.apache.org/jira/browse/KNOX-1141
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 1.0.0, 0.14.1
>
> Attachments: KNOX-1141.patch
>
>
> *** CID 1383538:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  436 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.getUpdatedConfigVersions(java.lang.String,
>  java.lang.String)()
> *** CID 1383537:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  211 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.persist(java.util.Properties,
>  java.io.File)()
> *** CID 1383536:  Null pointer dereferences  (NULL_RETURNS)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  148 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()
> *** CID 1383535:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  119 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadDiscoveryConfiguration()()
> *** CID 1383534:  Resource leaks  (RESOURCE_LEAK)
> /gateway-discovery-ambari/src/main/java/org/apache/hadoop/gateway/topology/discovery/ambari/AmbariConfigurationMonitor.java:
>  152 in 
> org.apache.hadoop.gateway.topology.discovery.ambari.AmbariConfigurationMonitor.loadClusterVersionData()()



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

[jira] [Resolved] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread Colm O hEigeartaigh (JIRA) 

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

Colm O hEigeartaigh resolved KNOX-1161.
---
Resolution: Fixed

> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Commented] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318701#comment-16318701
 ] 

ASF subversion and git services commented on KNOX-1161:
---

Commit 99e6a54afb53fdd8b4311f9a5892698d2551c635 in knox's branch 
refs/heads/master from [~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=99e6a54 ]

KNOX-1161 - Update hadoop dependencies to Hadoop 3 (Colm O hEigeartaigh, 
reviewed by Sandeep More)


> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Commented] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread Sandeep More (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318678#comment-16318678
 ] 

Sandeep More commented on KNOX-1161:


+1 !! 
Looks good, and thanks for RE2J license and exclusion of Kerby jars. 

> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Commented] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread Colm O hEigeartaigh (JIRA) 

[ 
https://issues.apache.org/jira/browse/KNOX-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318627#comment-16318627
 ] 

Colm O hEigeartaigh commented on KNOX-1161:
---

Thanks [~moresandeep], I updated the patch to fix the license issue + exclude 
the Kerby deps from the distribution, please take a look when you get a chance 
+ I will commit it then.

> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Updated] (KNOX-1161) Update hadoop dependencies to Hadoop 3

2018-01-09 Thread Colm O hEigeartaigh (JIRA) 

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

Colm O hEigeartaigh updated KNOX-1161:
--
Attachment: KNOX-1161-revised.patch.2

An update to the previous patch to add the RE2J license + exclude the Kerby 
jars from the distribution deps.

> Update hadoop dependencies to Hadoop 3
> --
>
> Key: KNOX-1161
> URL: https://issues.apache.org/jira/browse/KNOX-1161
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: Build
>Reporter: Sandeep More
>Assignee: Sandeep More
> Fix For: 1.0.0
>
> Attachments: KNOX-1161-revised.patch, KNOX-1161-revised.patch.2, 
> KNOX-1161.001.patch
>
>
> With the release of Hadoop 3 the upcoming release of Knox 1.0.0 should use 
> Hadoop 3 dependencies. 



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

[jira] [Created] (KNOX-1165) Knox - Another unnamed CacheManager already exists in the same VM.

2018-01-09 Thread Ernani Pereira de Mattos Junior (JIRA) 
Ernani Pereira de Mattos Junior created KNOX-1165:
-

 Summary: Knox - Another unnamed CacheManager already exists in the 
same VM.
 Key: KNOX-1165
 URL: https://issues.apache.org/jira/browse/KNOX-1165
 Project: Apache Knox
  Issue Type: Bug
  Components: KnoxSSO, Server
Affects Versions: 0.12.0
 Environment: JDK 1.8
CentOS-6 (64bit)
Reporter: Ernani Pereira de Mattos Junior
Priority: Critical


PROBLEM: 
Issue is described on the note ""Error:Shiro environment initialization failed" 
when starting KNOX"; 
 
ERROR env.EnvironmentLoader (EnvironmentLoader.java:initEnvironment(146)) - 
Shiro environment initialization failed 
org.apache.shiro.cache.CacheException: net.sf.ehcache.CacheException: Another 
unnamed CacheManager already exists in the same VM. Please provide unique names 
for each CacheManager in the config or do one of following: 

After implementing the solution of creating a new ehcache.xml and reference as 
 we still see the issue: 

Caused by: net.sf.ehcache.CacheException: Another CacheManager with same name 
'knox-tp' already exists in the same VM. Please provide unique names for each 
CacheManager in the config or do one of following:

STEPS TO REPRODUCE: 
When enabling the following parameters: 

 
main.cacheManager 
org.apache.shiro.cache.ehcache.EhCacheManager 
 
 
main.securityManager.cacheManager 
$cacheManager 
 
 
main.ldapRealm.authenticationCachingEnabled 
true 
 


MORE INFO: 
This KNOX-804 was open to solve this same issue but is not documented anywhere, 
but we can see the coding changes in GitHub.

-> The issue seems to be a racing condition on the Shiro lib class, in which 
depending on the processing power of the server there are two threads within 
the same "if" statement;

ref: 
https://github.com/apache/shiro/blob/master/support/ehcache/src/main/java/org/apache/shiro/cache/ehcache/EhCacheManager.java
 

1. The Default constructor only builds the Object, and does not do much: 
/** 
* Default no argument constructor 
*/ 
public EhCacheManager() { 
} 


2. Accordingly with shiro documentation: 
/** 
* Initializes this instance. 
*  
* If a {@link #setCacheManager CacheManager} has been 
* explicitly set (e.g. via Dependency Injection or programmatically) prior to 
calling this 
* method, this method does nothing. 
*  
* However, if no {@code CacheManager} has been set, the default Ehcache 
singleton will be initialized, where 
* Ehcache will look for an {@code ehcache.xml} file at the root of the 
classpath. If one is not found, 
* Ehcache will use its own failsafe configuration file. 
*  
* Because Shiro cannot use the failsafe defaults (fail-safe expunges cached 
objects after 2 minutes, 
* something not desirable for Shiro sessions), this class manages an internal 
default configuration for 
* this case. 
* 
* @throws org.apache.shiro.cache.CacheException 
* if there are any CacheExceptions thrown by EhCache. 
* @see net.sf.ehcache.CacheManager#create 
*/ 
public final void init() throws CacheException { 
ensureCacheManager(); 
} 

private net.sf.ehcache.CacheManager ensureCacheManager() { 
***It fails in here. 
} 


2.1 This is the head of the exception: 
The source of the existing CacheManager is: InputStreamConfigurationSource 
[stream=java.io.BufferedInputStream@675ffd1d] 
at 
org.apache.shiro.cache.ehcache.EhCacheManager.ensureCacheManager(EhCacheManager.java:224)
 
at org.apache.shiro.cache.ehcache.EhCacheManager.init(EhCacheManager.java:199) 
at org.apache.shiro.util.LifecycleUtils.init(LifecycleUtils.java:45) 
at org.apache.shiro.util.LifecycleUtils.init(LifecycleUtils.java:40) 


3. Starting from Knox-804, the KnoxCacheManager was introduced. 
public class KnoxCacheManager extends EhCacheManager { 
+ 
+ public KnoxCacheManager() { 
+ setCacheManager(net.sf.ehcache.CacheManager.create()); 
+ } 
+} 

*Remember that Init() will do nothing if anything in case the setCacheManager 
is explicitly set. 

ref: 
https://github.com/apache/knox/commit/f9d8e07d768459240c8665f139cc140575dc5216





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

Build failed in Jenkins: Knox-master-patch-scan #68550

2018-01-09 Thread Apache Jenkins Server 
See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/knox.git # timeout=10
Fetching upstream changes from https://github.com/apache/knox.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/apache/knox.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 772bc33d48dd37be5cd098992df3e50db24326f3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 772bc33d48dd37be5cd098992df3e50db24326f3
Commit message: "KNOX-1161 - Update hadoop dependencies to hadoop 3"
 > git rev-list 772bc33d48dd37be5cd098992df3e50db24326f3 # timeout=10
[Knox-master-patch-scan] $ /bin/bash /tmp/jenkins1116372419195825935.sh
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 
491440 491440 0  46894  0 --:--:--  0:00:01 --:--:-- 46937
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure