[ 
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)

Reply via email to