[teiid-issues] [JBoss JIRA] (TEIID-4664) Arquillian test failed due to new added ftp connector

Arquillian test failed due to new added ftp connector ----------------------------------------------------- Key: TEIID-4664 URL: https://issues.jboss.org/browse/TEIID-4664 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 9.2 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.2 Currently rest war generated works fine, but it may throw a duplicate resource error, if restart Server which already have the deployment of rest war: {code} 10:42:01,080 ERROR [org.jboss.as.controller.management-operation] (Worker2_async-teiid-threads4) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "PortfolioRest_1.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]" 10:42:01,087 WARN [org.teiid.RUNTIME] (Worker2_async-teiid-threads4) TEIID50109 Failed to deploy PortfolioRest_1.war: org.teiid.adminapi.AdminProcessingException: TEIID70006 {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"PortfolioRest_1.war\")]"}} at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.execute(AdminFactory.java:623) at org.teiid.adminapi.jboss.AdminFactory$AdminImpl.deploy(AdminFactory.java:921) at org.teiid.jboss.ResteasyEnabler$1.run(ResteasyEnabler.java:94) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} How to reproduce 1. make sure rest quick start work(https://teiid.gitbooks.io/teiid-quickstarts/content/vdb-restservice/) 2. restart server