From issues at jboss.org Wed Jun 3 08:31:02 2015 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 3 Jun 2015 08:31:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-471) GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException In-Reply-To: References: Message-ID: Ji?? ?tefek created ARQGRA-471: ---------------------------------- Summary: GrapheneContextualHandler: do not wrap AssertionErrors in IllegalStateException Key: ARQGRA-471 URL: https://issues.jboss.org/browse/ARQGRA-471 Project: Arquillian Graphene Issue Type: Enhancement Affects Versions: 2.1.0.Alpha2 Reporter: Ji?? ?tefek Priority: Trivial When you perform an assertion in e.g. a page fragment, which leads to throwing an AssertionError, the error is wrapped in IllegalStateException. This is imho an unwanted behaviour and these errors should be forwarded. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jun 8 16:47:01 2015 From: issues at jboss.org (Aslak Knutsen (JIRA)) Date: Mon, 8 Jun 2015 16:47:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1957) Internal TestResult in After is not correct when Test is failing in standalone mode In-Reply-To: References: Message-ID: Aslak Knutsen created ARQ-1957: ---------------------------------- Summary: Internal TestResult in After is not correct when Test is failing in standalone mode Key: ARQ-1957 URL: https://issues.jboss.org/browse/ARQ-1957 Project: Arquillian Issue Type: Bug Components: Base Implementation Affects Versions: 1.1.8.Final Reporter: Aslak Knutsen Assignee: Aslak Knutsen -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jun 9 09:57:06 2015 From: issues at jboss.org (Jozef Hartinger (JIRA)) Date: Tue, 9 Jun 2015 09:57:06 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-328) EJB-API dependencies in Weld EE container should be optional (causes failures on boot) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076107#comment-13076107 ] Jozef Hartinger commented on ARQ-328: ------------------------------------- This also causes problems with DeltaSpike > EJB-API dependencies in Weld EE container should be optional (causes failures on boot) > -------------------------------------------------------------------------------------- > > Key: ARQ-328 > URL: https://issues.jboss.org/browse/ARQ-328 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > > EJB APIs should be optional. If users do not supply the API jars, then EJB services should not attempt to load. This would enable easier configuration for those users who do not need EJB services, who only want Weld in EE-like container. > Currently the ejb-api maven dependency is required. > java.lang.NoClassDefFoundError: javax/ejb/Stateless > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.findEjbs(Ejbs.java:38) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.createEjbDescriptors(Ejbs.java:25) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.BeanDeploymentArchiveImpl.(BeanDeploymentArchiveImpl.java:81) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.(TestContainer.java:215) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:76) > at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:62) > at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:50) > at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) > at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) > at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:96) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:162) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) > Caused by: java.lang.ClassNotFoundException: javax.ejb.Stateless > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > ... 28 more -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue Jun 9 09:58:07 2015 From: issues at jboss.org (Jozef Hartinger (JIRA)) Date: Tue, 9 Jun 2015 09:58:07 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-328) EJB-API dependencies in Weld EE container should be optional (causes failures on boot) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076109#comment-13076109 ] Jozef Hartinger commented on ARQ-328: ------------------------------------- https://github.com/arquillian/arquillian-container-weld/pull/19 > EJB-API dependencies in Weld EE container should be optional (causes failures on boot) > -------------------------------------------------------------------------------------- > > Key: ARQ-328 > URL: https://issues.jboss.org/browse/ARQ-328 > Project: Arquillian > Issue Type: Feature Request > Components: Weld Containers > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > > EJB APIs should be optional. If users do not supply the API jars, then EJB services should not attempt to load. This would enable easier configuration for those users who do not need EJB services, who only want Weld in EE-like container. > Currently the ejb-api maven dependency is required. > java.lang.NoClassDefFoundError: javax/ejb/Stateless > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.findEjbs(Ejbs.java:38) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.createEjbDescriptors(Ejbs.java:25) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.BeanDeploymentArchiveImpl.(BeanDeploymentArchiveImpl.java:81) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.(TestContainer.java:215) > at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:76) > at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:62) > at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(ContainerDeployer.java:50) > at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) > at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) > at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:96) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:162) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:24) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) > Caused by: java.lang.ClassNotFoundException: javax.ejb.Stateless > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > ... 28 more -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 10 10:14:02 2015 From: issues at jboss.org (Matous Jobanek (JIRA)) Date: Wed, 10 Jun 2015 10:14:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1954) Support @Rule enrichement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076849#comment-13076849 ] Matous Jobanek commented on ARQ-1954: ------------------------------------- PR sent https://github.com/arquillian/arquillian-core/pull/85 > Support @Rule enrichement > ------------------------- > > Key: ARQ-1954 > URL: https://issues.jboss.org/browse/ARQ-1954 > Project: Arquillian > Issue Type: Feature Request > Components: Base Implementation > Affects Versions: 1.1.8.Final > Reporter: Karel Piwko > > Arquillian should by default enrich JUnit @Rule statements. > Similarly to https://github.com/aerogear/aerogear-testing-tools/blob/master/arquillian-rule/src/test/java/org/jboss/aerogear/arquillian/junit/RuleInjectionTest.java -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 11 08:45:04 2015 From: issues at jboss.org (Krassimir Valev (JIRA)) Date: Thu, 11 Jun 2015 08:45:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1958) Delete temporary instance root for Embedded Tomcat on exit In-Reply-To: References: Message-ID: Krassimir Valev created ARQ-1958: ------------------------------------ Summary: Delete temporary instance root for Embedded Tomcat on exit Key: ARQ-1958 URL: https://issues.jboss.org/browse/ARQ-1958 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Reporter: Krassimir Valev The embedded tomcat container (tested with version 7) does not cleanup temporary files after test execution - the temp folder is full of tomcat-embedded-***.tmp files. Similar issue was already reported for Glassfish - ARQ-923 that has already been resolved, but I guess nobody fixed the other containers. Looking at the source code of Glassfish, Tomcat and JBoss only the Glassfish one does setup deletion of the temp file within the setup() method: * https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishContainer.java * https://github.com/arquillian/arquillian-container-tomcat/blob/master/tomcat-embedded-7/src/main/java/org/jboss/arquillian/container/tomcat/embedded/Tomcat7EmbeddedContainer.java * https://github.com/arquillian/arquillian-container-jbossas/blob/master/jbossas-embedded-6/src/main/java/org/jboss/arquillian/container/jbossas/embedded_6/JBossASEmbeddedContainer.java -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon Jun 15 08:40:04 2015 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 15 Jun 2015 08:40:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079058#comment-13079058 ] Pavol Pitonak commented on ARQ-1952: ------------------------------------ [~lfryc], could you please provide some feedback on this issue? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 18 08:58:03 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 18 Jun 2015 08:58:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081048#comment-13081048 ] Luk?? Fry? commented on ARQ-1952: --------------------------------- Thanks guys for great feedback. [~pjotrovsky] your solution would work, unfortunately it would mean we would tie Graphene implementation to Warp's internals. [~aslak] {{ResourceProviderWrapper}} is a way to go in a long term. As a workaround, one can create own project-specific locally that would enforce service `.override(..)` (in alphas it seems as appropriate workaround). ---- I must apologize for not reaching you sooner - my incorrectly setup mail filter was hiding the whole conversation from me! :-( > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 18 09:03:03 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 18 Jun 2015 09:03:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? reassigned ARQ-1952: ------------------------------- Assignee: Luk?? Fry? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Assignee: Luk?? Fry? > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 18 09:04:03 2015 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Thu, 18 Jun 2015 09:04:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luk?? Fry? updated ARQ-1952: ---------------------------- Fix Version/s: warp_1.0.0.Beta1 > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 18 16:11:03 2015 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Thu, 18 Jun 2015 16:11:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081317#comment-13081317 ] P?tr Andreev commented on ARQ-1952: ----------------------------------- @[~Luk?? Fry?] concerning ??we would tie Graphene implementation to Warp's internals??- I don`t get it at all- my intention was clearly decouple the [Customizable|https://github.com/petrandreev/arquillian-graphene/blob/ARQ-1952/impl/src/main/java/org/jboss/arquillian/graphene/location/CustomizableURLResourceProvider.java] from anything else, even from the ARQ core` URLProvider, not to speak of the Warp. From my point of view the CustomizableURLResourceProvider is only useful in the narrow scope of "deploymentless" environment (which is rather a seldom use case) and should only take care of this not more and not less. The other thing is, that the proposed solution actually requires the rethinking of the _Provider_ concept in the way that _canProvide_ not just means one can provide instances of class but furthermore considers the current test/arquillian environment. Changing concepts could be risky though... The ResourceWapper draft would not work with the current core implementation as far as i could evaluate it, i guess for this the core provider handling should be re-factored a little. Just my two cents (i just don`t want the RF guys to throw out the Warp tests)... > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 18 16:12:03 2015 From: issues at jboss.org (=?UTF-8?Q?P=C3=ABtr_Andreev_=28JIRA=29?=) Date: Thu, 18 Jun 2015 16:12:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081317#comment-13081317 ] P?tr Andreev edited comment on ARQ-1952 at 6/18/15 4:11 PM: ------------------------------------------------------------ [~Luk?? Fry?] concerning ??we would tie Graphene implementation to Warp's internals??- I don`t get it at all- my intention was clearly decouple the [Customizable|https://github.com/petrandreev/arquillian-graphene/blob/ARQ-1952/impl/src/main/java/org/jboss/arquillian/graphene/location/CustomizableURLResourceProvider.java] from anything else, even from the ARQ core` URLProvider, not to speak of the Warp. From my point of view the CustomizableURLResourceProvider is only useful in the narrow scope of "deploymentless" environment (which is rather a seldom use case) and should only take care of this not more and not less. The other thing is, that the proposed solution actually requires the rethinking of the _Provider_ concept in the way that _canProvide_ not just means one can provide instances of class but furthermore considers the current test/arquillian environment. Changing concepts could be risky though... The ResourceWapper draft would not work with the current core implementation as far as i could evaluate it, i guess for this the core provider handling should be re-factored a little. Just my two cents (i just don`t want the RF guys to throw out the Warp tests)... was (Author: pjotrovsky): @[~Luk?? Fry?] concerning ??we would tie Graphene implementation to Warp's internals??- I don`t get it at all- my intention was clearly decouple the [Customizable|https://github.com/petrandreev/arquillian-graphene/blob/ARQ-1952/impl/src/main/java/org/jboss/arquillian/graphene/location/CustomizableURLResourceProvider.java] from anything else, even from the ARQ core` URLProvider, not to speak of the Warp. From my point of view the CustomizableURLResourceProvider is only useful in the narrow scope of "deploymentless" environment (which is rather a seldom use case) and should only take care of this not more and not less. The other thing is, that the proposed solution actually requires the rethinking of the _Provider_ concept in the way that _canProvide_ not just means one can provide instances of class but furthermore considers the current test/arquillian environment. Changing concepts could be risky though... The ResourceWapper draft would not work with the current core implementation as far as i could evaluate it, i guess for this the core provider handling should be re-factored a little. Just my two cents (i just don`t want the RF guys to throw out the Warp tests)... > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: P?tr Andreev > Assignee: Luk?? Fry? > Fix For: warp_1.0.0.Beta1 > > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jun 19 10:57:02 2015 From: issues at jboss.org (Petr Mensik (JIRA)) Date: Fri, 19 Jun 2015 10:57:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1959) Arquillian Governor doesn't work together with RestEasy REST client In-Reply-To: References: Message-ID: Petr Mensik created ARQ-1959: -------------------------------- Summary: Arquillian Governor doesn't work together with RestEasy REST client Key: ARQ-1959 URL: https://issues.jboss.org/browse/ARQ-1959 Project: Arquillian Issue Type: Bug Affects Versions: 1.0.0.Alpha2 Reporter: Petr Mensik Project which uses REST API (with RestEasy implementation) doesn't work with Governor-Jira because it has it's own com.atlassian.jira.rest.client implementation which misses some features. If you exclude this dependency then you are unable to use the extension in your project (ClassNotFoundException during runtime, obviously). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun Jun 21 15:27:02 2015 From: issues at jboss.org (Stefan Miklosovic (JIRA)) Date: Sun, 21 Jun 2015 15:27:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1959) Arquillian Governor doesn't work together with RestEasy REST client In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081958#comment-13081958 ] Stefan Miklosovic commented on ARQ-1959: ---------------------------------------- Until you do not point me to working JIRA client which would not clash with your RestEasy dependency, I am not able to do anything about it. > Arquillian Governor doesn't work together with RestEasy REST client > ------------------------------------------------------------------- > > Key: ARQ-1959 > URL: https://issues.jboss.org/browse/ARQ-1959 > Project: Arquillian > Issue Type: Bug > Affects Versions: 1.0.0.Alpha2 > Reporter: Petr Mensik > > Project which uses REST API (with RestEasy implementation) doesn't work with Governor-Jira because it has it's own com.atlassian.jira.rest.client implementation which misses some features. If you exclude this dependency then you are unable to use the extension in your project (ClassNotFoundException during runtime, obviously). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:31:04 2015 From: issues at jboss.org (=?UTF-8?Q?Cristina_Gonz=C3=A1lez_castellano_=28JIRA=29?=) Date: Wed, 24 Jun 2015 08:31:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: Cristina Gonz?lez castellano created ARQ-1960: ------------------------------------------------- Summary: Update Arquillian dependency for arquillian-container-osgi Key: ARQ-1960 URL: https://issues.jboss.org/browse/ARQ-1960 Project: Arquillian Issue Type: Component Upgrade Affects Versions: osgi_2.1.0.Final Reporter: Cristina Gonz?lez castellano Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:37:02 2015 From: issues at jboss.org (=?UTF-8?Q?Cristina_Gonz=C3=A1lez_castellano_=28JIRA=29?=) Date: Wed, 24 Jun 2015 08:37:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cristina Gonz?lez castellano updated ARQ-1960: ---------------------------------------------- Description: Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina Gonz?lez castellano > Priority: Minor > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:53:03 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:53:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler reassigned ARQ-1960: ----------------------------------- Assignee: Thomas Diesler > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:54:02 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:54:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1960: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-osgi/pull/44 > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:55:02 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:55:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1960: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Affects Versions: osgi_2.1.0.Final > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:57:04 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:57:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1960: -------------------------------- Fix Version/s: osgi_2.1.0.Final > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > Fix For: osgi_2.1.0.Final > > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:57:04 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:57:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1960: -------------------------------- Affects Version/s: (was: osgi_2.1.0.Final) > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > Fix For: osgi_2.1.0.Final > > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 08:57:04 2015 From: issues at jboss.org (Thomas Diesler (JIRA)) Date: Wed, 24 Jun 2015 08:57:04 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1960) Update Arquillian dependency for arquillian-container-osgi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated ARQ-1960: -------------------------------- Component/s: OSGi Containers > Update Arquillian dependency for arquillian-container-osgi > ---------------------------------------------------------- > > Key: ARQ-1960 > URL: https://issues.jboss.org/browse/ARQ-1960 > Project: Arquillian > Issue Type: Component Upgrade > Components: OSGi Containers > Reporter: Cristina Gonz?lez castellano > Assignee: Thomas Diesler > Priority: Minor > Fix For: osgi_2.1.0.Final > > > Arquillian OSGi container can't be used with the the arquillian-core 1.1.8.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 14:25:02 2015 From: issues at jboss.org (Dave Westerman (JIRA)) Date: Wed, 24 Jun 2015 14:25:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: Dave Westerman created ARQ-1961: ----------------------------------- Summary: Exception while undeploying application in WebSphere Liberty Profile Key: ARQ-1961 URL: https://issues.jboss.org/browse/ARQ-1961 Project: Arquillian Issue Type: Bug Components: WebSphere Containers Environment: OS: Windows 7 Professional Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 WebSphere Liberty Profile: 8.5.5.4 JUnit: 4.11 Java: IBM Java 1.7 in 1.6 mode Reporter: Dave Westerman Assignee: Gerhard Poul I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. All the tests run successfully. However, the JUnit test process always ends with an exception: org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) ... Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy FINER: ENTRY Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: ENTRY [AUDIT ] CWWKG0016I: Starting server configuration update. [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: RETURN Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: ENTRY Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 14:26:02 2015 From: issues at jboss.org (Dave Westerman (JIRA)) Date: Wed, 24 Jun 2015 14:26:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Westerman updated ARQ-1961: -------------------------------- Description: I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. All the tests run successfully. However, the JUnit test process always ends with an exception: org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) ... Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy FINER: ENTRY Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: ENTRY [AUDIT ] CWWKG0016I: Starting server configuration update. [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: RETURN Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: ENTRY Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: RETURN was: I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. All the tests run successfully. However, the JUnit test process always ends with an exception: org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) ... Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy FINER: ENTRY Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: ENTRY [AUDIT ] CWWKG0016I: Starting server configuration update. [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState FINER: RETURN Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: ENTRY Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop FINER: RETURN > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed Jun 24 16:43:02 2015 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Wed, 24 Jun 2015 16:43:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083531#comment-13083531 ] Gerhard Poul commented on ARQ-1961: ----------------------------------- Reviewed the code in question; there are several things that might help resolve this: 1) Check whether File.setWritable() helps 2) Maybe the calls to ZipExporter.class keep the file open and therefore it can't be deleted 3) Something else goes wrong and it makes sense to see whether File.exists() shows that we're on the right track at all Unfortunately in Java SE 6 we cannot get more information on what makes the delete fail directly; the API that shows more information in java.nio.file.Files is only available since Java SE 7. Will need to add additional debug code to this class. > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 25 10:53:03 2015 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 25 Jun 2015 10:53:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083861#comment-13083861 ] Gerhard Poul commented on ARQ-1961: ----------------------------------- [~dlwester] I added additional tracing and debug code; you can find it at https://github.com/gpoul/arquillian-container-was/tree/ARQ-1961 for testing; please let me know that shows anything in the trace. > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 25 13:59:02 2015 From: issues at jboss.org (Dave Westerman (JIRA)) Date: Thu, 25 Jun 2015 13:59:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Westerman updated ARQ-1961: -------------------------------- Attachment: DaveWesterman_arquillian-enhanced-trace.zip Hi, Gerhard. Here is my trace using your new code. > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 25 14:09:02 2015 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 25 Jun 2015 14:09:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084015#comment-13084015 ] Gerhard Poul commented on ARQ-1961: ----------------------------------- [~dlwester] from the trace it looks like all the retries for deletion fail consistently. Can you check whether the file has been deleted after the test finished and the test JVM stopped? (I also registered a deleteOnExit()) - If not, can you manually delete the file and rerun the test? If that test doesn't work I think I'm somehow out of options with the Java 6 APIs to trace this remotely from the container adapter :-/ > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu Jun 25 16:13:03 2015 From: issues at jboss.org (Dave Westerman (JIRA)) Date: Thu, 25 Jun 2015 16:13:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084049#comment-13084049 ] Dave Westerman commented on ARQ-1961: ------------------------------------- When running with your new code, the war file is gone when the JUnit test finishes. However, with the original code, the war file is still there after the Junit test finishes. I'm assuming that's because of your deleteOnExit(). I had been running my tests under Eclipse, so to try to rule it out as a contributing factor, I ran from the Maven command line, and had the same results. So I'm not sure if maybe WLP is the culprit. Is there some parameter with Arquillian to make it wait for awhile before trying to delete the archive? > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jun 26 00:45:03 2015 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Fri, 26 Jun 2015 00:45:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1961) Exception while undeploying application in WebSphere Liberty Profile In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084128#comment-13084128 ] Gerhard Poul commented on ARQ-1961: ----------------------------------- [~dlwester] From the trace it looks like WLP at least logs that it stopped the application before we try to delete it, but who knows. Good at least that the deleteOnExit() seems to work. I have not added this as a parameter, but you can find a Thread.sleep() that you can adjust here: https://github.com/arquillian/arquillian-container-was/compare/master...gpoul:ARQ-1961#diff-957685487719c29ce4c464fc2ec9cf39R412 Maybe you can make it long enough to either make it go away or see who is locking the file in a process explorer. What also occurred to me is that you might want to at least test once with Antivirus disabled if you have it installed; Just to be sure. Which version of Liberty are you using? Is it a publicly available build? Do you think there is a good chance this can be reproduced on a test VM? > Exception while undeploying application in WebSphere Liberty Profile > -------------------------------------------------------------------- > > Key: ARQ-1961 > URL: https://issues.jboss.org/browse/ARQ-1961 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Environment: OS: Windows 7 Professional > Arquillian: org.jboss.arquillian:arquillian-bom:1.1.6.Final > org.jboss.arquillian.container:arquillian-wlp-managed-8.5:1.0.0.Beta2 > Shrinkwrap: org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom:2.1.1 > WebSphere Liberty Profile: 8.5.5.4 > JUnit: 4.11 > Java: IBM Java 1.7 in 1.6 mode > Reporter: Dave Westerman > Assignee: Gerhard Poul > Attachments: DaveWesterman_arquillian-enhanced-trace.zip > > > I am trying to test my JEE application with Arquillian running under WebSphere Liberty Profile 8.5.5.4. My Arquillian tests run against an EJB and a REST service. > > All the tests run successfully. However, the JUnit test process always ends with an exception: > > org.jboss.arquillian.container.spi.client.container.DeploymentException: Exception while undeploying application. > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:419) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > ... > Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Unable to delete archive from apps directory > at org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer.undeploy(WLPManagedContainer.java:405) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > I ran this with a trace that Gerhard suggested, and here is the relevant section of the trace: > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer undeploy > FINER: ENTRY > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getServerXML > FINER: server.xml: /IBM/WLP8554/usr/servers/taskcalendar/server.xml > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: ENTRY > [AUDIT ] CWWKG0016I: Starting server configuration update. > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverApplication.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverKeyStore.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverBasicUserRegistry.xml > [AUDIT ] CWWKG0028A: Processing included configuration resource: C:\IBM\WLP8554\usr\servers\taskcalendar\serverTesting.xml > [AUDIT ] CWWKG0017I: The server configuration was successfully updated in 0.043 seconds. > [AUDIT ] CWWKT0017I: Web application removed (default_host): http://dlwester:30080/task-calendar-ejb-task-calendar-bean-test/ > [INFO ] SRVE0253I: [task-calendar-ejb-task-calendar-bean-test] [/task-calendar-ejb-task-calendar-bean-test] [ArquillianServletRunner]: Destroy successful. > [INFO ] OpenWebBeans Container was stopped for context path, [/task-calendar-ejb-task-calendar-bean-test] > [INFO ] CNTR4003I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application is stopping. > [INFO ] CNTR4004I: The task-calendar-ejb-task-calendar-bean-test.war EJB module in the task-calendar-ejb-task-calendar-bean-test application has stopped successfully. > [AUDIT ] CWWKZ0009I: The application task-calendar-ejb-task-calendar-bean-test has stopped successfully. > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer waitForMBeanTargetState > FINER: RETURN > Jun 24, 2015 11:14:18 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer getAppDirectory > FINER: appDir: /IBM/WLP8554/usr/servers/taskcalendar/apps > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: ENTRY > Jun 24, 2015 11:14:19 AM org.jboss.arquillian.container.was.wlp_managed_8_5.WLPManagedContainer stop > FINER: RETURN -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri Jun 26 04:58:02 2015 From: issues at jboss.org (Vitalii Grygoryuk (JIRA)) Date: Fri, 26 Jun 2015 04:58:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-472) TestCases are copy-pasted In-Reply-To: References: Message-ID: Vitalii Grygoryuk created ARQGRA-472: ---------------------------------------- Summary: TestCases are copy-pasted Key: ARQGRA-472 URL: https://issues.jboss.org/browse/ARQGRA-472 Project: Arquillian Graphene Issue Type: Bug Components: unit-test Affects Versions: 2.1-Tracking Reporter: Vitalii Grygoryuk TestHandlingOfStaleElements.testDeletion() and TestHandlingOfStaleElements.testReplacement() are both testing deletion, so there is no test case for node replacement logic: {code} @Test public void testDeletion() { rootElement.isDisplayed(); executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement); try { rootElement.isDisplayed(); fail("rootElement should not be found"); } catch (NoSuchElementException e) { } } @Test public void testReplacement() { rootElement.isDisplayed(); executor.executeScript("return arguments[0].parentNode.removeChild(arguments[0])", rootElement); try { rootElement.isDisplayed(); fail("rootElement should not be found"); } catch (NoSuchElementException e) { } } {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)