Build failed in Jenkins: Atlas-0.8-IntegrationTests #214

2018-07-17 Thread Apache Jenkins Server 
See 


Changes:

[apoorvnaik] ATLAS-2786: Honor ZK server ensemble provided in configuration

--
[...truncated 539.20 KB...]
127.0.0.1 - - [17/Jul/2018:17:55:12 +] "GET 
/api/atlas/v2/search/dsl?offset=0=from+Process=10 HTTP/1.1" 200 - 
"-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:13 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact_daily_mv
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:13 +] "GET 
/api/atlas/v2/lineage/dcf0a272-0355-4f12-9ac0-a6339ae6b2cd?depth=0=BOTH
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/DB?attr:name=Sales HTTP/1.1" 200 - 
"-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=time_dim 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact_daily_mv
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact_monthly_mv
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/LoadProcess?attr:qualifiedName=loadSalesDaily
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/LoadProcess?attr:qualifiedName=loadSalesMonthly
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:15 +] "GET 
/api/atlas/v2/lineage/dcf0a272-0355-4f12-9ac0-a6339ae6b2cd?depth=0=BOTH
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/LoadProcess?attr:qualifiedName=loadSalesDaily
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=time_dim 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact_daily_mv
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=sales_fact 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/DB?attr:name=Sales HTTP/1.1" 200 - 
"-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/guid/1e62ed05-beb5-493a-b4c1-924893a61502/classifications 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/View?attr:qualifiedName=product_dim_view
 HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/v2/entity/uniqueAttribute/type/Table?attr:qualifiedName=product_dim 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4=10=0 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4 HTTP/1.1" 200 - "-" 
"Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4=10=0 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4=10=1 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4=1=0 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
127.0.0.1 - - [17/Jul/2018:17:55:17 +] "GET 
/api/atlas/discovery/search/fulltext?query=dbWzTSHKozP4=1=2 
HTTP/1.1" 200 - "-" "Java/1.8.0_172"
Tests run: 135, Failures: 6, Errors: 0, Skipped: 1, Time elapsed: 208.537 sec 
<<< FAILURE! - in TestSuite
testEnterEmptyValues(org.apache.atlas.CredentialProviderUtilityIT)  Time 
elapsed: 1.221 sec  <<< FAILURE!
java.io.IOException: Invalid secret key format
at com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:856)
at java.security.KeyStore.load(KeyStore.java:1445)
at 
org.apache.hadoop.security.alias.AbstractJavaKeyStoreProvider.(AbstractJavaKeyStoreProvider.java:106)
at

[jira] [Commented] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

2018-07-17 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/ATLAS-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546906#comment-16546906
 ] 

ASF subversion and git services commented on ATLAS-2786:


Commit 6863cd3fcfc1dc08b08734a0911bd1cf2464987e in atlas's branch 
refs/heads/branch-0.8 from apoorvnaik
[ https://git-wip-us.apache.org/repos/asf?p=atlas.git;h=6863cd3 ]

ATLAS-2786: Honor ZK server ensemble provided in configuration

Change-Id: I3153f258276b534e864fb53b8bcc1cd6af936b5b

(cherry picked from commit 89fc835764c28e2f1e6e60ec9337e175bc0c0707)


> [Atlas HA] Zookeeper connection issue
> -
>
> Key: ATLAS-2786
> URL: https://issues.apache.org/jira/browse/ATLAS-2786
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: trunk, 0.8.3, 1.1.0
>
> Attachments: 
> 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch
>
>
> The curator client right now only connects to the very first zookeeper server 
> regardless of the number of zookeeper servers provided in the configuration.
>  
> Due to this behavior if the ZK (that Atlas connected to during startup) goes 
> down then Atlas fails to serve further request while constantly trying to 
> reconnect to the dead ZK server.
>  
> This patch makes the change in configuration parsing to allow fallback to 
> different ZK servers in case the primary goes down.



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

Re: Review Request 67942: ATLAS-2788 : Add policy permissions for tagsync user.

2018-07-17 Thread Sarath Subramanian 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67942/#review206155
---


Ship it!




Ship It!

- Sarath Subramanian


On July 17, 2018, 7:06 a.m., Vishal Suvagia wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67942/
> ---
> 
> (Updated July 17, 2018, 7:06 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, 
> Nixon Rodrigues, and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2788
> https://issues.apache.org/jira/browse/ATLAS-2788
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Tagsync user needs read permissions for accessing Tags / Classification from 
> Atlas-REST when using simple auth.
> PS : Seperate patch for branch-0.8 is attached on Apache JIRA.
> 
> 
> Diffs
> -
> 
>   authorization/src/main/resources/atlas-simple-authz-policy.json 01104a8 
>   authorization/src/test/resources/atlas-simple-authz-policy.json 01104a8 
>   distro/src/conf/atlas-simple-authz-policy.json 01104a8 
> 
> 
> Diff: https://reviews.apache.org/r/67942/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with fresh installation of Atlas and Ranger-Tagsync.
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>

[jira] [Created] (ATLAS-2790) Allow path expressions as attributeNames in Atlas basic search entityFilters

2018-07-17 Thread Barbara Eckman (JIRA) 
Barbara Eckman created ATLAS-2790:
-

 Summary: Allow path expressions as attributeNames in Atlas basic 
search entityFilters
 Key: ATLAS-2790
 URL: https://issues.apache.org/jira/browse/ATLAS-2790
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Reporter: Barbara Eckman


It would be nice if a search on a complex entity could perform a search on 
attributes of nested sub-entities or structs, as well as just top-level 
attributes.  

Here is an example of an Atlas basic search request object:
{
 "typeName": "hive_table",
 "excludeDeletedEntities": true,
 "classification" : "",
 "query": "",
 "limit": 25,
 "offset": 0,
 "entityFilters": {
 "attributeName": "name",
 "operator": "contains",
 "attributeValue": "testtable"
 },
 "tagFilters": null,
 "attributes": [""]
}

Here, attributeName must be one of the top-level attributes of the hive table 
entity.

This ticket requests that path expressions to attributes of sub-entities or 
structs also be allowed as attributeNames, eg column.name  (similar to DSL 
search).   This would execute a search on the name attribute of columns that 
are associated with the hive table.



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

[jira] [Updated] (ATLAS-2786) [Atlas HA] Zookeeper connection issue

2018-07-17 Thread Apoorv Naik (JIRA) 


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

Apoorv Naik updated ATLAS-2786:
---
Fix Version/s: 1.1.0
   0.8.3
   trunk

> [Atlas HA] Zookeeper connection issue
> -
>
> Key: ATLAS-2786
> URL: https://issues.apache.org/jira/browse/ATLAS-2786
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1, 0.8.2, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Critical
> Fix For: trunk, 0.8.3, 1.1.0
>
> Attachments: 
> 0001-ATLAS-2786-Honor-ZK-server-ensemble-provided-in-conf.patch
>
>
> The curator client right now only connects to the very first zookeeper server 
> regardless of the number of zookeeper servers provided in the configuration.
>  
> Due to this behavior if the ZK (that Atlas connected to during startup) goes 
> down then Atlas fails to serve further request while constantly trying to 
> reconnect to the dead ZK server.
>  
> This patch makes the change in configuration parsing to allow fallback to 
> different ZK servers in case the primary goes down.



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

[jira] [Commented] (ATLAS-2788) Add policy permissions for tagsync user

2018-07-17 Thread Vishal Suvagia (JIRA) 


[ 
https://issues.apache.org/jira/browse/ATLAS-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546661#comment-16546661
 ] 

Vishal Suvagia commented on ATLAS-2788:
---

Review request for master branch.

> Add policy permissions for tagsync user
> ---
>
> Key: ATLAS-2788
> URL: https://issues.apache.org/jira/browse/ATLAS-2788
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: ATLAS-2788-branch-0.8.patch, ATLAS-2788-master.patch
>
>
> Tagsync user needs read permissions for accessing Tags / Classification from 
> Atlas-REST when using simple auth.



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

Review Request 67942: ATLAS-2788 : Add policy permissions for tagsync user.

2018-07-17 Thread Vishal Suvagia via Review Board 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/67942/
---

Review request for atlas, Apoorv Naik, Ashutosh Mestry, Madhan Neethiraj, Nixon 
Rodrigues, and Sarath Subramanian.


Bugs: ATLAS-2788
https://issues.apache.org/jira/browse/ATLAS-2788


Repository: atlas


Description
---

Tagsync user needs read permissions for accessing Tags / Classification from 
Atlas-REST when using simple auth.
PS : Seperate patch for branch-0.8 is attached on Apache JIRA.


Diffs
-

  authorization/src/main/resources/atlas-simple-authz-policy.json 01104a8 
  authorization/src/test/resources/atlas-simple-authz-policy.json 01104a8 
  distro/src/conf/atlas-simple-authz-policy.json 01104a8 


Diff: https://reviews.apache.org/r/67942/diff/1/


Testing
---

Tested with fresh installation of Atlas and Ranger-Tagsync.


Thanks,

Vishal Suvagia

[jira] [Created] (ATLAS-2789) Prometheus /metrics http endpoint for monitoring integration

2018-07-17 Thread Hari Sekhon (JIRA) 
Hari Sekhon created ATLAS-2789:
--

 Summary: Prometheus /metrics http endpoint for monitoring 
integration
 Key: ATLAS-2789
 URL: https://issues.apache.org/jira/browse/ATLAS-2789
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core, atlas-intg
Affects Versions: 0.8.2
Reporter: Hari Sekhon


Feature Request to add Prometheus /metrics http endpoint for monitoring 
integration:

https://prometheus.io/docs/prometheus/latest/configuration/configuration/#%3Cscrape_config%3E



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

[jira] [Commented] (ATLAS-2759) Atlas start up fail with error Error creating bean with name 'setupSteps' defined in URL [jar:file:/data/apache-atlas/apache-atlas-1.0.0/server /webapp/atlas/WEB-INF/l

2018-07-17 Thread Mindaugas Pocius (JIRA) 


[ 
https://issues.apache.org/jira/browse/ATLAS-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546611#comment-16546611
 ] 

Mindaugas Pocius commented on ATLAS-2759:
-

Set this to false:
{code:java}
atlas.server.run.setup.on.start=false
{code}

> Atlas start up fail with error  Error creating bean with name 'setupSteps' 
> defined in URL [jar:file:/data/apache-atlas/apache-atlas-1.0.0/server 
> /webapp/atlas/WEB-INF/lib/atlas-webapp-1.0.0.jar!/org/apache/atlas/web/setup/SetupSteps.class]:"
> -
>
> Key: ATLAS-2759
> URL: https://issues.apache.org/jira/browse/ATLAS-2759
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core, atlas-webui
>Reporter: Mahesh Kakol
>Priority: Major
>
> Kindly help me fix this issue,
> {code:java}
> 2018-06-15 21:51:39,259 WARN - [main:] ~ Failed startup of context 
> o.e.j.w.WebAppContext@4e25282d{/,file:///data/apache-atlas/apache-atlas-1.0.0/server/webapp/atlas/,UNAVAILABLE
> }{/data/apache-atlas/apache-atlas-1.0.0/server/webapp/atlas} 
> (WebAppContext:529)
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'setupSteps' defined in URL 
> [jar:file:/data/apache-atlas/apache-atlas-1.0.0/server
> /webapp/atlas/WEB-INF/lib/atlas-webapp-1.0.0.jar!/org/apache/atlas/web/setup/SetupSteps.class]:
>  Unsatisfied dependency expressed through constructor parameter 0; nested 
> exception
> is org.springframework.beans.factory.NoSuchBeanDefinitionException: No 
> qualifying bean of type 'java.util.Set' 
> available: expected at least 1 b
> ean which qualifies as autowire candidate. Dependency annotations: {}
> at 
> org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:749)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:189)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1201)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1103)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)
> at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
> at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
> at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
> at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
> at 
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443)
> at 
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325)
> at 
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
> at 
> org.apache.atlas.web.setup.KerberosAwareListener.contextInitialized(KerberosAwareListener.java:31)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:843)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:816)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:345)
> at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1404)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1366)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262)
> at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:520)
> at 
>

