[
https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606390#comment-15606390
]
Attila Sasvari commented on OOZIE-2317:
---------------------------------------
[~rkanter], [~jaydeepvishwakarma], [~rohini]: I am wondering if it is worth to
update to latest version by the end of 2016. Oozie is working with embedded
Jetty and would require less configuration (most of the things can be
configured via oozie-site.xml / oozie-default.xml, using only a few environment
variables). Plus, we already use Jetty in Oozie tests.
Long story short, what I propose is to drop embedded Tomcat in favor of
embedded Jetty. It would make packaging (and starting scripts) cleaner and
simpler and we could remove the tomcat profile completely that OOZIE-2666 would
introduce. In my opinion supporting both embedded Oozie and Tomcat would make
things unnecessarily complicated.
If someone still wants to employ Tomcat or other servlet / web containers, they
still can - for example by deploying the war containing the proper web.xml
(i.e. web.xml or ssl-web.xml if HTTPS is a requirement).
> Figure out what to do about Tomcat 6 End of Life
> ------------------------------------------------
>
> Key: OOZIE-2317
> URL: https://issues.apache.org/jira/browse/OOZIE-2317
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
>
> [Tomcat 6 will be end of life on Dec 31
> 2016.|https://tomcat.apache.org/tomcat-60-eol.html]
> Even though that's a quite a while from now, it's best to stay ahead of
> things, so it would be good if we looked into a plan for this.
> Here are some options:
> # Upgrade to Tomcat 7
> # Upgrade to Tomcat 8
> # Switch to embedded Jetty 9
> I imagine upgrading to Tomcat 7/8 would be the easiest solution. I haven't
> looked into it much, but I imagine the build and deploy process could remain
> relatively the same; though we'd probably have to tweak some config files and
> things. As for which version, Tomcat has [this
> page|https://tomcat.apache.org/whichversion.html] to help.
> Switching to embedded Jetty 9 would require changing the build and deploy
> process, though that might be a good thing given how that can be
> complicated/confusing for users. And I know Tomcat makes things difficult
> for our packaging team in Cloudera. Many other Hadoop projects use embedded
> Jetty as well. We do know that Oozie runs properly in Jetty because our unit
> tests use Jetty.
> As part of this JIRA, the assignee should probably look into more specific
> pros/cons of the options and we should all reach a consensus before moving
> forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
