Description
The purpose of this task is to allow Oozie to run as a standalone application rather than being deployed to a container inside a WAR file.
- Build embedded jetty enabled Oozie by default
- Allow building Tomcat based Oozie by specifying the 'tomcat' profile
- Starting Oozie with oozied.sh detect webserver type based on the build info
- Oozie Web UI is working with JDK 8 if using embedded jetty
- If using Jetty, allow the user to configure the following settings via oozie-default / oozie-site xml:
- request / response header size
- allowed HTTPS protocols
- excluded / weak cipher suites
- threadpool size
Attachments
Attachments
Issue Links
- breaks
-
OOZIE-2788 Fix jobs API servlet mapping for EmbeddedOozieServer
- Closed
- is related to
-
OOZIE-2533 Oozie Web UI gives Error 500 with Java 8u91
- Closed
- relates to
-
OOZIE-3084 Add missing JVM properties to Jetty startup script
- Closed
-
OOZIE-3070 Remove references to org.mortbay.jetty
- Closed
- links to