[jira] [Updated] (ATLAS-2788) Add policy permissions for tagsync user

2018-07-17 Thread Vishal Suvagia (JIRA) 


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

Vishal Suvagia updated ATLAS-2788:
--
Attachment: ATLAS-2788-branch-0.8.patch
ATLAS-2788-master.patch

> Add policy permissions for tagsync user
> ---
>
> Key: ATLAS-2788
> URL: https://issues.apache.org/jira/browse/ATLAS-2788
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8.2, 1.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: ATLAS-2788-branch-0.8.patch, ATLAS-2788-master.patch
>
>
> Tagsync user needs read permissions for accessing Tags / Classification from 
> Atlas-REST when using simple auth.



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

Jenkins build is back to normal : Atlas-1.0-IntegrationTests #536

2018-07-17 Thread Apache Jenkins Server 
See

Jenkins build is back to normal : PreCommit-ATLAS-Build-Test #518-master-ATLAS-2788-master.patch

2018-07-17 Thread Apache Jenkins Server 
See

Build failed in Jenkins: Atlas-1.0-IntegrationTests #535

2018-07-17 Thread Apache Jenkins Server 
See 


--
[...truncated 648.40 KB...]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start 
(ContainerLifeCycle.java:131)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart 
(ContainerLifeCycle.java:113)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart 
(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start 
(ContainerLifeCycle.java:131)
at org.eclipse.jetty.server.Server.start (Server.java:422)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart 
(ContainerLifeCycle.java:105)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart 
(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart (Server.java:389)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start 
(AbstractLifeCycle.java:68)
at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty 
(AbstractJettyMojo.java:460)
at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.execute 
(AbstractJettyMojo.java:328)
at org.eclipse.jetty.maven.plugin.JettyRunWarMojo.execute 
(JettyRunWarMojo.java:64)
at org.eclipse.jetty.maven.plugin.JettyDeployWar.execute 
(JettyDeployWar.java:65)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
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:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0 (Native Method)
at sun.nio.ch.Net.bind (Net.java:433)
at sun.nio.ch.Net.bind (Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind 
(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind (ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind (ServerSocketAdaptor.java:67)
at org.apache.zookeeper.server.NIOServerCnxnFactory.configure 
(NIOServerCnxnFactory.java:95)
at org.apache.zookeeper.server.ServerCnxnFactory.createFactory 
(ServerCnxnFactory.java:126)
at org.apache.atlas.kafka.EmbeddedKafkaServer.startZk 
(EmbeddedKafkaServer.java:116)
at org.apache.atlas.kafka.EmbeddedKafkaServer.start 
(EmbeddedKafkaServer.java:80)
at org.apache.atlas.service.Services.start (Services.java:67)
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:498)
at 
org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke
 (InitDestroyAnnotationBeanPostProcessor.java:366)
at 
org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods
 (InitDestroyAnnotationBeanPostProcessor.java:311)
at

Jenkins build is back to normal : Atlas-master-IntegrationTests #1884

2018-07-17 Thread Apache Jenkins Server 
See