September 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1848?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1848 started by Ian Brandt. --------------------------------------- > Tomcat managed containers should start and stop Tomcat using the standard run scripts > ------------------------------------------------------------------------------------- > > Key: ARQ-1848 > URL: https://issues.jboss.org/browse/ARQ-1848 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: > * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). > * Logging configuration. > * Running with or without a security manager. > * Support for configuration in the 'setenv' script. > * Endorsed and temp directory configuration. > * Launching with JPDA related configuration. > * OS variant and TTY related configuration on UNIX. > By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: > * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > * ARQ-1650 - Managed container bypasses tomcat jul setup > * ARQ-1843 - Tomcat managed container ignores javaHome configuration > * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers > * ARQ-1847 - Support specifying JMX RMI server port > Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: > * Add all the missing features and logic. > * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. > * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1848?page=com.atlassian.jira.plugin.s... ] Ian Brandt updated ARQ-1848: ---------------------------- Fix Version/s: tomcat_1.0.0.Final > Tomcat managed containers should start and stop Tomcat using the standard run scripts > ------------------------------------------------------------------------------------- > > Key: ARQ-1848 > URL: https://issues.jboss.org/browse/ARQ-1848 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: > * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). > * Logging configuration. > * Running with or without a security manager. > * Support for configuration in the 'setenv' script. > * Endorsed and temp directory configuration. > * Launching with JPDA related configuration. > * OS variant and TTY related configuration on UNIX. > By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: > * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > * ARQ-1650 - Managed container bypasses tomcat jul setup > * ARQ-1843 - Tomcat managed container ignores javaHome configuration > * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers > * ARQ-1847 - Support specifying JMX RMI server port > Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: > * Add all the missing features and logic. > * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. > * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1848?page=com.atlassian.jira.plugin.s... ] Ian Brandt reassigned ARQ-1848: ------------------------------- Assignee: Ian Brandt > Tomcat managed containers should start and stop Tomcat using the standard run scripts > ------------------------------------------------------------------------------------- > > Key: ARQ-1848 > URL: https://issues.jboss.org/browse/ARQ-1848 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: > * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). > * Logging configuration. > * Running with or without a security manager. > * Support for configuration in the 'setenv' script. > * Endorsed and temp directory configuration. > * Launching with JPDA related configuration. > * OS variant and TTY related configuration on UNIX. > By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: > * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency > * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > * ARQ-1650 - Managed container bypasses tomcat jul setup > * ARQ-1843 - Tomcat managed container ignores javaHome configuration > * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers > * ARQ-1847 - Support specifying JMX RMI server port > Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: > * Add all the missing features and logic. > * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. > * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1848) Tomcat managed containers should start and stop Tomcat using the standard run scripts

by Ian Brandt (JIRA)

Ian Brandt created ARQ-1848: ------------------------------- Summary: Tomcat managed containers should start and stop Tomcat using the standard run scripts Key: ARQ-1848 URL: https://issues.jboss.org/browse/ARQ-1848 Project: Arquillian Issue Type: Feature Request Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Ian Brandt The [standard Tomcat run scripts|http://tomcat.apache.org/tomcat-8.0-doc/RUNNING.txt] contain a fair little bit of logic and features: * Multiple instance support (requiring the proper merging of resources from {{CATALINA_BASE}} and {{CATALINA_HOME}}). * Logging configuration. * Running with or without a security manager. * Support for configuration in the 'setenv' script. * Endorsed and temp directory configuration. * Launching with JPDA related configuration. * OS variant and TTY related configuration on UNIX. By building the Java command to launch Tomcat directly the current {{CommonTomcatManagedContainer}} forgoes the standard implementation of all this. There is a growing history of bug reports and feature requests that suggest this may not be the best approach: * ARQ-628 - Tomcat managed throws NullPointerException when application under test brings weld-servlet dependency * ARQ-866 - Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters * ARQ-1650 - Managed container bypasses tomcat jul setup * ARQ-1843 - Tomcat managed container ignores javaHome configuration * ARQ-1846 - Support configuration of the Tomcat system classpath from managed containers * ARQ-1847 - Support specifying JMX RMI server port Rather than reinventing the wheel here, we should just launch and stop Tomcat with the standard run script for the current OS, exposing it's environment variable-driven configuration via arquillian.xml and the {{CommonTomcatManagedConfiguration}}. This will: * Add all the missing features and logic. * Be simpler and presumably cheaper to maintain over trying to mirror the standard scripts. * Encourage better fidelity between managed containers and their production counterparts (e.g. identical {{CATALINA_BASE}} and {{CATALINA_HOME}} merging, as well as setenv script support). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Stephen Coy edited comment on ARQ-1847 at 9/5/14 10:26 PM: ----------------------------------------------------------- Note: org.jboss.arquillian.container.tomcat.CommonTomcatConfiguration contains the following two public setters: {code:java} public void setJmxUri(URI jmxUri) public void setManagerUrl(URL managerUrl) {code} which implies that they are configurable from arquillian.xml. However, these are both overwritten during validation. Therefore I'm tempted to remove these setters altogether. was (Author: sfcoy): Note: org.jboss.arquillian.container.tomcat.CommonTomcatConfiguration contains the following two public setters: {code:java} public void setJmxUri(URI jmxUri) public void setManagerUrl(URL managerUrl) {code:java} which implies that they are configurable from arquillian.xml. However, these are both overwritten during validation. Therefore I'm tempted to remove these setters altogether. > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Stephen Coy commented on ARQ-1847: ---------------------------------- Note: org.jboss.arquillian.container.tomcat.CommonTomcatConfiguration contains the following two public setters: {code:java} public void setJmxUri(URI jmxUri) public void setManagerUrl(URL managerUrl) {code:java} which implies that they are configurable from arquillian.xml. However, these are both overwritten during validation. Therefore I'm tempted to remove these setters altogether. > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1847 started by Stephen Coy. ---------------------------------------- > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-1847?page=com.atlassian.jira.plugin.s... ] Stephen Coy reassigned ARQ-1847: -------------------------------- Assignee: Stephen Coy > Support specifying JMX RMI server port > -------------------------------------- > > Key: ARQ-1847 > URL: https://issues.jboss.org/browse/ARQ-1847 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Stephen Coy > Assignee: Stephen Coy > > This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1847) Support specifying JMX RMI server port

by Stephen Coy (JIRA)

Stephen Coy created ARQ-1847: -------------------------------- Summary: Support specifying JMX RMI server port Key: ARQ-1847 URL: https://issues.jboss.org/browse/ARQ-1847 Project: Arquillian Issue Type: Feature Request Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR7 Reporter: Stephen Coy This additional configuration is necessary to support remote deployments behind firewalls -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1846) Support configuration of the Tomcat system classpath from managed containers

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1846?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1846 started by Ian Brandt. --------------------------------------- > Support configuration of the Tomcat system classpath from managed containers > ---------------------------------------------------------------------------- > > Key: ARQ-1846 > URL: https://issues.jboss.org/browse/ARQ-1846 > Project: Arquillian > Issue Type: Feature Request > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR7 > Reporter: Ian Brandt > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > In some rare cases, such as customization of Tomcat's internal logging, it may prove useful to augment or change the [system classpath used to start Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html]. Currently the managed containers hard code the Tomcat default configuration. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2014