June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-574) Tomcat managed should not require an installed tomcat server

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-574?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-574. ----------------------------- Resolution: Won't Fix > Tomcat managed should not require an installed tomcat server > ------------------------------------------------------------ > > Key: ARQ-574 > URL: https://issues.jboss.org/browse/ARQ-574 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Geoffrey De Smet > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.CR7 > > > When starting up tomcat6-managed, the first SNAPSHOT, I get this: > {code} > Either CATALINA_HOME environment variable or catalinaHome property in Arquillian configuration must be set and point to a valid directory! null is not valid directory! > {code} > There are 2 problems with this: > - it's a maintenance hurdle, especially on hudson build slaves > - the build is not reproducible: the test results depends on the tomcat server version you've installed on your machine. > Solution: > Set the tomcat zip as a dependency (so it's in ~/.m2/repository) and unzip it to target and use that server installation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-628) Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-628?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-628. ----------------------------- > Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > ----------------------------------------------------------------------------------------------------- > > Key: ARQ-628 > URL: https://issues.jboss.org/browse/ARQ-628 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Environment: tomcat-managed-7 > application - richfaces-showcase-4.1.0-20111011-M3-tomcat6.war > Reporter: Juraj Húska > Fix For: tomcat_1.0.0.Final > > > I have encountered this issue when I was testing richfaces-showcase application. It seems that tomcat-managed-7 has problem with applications which bring own weld-servlet dependency. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1810) Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1810?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1810. ------------------------------ > Update Tomcat Containers test suite to ShrinkWrap Resolver 2.0 > -------------------------------------------------------------- > > Key: ARQ-1810 > URL: https://issues.jboss.org/browse/ARQ-1810 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-866. ----------------------------- > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-701) Tomcat containers are not able to start after begin stop (AddressAlready in use)

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-701?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-701. ----------------------------- > Tomcat containers are not able to start after begin stop (AddressAlready in use) > -------------------------------------------------------------------------------- > > Key: ARQ-701 > URL: https://issues.jboss.org/browse/ARQ-701 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Setting a embedded Tomcat 7 container to manual control mode and calling, start/stop/start cause Address Already in use Exception. > stop should call tomcat.destroy > (possible other tomcat versions as well, investigate) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1519) Cannot load configuration with tomcat-managed-1.0.0.CR5

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1519?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1519. ------------------------------ > Cannot load configuration with tomcat-managed-1.0.0.CR5 > ------------------------------------------------------- > > Key: ARQ-1519 > URL: https://issues.jboss.org/browse/ARQ-1519 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > {code} > java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(DescriptorImporterBase.java:155) > at org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.from(DescriptorImporterBase.java:182) > at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:54) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.<init>(EventTestRunnerAdaptor.java:56) > {code} > When debugging this I see > {code} > java.lang.NoSuchMethodError: org.jboss.shrinkwrap.descriptor.spi.DescriptorImporterBase.fromStream(Ljava/io/InputStream;Z)Lorg/jboss/shrinkwrap/descriptor/api/Descriptor;{code} > this is however never fed back to the client -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1191) Tomcat Embedded 6 undeploy(archive) issue

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1191?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1191. ------------------------------ > Tomcat Embedded 6 undeploy(archive) issue > ----------------------------------------- > > Key: ARQ-1191 > URL: https://issues.jboss.org/browse/ARQ-1191 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Tomcat-embedded-6 > Reporter: George Vagenas > Assignee: Aslak Knutsen > Priority: Critical > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat.patch, SimpleArqTest.zip > > > Having two test classes that extend an abstract class that provides the deployment archive (actually the fact that they extend an abstract class is insignificant, the important point here is that the deployment archive name is the same). > When the test classes run individually pass the test. When these two test classes combined in a test suite, the first only pass and the second always fails. > @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Find attached @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Issue exists only on tomcat 6 container. I run the same test suite against tomcat-embedded-7 with success. > George -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1799. ------------------------------ > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1680) Tomcat 7 embedded adapter should be built against 7.0.52

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1680?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1680. ------------------------------ > Tomcat 7 embedded adapter should be built against 7.0.52 > -------------------------------------------------------- > > Key: ARQ-1680 > URL: https://issues.jboss.org/browse/ARQ-1680 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Environment: Tomcat 7.0.52, JDK 1.7 > Reporter: Tommy Tynjä > Assignee: Tommy Tynjä > Fix For: tomcat_1.0.0.Final > > > Tomcat 7 embedded container is built with a dependency on Tomcat 7.0.20, which was released 2011-08-11. The latest version of Tomcat is 7.0.52, and a lot of patches have been applied since 7.0.20 (see [changelog|http://tomcat.apache.org/tomcat-7.0-doc/changelog.html]). When relying on the 7.0.52 version of Tomcat 7 embedded in your project, it would be preferable to use an adapter that is built using that version, as in some (at least theoretical) corner cases, Arquillian could fail running tests in a 7.0.52 embedded container. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1650) Managed container bypasses tomcat jul setup

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1650?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1650. ------------------------------ > Managed container bypasses tomcat jul setup > ------------------------------------------- > > Key: ARQ-1650 > URL: https://issues.jboss.org/browse/ARQ-1650 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR5 > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: tomcat_1.0.0.Final > > > This code from the catalina startup script is not done in the manged deployable container > {code} > # Set juli LogManager config file if it is present and an override has not been issued > if [ -z "$LOGGING_CONFIG" ]; then > if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then > LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" > else > # Bugzilla 45585 > LOGGING_CONFIG="-Dnop" > fi > fi > if [ -z "$LOGGING_MANAGER" ]; then > LOGGING_MANAGER="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" > fi > {code} > As a result, tomcat logging does not work -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014