[
https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203363#comment-16203363
]
Andras Piros commented on OOZIE-3084:
-------------------------------------
It turns out we only need to add {{-Doozie.instance.id}}, every other missing
parameter is handled within {{oozie-default.xml}}.
JVM parameters w/ the patch:
{noformat}
bash-3.2$ ps ax | grep oozie.instance.id
27823 s003 S 0:20.49
/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/bin/java
-Doozie.home.dir=/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT
-Doozie.config.dir=/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/conf
-Doozie.log.dir=/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/logs
-Doozie.data.dir=/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/data
-Doozie.instance.id=Budapests-MacBook-Pro.local
-Doozie.config.file=oozie-site.xml
-Doozie.log4j.file=oozie-log4j.properties
-Doozie.log4j.reload=10
-Djava.library.path=
-cp
/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/embedded-oozie-server/*:/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/embedded-oozie-server/dependency/*:/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/lib/*:/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/libtools/*:/Users/forsage/Workspace/oozie/distro/target/oozie-5.0.0-SNAPSHOT-distro/oozie-5.0.0-SNAPSHOT/embedded-oozie-server
org.apache.oozie.server.EmbeddedOozieServer
{noformat}
Excerpt from {{logs/oozie.log}}:
{noformat}
2017-10-13 12:34:55,302 INFO StatusTransitService$StatusTransitRunnable:520 -
SERVER[Budapests-MacBook-Pro.local] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-]
ACTION[-] Running bundle status service from last instance time =
2017-10-13T10:33Z
2017-10-13 12:34:55,304 INFO StatusTransitService$StatusTransitRunnable:520 -
SERVER[Budapests-MacBook-Pro.local] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-]
ACTION[-] Released lock for [org.apache.oozie.service.StatusTransitService]
{noformat}
> Add missing JVM properties to Jetty startup script
> --------------------------------------------------
>
> Key: OOZIE-3084
> URL: https://issues.apache.org/jira/browse/OOZIE-3084
> Project: Oozie
> Issue Type: Bug
> Components: scripts
> Affects Versions: 5.0.0
> Reporter: Andras Piros
> Assignee: Andras Piros
>
> In OOZIE-2666, when Oozie has moved from Tomcat to Jetty, we also moved the
> Tomcat related JVM options inside the startup script {{bin/oozied.sh}} to the
> more specific {{bin/oozie-jetty-server.sh}}.
> It seems that not all the
> [*{{catalina_opts}}*|https://github.com/apache/oozie/blob/branch-4.3/distro/src/main/bin/oozied.sh#L54-L74]
> have been moved to
> [*{{jetty_opts}}*|https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-jetty-server.sh#L70-L86].
> Such an example is {{oozie.instance.id}}, causing we don't have any server
> name information within the Oozie server logs.
> So the task is to investigate startup scripts and put missing and needed
> {{catalina_opts}} to {{jetty_opts}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
