[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237479#comment-16237479 ] Andras Piros commented on OOZIE-3084: - Thanks [~asasvari], [~gezapeti] for the reviews! Committed to master. > 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 >Priority: Blocker > Fix For: 5.0.0b1 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch, OOZIE-3084.002.patch, OOZIE-3084.003.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237476#comment-16237476 ] Attila Sasvari commented on OOZIE-3084: --- [~andras.piros] thanks for the patch! It looks good to me. +1 > 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 >Priority: Blocker > Fix For: 5.0.0b1 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch, OOZIE-3084.002.patch, OOZIE-3084.003.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236430#comment-16236430 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [tools]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 2048 .Tests rerun: 54 .Tests failed at first run: org.apache.oozie.action.hadoop.TestJavaActionExecutor, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}*+1 Overall result, good!, no -1s*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/164/ > 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 >Priority: Blocker > Fix For: 5.0.0b1 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch, OOZIE-3084.002.patch, OOZIE-3084.003.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227079#comment-16227079 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch does adds/modifies 3 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} .Tests run: 2048 .Tests failed: 0 .Tests errors: 1 .The patch failed the following testcases: . .Tests failing with errors: . testJMXInstrumentation(org.apache.oozie.util.TestMetricsInstrumentation) {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/150/ > 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 >Priority: Blocker > Fix For: 5.0.0b1 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch, OOZIE-3084.002.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226987#comment-16226987 ] Attila Sasvari commented on OOZIE-3084: --- [~andras.piros] thanks for the explanation. Some comments: - In XTestCase, do not use wildcard import. {code} import org.apache.oozie.util.*; {code} - Please run shellcheck against the modified shell scripts. > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch, OOZIE-3084.002.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225662#comment-16225662 ] Peter Cseh commented on OOZIE-3084: --- I know it's used elsewhere, but I we always have to overwrite it's value as a passed in Java property there is no need - or sense to keep it in the oozie-default.xml as the value set in the xml will never be used. Can you verify this? > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225293#comment-16225293 ] Andras Piros commented on OOZIE-3084: - [~gezapeti] yep, {{oozie.instance.id}} is used also outside of test classes - it's used to obtain the Zookeeper ID in [*{{ZKUtils#ZKUtils()}}*|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/util/ZKUtils.java#L146-L149]. So cannot be removed easily. > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224967#comment-16224967 ] Peter Cseh commented on OOZIE-3084: --- Is {{oozie.instance.id}} is needed/useful in the [{{oozie-default.xml}}|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml#L2685] if we have to specify it via a Java property? We could remove it if it's not used for anything else. > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222640#comment-16222640 ] Andras Piros commented on OOZIE-3084: - [~asasvari] any thoughts on the previous one? > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210731#comment-16210731 ] Andras Piros commented on OOZIE-3084: - [~asasvari] thanks for the review! In fact I've checked that: * no other Tomcat related options are needed to be put to Jetty startup scripts * you're right, {{XLogService}} is started before (and should be started before, since we need appropriate logging) before {{ConfigurationService}}, that's why {{oozie.instance.id}} is not considered inside the log messages * with my patch {{oozie.instance.id}} is filled, please see my previous comment As for the testing, I've looked at {{TestXLog}}, but couldn't find a way to test any other thing that when a {{SERVER}} parameter is defined having the {{ConversionPattern}} containing {{oozie.instance.id}}, and that system property is set, log message would be rendered accordingly. This is the kind of test what is already tested, and / or regards Log4J functionality. ATM I cannot think of a test case where exactly the functionality covered by the patch (setting the system property from the startup scripts cause the log message to appear correctly) could be tested. > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205668#comment-16205668 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 2041 .Tests rerun: 72 .Tests failed at first run: org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC,org.apache.oozie.action.hadoop.TestJavaActionExecutor, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/115/ > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205572#comment-16205572 ] Attila Sasvari commented on OOZIE-3084: --- [~andras.piros] There are many tomcat related options that might not make sense for jetty. In fact, {{oozie.instance.id}} (unrelated to jetty itself) is in the {{oozie-default.xml}}. As I see from the logs, it is related how Oozie services are initialised and started. Logging service is started before the configuration service, that is why SERVER does not have oozie {{instance id}}. For example: {code} 2017-10-16 10:02:46,132 INFO PauseTransitService:520 - SERVER[] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] Acquired lock for [org.apache.oozie.service.PauseTransitService] {code} With you modification have you seen the {{ SERVER\[$oozie.instance.id]}}? To avoid this in the future, could you think of a test case? > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch, > OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204581#comment-16204581 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} - patch does not compile, cannot run testcases {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/112/ > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch, OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203748#comment-16203748 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [server]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} - patch does not compile, cannot run testcases {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/111/ > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203525#comment-16203525 ] Andras Piros commented on OOZIE-3084: - No test cases modified or added, tested entirely manually, see my previous comment. [~asasvari] can you please review? > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ https://issues.apache.org/jira/browse/OOZIE-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203519#comment-16203519 ] Hadoop QA commented on OOZIE-3084: -- Testing JIRA OOZIE-3084 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:red}-1{color} the patch does not add/modify any testcase {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} the patch does not seem to introduce new Javadoc warnings .{color:red}WARNING{color}: the current HEAD has 77 Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. . {color:green}+1{color} There are no new bugs found in [core]. . {color:green}+1{color} There are no new bugs found in [client]. . {color:green}+1{color} There are no new bugs found in [docs]. . {color:green}+1{color} There are no new bugs found in [sharelib/streaming]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive]. . {color:green}+1{color} There are no new bugs found in [sharelib/hive2]. . {color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. . {color:green}+1{color} There are no new bugs found in [sharelib/oozie]. . {color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. . {color:green}+1{color} There are no new bugs found in [sharelib/pig]. . {color:green}+1{color} There are no new bugs found in [sharelib/spark]. . {color:green}+1{color} There are no new bugs found in [sharelib/distcp]. . {color:green}+1{color} There are no new bugs found in [examples]. . {color:green}+1{color} There are no new bugs found in [tools]. . {color:green}+1{color} There are no new bugs found in [server]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 1774 .Tests rerun: 23 .Tests failed at first run: org.apache.oozie.service.TestActionService,org.apache.oozie.service.TestRecoveryService,org.apache.oozie.dependency.TestFSURIHandler,org.apache.oozie.TestDagEngine,org.apache.oozie.service.TestPartitionDependencyManagerService,org.apache.oozie.dependency.TestHCatURIHandler, {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:red}*-1 Overall result, please check the reported -1(s)*{color} {color:red}. There is at least one warning, please check{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/109/ > 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 > Fix For: 5.0.0 > > Attachments: OOZIE-3084.001.patch > > > 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)
[jira] [Commented] (OOZIE-3084) Add missing JVM properties to Jetty startup script
[ 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)