You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Jaydeep Vishwakarma (JIRA)" <ji...@apache.org> on 2015/06/17 12:28:01 UTC
[jira] [Commented] (OOZIE-1705) Enable gc logs and print thread id
in logs
[ https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589598#comment-14589598 ]
Jaydeep Vishwakarma commented on OOZIE-1705:
--------------------------------------------
As mentioned by [~rkanter], current setting of gc logs in CATALINA_OPS have error, You are trying to access oozie.log.dir before its initialization. oozie-env.sh is getting called at the beginning of oozied.sh.
You can access oozie log directory in {{setup_catalina_ops()}} method of oozied.sh. I have tried {code} catalina_opts="${catalina_opts} -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:${OOZIE_LOG}/gc.log" {code} in same place it is working for me.
> Enable gc logs and print thread id in logs
> ------------------------------------------
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)