From issues at jboss.org Wed Aug 15 03:05:00 2018 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Wed, 15 Aug 2018 03:05:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2190) Functional test error after updating to the latest version In-Reply-To: References: Message-ID: Tomas Remes created ARQ-2190: -------------------------------- Summary: Functional test error after updating to the latest version Key: ARQ-2190 URL: https://issues.jboss.org/browse/ARQ-2190 Project: Arquillian Issue Type: Bug Components: Extension - Drone Reporter: Tomas Remes I tried to update EAP BOM (jboss-eap-javaee7) to latest versions as follows: {noformat} 1.4.0.Final 2.5.1 2.3.2 3.1.3 {noformat} I tried to run functional test from EAP quickstarts for contacts-jquerymobile and I am getting following error: {noformat} [ERROR] Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 2.206 s <<< FAILURE! - in org.jboss.as.quickstarts.contacts.test.ContactsMobileBasicTest [ERROR] requiredFieldsValidationTest(org.jboss.as.quickstarts.contacts.test.ContactsMobileBasicTest) Time elapsed: 1.272 s <<< ERROR! org.jboss.arquillian.graphene.enricher.exception.PageFragmentInitializationException: java.lang.RuntimeException: Unable to instantiate Drone via org.openqa.selenium.firefox.FirefoxDriver(FirefoxOptions): java.lang.NoSuchMethodError: com.google.common.collect.ImmutableSortedSet.toImmutableSortedSet(Ljava/util/Comparator;)Ljava/util/stream/Collector; at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.createPageFragment(PageFragmentEnricher.java:178) at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.setupPageFragment(PageFragmentEnricher.java:231) at org.jboss.arquillian.graphene.enricher.PageFragmentEnricher.enrich(PageFragmentEnricher.java:86) at org.jboss.arquillian.graphene.enricher.GrapheneEnricher.enrich(GrapheneEnricher.java:55) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:51) at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:115) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:200) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:215) at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:279) at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:88) at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:273) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:177) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413) Caused by: java.lang.RuntimeException: Unable to instantiate Drone via org.openqa.selenium.firefox.FirefoxDriver(FirefoxOptions): java.lang.NoSuchMethodError: com.google.common.collect.ImmutableSortedSet.toImmutableSortedSet(Ljava/util/Comparator;)Ljava/util/stream/Collector; at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:166) at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:76) at org.jboss.arquillian.drone.webdriver.factory.FirefoxDriverFactory.createInstance(FirefoxDriverFactory.java:40) at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:127) at org.jboss.arquillian.drone.webdriver.factory.WebDriverFactory.createInstance(WebDriverFactory.java:38) at org.jboss.arquillian.drone.impl.DroneConfigurator$1.createInstance(DroneConfigurator.java:112) at org.jboss.arquillian.drone.impl.CachingCallableImpl.call(CachingCallableImpl.java:44) at org.jboss.arquillian.core.impl.threading.ThreadedExecutorService$ContextualCallable.call(ThreadedExecutorService.java:88) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NoSuchMethodError: com.google.common.collect.ImmutableSortedSet.toImmutableSortedSet(Ljava/util/Comparator;)Ljava/util/stream/Collector; at org.openqa.selenium.remote.NewSessionPayload.lambda$validate$4(NewSessionPayload.java:199) at java.util.stream.ReferencePipeline$11$1.accept(ReferencePipeline.java:372) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.stream.ReferencePipeline$11$1.accept(ReferencePipeline.java:373) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at org.openqa.selenium.remote.NewSessionPayload.validate(NewSessionPayload.java:215) at org.openqa.selenium.remote.NewSessionPayload.(NewSessionPayload.java:163) at org.openqa.selenium.remote.NewSessionPayload.create(NewSessionPayload.java:114) at org.openqa.selenium.remote.NewSessionPayload.create(NewSessionPayload.java:107) at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:67) at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:136) at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:545) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:209) at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:132) at org.openqa.selenium.firefox.FirefoxDriver.(FirefoxDriver.java:120) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:144) ... 11 more {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 23 02:57:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 23 Aug 2018 02:57:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2191) Arquillian tomcat managed container does not work on JDK9 In-Reply-To: References: Message-ID: Amos Feng created ARQ-2191: ------------------------------ Summary: Arquillian tomcat managed container does not work on JDK9 Key: ARQ-2191 URL: https://issues.jboss.org/browse/ARQ-2191 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Reporter: Amos Feng starting from Java 9 and onwards the JVM configuration flag java.endorsed.dirs was removed. This configuration flag is currently used for the Tomcat container and causes the JVM to terminate with the following message: {noformat} $JAVA_HOME/lib/endorsed is not supported. Endorsed standards and standalone APIs in modular form will be supported via the concept of upgradeable modules. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 23 03:23:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Thu, 23 Aug 2018 03:23:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2191) Arquillian tomcat managed container does not work on JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated ARQ-2191: --------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/41 > Arquillian tomcat managed container does not work on JDK9 > --------------------------------------------------------- > > Key: ARQ-2191 > URL: https://issues.jboss.org/browse/ARQ-2191 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Reporter: Amos Feng > > starting from Java 9 and onwards the JVM configuration flag java.endorsed.dirs was removed. This configuration flag is currently used for the Tomcat container and causes the JVM to terminate with the following message: > {noformat} > $JAVA_HOME/lib/endorsed is not supported. Endorsed standards and standalone APIs > in modular form will be supported via the concept of upgradeable modules. > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Aug 28 08:35:00 2018 From: issues at jboss.org (Jesus Lunar Perez (JIRA)) Date: Tue, 28 Aug 2018 08:35:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2192) Method ProxyUsageTracker.initializeRealURLMapping is not called which produces NPE on registerOperationalContextToUrl In-Reply-To: References: Message-ID: Jesus Lunar Perez created ARQ-2192: -------------------------------------- Summary: Method ProxyUsageTracker.initializeRealURLMapping is not called which produces NPE on registerOperationalContextToUrl Key: ARQ-2192 URL: https://issues.jboss.org/browse/ARQ-2192 Project: Arquillian Issue Type: Bug Components: Extension - Warp Affects Versions: 1.4.0.Final Reporter: Jesus Lunar Perez Attachments: arquillian.xml I'm getting this error: {code:java} Caused by: java.lang.NullPointerException at org.jboss.arquillian.warp.impl.client.proxy.ProxyUsageTracker.registerOperationalContextToUrl(ProxyUsageTracker.java:75) {code} After debugging, I've found method ProxyUsageTracker.initializeRealURLMapping is not called so it produces the NPE. When is it supposed to be called? I'm using Arquillian 1.4.0.Final and warp 1.0.0.Alpha8 deploying in a weblogic server (arquillian.xml attached) Thanks in advance. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Aug 29 05:54:01 2018 From: issues at jboss.org (Jesus Lunar Perez (JIRA)) Date: Wed, 29 Aug 2018 05:54:01 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2193) org.jboss.arquillian.warp.jsf.enricher.ManagedPropertyTestEnricher getting null JSF context In-Reply-To: References: Message-ID: Jesus Lunar Perez created ARQ-2193: -------------------------------------- Summary: org.jboss.arquillian.warp.jsf.enricher.ManagedPropertyTestEnricher getting null JSF context Key: ARQ-2193 URL: https://issues.jboss.org/browse/ARQ-2193 Project: Arquillian Issue Type: Bug Components: Extension - Warp Affects Versions: 1.4.0.Final Reporter: Jesus Lunar Perez resolveValueExpression method in org.jboss.arquillian.warp.jsf.enricher.ManagedPropertyTestEnricher is getting null JSF context. If I debug, my managed bean @PostConstruct is getting a valid FacesContext.getCurrentInstance(); but after that, same call at ManagedPropertyTestEnricher is getting null. Im running in WLS 12.2.1.2 using arquillian-wls-remote-rest. {code:java} @PostConstruct public void init() { int logtoken = Log.inicio("Gesti?n Solicitudes Bean - Init"); FacesContext ctx = FacesContext.getCurrentInstance(); Log.info("Context: " + ctx); //<-- Not null {code} After that, following method is called: {code:java} private Object resolveValueExpression(ManagedProperty property, Class expectedType, Object injectionPoint) { FacesContext context = FacesContext.getCurrentInstance(); // <-- Getting null String expression = property.value(); {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Aug 29 10:21:00 2018 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 29 Aug 2018 10:21:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2194) Tomcat 9 embedded adapter starts with no connectors In-Reply-To: References: Message-ID: Matej Novotny created ARQ-2194: ---------------------------------- Summary: Tomcat 9 embedded adapter starts with no connectors Key: ARQ-2194 URL: https://issues.jboss.org/browse/ARQ-2194 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Affects Versions: 1.0.1.Final Environment: Tomcat 9 embedded Weld servlet tests Reporter: Matej Novotny I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Aug 29 10:26:00 2018 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 29 Aug 2018 10:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2194) Tomcat 9 embedded adapter starts with no connectors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated ARQ-2194: ------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-container-tomcat/pull/42 > Tomcat 9 embedded adapter starts with no connectors > --------------------------------------------------- > > Key: ARQ-2194 > URL: https://issues.jboss.org/browse/ARQ-2194 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.1.Final > Environment: Tomcat 9 embedded > Weld servlet tests > Reporter: Matej Novotny > > I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. > Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. > As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Aug 29 10:26:00 2018 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 29 Aug 2018 10:26:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2194) Tomcat 9 embedded adapter starts with no connectors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny reassigned ARQ-2194: ---------------------------------- Assignee: Matej Novotny > Tomcat 9 embedded adapter starts with no connectors > --------------------------------------------------- > > Key: ARQ-2194 > URL: https://issues.jboss.org/browse/ARQ-2194 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.1.Final > Environment: Tomcat 9 embedded > Weld servlet tests > Reporter: Matej Novotny > Assignee: Matej Novotny > > I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. > Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. > As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Aug 29 10:33:00 2018 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 29 Aug 2018 10:33:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2194) Tomcat 9 embedded adapter starts with no connectors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated ARQ-2194: ------------------------------- Description: I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. Just FYI, [link to Tomcat BZ|https://bz.apache.org/bugzilla/show_bug.cgi?id=60368] which issued this change. was: I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. > Tomcat 9 embedded adapter starts with no connectors > --------------------------------------------------- > > Key: ARQ-2194 > URL: https://issues.jboss.org/browse/ARQ-2194 > Project: Arquillian > Issue Type: Bug > Components: Tomcat Containers > Affects Versions: 1.0.1.Final > Environment: Tomcat 9 embedded > Weld servlet tests > Reporter: Matej Novotny > Assignee: Matej Novotny > > I was trying to run Weld servlet tests on Tomcat 9 embedded utilizing [arquillian-container-tomcat|https://github.com/arquillian/arquillian-container-tomcat]. > Turns out this doesn't work because starting with Tomcat 9 there are no default connectors registered (e.g. Tomcat starts up and listens on no port) hence subsequent test execution fails. > As a fix a one-liner can be added to version 8 codebase - it causes no harm for Tomcat 8 and fixes Tomcat 9. I'll send a PR momentarily. > Just FYI, [link to Tomcat BZ|https://bz.apache.org/bugzilla/show_bug.cgi?id=60368] which issued this change. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 30 10:38:02 2018 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 30 Aug 2018 10:38:02 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2187) Updating WAS container to latest core results in injection failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2187 started by Gerhard Poul. ----------------------------------------- > Updating WAS container to latest core results in injection failures > ------------------------------------------------------------------- > > Key: ARQ-2187 > URL: https://issues.jboss.org/browse/ARQ-2187 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: 1.0.0.CR1 > Reporter: Bartosz Majsak > Assignee: Gerhard Poul > > Updating to Arquillian Core 1.4.0.Final results in build failure > https://gist.github.com/bartoszmajsak/2887a67d855260e8290470119fe781a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 30 10:38:03 2018 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 30 Aug 2018 10:38:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2187) Updating WAS container to latest core results in injection failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARQ-2187 stopped by Gerhard Poul. ----------------------------------------- > Updating WAS container to latest core results in injection failures > ------------------------------------------------------------------- > > Key: ARQ-2187 > URL: https://issues.jboss.org/browse/ARQ-2187 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: 1.0.0.CR1 > Reporter: Bartosz Majsak > Assignee: Gerhard Poul > > Updating to Arquillian Core 1.4.0.Final results in build failure > https://gist.github.com/bartoszmajsak/2887a67d855260e8290470119fe781a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 30 10:38:03 2018 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 30 Aug 2018 10:38:03 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2187) Updating WAS container to latest core results in injection failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626582#comment-13626582 ] Gerhard Poul commented on ARQ-2187: ----------------------------------- I've reproduce this locally and the errors look very similar to what was reported for Liberty at https://developer.ibm.com/answers/questions/181781/dependency-injection-problems-with-cdi-12-feature/ so I would assume this is related to this WELD issue and not to the upgrade to arquillian 1.4. Potentially this will be addressed in a subsequent fixpack of WAS. > Updating WAS container to latest core results in injection failures > ------------------------------------------------------------------- > > Key: ARQ-2187 > URL: https://issues.jboss.org/browse/ARQ-2187 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: 1.0.0.CR1 > Reporter: Bartosz Majsak > Assignee: Gerhard Poul > > Updating to Arquillian Core 1.4.0.Final results in build failure > https://gist.github.com/bartoszmajsak/2887a67d855260e8290470119fe781a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Thu Aug 30 10:45:00 2018 From: issues at jboss.org (Gerhard Poul (JIRA)) Date: Thu, 30 Aug 2018 10:45:00 -0400 (EDT) Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2187) Updating WAS container to latest core results in injection failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/ARQ-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626582#comment-13626582 ] Gerhard Poul edited comment on ARQ-2187 at 8/30/18 10:44 AM: ------------------------------------------------------------- I've reproduced this locally and the errors look very similar to what was reported for Liberty at https://developer.ibm.com/answers/questions/181781/dependency-injection-problems-with-cdi-12-feature/ so I would assume this is related to this WELD issue and not to the upgrade to arquillian 1.4. Potentially this will be addressed in a subsequent fixpack of WAS. This is an intermittent error and it doesn't seem to appear with every run. I've had clean runs with arquillian 1.4 as well. was (Author: gpoul): I've reproduce this locally and the errors look very similar to what was reported for Liberty at https://developer.ibm.com/answers/questions/181781/dependency-injection-problems-with-cdi-12-feature/ so I would assume this is related to this WELD issue and not to the upgrade to arquillian 1.4. Potentially this will be addressed in a subsequent fixpack of WAS. > Updating WAS container to latest core results in injection failures > ------------------------------------------------------------------- > > Key: ARQ-2187 > URL: https://issues.jboss.org/browse/ARQ-2187 > Project: Arquillian > Issue Type: Bug > Components: WebSphere Containers > Affects Versions: 1.0.0.CR1 > Reporter: Bartosz Majsak > Assignee: Gerhard Poul > > Updating to Arquillian Core 1.4.0.Final results in build failure > https://gist.github.com/bartoszmajsak/2887a67d855260e8290470119fe781a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)