You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 01:57:49 UTC
[jira] [Created] (BIGTOP-417) webapps shipped by bigtop components
should be using a system-provided Tomcat
webapps shipped by bigtop components should be using a system-provided Tomcat
-----------------------------------------------------------------------------
Key: BIGTOP-417
URL: https://issues.apache.org/jira/browse/BIGTOP-417
Project: Bigtop
Issue Type: Bug
Components: General
Affects Versions: 0.2.0, 0.4.0
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Fix For: 0.3.0, 0.4.0
We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Alejandro Abdelnur (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219440#comment-13219440 ]
Alejandro Abdelnur commented on BIGTOP-417:
-------------------------------------------
+1
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-417) webapps shipped by bigtop components
should be using a system-provided Tomcat
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-417:
------------------------------------
Attachment: BIGTOP-417-2.patch.txt
Attaching a second patch. This one hooks Oozie and HTTPFS to the bigtop-tomcat
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417-2.patch.txt, BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219532#comment-13219532 ]
Peter Linnell commented on BIGTOP-417:
--------------------------------------
+1
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-417) webapps shipped by bigtop components
should be using a system-provided Tomcat
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-417:
------------------------------------
Fix Version/s: (was: 0.3.0)
Too risky for 0.3 and fixed in 0.4
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
> Attachments: BIGTOP-417-2.patch.txt, BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221102#comment-13221102 ]
Roman Shaposhnik commented on BIGTOP-417:
-----------------------------------------
@Bruno -- thanks for the feedback. Took care of all the points.
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417-2.patch.txt, BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220301#comment-13220301 ]
Bruno Mahé commented on BIGTOP-417:
-----------------------------------
* why build-depends on git-core?
* some indentation issues
* {noformat}+BIGTOP_TOMCAT_BASE_VERSION=6.0.35
+BIGTOP_TOMCAT_PKG_VERSION=6.0.35{noformat}
If they are the same, just use BIGTOP_TOMCAT_BASE_VERSION
Not blockers, but would be nice to have it fixed or tickets opened.
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219426#comment-13219426 ]
Bruno Mahé commented on BIGTOP-417:
-----------------------------------
+1
Seems like a great idea!
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Roman Shaposhnik (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219365#comment-13219365 ]
Roman Shaposhnik commented on BIGTOP-417:
-----------------------------------------
After spending some time reviewing the versions and availability of Tomcat for the platforms we have to support I'm leaning towards a solution of making tomcat be part of the Bigtop distribution itself. That will help us get around a sad state of affairs on platforms like CentOS 5 (where only Tomcat 5 is available, and Oozie/HTTPFS need at least 6) and also give a greater control over the versioning of Tomcat in general (we can keep it uniform across all the distros).
Of course, we will not be a producing a general-purpose Tomcat packaging solution here. Think of it as an "embedded Tomcat" or as a Bigtop Container Platform (BCP). The proposed package name will be bigtop-tomcat and the location of files will be /usr/lib/bigtop-tomcat. No init.d scripts or /usr/bin scripts will be provided since the entry point will remain via the init.d scripts of individual components (e.g. /etc/init.d/{oozie,httpfs}).
Thoughts?
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BIGTOP-417) webapps shipped by bigtop components
should be using a system-provided Tomcat
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-417:
------------------------------------
Attachment: BIGTOP-417.patch.txt
Attaching the first rough cut of the packaging. Once this is approved I'll try to make Oozie and HTTPFS use this package instead of bundling the Tomcat.
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BIGTOP-417) webapps shipped by bigtop
components should be using a system-provided Tomcat
Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220233#comment-13220233 ]
Peter Linnell commented on BIGTOP-417:
--------------------------------------
+ 1 on the patch. Looks like a good start. Is this version of tomcat the preferred one ?
> webapps shipped by bigtop components should be using a system-provided Tomcat
> -----------------------------------------------------------------------------
>
> Key: BIGTOP-417
> URL: https://issues.apache.org/jira/browse/BIGTOP-417
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.2.0, 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.3.0, 0.4.0
>
> Attachments: BIGTOP-417.patch.txt
>
>
> We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
> http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
> http://willcode4beer.com/ware.jsp?set=tomcat_config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira